Skip to main content

Static Deposits - MXN, ARS, COP and USD

Introduction​

A static deposit is a permanent deposit detail that belongs to an account, one per currency:

  • a CLABE in Mexico, for MXN;
  • a CVU in Argentina, for ARS;
  • a Bre-B key in Colombia, for COP;
  • a SWIFT receiving account in the United States, for USD sent by international transfer.

Your user saves it once and uses it as many times as they want, with any amount, whenever they want. You don't create a quote or a ticket before each payment. Every deposit that lands on it is converted to USDC and credited to the INTERNAL balance of the account the detail belongs to.

If you already use the account's static BR Code for PIX, this is the same idea for MXN, ARS, COP and USD.

Availability

The MXN, ARS and COP details are available in sandbox, and production uses the same fields and the same flow when it is released, so an integration built on sandbox does not change. The USD SWIFT receiving account is enabled by Avenia for each account: ask your account manager to turn it on, in sandbox or in production.

What it is good for​

  • Recurring deposits. A salary, a monthly top-up or any payment your user repeats can always go to the same detail.
  • Showing it once. Display the detail on your user's screen or profile once; they don't need a new one for the next payment.
  • Reconciling without extra work. Avenia creates a ticket for every deposit that arrives, so each one shows up in your tickets and webhooks like any other operation. See What Happens When a Deposit Arrives.

Static deposit or ticket​

A ticket is made for one payment: you ask for a quote, the rate and the amount are fixed up front, the ticket has a deadline, and its deposit instruction is used for that payment only.

Static depositTicket
Deposit detailPermanent, one per currencyA new one for each payment
AmountAny amount, chosen by whoever paysFixed by the quote
RateAvenia's quote when the deposit is processedFixed when the ticket is created
DeadlineNoneThe ticket expires
Created byAvenia, when the deposit arrivesYou, before the payment

Use a ticket when you need to know the exact rate and the amount of USDC before your user pays, or when a payment has to be tied to a specific order. Use a static deposit when your user just needs a place to send money at any time. See Bank Account - MXN, Bank Account - ARS and Bank Account - COP for the ticket flow.

Get the Static Deposit Details​

The details come as separate fields of the Account Info endpoint, next to brCode: clabe for MXN, cvu for ARS, bre-b for COP and swiftReceivingAccount for USD by SWIFT. Pass subAccountId to read the details of a sub-account: each sub-account has its own, and a deposit to them is credited to that sub-account.

Endpoint​

GEThttps://api.sandbox.avenia.io:10952/v2/account/account-info

Parameters​

FieldTypeDescription
subAccountIdstringOptional. The sub-account to read. Omit it to read the main account.

Request example​

cURL
curl -X GET "https://api.sandbox.avenia.io:10952/v2/account/account-info?subAccountId=00000000-0000-0000-0000-000000000000" \
-H "Authorization: Bearer eyJhdXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"

Response​

The other Account Info fields are left out here. See Account Info for the full response.

JSON
{
"id": "00000000-0000-0000-0000-000000000000",
"brCode": "00020126580014br.gov.bcb.pix0136...6304XXXX",
"clabe": "999999000000123455",
"cvu": "0009999099000000000897",
"bre-b": "@SBX000000000893",
"swiftReceivingAccount": {
"beneficiaryName": "Jane Doe",
"bankName": "Sandbox Bank",
"bic": "SBXXUS33XXX",
"accountNumber": "9999000123456789",
"routingNumber": "999999999",
"bankAddress": {
"street1": "1 Sandbox Plaza",
"street2": "",
"city": "New York",
"region": "NY",
"postalCode": "10001",
"country": "US"
}
}
}

Fields​

FieldCurrencyFormatNotes
clabeMXN18 digitsYour user transfers from a Mexican bank account.
cvuARS22 digitsYour user transfers from an Argentine bank or wallet account.
bre-bCOPA Bre-B key starting with @Your user pays the key from their Colombian banking app.
swiftReceivingAccountUSDAn object, see belowYour user, or someone paying them, sends a SWIFT transfer in USD.

clabe, cvu and bre-b are strings. The COP field is named bre-b, with a hyphen, so read it by key (for example info["bre-b"] in JavaScript) rather than as a plain property.

swiftReceivingAccount holds what the sender's bank asks for to send a SWIFT transfer:

FieldDescription
beneficiaryNameThe account holder: your user's KYC name, or the company's legal name.
bankNameThe receiving bank.
bicThe receiving bank's SWIFT/BIC code.
accountNumberThe account number to send to.
routingNumberThe receiving bank's ABA routing number. Some senders' banks ask for it next to the BIC.
bankAddressThe receiving bank's address: street1, street2, city, region, postalCode and country.

Reading the fields​

  • Read the field of the currency you need. clabe for MXN, cvu for ARS, bre-b for COP, swiftReceivingAccount for USD by SWIFT.
  • A field appears only for a currency that is unlocked. A currency that is not unlocked is left out of the response entirely: the field is not sent as an empty string or as null. The MXN, ARS and COP fields show up once the account's KYC or KYB for that currency is approved: KYC - MXN, KYC - ARS, KYC - COP, or KYB - MXN, KYB - ARS, KYB - COP for company accounts. swiftReceivingAccount shows up once Avenia enables SWIFT deposits for the account.
  • Read it again when a field is missing. Right after a currency is unlocked, its field can take a moment to show up. Call Account Info again rather than caching the missing value.
  • Show the value as it is. Don't reformat or trim it: your user's bank needs the exact detail.
  • Ignore fields you don't know. If fixed deposit details for other methods are added, they show up as new fields in Account Info, so an integration that reads only the fields it knows keeps working. The same goes for new fields inside swiftReceivingAccount.

What Happens When a Deposit Arrives​

  1. Your user sends MXN, ARS or COP to the clabe, cvu or bre-b detail, or a SWIFT transfer in USD to the swiftReceivingAccount.
  2. Avenia creates a ticket for the deposit by itself. It shows up in your tickets, and you receive the ticket webhooks for it, ending in TICKET-COMPLETE. See Webhook Events.
  3. The deposit is converted to USDC at Avenia's quote for that currency when it is processed, with the fees that apply to your account. See Fees in a quote.
  4. The USDC is credited to the INTERNAL balance of the account or sub-account the details belong to.

The rate is set when the deposit is processed, so the amount of USDC is known only then. Read it from the ticket.

These deposits are international transfers: once one is credited, you receive a TICKET-PURPOSE-CODE-REQUIRED webhook asking for its purpose code. The deposit is already credited by then. See When Avenia asks for the code afterwards.

USD by SWIFT​

  • The ticket of a SWIFT deposit has inputCurrency USD and inputPaymentMethod SWIFT. Its inputAmount is what reached the account, after any charges taken from the transfer on its way, so it can be less than what the sender sent.
  • The sender is compared with the account holder. SWIFT carries the sender's name, not a tax ID, so Avenia compares that name with the account holder's. A transfer from someone else is a third-party deposit and is priced as one. When the account doesn't accept third-party deposits, it is held for compliance review instead of being credited.
  • Only USD is received. A transfer in another currency is not credited to the account.

Limits​

Static deposits count against the account's monthly fiat-in limit for that currency and against its global limit, like any other deposit. See Limits.

A deposit that goes over the limit is not credited. For MXN, ARS and COP no ticket is created for it. An ARS deposit over the limit is sent back to the account that paid it. For an MXN or COP deposit over the limit, contact Avenia support with the deposit's details. A SWIFT deposit over the limit gets its ticket, which ends without the credit, and the money is sent back to the sender's bank.

Sandbox and Production​

SandboxProduction
DetailsTest details no real bank account can pay: a CLABE starting with 999999, a CVU starting with 0009999, a Bre-B key starting with @SBX, and a SWIFT account number starting with 9999The account's real details
MoneySimulated, no real transfer. A deposit to any of the details is simulated with an API call: see Simulate Static DepositReal transfers
Fields and flowSame as productionSame as sandbox

Don't hard-code the test values: read clabe, cvu, bre-b and swiftReceivingAccount from Account Info in every environment. Moving to production changes the values, not your integration.

Conclusion​

In this section, you have learned how to use static deposits:

  • ✅ Reading the details – the clabe, cvu, bre-b and swiftReceivingAccount fields of Account Info, for the main account or a sub-account.
  • ✅ Knowing what is unlocked – a field is present only once its currency is unlocked, or, for SWIFT, once Avenia enables it.
  • ✅ What a deposit does – it is credited as USDC through a ticket Avenia creates, within the account's limits.