Quickstarts

Capture only after fulfilment

Connect an Order to a PayNote so payment capture is requested only after the required providers confirm fulfilment.

This quickstart keeps three facts distinct: why payment should happen, how the payment process is governed, and what the payment rail actually did.

Create the commercial Order#

Use an Order with a bouquet item and a dinner item. Alice and Bob each have a participant Channel and must confirm their own fulfilment leg.

The Order begins in awaiting-confirmations. Its rules say capture may be requested only after both confirmations.

Attach one PayNote transaction#

Create a separate PayNote for the customer transaction. It contains payer, payee or allocation information, guarantor Channel, expected amount, conditions, requests, Responses, and lifecycle state.

The PayNote is not the card network or bank ledger. It governs and records the process around one transaction.

Authorize or secure funds#

The commercial flow requests authorization. The provider verifies its own rail consent, credentials, fraud controls, and idempotency, then writes an attributed Response.

A Payment Authorized Response is provider truth. An Order field changed by the customer is not.

Confirm each fulfilment leg#

Alice confirms the bouquet. Bob confirms the dinner. Each action arrives through its own provider-backed Timeline Channel and changes the Order deterministically.

After only one confirmation, the capture condition remains false.

Request capture when conditions match#

When both confirmations are present, the Order emits a typed completion or capture Request to the PayNote. The Request explains why the rail action is now eligible; it does not claim that capture already occurred.

BEX may calculate the deterministic request or amount. It does not call the payment API.

Process the provider outcome#

The guarantor performs the external action and returns an attributed Payment Completed, Declined, Failed, or other rail-specific Response. The PayNote processes that fact and emits selected events to the Order.

Result: the Order reaches its paid or completed consequence only after the configured provider reports the authoritative rail outcome.

Test cancellation or partial fulfilment#

Cancel one leg before capture, or configure a fallback and partial amount. Use a separate transaction and PayNote for a refund, referral fee, or independently governed payout.

Separate payment transactions preserve their own participants, evidence, lifecycle, and dispute path.