Skip to content

Payment methods · Argentina

Debin in Argentina: collect with a debit request

Let your customers pay straight from their bank account. You create the request, they approve it, and the result reaches your system by webhook.

  • Bank redirect
  • Argentina
  • Pay-in

Key facts

Pull payments in Argentina

Figures published by the BCRA and the World Bank.

What it is

Pay from the bank account, with the payer’s approval

Debin is an Argentine payment method based on a debit request. Your business creates the request through Localpayment, the payer reviews it and approves it from their bank, and the payment is confirmed asynchronously. The request expires after 2 days if it is not approved.

  • Debit request approved by the payer from their bank
  • Request expires after 2 days
  • Final status delivered by signed webhook

How it works

How a Debin payment works

Actors and steps follow the documented flow. The final status always arrives by signed webhook.

  1. 1

    Your businessLocalpayment:

    Debit request

    POST /api/payin/ with country, currency, amount and payer data. The response confirms the debit request was created and is waiting for the payer. Status 100 (INPROGRESS). The request expires after 2 days.

  2. 2

    Bank · DebinCustomer:

    Bank notification

    The payer’s bank shows the pending debit request in online banking or the bank app.

  3. 3

    CustomerBank · Debin:

    Payer approves

    The payer reviews the debit request in their bank and approves it.

  4. 4

    LocalpaymentYour business:

    Webhook

    Localpayment receives the confirmation and updates the transaction. Signed with HMAC-SHA256 (x-Signature). Status 200 means completed; deduplicate on externalId.

Simplified diagram. Timing depends on the rail and the bank; see the key facts below.

How it works

See Debin in action

A simplified, fictitious walkthrough. Names and amounts are examples.

  1. 1Comercio EjemploThe customer picks Debin to pay ARS 45,000.00.
  2. 2Banco EjemploThe payer reviews ARS 45,000.00 and approves in their bank or wallet app.
  3. 3Payment confirmedYour system receives the signed webhook and releases the order.

Key facts

Debin: key facts

  • Country

    Detail
    🇦🇷 Argentina
  • Currency

    Detail
    ARS
  • Direction

    Detail
    Pay-in only
  • Debin

    Detail
    Asynchronous, confirmed by webhook · ARS 1 – 10,000,000
  • Flow

    Detail
    Payer approves the debit request in their bank

Taken from the Localpayment documentation for each country. Limits and availability can change; confirm them with your account manager.

Consumer experience

What your customer sees with Debin

Authorization, limits and refunds as documented on docs.localpayment.com. Limits are shown only where the documentation states them.

  • How the customer authorizes

    The customer enters their CBU (bank account; CVU wallets are not accepted) at your checkout. A real-time request appears in their bank app, where they review the amount and approve. Declining rejects the pay-in; without a response it expires two days after creation.

  • Documented limits

    Debin (Pay-in): ARS 1 – 10,000,000. Per transaction, as published in the documentation; contractual limits may differ.

  • Refunds and returns

    A completed pay-in can be refunded with PATCH /api/payin/{externalId}/refund. Only full refunds are supported; the money goes back to a bank account of the payer and the transaction ends in status 902 (REFUNDED). While a payment is still pending it can be canceled instead.

Integration checklist

Go live with Debin in five steps

The same sequence for every rail. Watch the animated checkout for this country before you build.

  1. Get Stage credentials

    Request access, receive sandbox credentials and obtain a JWT with POST /api/token/.

  2. Create the pay-in

    POST /api/payin/ with the Localpayment code from the key facts table, ISO-3 country, currency, amount and payer data.

  3. Show the instructions

    Render the QR, code, redirect or account details from the response and respect the expiration date.

  4. Verify the webhook

    Validate x-Signature (HMAC-SHA256), release the order on status 200 and deduplicate on externalId.

  5. Watch the animated checkout

    Every method of this country, screen by screen, in the checkout experiences gallery.

History

How Debin came to be

Source: Banco Central de la República Argentina (BCRA), Informe de Pagos Minoristas Anual 2025.

  1. The BCRA creates Debin

    The central bank defines the Débito Inmediato: a payee requests a debit and the payer approves it from their own bank, in real time.

  2. Live across the banking system

    Banks roll out Debin in home banking and mobile apps, making it the first immediate pull instrument in Argentina.

  3. Part of Transferencias 3.0

    Debin becomes the pull leg of the interoperable immediate-payments framework alongside push transfers and QR by transfer.

  4. 471 million pull transfers

    Immediate pull transfers reach 470.9 million operations in the year, while immediate payments account for 64% of retail operations.

Why Localpayment

Why use Debin with Localpayment

  • One API for pay-ins and payouts

    Debin runs on the same API as every other method: POST /api/payin/ to collect, POST /api/payout/ to pay out, and new markets by configuration.

  • Webhook status on every transaction

    Every status change is pushed to your endpoint, signed with HMAC-SHA256, so you can verify and automate.

  • Reconciliation in the Business Portal

    Match every transaction through your externalId and our internalId, with Business Portal reports and balance APIs.

FAQ

Debin: frequently asked questions

How does a Debin payment work?

You create a debit request through Localpayment and the payer approves it from their bank. Confirmation is asynchronous, so the final status reaches you by signed webhook and your order flow should rely on that notification.

How long is a Debin request valid?

A Debin request expires after 2 days. If the payer has not approved it by then, the payment is not completed and you can create a new request.

Which code and limits apply?

Debin uses Localpayment code 1040 in Argentina. See the key facts table above for the documented details, and confirm limits and availability for your account with your account manager.

Why does the documentation only accept CBU accounts?

Debin requests are routed to banks. A CBU identifies a bank account and never starts with three zeros; CVU wallet accounts are not eligible for this method, so point wallet users to QR or CVU transfers instead.

How long does the customer have to approve?

Two days from creation. Until then the pay-in stays in 100 (INPROGRESS); if the customer declines it is rejected, and if nothing happens it expires.

Can I refund a Debin payment?

Yes, in full, with PATCH /api/payin/{externalId}/refund on a completed transaction. The pay-in ends in 902 (REFUNDED); partial refunds are not supported.

Is Debin suitable for recurring charges?

Each Debin is an individual request the customer approves in their bank. For recurring collection, talk to sales about direct debit availability in Argentina.

Add Debin to your payments

Tell us your markets and volumes. We start you on Stage (sandbox) credentials and guide you to go-live.

How can we help?

Download your copy

Leave your details and get the full edition instantly.