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. 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.

​
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. Bank account issuance is implemented for production and staging with different destination allowlists. Live certification and app enablement are separate from this implementation support; see the US bank environment table below.

​
Fiat payout

Sending fiat out of an account. Linked banks are reusable beneficiaries and can belong to suppliers, contractors or the sending customer. Linking does not prove ownership by the UPA subject. US payouts use a verified saved bank; inline one-time US bank transfers remain unavailable.

​
US bank environments and certification

Both environments publish the funding-account endpoints and the linked-bank Payment shape. A published endpoint or supported destination does not enable a rail for an app. Production use requires enabled app permissions and market access, an operational provider route, and approved account-level bank_onramp or linked_bank access for the requested rail. Approval for one capability 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 bank onramp delivery, use the requirements response’s supportedDestinations and destinations instead of the general stablecoin network list. USDT is not in the current bank-onramp destination allowlist. Before launch, confirm the target rail’s production certification with Stableyard, including financial completion, provider webhook processing and delivery of signed partner webhooks. Staging certification does not establish those production outcomes.

​
Linking a bank account

Saving a bank beneficiary under a UPA for reuse. Philippine links remain pending verification; Vietnam has independent beneficiary verification. Neither saved-bank path can execute a payout today. 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. Field schemas exist for a further 47 countries, and named schemes including PIX, UPI, PayNow, Interac, SPEI and Zelle are defined as input contracts. None of them is callable today; the requirements endpoint reports each as unavailable.

​
Capabilities that are not released

​
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, deposit and refund states, and which are terminal.