Blindpay

BlindPay Integration

BlindPay is a global payment API. One integration covers bank rails (ACH, wire, RTP, SWIFT, Pix, SPEI, ACH COP, Transfers 3.0, SEPA) and stablecoins (USDC, USDT) across seven chains. Every payment settles through stablecoins under the hood, and BlindPay is a non-custodial processor: funds stay under the customer's control, and failed transactions are returned to the originating wallet or bank account.

The docs come in two flavors and the reference files keep both, marked inline:

• Abstracted flavor: bank-rails framing. Virtual accounts, payins as deposits, payouts as bank transfers. BlindPay handles the stablecoin leg.
• Advanced flavor: stablecoin framing. Managed and external wallets, chains and tokens, on-chain authorization, cross-chain transfers.

Both run on the same API, keys, instances and webhooks. When answering, pick the flavor that matches what the user is building.

Terminology

receiver was renamed to customer. The API path is /customers, IDs still start with re_. Older integrations may use /receivers; new code should use /customers.

Authentication

Every call needs a secret API key and an instance ID in the path:

curl --request GET \
  --url https://api.blindpay.com/v1/instances/in_000000000000/customers \
  --header 'Authorization: Bearer YOUR_API_KEY'

Keys are per instance. A development instance is the sandbox (testnets, USDB test token, simulated fiat); a production instance moves real money. See [Sandbox vs production](references/essentials/sandbox-vs-production.md).

The two core flows

Payout: money out to a bank account

1. Accept Terms of Service → tos_id
2. Create a customer (KYC/KYB) → re_..., wait for approved
3. Add a bank account → ba_...
4. Create a payout quote → qu_... (valid 5 minutes)
5. Fund the payout: a managed wallet balance needs no signature; an external wallet needs authorization (ERC-20 approve on EVM, signed XDR on Stellar, token delegation on Solana)
6. Execute the payout → po_..., then track it over webhooks

Start at [Payouts](references/payouts/payouts.md).

Payin: money in from a bank account

1. Accept Terms of Service → tos_id
2. Create a customer (KYC/KYB) → re_..., wait for approved
3. Pick a destination: managed wallet (bl_...), external blockchain wallet (bw_...), or issue a virtual account for standing deposits
4. Create a payin quote → pq_... (valid 5 minutes)
5. Execute the payin → pi_... and show the payer the returned instructions (Pix code, CLABE, memo code, ACH/wire details)
6. Funds arrive, BlindPay delivers the stablecoin leg and fires webhooks

Start at [Payins](references/payins/payins.md).

Main endpoints

All paths are prefixed with https://api.blindpay.com/v1/instances/{instance_id}.

| Resource | Endpoint | | --- | --- | | Customers | /customers, /customers/{re} | | Terms of Service | /e/instances/{instance_id}/tos (public, no key) | | Bank accounts | /customers/{re}/bank-accounts | | Offramp wallets | /customers/{re}/bank-accounts/{ba}/offramp-wallets | | Blockchain wallets | /customers/{re}/blockchain-wallets, .../sign-message | | Managed wallets | /customers/{re}/wallets, .../wallets/{bl}/balance | | Virtual accounts | /customers/{re}/virtual-accounts | | Payout quotes | /quotes | | Payouts | /payouts, /payouts/evm, /payouts/stellar, /payouts/stellar/authorize | | Payin quotes | /payin-quotes | | Payins | /payins/evm | | Transfers | /transfer-quotes, /transfers | | RFI and limits | /customers/{re}/rfi, /customers/{re}/limit-increase | | Partner fees | /partner-fees | | Webhooks | /webhook-endpoints, .../{we}/secret | | Upload | https://api.blindpay.com/v1/upload?instance_id={instance_id} |

Amounts are always integers in minor units: 100000 is $1,000.00.

ID prefixes

| Prefix | Resource | | --- | --- | | in_ | Instance | | re_ | Customer (formerly receiver) | | ba_ | Bank account | | bw_ | External blockchain wallet | | bl_ | BlindPay-managed wallet | | qu_ | Payout quote | | po_ | Payout | | pq_ | Payin quote | | pi_ | Payin | | tr_ | Transfer | | pf_ | Partner fee | | we_ | Webhook endpoint |

Payment methods

| Method | Country | Currency | Direction | | --- | --- | --- | --- | | international_swift | Global | USD | Send | | ach | United States | USD | Receive + send | | wire | United States | USD | Receive + send | | rtp | United States | USD | Send | | pix | Brazil | BRL | Receive + send | | spei_bitso | Mexico | MXN | Receive + send | | ach_cop_bitso | Colombia | COP | Send | | PSE | Colombia | COP | Receive | | transfers_bitso | Argentina | ARS | Receive + send | | sepa | Europe (SEPA zone) | EUR | Send |

Pix, SPEI and Transfers settle in minutes; RTP is instant; ACH, wire, ACH COP and SEPA take 1-2 business days; SWIFT up to 5. See [Cut-off times](references/kb/cut-off-times.md).

Chains and tokens

| Chain | Mainnet | Testnet (development) | Mainnet tokens | | --- | --- | --- | --- | | Ethereum | ethereum | sepolia | USDC, USDT | | Polygon | polygon | polygon_amoy | USDC, USDT | | Base | base | base_sepolia | USDC | | Arbitrum | arbitrum | arbitrum_sepolia | USDC | | Stellar | stellar | stellar_testnet | USDC | | Solana | solana | solana_devnet | USDC, USDT | | Tron (beta) | tron | none | USDT |

A production instance can only use USDC or USDT on a mainnet; a development instance can only use USDB (BlindPay's test token) on a testnet. Mismatched combinations are rejected. See [Supported chains](references/kb/supported-chains.md).

Testing on a development instance

Set the quote's request_amount to a sentinel value to force an outcome:

| request_amount | Result | | --- | --- | | 66600 ($666.00) | failed | | 77700 ($777.00) | refunded | | anything else | completed (payins auto-complete about 30 seconds after creation) |

Create a customer with first name Fail to simulate a KYC rejection. Mint USDB from the dashboard (EVM) or the mint endpoints (Stellar, Solana).

Customer KYC statuses

verifying, approved, rejected, compliance_request (an RFI is open and the customer is paused), approved_rfi (operational with an open RFI). Standard KYC clears in about 60 seconds; enhanced KYC and KYB take 3 hours to 1 business day. See [Customers](references/essentials/customers.md) and [RFI](references/essentials/rfi.md).

Common errors

• please_accept_terms_of_service: the customer must accept the current TOS version
• quote expired: payout and payin quotes live 5 minutes, transfer quotes 15 seconds; create a new one
• insufficient balance or allowance: the wallet lacks funds, or the ERC-20 approval is below the quote amount
• KYC not approved: the customer is still verifying, rejected, or paused by an RFI
• unsupported token/chain pairing: check the chain table above

Reference documentation

Getting started

• [Introduction](references/getting-started/introduction.md) - BlindPay is a global payment API that moves money over bank rails and stablecoins from a single integration.
• [Overview](references/getting-started/overview.md) - Connect to bank rails or stablecoin networks (or both) through one REST API. Issue virtual accounts and move fiat payins and payouts, or hold, send, and receive USDC and USDT across chains.
• [Stablecoins to bank transfer](references/getting-started/quickstart-payout.md) - Send your first off-ramp payout from a BlindPay-managed wallet to a bank account on a development instance, using only the REST API.
• [Bank transfer to stablecoins](references/getting-started/quickstart-payin.md) - Accept a bank transfer and have BlindPay deliver the equivalent stablecoins automatically on a development instance, using only the REST API.
• [SDKs](references/getting-started/sdks.md) - Official BlindPay SDKs for Node.js, Python, Go, PHP, and Swift, plus the OpenAPI spec and REST API reference.
• [Build with AI](references/getting-started/build-with-ai.md) - Connect AI coding agents and AI builders to BlindPay with an MCP server, Agent Skills, and a REST API.

Essentials

• [Instances](references/essentials/instances.md) - Instances are isolated BlindPay environments, one per stage of your stack, created in the dashboard.
• [Sandbox vs. production](references/essentials/sandbox-vs-production.md) - The exact behavioral differences between development and production instances, plus a checklist for switching over.
• [Billing](references/essentials/billing.md) - How BlindPay charges for virtual accounts, transactions, and partner fees, and when invoices go out
• [Partner fees](references/essentials/partner-fees.md) - Add percentage or flat fees to your customers' transactions and withdraw the accumulated revenue monthly.
• [Customers](references/essentials/customers.md) - People or businesses that send or receive payments and stablecoins through BlindPay.
• [Terms of Service](references/essentials/terms-of-service.md) - A legal agreement your customers must accept before you create them and start KYC.
• [RFI](references/essentials/rfi.md) - Respond programmatically when BlindPay's compliance team needs additional documentation from a customer.
• [Limit increase](references/essentials/limit-increase.md) - Request higher per-transaction, daily, or monthly transfer limits for a customer by submitting a supporting document, and track the request through compliance review.
• [Upload](references/essentials/upload.md) - Generate encrypted file URLs from customer KYC documents and pictures.
• [Analyze document](references/essentials/analyze-document.md) - Read a KYC document with AI and get an approval-rate signal before you submit it.
• [API keys](references/essentials/api-keys.md) - Authenticate all BlindPay API requests with an instance-scoped API key created in the dashboard.
• [Webhooks](references/essentials/webhooks.md) - Receive real-time events for customers, payments, virtual accounts, wallets, and transfers instead of polling the API.
• [Webhooks events](references/essentials/webhooks-events.md) - The full BlindPay webhook event catalog, grouped by domain, with an example payload.
• [Webhook verification](references/essentials/webhooks-verification.md) - Verify the signature on every BlindPay webhook call using the svix-id, svix-timestamp, and svix-signature headers.

Payouts (money out to a bank account)

• [Payouts](references/payouts/payouts.md) - Execute a payout to a recipient's bank account and track it from processing to completed, failed, or refunded.
• [Bank accounts](references/payouts/bank-accounts.md) - Add recipient bank accounts BlindPay pays out to, across SWIFT, ACH, wire, RTP, Pix, SPEI, ACH COP, Transfers, and SEPA rails.
• [Payout quotes](references/payouts/payout-quotes.md) - Lock the exchange rate and fee split before executing a payout, and see the exact fee breakdown and recipient amount in the response.
• [Payout with managed wallet](references/payouts/payout-managed-wallet.md) - Fund a payout from a BlindPay-managed wallet with a single REST call, no on-chain approval or signing involved.
• [Payout with EVM](references/payouts/payout-evm.md) - Fund a payout from an external EVM wallet, approve the ERC-20 token transfer, then execute the payout.
• [Payout with Stellar](references/payouts/payout-stellar.md) - Fund a payout from an external Stellar wallet, authorize the payout, sign the XDR transaction, then create the payout.
• [Payout with Solana](references/payouts/payout-solana.md) - Fund a payout from an external Solana wallet, delegate the tokens to BlindPay, then create the payout.
• [Offramp wallets](references/payouts/offramp-wallets.md) - What a BlindPay offramp wallet is, the chains and stablecoins it supports, minimums, and how deposits automatically convert to a fiat payout.

Payins (money in from a bank account)

• [Payins](references/payins/payins.md) - Create a payin, deliver funds to the destination, and track it through settlement.
• [Payin quotes](references/payins/payin-quotes.md) - Lock the amount, fee split, and destination for a payin before creating it.
• [Blockchain wallets](references/payins/blockchain-wallets.md) - Register an external, customer-controlled wallet address to receive stablecoin payins and send stablecoin payouts.
• [Payin with managed wallet](references/payins/payin-managed-wallet.md) - Accept a fiat payment and have the equivalent stablecoins delivered into a BlindPay-managed wallet, two REST calls with no signing.
• [Payin with blockchain wallet](references/payins/payin-blockchain-wallet.md) - Accept a fiat payment and have the equivalent stablecoins delivered to a wallet your customer controls.

Virtual accounts

• [Virtual accounts](references/virtual-accounts/virtual-accounts.md) - Issue a virtual account (virtual bank account) that receives USD bank transfers and settles automatically to stablecoins like USDC or USDT in your customer's wallet.
• [Create a virtual account](references/virtual-accounts/virtual-accounts-create.md) - Create a virtual account with the BlindPay API, from customer prerequisites and required compliance fields to the webhooks that confirm approval.

Wallets, transfers and stablecoins

• [Store](references/wallets/store.md) - Hold a customer's balance in a BlindPay-managed wallet, or register an external wallet the customer already controls.
• [Managed wallets](references/wallets/wallets.md) - Create a BlindPay-managed wallet, check its balance, and use it on payins and payouts.
• [Send](references/wallets/send.md) - Send stablecoins out of a BlindPay-managed wallet to another managed wallet or any external address, using the BlindPay API.
• [Transfer quotes](references/wallets/transfer-quotes.md) - Create a transfer quote to lock in the source wallet, destination address, token, network, and amount before executing a transfer.
• [Transfers](references/wallets/transfers.md) - Execute a stablecoin transfer from a transfer quote and track it through to completion with the BlindPay API.
• [Receive](references/wallets/receive.md) - Receive stablecoins into a BlindPay-managed wallet and track every deposit through the wallet.inbound webhook.
• [Mint USDB](references/wallets/mint-usdb.md) - Mint BlindPay's USDB test stablecoin on EVM testnets, Stellar Testnet, and Solana Devnet to simulate payments on development instances.

Knowledge base (compliance, coverage, operations)

• [Cut-off times](references/kb/cut-off-times.md) - ACH, wire, and SWIFT cut-offs and settlement, instant rails, quote expiry windows, onboarding SLAs, and refund timing.
• [Information requests](references/kb/information-requests.md) - A Request for Information (RFI) is how BlindPay compliance asks for missing KYC or KYB details before a customer can be approved.
• [Instance requests](references/kb/instance-requests.md) - How BlindPay compliance asks your team for additional information about your own account, and how to respond before the 27-day window closes.
• [KYB documents](references/kb/kyb-documents.md) - Document requirements for business KYB verification — formation docs, ownership proof, UBO identification, and proof of address.
• [KYC basics](references/kb/kyc-basics.md) - Required KYC verification levels, document-quality standards, and submission guidelines for BlindPay customers.
• [KYC requirements](references/kb/kyc.md) - Verification levels, required fields, statuses, limits, document quality, terms of service, and RFIs for BlindPay customers.
• [NAICS codes](references/kb/naics-codes.md) - Find the NAICS industry code for your business during BlindPay onboarding.
• [Nested payments](references/kb/nested-payments.md) - Nesting is moving money on behalf of a party BlindPay cannot see; this guide explains how to recognize it and stay compliant.
• [On-hold transactions](references/kb/on-hold-transactions.md) - Transactions

…

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: blindpaylabs
• Source: blindpaylabs/skills
• License: MIT

Install and usage instructions live in the source repository linked above.