Skip to main content
Production runs the same routes, bodies and states as staging. Three things change: what Stableyard has enabled for you, what you re-create, and which legs a real bank now runs.

What Stableyard must enable

None of these is self-serve, in staging or in production. Each one has a check you can run yourself. Your partner fee is one rate on your organization, partnerFeeBps, set by Stableyard and returned under fees. There is no per-payment fee field. See Assessing fees.

Nothing carries over

What production adds

  • Real review. Identity and capability decisions can sit in requires_review or provider_review while a person looks. Your screens need a waiting state.
  • Real banks. A transfer into an on-ramp account arrives on the sender’s bank’s schedule, and a payout lands on the banking partner’s.
  • Real first runs. Some corridors cannot be rehearsed end to end outside production, so your first production transfer is also the first real test of that corridor.
On-ramp account issuance and payouts to a linked US bank are certified on staging and not yet proven in production. Confirm with Stableyard that your production program is live before you point customers at either.

The checklist

1

Read your configuration in production

GET /v2/partners/config with the production credential. Check KYB, products, email policy and fees again; nothing is inherited from staging.
2

Register production webhooks

Subscribe to account.updated, kyc.updated, compliance.*, bank_funding.* and payment.*. Verify every signature, and treat each event as a prompt to read the resource. See Webhooks.
3

Create production accounts

Your first production call for each customer is a create, with a new Idempotency-Key.
4

Build the waiting and human states

requires_review, provider_review, requires_intervention and contact_support all mean a person acts. Decide who on your side tells the customer, and who contacts Stableyard.
5

Keep secrets out of logs

Never log or store hosted nextAction.url links, deposit instructions or full bank numbers. Mask them in your support tools.
6

Run one supervised transfer each way

One small bank transfer into an on-ramp account and one small payout to a linked bank you control, both reconciled from the resources, not from the responses you got at creation.

Next: Webhooks

Events, delivery guarantees and signature verification.