Skip to content
Seismic Orchestration

GET /customers/:id/pay-in-approvals

List the currency + rail combinations this customer may be funded with. Its mirror, GET /customers/:id/payout-approvals, lists what they may be paid out to.

Only rows with status of approved can carry a payment; quoting an unapproved one fails. Use this to narrow a funding-method picker to options that will actually succeed, rather than surfacing a quote error afterwards.

The list is narrowed to the currencies and rails your organization is approved for, so everything it returns is something you could transact on today if the status allows.

Answers are cached for up to an hour, so a freshly granted approval can take that long to appear here.

Response 200

{
  "pay_in": [
    {
      "currency": "USD",
      "rail": "ach",
      "status": "approved"
    },
    {
      "currency": "USDC",
      "rail": "base",
      "status": "pending",
      "status_detail": "UNDER_REVIEW"
    }
  ]
}

rail uses the same rail names as GET /rails and account creation, so a value here can be passed straight back to us.

status

ValueMeaning
approvedCleared — this currency and rail can carry a payment today.
pendingUnder review. Nothing to do but wait.
action_requiredBlocked on the customer supplying something.
rejectedWill not be approved as it stands.
not_startedNever submitted for review.

status_detail carries the reviewer's own finer-grained wording when there is one. It is not a fixed set and may change without notice — branch on status, and treat status_detail as a human-readable hint only.

Errors

401 (missing or invalid API key), 404 (unknown customer, or a customer belonging to a different org), 503 (approvals are unavailable on this environment).

Example

curl "$SEISMIC_ORCHESTRATION_URL/v0/customers/2f10…/pay-in-approvals" \
  -H "Api-Key: $SEISMIC_ORCHESTRATION_API_KEY"