Corridor-specific field requirements

Last Updated: April 14, 2026 Version: 2.0

This page is a companion to CreateNewOrder. Use it when you need to know how sender country, recipient country, payment rail (TypeOfPaymentID / ACH, FedNow-style instant credit, TED/DOC, PIX, etc.), and transaction type (P2P, P2B, B2B, B2P) interact beyond the generic R / O / C column in the main field tables.

Legend

Brazil: RecipientTIN and beneficiary type

For every order with RecipientCountry = BR, RecipientTIN is mandatory on CreateNewOrder. The value must match who receives the funds:

• CPF — 11 digits, digits only — natural person (individual beneficiary).
• CNPJ — 14 digits, digits only — legal entity (company beneficiary).

The API uses this distinction together with name and company fields: when RecipientTIN is treated as a CPF (11 digits), RecipientFirstName cannot be empty (empty XML elements count as missing). When it is treated as a CNPJ (14 digits), RecipientCompany must contain the legal company name. Do not send a CPF for a corporate beneficiary or a CNPJ for an individual.

For non-production environments, syntactically valid sample numbers may be built with third-party generators such as CPF generator and CNPJ generator; use only sandboxes, never real taxpayer data you do not own.

Field requirements by corridor

Each block below is one corridor: origin → destination and payment rail. The Brazil matrices — bank deposit (TED/DOC) and PIX — are titled * → Brazil and follow the * → BR partner sheets (any sender country). Full request rules remain in CreateNewOrder. For Brazil payouts, read Brazil: RecipientTIN and beneficiary type above in addition to the matrices.

← Back to CreateNewOrder