Skip to main content
Two layers, and they are not the same. Published coverage describes what a commercial agreement can include. What your credential can call today is narrower and is reported by GET /v2/partners/config. Build your interface from the config response, not from this page.

Markets

Fiat rails by market. Stablecoin collection and settlement work the same in every market, on the networks below. Additional QR catalog markets are Indonesia (IDR, whole rupiah, 20,000 IDR minimum), Brazil (BRL), Colombia (COP), Peru (PEN) and Thailand (THB). They require route configuration, app access and live certification before activation; they do not add bank linking or bank payout support. The tables further down give each rail’s exact limits.

Stablecoin networks

Assets are USDC and USDT on the supported EVM chains, Solana and Movement, JPYC on Polygon, THBT on Movement, USDG on Robinhood Chain, and PUSD on Tempo. Native assets are usable as routing sources only.
Deposit-address issuance is paused for Tron and Bitcoin. Addresses already issued are still monitored. Both remain valid routing sources. Native BNB reusable deposits are also paused; BNB-chain USDC and USDT remain available.

Deposit minimums

A transfer to a reusable deposit address below its minimum is recorded as ignored and not credited. A payment’s own option states the exact amount to send and takes precedence over this table. Read live minimums, token addresses and decimals from GET /v2/partners/config.

Fiat collection

Receiving fiat into an account, delivered as stablecoin. On-ramp accounts are available in sandbox; contact Stableyard for production. Each environment delivers to a different chain; see US bank environments. Your app and the account must be enabled first.

Fiat payout

Sending fiat out of an account. Linked banks are reusable beneficiaries and can belong to suppliers, contractors or the sending customer. Linking a bank does not verify that the account holder owns it. US payouts use a verified saved bank; one-time US bank transfers are not supported.

US bank environments

A published endpoint does not enable a rail for your app. Production use requires your app to be enabled for the rail and market, and account-level bank_onramp or linked_bank approval for the requested rail. Approval for one does not grant the other. Read GET /v2/partners/config, GET /v2/accounts/{accountId}/capabilities, and the relevant bank requirements endpoint with credentials for the target environment. For on-ramp delivery, use the requirements response’s supportedDestinations and destinations instead of the general stablecoin network list. USDT is not a supported on-ramp destination. Before launch, confirm with Stableyard that the rail is enabled for your app in production.

Linking a bank account

Saving a bank beneficiary under a UPA for reuse. Philippine and Vietnamese payouts use a one-time beneficiary with destination.type: "external_bank"; see Fiat payout. A US linked bank can be paid through a send Payment, but cannot receive settlement from a receive Payment.

Local payment methods by market

A local payment method is reached either by scanning a merchant’s code or by paying a typed destination such as an account number or a phone number. No other market is available today. The requirements endpoint reports each market’s availability.

Capabilities that are not supported

Checking availability at runtime

The response reports the products enabled for your app, the networks and assets available, the payment methods currently operational, and the permissions of the calling credential. A capability is usable only when all of those agree.

Next

Capabilities

What each capability does and which resources express it.

Status codes

Payment and deposit states, and which are terminal.