Stablecoin issuer vs payout API: how the USDC payments stack fits together

An issuer such as Circle creates and redeems USDC and EURC. A payout API such as BlindPay takes USDC or USDT and delivers local currency to a bank account over rails like Pix, SPEI, ACH, SEPA and SWIFT (POBO/COBO). They sit at different layers of the stack, so they complement each other rather than compete.

This guide splits the stablecoin payments stack into four layers and shows who does what, as of October 2026. For the product itself, see what a stablecoin payouts API is. BlindPay publishes this post, so BlindPay is listed first and Circle's facts come from Circle's own pages and our BlindPay vs Circle comparison.

Key takeaways

• A stablecoin payments stack has four layers: issuance, liquidity and conversion, local-rail payout, and compliance.
• Circle sits at the issuance layer: it issues USDC and EURC and offers minting and redemption through Circle Mint, plus the Circle Payments Network for institutions.
• BlindPay owns the payout layer: USDC or USDT in, local currency out over Pix, SPEI, ACH, RTP, SEPA, Faster Payments and SWIFT (POBO/COBO), with UETR tracking and MT103 confirmations.
• BlindPay does not issue, mint or redeem tokens, and it is not a card acquirer or a consumer wallet.
• Most teams integrate the layer they need today and leave the others to specialists.

What are the four layers of a stablecoin payments stack?

Issuance, liquidity and conversion, local-rail payout, and compliance. Each layer answers a different question, and one provider rarely covers all four well.

1. Issuance. Who creates the token and guarantees redemption? This is Circle for USDC and EURC.
2. Liquidity and conversion. Where does the stablecoin become a local currency, and at what quoted rate? A payout API locks that rate in a quote.
3. Local-rail payout. Who delivers money to the recipient's account, on which rail, and with what status tracking?
4. Compliance. Who verifies the customer, screens sanctions and passes the travel rule data?

Picture the layers stacked: issuance at the bottom, then conversion, then the payout rail, with compliance running up the side of all three. A payment touches every layer even when you integrate only one. What stablecoin infrastructure is and stablecoin platform vs payout API describe the same idea from a platform angle. For the token itself, read what USDC is.

Who does what: BlindPay or Circle?

BlindPay does the payout, conversion and payee-level compliance. Circle does issuance and reserve custody, plus its own institutional network. The table lists BlindPay first, then Circle, from each company's public pages.

Sources for the Circle column are Circle's USDC page, Circle's transparency page, Circle Payments Network and Circle's developer docs. Where Circle does not publish a detail, such as payout rails by corridor, this post does not guess.

What does the issuer layer do?

It creates the token and stands behind it. Circle issues USDC and EURC and, per its pages, holds the reserves and processes minting and redemption for institutions through Circle Mint.

That matters to a payout team in three ways. First, the reserve and redemption design is what makes a token trusted by banks and regulators. Second, in the EU, Circle obtained an electronic money institution license in France and issues USDC and EURC as MiCA e-money tokens, as described in Circle's announcement and our MiCA explainer. Third, an issuer's job ends when the token is redeemed for dollars or euros: it does not deliver Pix to a Brazilian supplier.

BlindPay is not an issuer, a mint and redeem provider, a card acquirer or a wallet app. It uses USDC and USDT that you already hold and focuses on what happens next.

What does the payout layer do?

It converts the stablecoin and delivers local currency, with a firm price and a status for every payment. This is BlindPay's layer.

The flow has three steps: add the recipient bank account once, create a payout quote that locks the exchange rate and fees for 5 minutes, then execute the payout. The quote returns sender_amount, receiver_amount, flat_fee, partner_fee_amount, billing_fee_amount, commercial_quotation and blindpay_quotation, so your customer sees a final number before committing. Payouts move through processing, on_hold, completed, failed and refunded, with webhooks payout.new, payout.update and payout.complete.

For cross-border wires BlindPay runs SWIFT (POBO/COBO) payments and collections on behalf of, with UETR tracking and MT103 confirmations. Teams that already hold USDC through Circle add BlindPay for local-currency payouts over Pix, SPEI, ACH, SEPA and SWIFT (POBO/COBO). See how stablecoin payouts work step by step and the payouts docs.

Where does the Circle Payments Network fit?

At the institution-to-institution layer. In Circle's description, an originating institution sends USDC through the network and a beneficiary institution delivers local fiat, with quote aggregation, travel rule data exchange and webhooks (Circle docs).

That model suits a bank or licensed payment company that joins the network as a participant. A fintech, payroll platform or marketplace that wants to call one API for Pix, SPEI or SEPA payouts to its own customers' payees is solving a different problem, and BlindPay is built for that one. The two can coexist: Circle for issuer-level access and the network, BlindPay for payee-level payouts with compliance inside the call.

How does compliance split across the layers?

Each layer has its own obligations. The issuer carries reserve and redemption rules, the network vets its members, and the payout layer checks the person or company that receives the money.

For the payout layer, the FATF Recommendation 16 update on payment transparency (June 2025) is the reference for the data that must travel with a transfer. BlindPay folds KYC, KYB, sanctions screening and the travel rule into the payout and payin API: the API user collects KYC data and BlindPay verifies it. Standard KYC runs automatically in about 60 seconds, while Enhanced KYC and Standard KYB take 3 hours to 1 business day of manual review. See stablecoin payout compliance for the detail.

When should you integrate at each layer?

Integrate a layer yourself only when it is your product. The guide below gives a default for each layer.

If you are weighing a full in-house build, our guide to building stablecoin payouts in-house gives a component table and a scorecard. If you are comparing a full-stack platform with a payout API, see stablecoin platform vs payout API.

What does BlindPay cost across this stack?

BlindPay's pricing 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.

BlindPay has no setup fee and no monthly minimum, and development instances are always free. A US virtual account costs 1.50 USD per month per active account. The fee schedule is available through the billing fees endpoint for owner and admin roles. See stablecoin payout API pricing and the billing docs. On custody, BlindPay states: 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.

Methodology and sources

External sources: Circle USDC, Circle transparency, Circle Payments Network, Circle's fiat payouts docs, Circle's MiCA announcement and the FATF Recommendation 16 update. Circle facts also come from the vetted BlindPay vs Circle page.

BlindPay docs used: payouts, payout quotes, supported chains, billing and KYC.

What to do next

Map your own flow to the four layers and mark which ones you need to own. Then check the networks and tokens you can fund payouts with in the supported chains reference, and send a first payout on a free development instance with the payout quickstart.