POST /quotes/:id/accept

Turn a snapshot into an order.

Request body

All fields are optional, as is the body itself: a bodyless POST accepts the snapshot's best-ranked quote. Two fields become required for specific inline sources: from_address for a blockchain source whose quote has no sending wallet (unless the payment is funded through a deposit address), and source_account_number when the chosen quote's acceptance_requirements.source_account_number_required is true.

Reference format

reference travels with the payment and can land on the beneficiary's bank statement, so it is capped at 128 characters and restricted to the set every settlement network accepts:

• letters A–Z and a–z
• digits 0–9
• spaces
• dashes (-)
• colons (:)

Anything else — underscores, periods, commas, slashes, #, @, accented letters — fails with an InvalidRequest whose violations array pins the reference field and names the first offending character:

{
  "ok": false,
  "error": {
    "code": "InvalidRequest",
    "message": "1 field needs attention",
    "violations": [
      {
        "field": "reference",
        "reason": "invalid_format",
        "description": "`reference` may only contain letters, numbers, spaces, dashes, and colons. Remove '_'."
      }
    ]
  }
}

A reference longer than 128 characters is rejected the same way, with a too_long reason instead:

{
  "ok": false,
  "error": {
    "code": "InvalidRequest",
    "message": "1 field needs attention",
    "violations": [
      {
        "field": "reference",
        "reason": "too_long",
        "description": "`reference` may be at most 128 characters; this one is 135."
      }
    ]
  }
}

Dispatch on the field + reason pair ("reference" + "invalid_format" or "too_long"), never on the description text. Nothing is charged or dispatched — the accept is rejected before the snapshot is consumed, so the snapshot stays acceptable and a corrected retry works until the quote expires.

UUIDs and typical invoice ids (invoice-2026-04-001) satisfy this as-is. If your ids use other separators, strip or substitute them before sending; comment is free-form and is a better home for anything that doesn't need to travel with the payment.

Supporting document types

Each files entry declares its type, one of:

• invoice
• purchase_order
• delivery_slip
• contract
• customs_declaration
• bill_of_lading
• other

Compliance review reads the document as its declared type, so a payment held for review clears faster when the type matches the document. Use other only when no other type describes it. A bare data-URI string entry declares no type; it is deprecated and rejected from November 1, 2026.

{
  "files": [
    {
      "type": "invoice",
      "file": "data:application/pdf;base64,JVBERi0xLjcK…"
    }
  ]
}

Payment reasons

payment_reason is one of:

• charitable_contributions
• education_fees
• employee_salaries_or_wages
• gifts
• investments
• dividend
• purchase_of_goods
• purchase_of_services
• personal_transfers
• rent
• loans
• utility_bills
• family_support
• friends_support
• real_estate
• insurance
• intercompany_transfer
• taxes
• travel

Both family_support and friends_support remain accepted, but each is settled under a single consolidated "family and friends support" category.

dividend is settled under the investments category.

Sources of funds

source_of_funds is one of:

• salary
• savings
• business_revenue
• company_capital
• investment_returns
• inheritance
• trust
• gift
• grant
• sale_of_assets
• real_estate
• loan
• private_capital
• marital
• winnings
• other

The same set the sender's verification profile records, so a payment-level declaration and a profile one are directly comparable.

Request headers

Response 200

The full order is returned inline. No follow-up GET /v0/orders/:id needed to read funding_instructions or lifecycle status.

{
  "id": "f01e…",
  "status": "awaiting_funds",
  "source": {
    "amount": "100.00",
    "currency": "EUR",
    "rail": "sepa",
    "account_id": "5d8a…"
  },
  "destination": {
    "amount": "108.42",
    "currency": "USDC",
    "rail": "base",
    "account_id": "9b2f…"
  },
  "funding_instructions": {
    "iban": "GB29NWBK60161331926819",
    "reference": "REF-8A3C"
  },
  "reference": "invoice-2026-04-001",
  "comment": "Off-ramp for Acme March payroll",
  "payment_reason": "employee_salaries_or_wages",
  "idempotency_key": "8b3c4d5e-…",
  "created_at": "2026-04-12T14:23:01.000Z"
}

Fields

Status reasons

When a payment settles into a terminal refunded or failed status, status_reason carries the settlement network's reason code, forwarded verbatim. These are the codes observed so far:

The set is open: settlement networks add codes, so treat any unrecognized value as an opaque string rather than failing on it. Use status for control flow and status_reason for surfacing the explanation.

An under_review order can also carry one of these codes of Seismic's own while the payment is held for a supporting document:

A payment can also be held for a compliance review before anything is sent, right after the accept. Such an order reads under_review with no status_reason until the review clears, then moves to the status the settlement reports (processing, awaiting_funds, …); a payment the review blocks ends failed with BLOCKED_BY_COMPLIANCE, like any compliance block. Each change fires an order.status_changed webhook.

Errors

See the Errors reference for the full code enum:

A finished snapshot with nothing priced returns the same error as GET /quotes/:id, whether or not the body names a quote_id.

Document required

Every priced quote includes acceptance_requirements.files_required. When true, collect a supporting document and include it in files before accepting that quote. This signal describes payment acceptance, separately from the external-account registration requirements.

Documents are required for destinations in INR, CNY, and GHS at any amount, and BRL when the quote's out.amount is at least 50,000. The signal uses each quote's destination amount for both exact-in and exact-out requests. Some routes also require one at any amount when the beneficiary is not the customer, such as certain payouts over swift; GET /quotes/requirements lists them as route_conditions. Check the selected quote rather than hardcoding these rules; they can change.

On such a route, the first file in files is submitted for review with the order. The document must show the relationship between the customer and the beneficiary. While it is reviewed, the order reads under_review with status_reason: documents_under_review; if it is turned down, the order reads documents_rejected and takes a new one through POST /customers/orders/:id/documents (see Status reasons).

A payment funded by sending stablecoins to a deposit address, with no source account, is placed only once the deposit arrives, so files cannot travel with it. Its quote leaves such a route out of files_required, and the order asks for the document with status_reason: documents_required instead.

Known requirements are checked before an order is dispatched. Additional document requirements may be encountered during processing, so keep handling the typed rejection. When a required attachment is absent, the accept fails with an InvalidRequest whose violations array pins the files field:

{
  "ok": false,
  "error": {
    "code": "InvalidRequest",
    "message": "1 field needs attention",
    "violations": [
      {
        "field": "files",
        "reason": "missing",
        "description": "Please upload an invoice for the payment."
      }
    ]
  }
}

Dispatch on the field + reason pair ("files" + "missing"), never by matching the description text, which is free-form and may change. Collect a document from your user and retry the accept with files populated. The snapshot stays acceptable until the quote expires. The TypeScript client ships this check as acceptRequiresFiles.

Expired-quote behavior

A quote is only good for a short window. expired_quote_behavior decides what happens when the funds land after it lapsed:

• refund_payment — the funds are returned. The default when the field is omitted.
• flexible_destination_amount — the payment is re-quoted at the market rate and settled, so the recipient's amount moves.
• flexible_source_amount — the payment is re-quoted at the market rate and settled, so the amount pulled from the sender moves. Requires a registered account on the source leg: a manually funded payment has nothing to re-debit.

A payment funded by sending stablecoins to a deposit address (the order comes back awaiting_funds with funding_instructions.toAddress) is priced again when the deposit arrives:

• With refund_payment (or no value), the payout goes ahead only if it pays the out.amount you accepted, less your tolerance, or more. Otherwise the order ends expired with nothing sent, and the funds remain in the customer's wallet.
• With flexible_destination_amount, the payout goes ahead at the new price, so the recipient's amount can move.

A payment held for a compliance review whose quote expires before the review clears is priced again the same way when it is released: sent if the new price is within your tolerance, otherwise ended expired with nothing sent.

Tolerance. expired_quote_tolerance_bps is measured on what the recipient receives after fees, for the same amount sent, so it compares the effective rate of the accepted quote with the new one. 0 sends only at the accepted price or better; 500 accepts up to a 5% worse price. When the accept omits it, your org's expired_quote_tolerance_bps applies (1 unless you change it with PATCH /org).

Each quote lists the behaviors it can honor in its supported_expired_quote_behaviors field. Check it before setting expired_quote_behavior. When the request carries a value the chosen quote doesn't support, the accept fails with an InvalidRequest whose violations array pins the field and echoes the supported set in allowed:

{
  "ok": false,
  "error": {
    "code": "InvalidRequest",
    "message": "1 field needs attention",
    "violations": [
      {
        "field": "expired_quote_behavior",
        "reason": "not_in_allowed_set",
        "description": "This quote does not support the requested expired-quote behavior; see the quote's `supported_expired_quote_behaviors`.",
        "allowed": []
      }
    ]
  }
}

Dispatch on the field + reason pair ("expired_quote_behavior" + "not_in_allowed_set"). Retry without the field to accept with the default behavior (refund_payment).

Examples

curl -X POST "$SEISMIC_ORCHESTRATION_URL/v0/quotes/9d8c…/accept" \
  -H "Api-Key: $SEISMIC_ORCHESTRATION_API_KEY" \
  -H "content-type: application/json" \
  -d '{}'

curl -X POST "$SEISMIC_ORCHESTRATION_URL/v0/quotes/9d8c…/accept" \
  -H "Api-Key: $SEISMIC_ORCHESTRATION_API_KEY" \
  -H "content-type: application/json" \
  -d '{ "quote_id": "q_9e4d…" }'

curl -X POST "$SEISMIC_ORCHESTRATION_URL/v0/quotes/9d8c…/accept" \
  -H "Api-Key: $SEISMIC_ORCHESTRATION_API_KEY" \
  -H "Idempotency-Key: 8b3c4d5e-…" \
  -H "content-type: application/json" \
  -d '{
    "quote_id": "q_9e4d…",
    "reference": "invoice-2026-04-001",
    "comment": "Off-ramp for Acme March payroll"
  }'

curl -X POST "$SEISMIC_ORCHESTRATION_URL/v0/quotes/9d8c…/accept" \
  -H "Api-Key: $SEISMIC_ORCHESTRATION_API_KEY" \
  -H "content-type: application/json" \
  -d '{
    "payment_reason": "purchase_of_services"
  }'

curl -X POST "$SEISMIC_ORCHESTRATION_URL/v0/quotes/9d8c…/accept" \
  -H "Api-Key: $SEISMIC_ORCHESTRATION_API_KEY" \
  -H "content-type: application/json" \
  -d '{
    "return_address": "0x1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b"
  }'

curl -X POST "$SEISMIC_ORCHESTRATION_URL/v0/quotes/9d8c…/accept" \
  -H "Api-Key: $SEISMIC_ORCHESTRATION_API_KEY" \
  -H "content-type: application/json" \
  -d '{
    "expired_quote_behavior": "flexible_destination_amount"
  }'

curl -X POST "$SEISMIC_ORCHESTRATION_URL/v0/quotes/9d8c…/accept" \
  -H "Api-Key: $SEISMIC_ORCHESTRATION_API_KEY" \
  -H "content-type: application/json" \
  -d "{
    \"files\": [
      {
        \"type\": \"invoice\",
        \"file\": \"data:application/pdf;base64,$(base64 -w0 invoice.pdf)\"
      }
    ]
  }"