---
title: "How long does it take to launch cross-border stablecoin payouts? From first API call to first live payout"
seoTitle: "How long to launch cross-border stablecoin payouts?"
description: "The go-live critical path for stablecoin payouts: instance setup, KYB, integration, first customer KYC, and first-payout holds, with each wait."
date: "2026-10-14"
updated: "2026-10-14"
category: "payments"
author: "BlindPay Team"
howto:
  name: "How to go live with cross-border stablecoin payouts"
  steps:
    - name: "Open a development instance and start production onboarding the same day"
      text: "Development instances are ready immediately. Start your company's production onboarding in parallel, since a new production instance can take up to 3 business days to set up and your KYB documents gate it."
    - name: "Build the payout flow on the development instance"
      text: "Implement terms of service acceptance, customer creation, bank accounts, quotes, payouts, and webhooks. On development, KYC is auto-approved, payins complete in about 30 seconds, and payouts complete without moving real money."
    - name: "Onboard your first real customers in production"
      text: "KYC Standard is automated in about 60 seconds. KYC Enhanced and KYB Standard are manual and take 3 hours to 1 business day. Answer any request for information quickly."
    - name: "Send a small first payout per corridor"
      text: "Quote and execute one low-value payout per rail you plan to use. Expect a possible compliance hold on first-time activity, and on USD ACH, wire, RTP, and SWIFT payouts, which are reviewed after the funds are captured."
    - name: "Scale up volume"
      text: "Raise volumes after the first payouts complete cleanly, request limit increases with supporting documents if needed, and keep the webhook handler as the source of truth for status."
faq:
  - q: "How long does it take to go live with a stablecoin payout API?"
    a: "The provider-side waits are short and documented: a BlindPay production instance takes up to 3 business days to set up, KYB review takes 3 hours to 1 business day, and KYC Standard takes about 60 seconds. Most of the calendar goes to your own integration, internal approvals, and how fast you answer compliance questions, so the total varies by team."
  - q: "Can I start building before my company's onboarding is approved?"
    a: "Yes. BlindPay development instances are ready immediately and expose the same API surface as production, with auto-approved KYC, simulated payins that complete in about 30 seconds, and payouts that complete without moving real money. Build against development while production onboarding runs in parallel, then switch API keys."
  - q: "What slows down a stablecoin payouts launch the most?"
    a: "Usually incomplete onboarding documents and slow answers to requests for information, not the API. A share register that doesn't name every beneficial owner, a stale proof of address, or a business description that doesn't match the website all add review rounds. On the build side, quote expiry and webhook handling are the parts teams underestimate."
  - q: "Do virtual accounts take longer to activate than payouts?"
    a: "Yes. Virtual accounts go through compliance review and then a bank review, which typically takes several business days depending on the banking partner and account type. If the bank asks for more documents, the clock restarts from the day they are submitted. Payout-only launches skip this step."
  - q: "Why was my first live payout put on hold?"
    a: "First-time withdrawals and unusual activity are common compliance hold triggers, and on BlindPay all USD ACH, wire, RTP, and SWIFT payouts are reviewed after the funds are captured. SWIFT payouts also start on_hold until any required document is approved. Holds can take up to 30 days, so make your first payout small and early."
  - q: "Do I need a new integration to move from sandbox to production?"
    a: "No. Every request goes to the same api.blindpay.com hostname, and the environment is decided by which instance your API key belongs to. Endpoints, fields, and webhook payloads match. What changes is behavior: real KYC review, real bank settlement times, real stablecoins instead of the USDB test token, and no development rate limit."
---

Launching cross-border stablecoin payouts usually takes days on the provider side and weeks on yours. A BlindPay production instance takes up to 3 business days to set up, KYB review takes 3 hours to 1 business day, and a first payout settles in minutes on Pix or SPEI. The rest is your integration and how fast you answer compliance.

The flow you're integrating is the [stablecoin sandwich](/resources/more/what-is-a-stablecoin-sandwich): stablecoins in, a locked quote, local currency out. Each layer has its own review step, and knowing which ones block each other is what keeps a launch on schedule.

**Key takeaways**

- Start production onboarding on day one. It runs in parallel with development and is the longest provider-side wait.
- Development instances are ready immediately and match the production API, so integration doesn't wait for approval.
- KYC Standard takes about 60 seconds. KYC Enhanced and KYB Standard are manual: 3 hours to 1 business day.
- Virtual accounts add a bank review of several business days. Payout-only launches skip it.
- Expect a compliance hold on early payouts. Make the first one small.

## What does the go-live critical path look like?

Five phases, two of which overlap. Provider timings below come from BlindPay's [cut-off times and onboarding SLAs](/docs/kb/cut-off-times) and [instances](/docs/learn/instances) docs. Integration time is an estimate and depends on your team.

| Phase | What happens | Typical time | Blocks the next phase? |
| --- | --- | --- | --- |
| 1. Development instance | Create it in the dashboard, get an API key | Minutes | No |
| 2. Production onboarding | Your company's KYB, then instance setup | Up to 3 business days for setup, plus document collection | Yes, for live payouts |
| 3. Integration | Customers, bank accounts, quotes, payouts, webhooks | Estimate: days to a few weeks | Yes |
| 4. First real customers | KYC or KYB per customer | About 60 seconds (KYC Standard) to 1 business day (manual) | Yes, per customer |
| 5. First live payouts | One small payout per rail | Minutes (Pix, SPEI) to up to 5 business days (SWIFT), plus any hold | No |

Phases 2 and 3 should run side by side. Teams that finish the integration first and only then start onboarding lose the whole onboarding window.

## How long does production onboarding take?

The setup itself is quick. Collecting documents is what drags. BlindPay's docs say new production instances "may take up to 3 business days to set up," and KYB is a manual review.

KYB means proving who owns and controls your company. The bar comes from rules like FinCEN's [customer due diligence rule](https://www.fincen.gov/resources/statutes-and-regulations/cdd-final-rule), which asks institutions to identify any individual who owns 25 percent or more of a legal entity and one individual who controls it. BlindPay's [KYB documents guide](/docs/kb/kyb-documents) lists what to prepare:

- Articles of organization and certificate of incorporation, all pages
- A share register or legal document showing every shareholder, percentage, and UBO
- Proof of business address dated within the last 90 days
- Government ID and proof of residence for each UBO

Gather these before you start. A first page instead of the full document, or a proof of address from four months ago, is the typical cause of a second round. [What is KYB](/resources/more/what-is-kyb) explains the checks behind each document.

## What can you build before production is approved?

All of it. Development instances "are ready immediately," and BlindPay's [sandbox vs production page](/docs/learn/sandbox-vs-production) says both environments "expose the same API surface: same endpoints, same fields, same response shapes."

On development:

- KYC is auto-approved, so you can create customers without real documents
- Payins auto-complete about 30 seconds after creation, delivering the USDB test token
- Payouts move to `completed` automatically, with no real bank transfer
- Webhooks behave exactly like production
- The rate limit is roughly 100 requests per minute per instance

Build the full path: terms of service acceptance, customer, bank account, quote, execute, webhook handling. The two places teams underestimate are quote expiry (payout quotes lock the rate and fees for 5 minutes) and idempotent retries. [How to integrate a stablecoin API](/resources/more/how-to-integrate-a-stablecoin-api) walks the build, and [sandbox vs production](/resources/more/stablecoin-api-sandbox-vs-production) lists what testing misses.

## How long does it take to onboard your own customers?

Seconds to a business day, depending on the verification level:

| Verification | Review | Timeline |
| --- | --- | --- |
| KYC Standard (individuals) | Automated | About 60 seconds |
| KYC Enhanced (individuals) | Manual | 3 hours to 1 business day |
| KYB Standard (businesses) | Manual | 3 hours to 1 business day |

Customers from high-risk countries always go to KYC Enhanced. If compliance needs more, the customer moves to `compliance_request` and you have 27 days to answer. [Why a cross-border payout gets an RFI](/resources/more/cross-border-payout-rfi-how-to-answer) covers how to answer the first time.

Plan your launch customers accordingly. A payroll product paying individuals can onboard in minutes. A B2B product whose first customers are companies should onboard them a day or two before the first payout date.

## Do virtual accounts change the timeline?

Yes, they add the longest wait. Virtual accounts go through compliance review, then a bank review that BlindPay's docs describe as varying "by banking partner and account type; typically several business days." If the bank asks for more documents, the clock restarts from the day you submit them.

If your launch only sends payouts, skip this. If you also collect US bank transfers into virtual accounts, request them as soon as the customer is approved, not on launch day.

## What happens on the first live payouts?

They settle on the rail's normal timing, with one caveat: early activity attracts review. BlindPay lists "first-time withdrawals or unusual activity patterns" among common compliance hold triggers, and all USD ACH, wire, RTP, and SWIFT payouts land `on_hold` for manual review after the funds are captured. Holds can take up to 30 days.

| Rail | Settlement once released |
| --- | --- |
| Pix, PIX Safe | Minutes. Pix runs 24/7 ([Banco Central do Brasil](https://www.bcb.gov.br/en/financialstability/pix_en)) |
| SPEI | Minutes, around the clock ([Banxico](https://www.banxico.org.mx/services/interbanking-electronic-payme.html)) |
| Transfers 3.0 | Minutes |
| RTP | Instant |
| ACH, wire, TED, ACH Colombia, SEPA, Faster Payments | About 1 to 2 business days |
| SWIFT (POBO/COBO) | Up to 5 business days, after documents are approved |

Timing per BlindPay's [payment methods reference](/docs/kb/payment-methods).

So send one small payout per rail a few days before the real launch. It surfaces bank-detail errors, document requirements, and hold behavior while nothing is at stake. [How to send a SWIFT payout from USDC](/resources/more/how-to-send-swift-payout-from-usdc) covers the extra SWIFT steps.

## Why does the integration take longer than the provider?

Because the provider waits are fixed and short, while your own work isn't. The Federal Reserve's [March 30, 2026 FEDS Note](https://www.federalreserve.gov/econres/notes/feds-notes/payment-stablecoins-and-cross-border-payments-benefits-and-implications-for-monetary-policy-20260330.html) explains why traditional cross-border payments need correspondent banks: setting up foreign branches and cross-border compliance capacity carries high fixed costs. An API removes those from your plan, but it leaves product decisions on your side.

The decisions that eat calendar time:

1. **Who pays fees,** sender or recipient, per product.
2. **Which rails and corridors** you launch with.
3. **How you show the quote** to users, and what happens when it expires.
4. **How support answers** "where is my payout" from webhook statuses.
5. **Internal sign-off** from finance, legal, and compliance on the flow.

Write those answers down in week one. They don't depend on the provider at all.

## How does BlindPay handle go-live?

You get a development instance immediately, with the same API, webhooks, and SDKs as production, a test stablecoin, and simulated settlement. Production onboarding runs in parallel, with instance setup up to 3 business days. After that, KYC Standard is automated in about 60 seconds, and KYB is a manual review of 3 hours to 1 business day. Payouts run over Pix, SPEI, ACH, RTP, SEPA, Faster Payments, and SWIFT (POBO/COBO) with UETR tracking and MT103 confirmations. Fees vary by rail and network and are disclosed in the live quote before execute, on top of a monthly plan.

## What to do next

Open a development instance today and start your company's KYB the same afternoon, with the documents above ready. Then pick the one corridor you'll launch first and get a single payout through it end to end on development.