Skip to content

Virtual accounts · Our flagship

Give every customer their own local account, with incoming payments reconciled automatically.

Issue local account numbers on demand and collect bank transfers — including high-value tickets — with every payment matched to the right customer, in real time.

Contact salesGo to our docs
  • Single or batch creation via API
  • Real-time webhooks, 24/7
  • Local and USD accounts where supported
Countries with local account formats
7
Pix key and IBAN too — the local identifier in each country
CLABE · CVU · CCI
Individual or batch account creation
API
On every incoming payment
Webhook

Why virtual accounts

Bank transfers without the manual matching

Transfers are the preferred way to pay large amounts in Latin America. Virtual accounts make them as easy to reconcile as a card payment.

  • One account per customer

    Assign a dedicated local account number to each payer, order or invoice, with no reference codes to type.

  • Automatic reconciliation

    Every incoming transfer is attributed to its virtual account, so your ledger updates without spreadsheets or manual review.

  • Real-time notifications

    Receive a webhook the moment funds arrive, with the payer details and amount, and trigger fulfillment instantly.

  • Built for high-value tickets

    Collect large B2B and cross-border payments that card limits and installment rules would otherwise block.

  • Scales with you

    Create accounts one by one or in batches through the API, and open new markets through configuration, not reintegration.

  • Local currency and USD

    Collect in local currency, and in USD where local rails allow: SPID in Mexico and USD accounts in Peru and Costa Rica.

Money flow

One account per customer, reconciled for you

Each customer pays into their own local account number, so every incoming transfer is matched to the right customer.

  1. 1

    Your platformLocalpayment:

    Create a virtual account

    A CLABE, CVU, Pix key or CCI number linked to your customer.

  2. 2

    LocalpaymentCustomer:

    Account details shown

    In your app, checkout or invoice.

  3. 3

    CustomerLocal rail / bank:

    Transfers from any bank

    A normal domestic transfer, with no integration on the payer’s side.

  4. 4

    Local rail / bankLocalpayment:

    Funds arrive

    The transfer is matched to the virtual account automatically.

  5. 5

    LocalpaymentYour platform:

    Webhook and report

    Customer, amount and reference arrive ready to reconcile.

Illustrative flow. Identifier formats depend on the country.

How it works

From account creation to credited funds

  1. 01

    Create the account

    Call the API to issue a virtual account for a customer, order or invoice in the target country — one by one or in batches.

  2. 02

    Share payment instructions

    Show the account number and payment instructions in your checkout, invoice or app.

  3. 03

    Customer transfers

    Your customer pays from their usual local bank app to the virtual account. Only electronic transfers are credited.

  4. 04

    Webhook and credit

    We match the transfer to the account, send a webhook with the confirmed amount and payer data, and credit your Localpayment balance.

Local formats

Seven countries, one API

Each account uses the format local banks already know, so payers transfer from their usual app.

  • Argentina

    Local format
    CVU (22 digits)
    Currency
    ARS
    Rail
    COELSA
    Good to know
    Payment-intent CVUs accept only the exact amount before expiry; one alias per account

  • Brazil

    Local format
    Account with a Pix key (email, phone or random)
    Currency
    BRL
    Rail
    Pix · TED
    Good to know
    The same account receives Pix and TED; Pix confirms in seconds, 24/7

  • Chile

    Local format
    Account number
    Currency
    CLP
    Rail
    Bank transfer (TEF)
    Good to know
    Real-time confirmation, 24/7

  • Colombia

    Local format
    Bre-B key
    Currency
    COP
    Rail
    Bre-B
    Good to know
    Instant account-to-account transfers, 24/7

  • Costa Rica

    Local format
    IBAN (CR + 20 digits)
    Currency
    CRC · USD
    Rail
    SINPE
    Good to know
    Separate accounts for colones and dollars

  • Mexico

    Local format
    CLABE (18 digits)
    Currency
    MXN · USD
    Rail
    SPEI · TEF · SPID
    Good to know
    SPEI in real time; TEF next business day; SPID in USD from company payers, on business days

  • Peru

    Local format
    CCI (20 digits)
    Currency
    PEN · USD
    Rail
    CCE
    Good to know
    Currency follows your Localpayment account configuration

Source: docs.localpayment.com. Formats, limits and availability can change; confirm them with your account manager.

Operations

Simplify daily reconciliation

Reports and APIs give finance teams an itemized view of every collection, matched to its virtual account and ready for your ERP.

  • Business Portal reports with XLS export
  • Balance, activity and balance-reconciliation APIs per account
  • Itemized per transaction, per account and per currency
  • Full control of payment status, 24/7
Explore reporting & reconciliation

Total balance

USD 4,971,203.18

▲ 8.3%
  • USDUS Dollar1,284,560.00+4.2%
  • BRLBrazilian Real3,420,118.40+12.8%
  • MXNMexican Peso8,905,332.10+6.1%
  • COPColombian Peso912,450,000+3.4%
  • ARSArgentine Peso248,901,220.55+9.7%

Assignment models

Assign accounts the way your business works

  • Per transaction

    A single-use account for each order or invoice, which can be deleted once paid. In Argentina, payment-intent CVUs also fix the exact amount and an expiry date.

  • Per submerchant

    One account per seller, branch or business unit, so payments are grouped by entity. Ideal for marketplaces.

  • Per user

    A permanent account each user reuses, for example to top up a wallet balance. In Argentina you can also set an alias on each CVU.

  • Omnibus

    One shared account for many payers, reconciled with the payer and tracking data in each webhook.

Use cases

Where virtual accounts shine

For developers

One call to create a virtual account

REST API with JSON requests, Bearer-token authentication and webhook notifications. Test every flow on Stage — including simulated incoming transfers — before going live.

  • Endpoint: Create a Virtual Account (POST /api/virtual-account)
  • Your own unique externalId on every account
  • Batch endpoint for bulk creation within one country
  • Payment simulator on Stage: POST /api/simulate/va
Virtual accounts guide
# Create a Virtual Account · POST /api/virtual-account
# Illustrative request — see docs.localpayment.com for the exact contract
curl -X POST https://api.stage.localpayment.com/api/virtual-account \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "externalId": "e7a1c3d5-0000-4000-8000-000000000123",
    "accountNumber": "<your-account-number>",
    "country": "MEX",
    "beneficiary": {
      "type": "COMPANY",
      "name": "Comercio Ejemplo S.A. de C.V.",
      "document": { "type": "RFC", "id": "CEJ200101AB1" },
      "address": {
        "street": "Av. Reforma",
        "number": "100",
        "city": "Ciudad de México",
        "state": "CDMX",
        "country": "Mexico"
      },
      "website": "https://comercio-ejemplo.example"
    }
  }'

Frequently asked questions

What is a virtual account?

A virtual account is a unique local account number linked to your Localpayment account. Transfers sent to it are automatically identified and attributed to the customer, order or invoice you assigned it to.

In which countries can I issue virtual accounts?

In seven countries: Argentina (CVU), Brazil (an account with a Pix key that receives Pix and TED), Chile (local account number), Colombia (Bre-B key), Costa Rica (IBAN, in CRC and USD), Mexico (CLABE over SPEI and TEF, plus USD via SPID) and Peru (CCI, in PEN and USD).

How fast are payments confirmed?

Most virtual accounts confirm in real time, 24/7, and a webhook fires as soon as the transfer is matched. The exceptions are in Mexico: TEF transfers confirm the next business day, and SPID (USD) runs on banking business days.

Can customers pay in cash into a virtual account?

No. Only electronic transfers are credited; cash deposits at branches or ATMs are not.

Can I use virtual accounts for large amounts?

Yes. Virtual accounts are designed for high-value tickets such as B2B invoices and cross-border payments, subject to local limits, regulation and your risk profile.

How do I reconcile incoming payments?

Each transfer is matched to its virtual account automatically. You receive a webhook in real time and can pull reports and balance-reconciliation data from the Business Portal or the API.

Can I close or reassign a virtual account?

Yes, in most countries: the API lets you disable, re-enable or delete an account, and creating a new one takes a single call. Available operations vary by country and rail — for example, Peru accounts cannot be deleted, and in Chile accounts are enabled or disabled through a support ticket.

What happens if a customer sends the wrong amount?

A standard virtual account accepts any transfer within the method’s limits, and the webhook reports the exact amount received, so you decide how to handle the difference — for example with a full refund through the API. In Argentina, a payment-intent CVU only confirms when the exact amount arrives before it expires.

Also on the same API

Start collecting with virtual accounts

Get Stage credentials at the start of the partnership, simulate incoming transfers and go live in weeks.

Contact salesRequest sandbox access

How can we help?

Download your copy

Leave your details and get the full edition instantly.