What is a stablecoin payouts API? How it works and when to use one (2026)

A stablecoin payouts API lets a company fund a payment in a dollar stablecoin such as USDC or USDT, while the provider converts it and delivers local currency to the recipient's bank account over a local rail such as Pix, SPEI, ACH, SEPA or SWIFT. The recipient needs only a bank account. The sender integrates once.

This guide is the hub of BlindPay's stablecoin payouts series. It reflects the product and public rules as of October 2026 and links to deeper pages on each topic. BlindPay publishes it, so read the comparisons with that in mind.

Key takeaways

• A stablecoin payout has three API steps: add the recipient's bank account once, create a quote that locks the rate and fees (5 minutes by default), then execute the payout.
• The recipient receives local currency in a bank account and does not need a crypto wallet.
• BlindPay supports 12 payout rail types, from instant ones (Pix, SPEI, RTP, Argentine Transfers) to SWIFT for 100+ countries.
• KYC, KYB, sanctions screening and travel rule checks sit in the same API flow as the payout, not in a separate vendor contract.
• A payouts API is the wrong tool for domestic-only money movement, or when your main job is issuing stablecoins, issuing cards or holding balance accounts.

What is a stablecoin payouts API?

It is a REST API that turns a stablecoin balance into a bank deposit in another country. You send one request to price the payment and another to execute it. The provider handles conversion, the local bank rail, compliance and status updates.

A stablecoin is a token pegged to a currency, usually the US dollar, that moves on a blockchain network at any hour. USDC and USDT are the two used most for payments. In a payouts API the token is settlement plumbing: it carries value from the sender to the provider, and the provider pays the recipient in the currency the recipient banks in.

That framing matters for buyers. You are not buying a wallet or an exchange account. You are buying the ability to say "pay this person 1,200 Brazilian reais at this bank account" and have it happen, with a firm price shown first. For the wider category, see what a stablecoin API is and the stablecoin payments guide.

How does a stablecoin payout work?

Three steps: add a bank account, create a quote, execute the payout. The same pattern applies on every rail.

1. Add the recipient's bank account once. You save the account details for the rail that matches the destination: a Pix key for Brazil, a CLABE for Mexico, a routing and account number for US ACH, an IBAN for SEPA. The recipient can be the sender's own customer or a third party, because BlindPay lets you set a recipient_relationship other than first_party.
2. Create a payout quote. The quote locks the exchange rate and the fees for 5 minutes by default. It can be shorter for SEPA and Faster Payments, so read expires_at, which is in epoch milliseconds, instead of hard-coding a window. The response shows sender_amount, receiver_amount and the fee fields.
3. Execute the payout. You pass the quote_id and the funding wallet. BlindPay pulls the stablecoins, converts them and sends local currency over the rail. You follow status through the API or webhooks.

The sender chooses who pays the fee. With cover_fees set to false, fees come out of the fiat the recipient receives, which is the common case. With true, fees are added on top, so the recipient gets the full quoted amount, which is the usual choice for payroll.

Statuses run processing, on_hold, completed, failed and refunded. Webhooks announce each change: payout.new, payout.update and payout.complete. For a plain-language walk through the underlying movement of money, read how a stablecoin payment works and stablecoin payout statuses explained.

How is it different from a traditional payout API, an exchange or a wallet?

A traditional payout API moves local money through banks you or the provider already hold accounts with. An exchange sells you tokens. A wallet stores them. A stablecoin payouts API takes tokens in and bank money out.

The practical difference for a finance team is funding. Instead of pre-funding accounts in Brazil, Mexico, Europe and the UK, you hold one dollar stablecoin balance and let each payout convert on demand. Stablecoin platform vs payout API explains how this differs from buying a full platform, and types of stablecoin APIs maps the categories.

Which rails and countries can a payouts API reach?

BlindPay delivers over 12 rail types. Local rails cover the US, Brazil, Mexico, Colombia, Argentina, Europe and the UK, and SWIFT reaches more than 100 countries.

Speeds come from the BlindPay bank accounts docs. The "instant" rails depend on the destination country's own system. Banco Central do Brasil runs Pix and it operates every hour of the year. Banco de México operates SPEI, says a payment should take no more than 30 seconds after approval, and identifies accounts with an 18-digit CLABE. In the US, RTP from The Clearing House is instant and always on.

Banking cut-offs still apply to the slower rails. Requests that arrive after a rail's daily cut-off are processed the next business day, and SWIFT settlement can reach 5 business days according to the cut-off times reference. All SWIFT payouts start on_hold until compliance documents are submitted and approved. BlindPay runs cross-border wires as SWIFT payments and collections on behalf of (POBO/COBO), with UETR tracking and MT103 confirmations.

Each rail has a minimum: 100 USD requested amount for SWIFT, 50 USDC (by sender) or 40 EUR (by receiver) for SEPA, 70 USDC or 50 GBP for Faster Payments, and 10 USD sender amount for every other rail. A quote below the minimum is rejected, for example with LIMITS_AMOUNT_OUT_OF_RANGE. For Latin America specifically, read stablecoins and local rails in Latin America and the USDC to Pix guide.

What does the API handle besides the money movement?

Compliance, status tracking and refunds. These are the parts that cost teams the most engineering time when they build payouts themselves.

On compliance, the business collects KYC data for its customers through the API and BlindPay verifies it. KYB, sanctions screening and travel rule compliance are part of the payout and payin API. The travel rule comes from FATF Recommendation 16, which FATF revised in June 2025 under the title payment transparency. KYC Standard takes about 60 seconds when automated. KYC Enhanced and KYB Standard need manual review that takes 3 hours to 1 business day, per the cut-off times reference. Details are in the KYC docs.

On refunds and custody, BlindPay documents the path precisely:

BlindPay operates as a non-custodial payment processor for payout flows from customer-controlled wallets: you authorize the exact amount and BlindPay executes that single transaction. If a payout cannot be delivered after the stablecoins are collected, BlindPay refunds them to the quote's refund wallet, or to the sending wallet when none is set; on Pix and other non-USD local rails the refund is automatic, while USD payouts and payouts whose review times out are refunded after an operator review. Optional BlindPay-managed wallets (beta) are custodial when you choose that path.

A payout that reaches failed, or that sits past review, is not refunded automatically. Contact support@blindpay.com in that case. Holds can last up to 30 days, and a timeout fails the payout.

Who uses a stablecoin payouts API?

Teams that send money to people or companies in other countries on a recurring basis, and want one integration instead of one per corridor.

• Remittance companies that pay out to families in Brazil, Mexico or Colombia.
• Payroll and contractor platforms that pay a global team in local currency, usually with cover_fees set to true.
• Marketplaces and creator platforms that pay sellers and creators in many countries.
• Import and export businesses that pay suppliers abroad, including by SWIFT where no local rail exists.
• Payment service providers and fintechs that embed cross-border payouts in their own product.

Typical flows go from the United States to Latin America and Europe. BlindPay serves teams of any size, with no volume floor.

When should you not use a stablecoin payouts API?

Skip it when every payment is domestic, when your main job is something else, or when no stablecoin step adds value.

• Domestic-only flows. If you pay US recipients from a US bank account, ACH or RTP through your bank is simpler.
• Issuance. If you need to create or redeem a stablecoin, you want an issuer. BlindPay is the payout layer after issuance, so it complements issuers.
• Cards and balance accounts. If the product is a card, a multi-currency account or a consumer wallet, a payouts API is a component, not the product.
• One-off, low-volume payments. A bank wire may be fine if you send a handful per year and the corridor is well served.

You need a stablecoin payouts API if...

Use this checklist. Three or more yeses mean a payouts API is worth a trial.

• You send recurring payments to bank accounts in Brazil, Mexico, Argentina, Colombia, Europe or the UK.
• Recipients expect local currency in a local bank account, and you cannot ask them to hold tokens.
• You want one dollar balance to fund many corridors instead of pre-funding each currency.
• Your recipients need money on weekends and holidays, which only instant rails such as Pix and SPEI can do.
• You need a firm price shown before the customer commits, locked for a few minutes.
• You want KYC, sanctions screening and travel rule data in the same flow as the payment.
• You pay third parties, such as suppliers, sellers or contractors, not only your own accounts.
• Your engineers prefer webhooks and a sandbox over a bank portal and a spreadsheet.

What are the key terms?

Short definitions, so the rest of the series reads cleanly.

• Payout: an outgoing payment that ends as local currency in a recipient's bank account.
• Payin: an incoming payment, usually a bank transfer converted to stablecoins.
• Off-ramp: the conversion of stablecoins into fiat currency. See what a stablecoin off-ramp is.
• Quote: a priced offer that locks rate and fees for a short window.
• Local rail: the domestic payment network of a country, such as Pix or SPEI.
• Travel rule: the requirement that originator and beneficiary information travels with a transfer.
• KYC and KYB: identity checks for individuals and for businesses.
• Non-custodial: the processor executes only the exact amount you authorize and does not hold your balance.

What should you check when you compare providers?

Check the delivery, not the label. Five questions separate providers that look alike on a features page.

1. Which countries and rails does it deliver to? Ask for the named rail in each country you serve, such as Pix in Brazil or SPEI in Mexico, not a regional claim.
2. Is compliance in the same API flow? KYC, KYB, sanctions screening and travel rule data should not need a second vendor.
3. Does every quote show the full fee before you commit? You want the rate, the fees and the expiry in one response.
4. What is the custody model? Know whether the provider executes only the amount you authorize or holds your balance.
5. Can you test for free? A development instance with forced failure and refund outcomes shortens integration.

Teams that already use an issuer for USDC or an account provider for balances often add a payout layer on top rather than replace them. BlindPay ships local-currency payouts over Pix, SPEI, ACH, SEPA and SWIFT (POBO/COBO), so it fits next to those tools. For the cost side of the decision, read on.

How much does a stablecoin payouts API cost?

Cost has three parts: the provider's fee, the network fee and the exchange rate. Compare the amount the recipient actually receives, since the rate is part of the price.

BlindPay's pricing, in its own canonical wording: BlindPay combines a monthly plan (platform access) with per-transaction fees that vary by rail and network and are disclosed only in the live quote before execute. BlindPay does not publish a static flat rate card; always cite the quote's fee breakdown rather than a fixed bps number.

From the billing docs: there is no setup fee and no monthly minimum, development instances are always free, and a US virtual account costs 1.50 USD per month per active account. Owners and admins can read the fee schedule through the billing fees endpoint. For earning on top of payouts, see partner fees.

How do you get started?

Build against the free development instance first. Payouts complete automatically there, and you can force a failed result with a request_amount of 66600 or a refunded result with 77700.

1. Create a development instance and an API key.
2. Onboard a customer with KYC and add a bank account.
3. Create a payout quote and read the fee breakdown.
4. Execute the payout and listen for payout.complete.
5. Test the failure paths, then move to production.

The payouts docs and payout quotes docs have request examples. BlindPay also ships official SDKs (SDKs docs), an MCP server and Agent Skills for AI tooling (build with AI).

Methodology and sources

External sources: Banco Central do Brasil on Pix, Banco de México on SPEI, The Clearing House on RTP and FATF Recommendation 16 update, June 2025.

BlindPay docs: Payouts, Payout quotes, Bank accounts, Cut-off times, Billing, KYC and SDKs. Rail speeds and minimums were checked against the docs in October 2026 and can change. Check them before you design around a number.

What to do next

Open a free BlindPay development instance, add a test bank account and run your first payout quote end to end. Start with the payout quickstart, then read pricing to see how quotes disclose fees.