> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stableyard.fi/llms.txt
> Use this file to discover all available pages before exploring further.
# Supported regions and currencies
> Which markets, currencies, chains and assets are supported, and for which capability.
**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.
| Market | Currency | Rails |
| - | - | - |
| 
United States | USD | ACH, Fedwire and FedNow into a bank account in the customer's name; payouts to the customer's own linked bank. Both certified on staging |
| 
United Arab Emirates | AED | Coming soon |
| 
Vietnam | VND | Local payment methods, scanned or typed; one-time bank transfers to a third party |
| 
Philippines | PHP | Local payment methods, scanned or typed; one-time bank transfers to a third party |
| 
Kenya | KES | Local payment methods, by scanning a merchant code |
The tables further down give each rail's exact limits.
## Stablecoin networks
| Chain | Chain ID | Collect | Settle | Deposit addresses |
| - | - | - | - | - |
| 
Arbitrum | 42161 | Yes | Yes | Yes |
| 
Ethereum | 1 | Yes | Yes | Yes |
| 
Base | 8453 | Yes | Yes | Yes |
| 
Polygon | 137 | Yes | Yes | Yes |
| 
BNB Chain | 56 | Yes | Yes | Yes |
| 
Solana | 10103 | Yes | Yes | Yes |
| 
Robinhood Chain | 4663 | Yes | Yes | Yes |
| 
Movement | 10002 | Payer submits the transaction | Yes | Yes |
| 
Tron | 728126428 | Routing source only | No | **Issuance paused** |
| 
Bitcoin | 10001 | Routing source only | No | **Issuance paused** |
| 
Avalanche | 43114 | No collection path | Yes | Yes |
| 
Tempo | 4217 | No collection path | Yes | Yes |
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`.
| Asset and chain | Decimals | Deposit-address minimum |
| - | - | - |
| USDC and USDT on EVM chains, Solana and Movement | 6; BNB Chain USDC and USDT use 18 | `0.5`, inclusive |
| Robinhood USDG | 6 | `0.5`, inclusive |
| Tron USDT | 6 | `10`, inclusive |
| Bitcoin BTC | 8 | `0.0001` (10,000 sats), inclusive |
| Polygon JPYC | 18 | `POLYGON_JPYC_MIN_AMOUNT`, inclusive; default `100` |
| Movement THBT | 6 | `16.5`, inclusive |
## Fiat collection
Receiving fiat into an account, delivered as stablecoin.
| Capability | Markets | Rails |
| - | - | - |
| Bank account issued in the customer's name | United States, USD | ACH, Fedwire, FedNow |
| Fiat at checkout | The enabled provider's markets | Card and local methods |
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.
| Market | Local methods | One-time bank beneficiary | Saved linked-bank beneficiary |
| - | - | - | - |
| United States, USD | No | Not released | Implemented; staging-certified |
| United Arab Emirates, AED | Coming soon | Coming soon | Coming soon |
| Vietnam, VND | Yes | Yes | No |
| Philippines, PHP | Yes | Yes | No |
| Kenya, KES | Yes | **No bank rail** | No |
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
| Environment | Base URL | Implemented bank-onramp destination | Recorded live validation |
| - | - | - | - |
| Sandbox/staging | `https://staging-api-v2.stableyard.fi` | USDC on Arbitrum Sepolia (`421614`) | Staging bank funding and linked-bank payout certification |
| Production | `https://prod-api.stableyard.fi` | USDC on Arbitrum One (`42161`) | Production money-movement certification is not established by this guide |
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.
| Market | Can be linked | Can receive payouts | Can receive settlement |
| - | - | - | - |
| United States | Yes | Implemented; staging-certified | No |
| United Arab Emirates | Coming soon | Coming soon | Coming soon |
| Vietnam | Yes | **No** | No |
| Philippines | Yes | **No** | No |
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.
| Market | Scan a merchant code | Typed destination |
| - | - | - |
| United Arab Emirates | Coming soon | Coming soon |
| Vietnam | Yes | Yes |
| Philippines | Yes | Yes |
| Kenya | Yes | No |
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
| Capability | State |
| - | - |
| Card payments | Not released. The entitlement exists and nothing is behind it |
| Business accounts outside US bank rails | Not supported. A business reaches US linked banks and US dollar virtual accounts after hosted KYB. One-time bank and QR payments remain individual only |
| Vaults outside Arbitrum | Not supported. Arbitrum only, USDC and USDT |
## Checking availability at runtime
```bash theme={null}
curl https://staging-api-v2.stableyard.fi/v2/partners/config \
-u "$APP_ID:$APP_SECRET"
```
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
What each capability does and which resources express it.
Payment, deposit and refund states, and which are terminal.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.