What is the Argentine CBU?
The Clave Bancaria Uniforme (CBU) is the unique identifier for bank accounts in Argentina, created by the Central Bank (BCRA) in 1991 to standardize electronic transfers. It consists of 22 numeric digits that encode bank, branch, and account information.
CBU revolutionized Argentina's banking system by enabling immediate transfers between different entities without bilateral agreements. Today it's mandatory for all bank accounts (savings, checking, salary accounts) and essential for automatic debits, salary deposits, and digital payments.
Structure: BBBBSSSCVVVVVVVVVVVVVC where BBBB is the bank code, SSS the branch, C the first check digit, V the account number (13 digits), and C the second check digit. This architecture enables offline validation, ideal for high-volume systems like Mercado Pago, utility debits, and online banking.
How the validation algorithm works
CBU implements a double verification system based on the modulo 10 algorithm (similar to Luhn but with specific weightings):
First verification (bank-branch block):
- Take the first 7 digits (BBBBSSS)
- Multiply by the fixed sequence: 7, 1, 3, 9, 7, 1, 3
- Sum products and calculate remainder when dividing by 10
- The check digit (position 8) must be (10 - remainder) mod 10
Second verification (account block):
- Take the 13 account digits + already validated check digit (positions 9-21)
- Multiply by: 3, 9, 7, 1, 3, 9, 7, 1, 3, 9, 7, 1, 3
- Same process: sum, remainder by 10, comparison with digit 22
This independent double checksum detects 99.8% of transcription errors and 100% of adjacent digit transposition errors. BCRA publishes the official algorithm in its Communication A 2779 regulation.
When and why to validate a CBU
CBU validation is critical in multiple daily financial operations in Argentina:
- Bank transfers: before initiating a transfer (immediate debit, transfer 3.0), validation avoids rejections that take 24-48 hours to reverse
- Vendor onboarding: companies must validate vendor CBUs for automatic payments, avoiding errors that create tax and accounting issues
- Automatic debits: services (telecom, streaming, cards) validate CBU before processing subscriptions to avoid bounces that penalize merchants
- Online banking and digital wallets: Mercado Pago, Ualá, Naranja X validate CBU in real-time when linking accounts to prevent fraud
According to BCRA data, over 2.4 billion transfers were processed in Argentina in 2023. Validating CBU before sending reduces reversal costs (typically $500-1000 per failed operation) and dramatically improves user experience.
Limitations and common mistakes
This validator checks the mathematical coherence of CBU, but cannot confirm operational aspects:
- Does not verify account existence: a CBU can be format-valid but not correspond to an active bank account
- Does not validate ownership: cannot confirm the CBU belongs to a specific person or company
- Does not detect closed accounts: if an account was closed, the CBU maintains its mathematical validity
- Does not verify judicial blocks: embargoes or inhibitions are not detectable by format validation
Common errors: confusing CBU with CVU (Virtual Uniform Key, used in digital wallets like Mercado Pago), copying CBU with spaces or hyphens that some systems reject, using test CBUs (like 0000003100000000000000) in production. For critical real-existence validations, use COELSA APIs (BCRA's electronic chamber) or banking account verification services that query the destination bank directly.