Accept a quote

Handling for a payment funded after its quote expired. Defaults to refund_payment; a quote's supported_expired_quote_behaviors lists the alternatives it can honor when accepted with expired_quote_behavior set.

With refund_payment, how far a payment priced again after the accepted quote expired may fall short of the accepted amount and still be sent, in basis points (0–500) of what the recipient receives after fees. Beyond it the funds are returned. Defaults to the org's expired_quote_tolerance_bps; rejected with a flexible behavior.

Sending wallet for a blockchain-sourced payment with no attached source account. Overrides the source address captured when the quote was created. Required when neither the quote nor an attached account identifies the source, unless the payment is funded through a deposit address (the order comes back awaiting_funds with funding_instructions.crypto.deposit_address), where it is optional. Rejected for fiat sources and attached source accounts.

Why a payment is being made. Banks key compliance decisions off this, so downstream settlement networks require one of these fixed categories on every payment. Partner-facing: supplied on the accept request, persisted on the order, and mapped to the settlement network's enum at dispatch.

Distinct from [SourceOfFunds] — that answers where the money came from; this answers why it's being sent. The two are carried as separate fields end to end.

Which quote in the snapshot to accept, addressed by its id. When omitted the service accepts the best-ranked quote.

Message carried with the payment, commonly an invoice id. Echoed back on the resulting order. At most 128 characters, limited to letters, numbers, spaces, dashes, and colons — the reference travels onto the beneficiary's statement, and settlement networks refuse anything else.

Refund address for stablecoin-sourced payments: if the payment fails or expires, funds are returned to this address on the source chain. Omitted → defaults to the sending wallet when one is known. Rejected when the source leg is fiat.

Bank account number the payment will be funded from. Required when the chosen quote's acceptance_requirements.source_account_number_required is true — the local network needs the originating account declared before funds are sent. Rejected when it is false.

Why a payment is being made. Banks key compliance decisions off this, so downstream settlement networks require one of these fixed categories on every payment. Partner-facing: supplied on the accept request, persisted on the order, and mapped to the settlement network's enum at dispatch.

Distinct from [SourceOfFunds] — that answers where the money came from; this answers why it's being sent. The two are carried as separate fields end to end.

Why the payment is in its current status. A payment that ended in a terminal failure — a refunded or failed order — carries the settlement network's reason code (e.g. COMPLIANCE_BLOCKED, INVALID_EXTERNAL_ACCOUNT_DETAILS). A processing order held for a supporting document reads documents_required or documents_rejected (submit one with POST /customers/orders/{id}/documents), then documents_under_review, then documents_approved once it continues. Omitted for healthy orders and when no reason was reported.

On-chain settlement hash for the order's crypto leg, present once the order settles over a blockchain rail and Seismic has observed the settlement. Absent for fiat-only orders.

SWIFT Unique End-to-end Transaction Reference (UETR) of the order's fiat leg, present once the settlement network reports it for a wire payout. Give it to the beneficiary's bank to trace the payment. Absent for other rails and until the network reports it.