This endpoint lets you create a fiat receiving account (Virtual Account, “VA”) for a specific currency. A VA is a bank-style deposit handle issued to you (or to your end-customer under your tenancy) so funds can be received and reconciled automatically and later used in transfer flows.Supported VA types & rails: see Supported Virtual Accounts (link to be provided). Different rails may have different attributes (e.g., bank code, branch, IBAN/CLABE/PIX key).Currency: pass the 3-letter ISO 4217 code (e.g., BRL, USD, EUR). The VA will be issued on the corresponding fiat rail for that currency.
Mandatory merchant profile fieldsThe following fields are required in the two scenarios below:Creating a DYNAMIC QR for any rail (currency = BRL,accountSubType = DYNAMIC).
Creating a BRAZA STATIC PIX KEY (currency = BRL, accountSubType = STATIC, with pixKeyType).
| Required field | Corporate field | Individual field |
|---|
| Name | companyName (top-level) / companyInfo.entityName | individualInfo.firstName + individualInfo.lastName |
| Industry | companyInfo.industry | individualInfo.industry |
| Merchant URL | companyInfo.businessPlatformUrl | individualInfo.businessPlatformUrl |
| Company registration number | companyInfo.registrationNumber | individualInfo.taxIdNumber |
| Registration country (ISO 3166-1 alpha-2, 2-letter) | companyInfo.incorporatedCountry | individualInfo.taxCountry |
Create for your customer (sub-user)
1
Create Virtual Account
Simply call this endpoint and submit the required information to open a Virtual Account (VA) under your customer (sub-user).
All necessary KYB/KYC information for the customer should be prepared and included as specified in the request parameters.
For details on required verification fields, please refer to the KYB/KYC documentation below:
Virtual Account(VA) Support ListThe response returns the virtual account details issued by the rail (e.g., account number / bank code / holder name / PIX key, depending on the rail).
Use the VA only for the specified currency. Cross-currency deposits are not supported.
For compliance (e.g., Travel Rule / payer data), some rails may require payer metadata at deposit time; follow the rail-specific guidance in the Supported Virtual Accounts page.
To remove a VA that is no longer needed, use the Delete Account endpoint.