# POBO and COBO over SWIFT: BlindPay

Collect international Wires into accounts named after your customer, and send global SWIFT payouts from stablecoins with a compliance document gate and per-rail payment references.

## Collection on behalf of (COBO)
- Each customer gets a dedicated account with its own BIC and IBAN.
- Inbound Wires settle straight into stablecoins.
- Inbound SWIFT payins require a virtual account: the account is what gives the wire a named beneficiary.
- Every payin reports `sender_name`, `sender_bank_name`, `sender_account_number` and `transaction_reference`.

## Payment on behalf of (POBO)
- Pay suppliers over SWIFT from a USDC or USDT balance.
- The wire is funded from the customer's own account when they hold one, which is what puts their name on the debit. Without a named account the payout is funded from our master account and the customer is identified in the payment reference.
- Minimum SWIFT payout: 100 USD.
- Business payouts require a document proving the sender-customer relationship: invoice, purchase order, delivery slip, contract, customs declaration or bill of lading.
- `tracking_documents.status` reports `waiting_documents`, then `compliance_reviewing`, then null once cleared. Thirty days to submit, up to eight days to review.

## Payment tracking, per rail
- SWIFT: `provider_uetr` (Unique End-to-end Transaction Reference) and `provider_clearing_system`.
- Domestic Fedwire: `provider_uetr`, plus `provider_imad` (Fed Input Message Accountability Data).
- ACH: no UETR and no IMAD. `provider_reference` is returned instead, a bank-side reference rather than the formal network trace number.
- All of these arrive on `GET /payouts/{id}` and on the `payout.complete` webhook.

## Links
- Virtual accounts: https://blindpay.com/virtual-accounts
- SWIFT deliverability: https://blindpay.com/docs/kb/swift-deliverability
- SWIFT statuses: https://blindpay.com/docs/kb/swift-statuses
- Docs: https://blindpay.com/docs/introduction
- Sign up: https://app.blindpay.com/sign-up