Coverage

Caliza enables cross-border payments and USD account infrastructure for global businesses. This page describes every corridor available on the platform — organized by country, with dedicated sections for SWIFT international transfers and stablecoin blockchain transfers.

Each section includes available payment rails, required recipient fields, field formatting rules, and operational notes. For the full recipient API reference, see Create Recipients. For validation error messages, see Response Codes.

---

Address requirements

Several rails (ACH, WIRE, SWIFT) require address objects for the recipient and/or bank. All address fields follow the same structure:

---

Argentina

ARS via CVU

Required recipient fields

Field formatting rules

• Both fields are validated for presence only. No format or checksum validation is applied to the cvu value.

Operational notes

• CVU is the lightest-weight fiat rail on the platform — only two fields required, no address information needed.

---

Brazil

BRL via PIX

Required recipient fields

Field formatting rules

• documentNumber must be either 11 digits (CPF) or 14 digits (CNPJ) after removing formatting characters (/, -, .). The API strips these automatically before validating length.
• pixKey is validated for presence but the format depends on the key type (CPF, email, phone, or UUID).

Operational notes

• BRL deposits are converted to USDC immediately upon receipt.
• A sandbox endpoint is available to simulate PIX deposits: POST /v1/transactions/sandbox/pix. You must provide the beneficiary's document (CPF or CNPJ) and simulationId.
• PIX settlements are typically near-instant during business hours.

---

Colombia

COP via COP

Required recipient fields

Conditional fields (third-party withdrawals)

If thirdPartyWithdrawal is set to true, the following fields become required:

Field formatting rules

• accountType values are uppercase: CHECKING or SAVINGS. Other values (including mixed case) are rejected.
• thirdPartyWithdrawal defaults to false. Only set it to true when the payout goes to an account not owned by the beneficiary.

---

Mexico

MXN via SPEI

Required recipient fields

Field formatting rules

• clabe must be exactly 18 digits and must pass a checksum validation. The check digit is computed using a weighted algorithm (weights: 3, 7, 1 repeating). An invalid checksum will be rejected.
• bankCode is a numeric string identifying the Mexican bank.

Operational notes

• A sandbox endpoint is available to simulate SPEI deposits: POST /v1/transactions/sandbox/spei.
• SPEI operates during the business hours of the Mexican banking system. Transactions submitted outside these hours may be queued.

---

United States

The US supports multiple domestic payment rails, all settling in USD. For international USD transfers, see the SWIFT section below.

USD via ACH

Required recipient fields

Field formatting rules

• routingNumber must be exactly 9 characters and is validated against a US bank directory. Invalid or unknown routing numbers are rejected.
• accountType values are case-sensitive: Checking, Savings, GeneralLedger, Loan.

Operational notes

• ACH is a batch-processing system. Settlement typically occurs within 1–2 business days.
• Same-day ACH is available by setting achSameDay: true on the simulation request. SDACH batches are submitted at 10:00 AM ET, 1:00 PM ET, and 4:00 PM ET. Any remaining transactions are picked up at 6:00 PM ET as standard (next-day) ACH.

---

USD via WIRE

Required recipient fields

Field formatting rules

• routingNumber must be exactly 9 characters and is validated against a US bank directory.
• Both bankAddress and recipientAddress are required (unlike ACH, which only requires recipientAddress).

Operational notes

• Wire transfers are processed individually and typically settle same-day during Fedwire operating hours.
• Wires must be submitted by 5:00 PM ET to be processed the same business day. Wires submitted after this cutoff are processed the next business day.

---

USD via RTP

Required recipient fields

Field formatting rules

• routingNumber must be exactly 9 characters.
• No address fields are required for RTP recipients.

Operational notes

• RTP is the lightest-weight US rail — only two fields are required.
• Transactions settle in seconds, 24/7/365.
• Not all US banks participate in the RTP network. If the receiving bank does not support RTP, the transaction will fail.

---

SWIFT

SWIFT enables international USD transfers to 179 countries via the SWIFT banking network. Unlike the domestic rails above, SWIFT is not tied to a single destination country — it's the mechanism for moving USD across borders.

USD via SWIFT

Required recipient fields

Intermediary bank routing

Caliza automatically determines the optimal intermediary bank route for SWIFT transfers. If you need to specify routing explicitly, you can provide the following optional fields:

Field formatting rules

• swiftCode must be 8 or 11 characters and is validated against the SWIFT directory.
• iban, if provided, is validated against an IBAN directory.
• routingNumber, if provided, is validated against a US bank directory.
• bankAddress.country must not be US. For domestic USD transfers, use ACH, WIRE, or RTP instead.

Operational notes

• Settlement times vary by destination country, typically 1–3 business days.
• SWIFT transfers must be submitted by 5:00 PM ET to be processed the same business day. Transfers submitted after this cutoff are processed the next business day.
• A sandbox endpoint is available to simulate USD deposits: POST /v1/transactions/sandbox/usd-deposit.

Supported destination countries

SWIFT transfers can be sent to any country participating in the SWIFT network. Specify the destination via the bankAddress.country field using an ISO 3166-1 alpha-2 code.

Europe

Americas

Africa

Asia & Middle East

Oceania & Pacific

Other territories

---

Stablecoins

Stablecoins serve as the operational backbone of the Caliza platform. Most fiat deposits are converted to USDC immediately, and stablecoin transfers move funds between wallets on supported blockchain networks. Stablecoins are not tied to a specific country.

USDC (USD Coin)

Primary operational currency on the platform.

USDT (Tether)

Supported stablecoin, convertible to USDC.

Required recipient fields (all crypto rails)

Operational notes

• Blockchain transfers settle based on network confirmation times — typically seconds to minutes depending on congestion.
• Ensure the walletAddress is valid for the specified network. Sending to an address on the wrong network may result in permanent loss of funds.

---

Quick reference

Next steps