Choose your pattern

Pick the pattern that matches who your customers are and how their money moves. Each one lists the parties to confirm, the gates in order, and what works where today.

Embedded ramps for individuals

People fund from a US bank and cash out to their own bank, inside your app.

Platform for business customers

Companies get US bank access through your product after hosted verification.

Crypto-only payouts

Stablecoin to wallets, accounts and handles, with no verification.

Pattern	Signals	What to scope
Embedded ramps for individuals	End users are people. They need bank details to fund and a bank to cash out to	Who signs from the wallet. US-only funding. Which payout markets you need
Platform for business customers	End users are companies. A representative completes verification	Business verification enabled for you. US bank rails only. Who the representative is
Crypto-only payouts	Value stays in stablecoin, wallet to wallet or account to account	Who signs from the payment source. Chains and assets from your configuration

Pattern: Embedded ramps for individuals

Use when: a consumer app, wallet or fintech gives individual users a USD on-ramp and an off-ramp to their own bank, inside its own product.

Party	Confirm before building
Customer of record	Each user is an `individual` account. `subjectType` never changes, so create a company as `business` from the start
Wallet controller	Who signs from the wallet that receives on-ramped funds and funds payouts: the user, or your platform
Your organization	Your KYB is approved. Until it is, no fiat step below works
Support owner	Who tells the user what to do when verification is rejected or a payout needs review

Create the account

POST /v2/accounts with subjectType: "individual" and the user’s wallet. See Universal Payment Account.

Verify the email

A code Stableyard emails, or your own assertion where Stableyard has enabled it. See Email verification.

Verify identity

POST /v2/accounts/{accountId}/kyc/session, then send the user to the provider-hosted verificationUrl. See Individual KYC.

Activate the bank capabilities

bank_onramp to fund, linked_bank to cash out. Each can return a one-time Stableyard-hosted form. See Capability activation.

Issue an on-ramp account

POST /v2/accounts/{accountId}/onramp-bank-accounts, then show the deposit instructions. See On-ramp accounts.

Link the user's bank

POST /v2/accounts/{accountId}/bank-accounts with the country’s fields. See Bank accounts.

Pay out

POST /v2/payments with destination.type: "bank_account". The wallet funds the payment’s escrow. See Sending payments.

Leg	Where it works today
Fund by bank transfer	United States, USD, over ACH, Fedwire or FedNow. Certified on staging
Link a bank	United States, Philippines and Vietnam
Pay out to a linked bank	United States only. Certified on staging. Philippine and Vietnamese links cannot receive payouts yet
Pay a bank in the Philippines or Vietnam	A one-time bank transfer by account details, `destination.type: "external_bank"`

Verification needs a person. Every user completes an identity check hosted by a verification provider and, for each bank capability, a form hosted by Stableyard. No API accepts identity documents from you.

Stableyard enables: Identity & KYC, the on-ramp, the linked-bank route for each country, and External Bank Transfer for one-time bank transfers.

Pattern: Platform for business customers

Use when: your customers are companies, such as merchants, suppliers or payroll clients, and each needs US bank access through your product.

Party	Confirm before building
Customer of record	Each company is a `business` account. Your own company is not one of them: your organization’s KYB covers it
Authorized representative	The person at each company who completes verification. The hosted link is a credential; send it only to them
Legal name	The company’s exact legal name. It is sent once, and a different name later is refused
Support owner	Who handles an expired or rejected business application with Stableyard

Create the account

POST /v2/accounts with subjectType: "business". Add a displayProfile for how payers see the company. See Universal Payment Account.

Start business verification

POST /v2/accounts/{accountId}/capability-activations with capability: "linked_bank" and business.legalName. A business skips the email and individual identity steps. See Business KYB.

Send the representative the hosted link

continue_business_verification means the link is not ready: send the same request again. complete_compliance carries the link. Wait for ready: true. See Capability activation.

Fund in USD, if you need it

Activate bank_onramp on the same approved company, without business, then issue an on-ramp account. See On-ramp accounts.

Link the company's US bank

POST /v2/accounts/{accountId}/bank-accounts with country: "US". See Bank accounts.

Pay out

POST /v2/payments with destination.type: "bank_account". See Sending payments.

Leg	Where it works today
Bank access for a business	US bank rails only: a linked US bank, a USD on-ramp account and payouts to that bank
One-time transfers to a third party’s bank, and QR payments	Not available to `business` accounts
Stablecoin collection, payouts, handles and deposit addresses	Available without verification

Stableyard enables: business verification for the banking program, plus the on-ramp and the US linked-bank route. Until it is enabled, a business activation is refused.

Pattern: Crypto-only payouts

Use when: value stays in stablecoin: payouts to wallets, transfers between your customers by handle, or top-ups to a reusable deposit address.

Party	Confirm before building
Customer of record	Any `individual` or `business` account. No verification is needed
Wallet controller	Who signs from the payment source, or whether a Vault authorizes sends without a per-send signature
Recipient	A wallet address, another account, or a payment handle

Create the account with a wallet

POST /v2/accounts with wallets. See Universal Payment Account.

Set the payment source

PUT /v2/accounts/{accountId}/payment-source names the wallet or Vault that funds sends. See Sending payments.

Preview the send

POST /v2/payments/preview. Proceed only when your source’s funding option reports available: true.

Create and confirm it

POST /v2/payments with a crypto_wallet, payment_handle or upa destination, then POST /v2/payments/{paymentId}/confirm with the proof nextAction asks for.

Collect, if you need it

Give a customer a reusable address with POST /v2/accounts/{accountId}/deposit-addresses. See Depositing funds.

Chains and assets come from networks in GET /v2/partners/config, not from a table. See Supported regions and currencies.

Confirm before building

Name the customer of record

Decide individual or business for every customer type. It cannot be changed after creation.

Read your configuration

compliance.partnerKyb.status is approved and the products you need are available. See Going live.

Check coverage for your markets

Fiat is enabled per country, per rail and per app. See Supported regions and currencies.

Decide who signs

Stableyard never signs for a connected wallet. Your user or your platform does.

Assign support ownership

Rejected verification, expired links and payments that need intervention all reach a person. Decide whose.

Next: Quickstart

Run the embedded-ramps pattern end to end on staging.

Start here

Ship it

Embedded ramps for individuals

Platform for business customers

Crypto-only payouts

Pattern: Embedded ramps for individuals

Pattern: Platform for business customers

Pattern: Crypto-only payouts

Confirm before building

Next: Quickstart

Embedded ramps for individuals

Platform for business customers

Crypto-only payouts

​Pattern: Embedded ramps for individuals

​Pattern: Platform for business customers

​Pattern: Crypto-only payouts

​Confirm before building

Next: Quickstart

Pattern: Embedded ramps for individuals

Pattern: Platform for business customers

Pattern: Crypto-only payouts

Confirm before building