Get on-ramp requirements
Discover the funding rails and eligible wallets before issuing an on-ramp account.
supportedDestinations and destinations for this environment. When no rail or eligible wallet is available, available is false and unavailableReason says why. Any other failure returns a normal HTTP error; do not treat it as unavailable. Issuance separately requires the account’s bank_onramp approval.
recipientOnFile reports whether a verified recipient name and address can be reused. When true, omit recipientType, recipientName and recipientAddress together at issuance. Otherwise, supply all three. This flag does not grant bank access or replace capability approval.Authorizations
HTTP Basic auth. Username is the Stableyard app ID. Password is the app secret. The optional Stableyard-Version request header must match the environment pin.
Headers
Optional contract-version assertion. Omit it to use the app environment's pinned version. A different supported version is accepted only after that environment is explicitly migrated.
2026-09-09 Path Parameters
Canonical account id returned by the Accounts API.
"acct_123"
Response
On-ramp bank account requirements
"acct_123"
True when a verified name and address is on file, so the funding account can be created without recipient details.
True only when at least one rail is available and at least one connected wallet is on a supported destination.
Why the flow cannot be started, or null when it can.
onramp_route_not_configured, no_eligible_destination, null Supported delivery chains and assets, including when this UPA has no eligible wallet. Listing does not grant rail access or approval.
individual, business Rails available in this environment. One rail can be available while another is not.
Connected wallets on a supported destination chain, with the asset codes supported on that chain.