Confirm fulfillment (internal)

post

https://api.acc.funtrips.io/{stage}/internal/fulfillment/confirm

Signals to a running fulfillment workflow that payment has been confirmed.
Called by the payment processor after receiving a successful PSP webhook.

Events fired

Event	Trigger	Description
`fulfillment.FulfillmentConfirmed`	sync	Fired when payment confirmation is signalled to the workflow.
`fulfillment.FulfillmentCompleted`	async	Fired by the workflow once tickets are generated and delivered.
`fulfillment.FulfillmentFailed`	async	Fired by the workflow if ticket generation fails.
`fulfillment.FulfillmentCancelled`	async	Fired by the workflow if the fulfilment is cancelled during processing.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Signals payment confirmation to a running fulfillment workflow.

fulfillment_order_id

uuid

required

date-time

required

Timestamp of payment confirmation.

customer_email

string | null

order_display_id

string | null

Human-readable order reference (e.g. CRF-4578767) issued by qup-core
at CheckoutOrder time. Stamped onto the fulfillment order so the
ticket email can render {{ order_number }} from a friendly value
instead of the UUID. Optional: legacy callers that don't supply it
cause the email to fall back to the UUID order_id.

order_id

uuid | null

qup-core's order UUID, supplied alongside order_display_id. Stamped
onto the fulfillment order so the workflow can report completion back
to qup-core once tickets are delivered (otherwise the order stays
pending in core admin). Optional: when absent, the completion
callback to core is skipped.

provider_params

object | null

Provider-specific parameters merged into the fulfillment order
before the workflow is signalled. Used by callers (e.g. qup-core)
to pass through fulfillment metadata only known at confirm time.

Headers

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Responses

Language

Credentials

Header

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

application/problem+json

200Fulfillment confirmation accepted.

400The request body or parameters are invalid.

500An unexpected server error occurred.