DEBIN (Argentina)
This payment solution is only available in Argentina
DEBIN is a payment method that means Immediate Debit, created by the Central Bank of Argentina, which utilizes a bank transfer payment methodology. This process essentially involves a transaction where funds are deducted from a CBU account in real time at the moment the payment request is generated, meaning the amount is immediately withdrawn from the sender's account.
It is a simple procedure that works as follows: the customer is given the opportunity to generate a payment request with the amount and details of the customer's account. This request is sent directly to the user with a CBU account via a webhook, ensuring that they receive an immediate notification in their banking app. From there, they can review the transaction and make an informed decision to approve or reject it with a single click. That's it—no cards, no cash, no wallet. Everything is done digitally.
The Immediate Debit operates 24/7.
The payment will only be considered complete once the customer accepts it in their banking application, or it will be rejected if the customer declines it. Otherwise, the payment will move to an expired status.
The payment request can only be made to CBU accounts. These account numbers are distinguished by the fact that their first three digits do not begin with zero.
A wire transfer payment order expires by default 2 days from the date of creation.
This payment solution is only available in Argentina
Money request
POST
https://api.stage.localpayment.com/api/payin
Headers
Authorization*
string
Mandatory. JWT token in format Bearer eyJ0...
. For more information about authentication, please refer to Authentication
Request Body
paymentMethod*
OBJECT
Mandatory. Payment method details
paymentMethod.type*
string
Mandatory.wallet
paymentMethod.code*
string
Mandatory. Select among the codes available in each country here NOTE: yment method code might affect the collection currency in bimonetary countries. For more info, see the side note on currency
field.
paymentMethod.flow*
string
Mandatory. The payment method data could be embeded in the API request (DIRECT)
or collected via an aditional form or plugin (REDIRECT)
. Currently, only DIRECT
flow is allowed.
externalId*
string
Mandatory. An ID that is meaningful to you and your system. It must be unique and alphanumeric, no characters allowed.
amount*
number
Mandatory. Amount to charge to your end user. For GTQ, use 2 decimal places separated by a dot.
currency*
string
Mandatory. The currency in which the amount is expressed. It could be A) the local currency of the selected country or B) the account's currency. If A), the amount will be charged to the customer's cash payment method. If B) and it differs from the local currency, the amount specified will be credited to your account and Localpayment will perform a Foreign Exchange operation to collect the amount expressed in local currency. In bimonetary countries, paymentMethod.code resolves possible ambiguity: the payment will be executed in the currency of that specific payment method network. e.i.: SPID (USD); SPEI (MXN)
accountNumber*
string
Mandatory. Your Localpayment account number in which the amount will be credited.
conceptCode*
string
Mandatory. Choose the suitable concept code from our Concept Code List. Based on our experience, the most usual are 0039 (remittances) and 0040 (corporate payments).
comment
string
Optional. A comment related to the transaction. It should be something meaningful to your business.
merchant*
OBJECT
Mandatory. Party Object.
merchant.type*
string
Mandatory. Possible value: COMPANY
merchant.name*
string
Mandatory. Name of business
payer*
OBJECT
Mandatory. Party Object. Information related to the payer.
type*
string
Mandatory. Possible values: COMPANY
, INDIVIDUAL
name*
string
Mandatory. Individual first name / company name
lastName
string
Mandatory for individuals / Ignored for companies.
document.id*
string
Mandatory. Identity document Id. Usually numbers or combination of numbers and letters.
userReference
string
Optional. Username or id in your platform.
bank*
OBJECT
Mandatory. Party Object. Payer account data.
bank.name
string
Bank Name
bank.account*
OBJECT
Mandatory. Party Object. Payer account information.
bank.account.number*
string
Mandatory. Payer account number
string
Mandatory
phone
OBJECT
Mandatory. Party Object. Contact phone number
phone.countryCode
string
Mandadatory. Possible values: gt
phone.areaCode
string
Mandatory. Country Area Code
phone.number
string
Mandatory. Phone number registered in the application
birthdate
string
Optional. Individual birthdate / company incorporation date. ISO 8601 format (YYYY-MM-DD)
nationality
string
Optional
address
OBJECT
Optional. Party Object. Contact address
address.street
string
Optional
address.number
string
Optional
address.city
string
Optional
address.state
string
Optional
address.country
string
Optional
address.comment
string
Optional. Additional info, such as floor or apartment number.
intermediaries
array
Optional. Array of Party objects. It represents others parties in the payment chain because of the end user is not your direct customer. Take into account the array sequence: your client should be the first element, the client of your client should be the second and so on, until there are no more intermediaries.
commercialData
OBJECT
Mandatory. Party Object. Extra information related to the goods or services traded.
item.id
string
Mandatory. Item ID
items.quantity
number
Mandatory. Item quantity
items.description
string
Mandatory. Item description
item.title
string
Mandatory. Item title
item.unitPrice
number
Mandatory.Unit price
Examples: Money request
To create a payment order through the LP api, examples of the request body are detailed below.
Check the Payin Status Codes
PayinLast updated