Payouts to USA

Review these US-specific requirements before initiating USD payouts. For the general cross-border
payment flow, see Sending Cross-Border Payments.

⚠️

Available to CA banks only

USD payouts to the USA are only valid for CA (Canada) banks. Contact Cybrid support to confirm
eligibility before initiating payouts.

Supported configurations

USA payouts support the following participant types:

• C2C (consumer-to-consumer) — individual customer to individual counterparty
• B2C (business-to-consumer) — business customer to individual counterparty
• B2B (business-to-business) — business customer to business counterparty

All three use the bank_account route via the ACH or RTP payment rails. RTP is supported in production only.

Trading account requirement

USA payouts require a USDC_SOL trading account as the source. Other trading account types
(such as USDC or USDC_NPL) are not supported for USD payouts.

Verify USD payout availability

Confirm your bank supports USD payouts for your participant type and the bank_account route.

ℹ️

Bank configuration required

Contact Cybrid support to enable USD payouts and configure USA as a supported corridor for your bank.

GET /api/banks/{bank_guid}
Authorization: Bearer YOUR_TOKEN

Look for an entry in supported_payout_symbols where:

• symbol: USD-USDC_SOL
• country_code: US
• participants_type: C2C, B2C, or B2B
• route: bank_account

You can also query prices for the United States:

GET /api/prices?payout_country_code=US
Authorization: Bearer YOUR_TOKEN

Identity verification requirements

The platform validates all required KYC fields when you create a plan for USD payouts. Requirements
differ by participant type.

Originator (Customer)

Individual originator (C2C):

• name.first, name.last
• date_of_birth
• address.street, address.city, address.country_code
• identification_numbers with at least one of:
  • social_security_number
  • drivers_license
  • passport
  • passport_card
  • identification_card
  • residence_card
  • national_identification_number
  • tax_identification_number

Business originator (B2C, B2B):

• name.full (registered name)
• address.street, address.city, address.country_code
• identification_numbers with one of:
  • business_registration_number
  • tax_identification_number
  • employer_identification_number

Receiver (Counterparty)

Create the counterparty with the
standard required fields
for the appropriate type, plus the US-specific address fields below. The counterparty must be in
verified state before you can create the external bank account and plan.

Individual counterparty (C2C, B2C):

• address.street, address.subdivision, address.postal_code

Business counterparty (B2B):

• address.street, address.subdivision, address.postal_code

Purpose of transaction

For USA payouts, purpose_of_transaction is required for all participant types. All standard
purpose values are accepted.

Supporting documents

B2B payouts to the USA require at least one supporting document. No specific document type is
mandated, so you can use any supported type: invoice, purchase_order, delivery_slip,
contract, bill_of_lading, or others. C2C and B2C payouts require no supporting documents.

Requirements:

• At least one supporting document is required (B2B only).
• Up to 3 documents per plan.
• Each file must be uploaded with a type matching the document type.
• Allowed file formats: application/pdf, image/jpeg, image/png.
• Each file must be no larger than 8 MB, with a filename of 64 characters or fewer.

Upload each file via File Upload and wait for
state: completed before referencing its GUID. For the full supporting_documents field
structure, see
Sending Cross-Border Payments.

External bank account setup

USA payouts support the ACH and RTP payment rails. Both use ABA routing to identify the credit
party by routing number and account number. For ACH, an optional account type can also be specified.

⚠️

RTP not available in sandbox

The RTP payment rail is supported in production only. Use ACH when testing in sandbox.

Send a POST request to /api/external_bank_accounts with the following format:

{
  "account_kind": "raw_routing_details",
  "name": "US beneficiary account",
  "counterparty_bank_account_details": [{
    "bank_code_type": "ABA",
    "bank_code": "021000021",
    "account_identifier": "123456789",
    "account_type": "checking",
    "payment_rail": "ACH"
  }],
  "counterparty_guid": "counterparty_guid",
  "customer_guid": "customer_guid",
  "asset": "USD"
}

ℹ️

Switching to RTP

To use RTP in production, set "payment_rail": "RTP" in the counterparty_bank_account_details array item.
All other fields remain the same.

ℹ️

Default account type

checking is the default and can be omitted. Set account_type to savings for savings accounts.

ℹ️

API versioning

Creating external bank accounts with raw routing details requires
Accept-Version: 2025-10-01 or later.

For the full account model and field reference, including ABA/ACH examples, see
Add Counterparty External Bank Accounts.

Common validation errors

Related resources

• Sending Cross-Border Payments
• Add Counterparty External Bank Accounts
• Creating a Counterparty
• Verifying a Counterparty
• Create Plan API Reference