Supported Rails
Human-readable rail catalog and rail request caveats.
The metadata endpoint returns the supported rail catalog. Availability can still depend on customer type, country, currency, verification status, and flow.
Rail Catalog
| Category | Rails |
|---|---|
| Fiat bank transfer | ach, fedwire, sepa, pix, spei, pse, swift |
| Fiat card | card, apple_pay |
| Crypto | polygon, bsc, base, ethereum, arbitrum, optimism, avalanche, tron, solana, stellar, ton |
Customer Rail Requests
Customer rail verification currently accepts qualified bank-transfer rails for ach, fedwire, sepa, swift, and pix, plus base aliases for those rails.
| Variant | Request examples |
|---|---|
| Pooled | ach_pooled, fedwire_pooled, sepa_pooled, swift_pooled, pix_pooled |
| Named | ach_named, fedwire_named, sepa_named, swift_named, pix_named |
Customer rail status rows use cfr_* IDs. These are useful for rail tracking, but they are not bank account IDs. Account and payout flows expect acc_* customer account IDs or racc_* recipient account IDs.
If an account, recipient-account, pay-in quote, or payout quote call depends on a rail that is not yet ready_to_use, the API returns 409 rail_not_ready with the acceptable requiredRails and the requestRailEndpoint to call before retrying.
Business Rail Applications
Business customers also have v2 rail-state and rail-application resources:
GET /v2/customers/business/{customerId}/rails returns every exposed rail for that business. Rail discovery statuses are:
| Status | Meaning |
|---|---|
available | Rail is supported for the business and has no application yet |
unavailable | Rail cannot be requested for this business |
ready_for_review | Required information is present and the application can advance |
in_review | Application is under review |
needs_information | More information, corrected profile data, or replacement documents are needed |
active | Rail is approved and usable |
declined | Application was declined |
Create or advance applications with:
The response returns successful application resources in data and item-level failures in errors:
Application resources use the same review vocabulary except available and unavailable, which are rail discovery states only. Responses do not expose enabled, allowed, canSubmit, or a duplicate applicationId; the application id is the cfr_* rail row.
API Reference
| Operation | Use it for |
|---|---|
GET /v1/meta/rails | Retrieve the rail catalog. |
POST /v1/customers/{customerId}/rails | Request customer rail verification. |
GET /v2/customers/business/{customerId}/rails | List business rail states. |
POST /v2/customers/business/{customerId}/rail-applications | Create or advance business rail applications. |