DEBIN

This guide explains how to integrate DEBIN, Argentina's official online transfer system, with the EBANX Direct API. DEBIN is a payment method regulated by the Central Bank of Argentina (BCRA) that enables merchants to initiate transfer requests which customers can authorize directly through their internet banking or mobile banking platforms. DEBIN supports transactions in both Argentine Pesos (ARS) and US Dollars (USD), with transactions only permitted between accounts of the same currency, operating 24/7 through Argentina's regulated payment infrastructure.

Requirements

• API credentials - Ensure you have your EBANX integration key. If not, complete the Merchant Signup Form.
• Familiarity with EBANX Direct - This setup follows the same general structure as other payment methods, with specific parameters for Argentine bank transfers. See EBANX Direct for more info.

How it works

DEBIN operates as a bank transfer request system that enables secure payments between bank accounts in Argentina. The payment flow involves creating a transfer request that customers authorize through their banking platform.

Here's how the process works when integrated with the EBANX API:

• Payment initiation - Customer selects DEBIN as their payment method during checkout and provides their CUIT (tax identification number) and CBU (bank account number) details.
• Transfer request creation - EBANX processes the payment request and generates a DEBIN transfer request in the Argentine banking system. The payment status becomes pending (PE) while awaiting customer authorization.
• Customer authorization - The customer receives a notification through their bank's internet banking platform or mobile app about the pending transfer request and can view the payment details including amount, merchant information, and due date. The customer then accepts or rejects the immediate debit request through their internet banking or mobile banking platform.
• Payment confirmation - Once the customer approves the transfer, EBANX receives confirmation from the banking system and updates the payment status to confirmed (CO). If the customer rejects the transfer or the due date expires, the status changes to canceled (CA).

Instructions

Follow the steps below.

1. Select your environment

   Select the appropriate environment for your integration. Use the sandbox environment for testing, or the production environment for live transactions. Use the URL for your HTTP requests based on your selection.

   SandboxProduction

   https://sandbox.ebanx.com/ws/direct

2. Create a DEBIN payment request

   DEBIN operates as an asynchronous bank transfer method, so you'll need to create a payment request that will be processed through the Argentine banking system. To initiate this request, call the ws/direct endpoint with the required parameters including the customer's banking information.

   Basic parameters:

   Parameter	Description	Required?
   operation	Set to request	Required
   integration_key	Your EBANX integration key	Required
   payment_type_code	Set to debin	Required
   country	Set to ar for Argentina	Required

   Customer data:

   Parameter	Description	Required?
   name	Customer name	Required
   email	Customer email	Required
   document	Customer's CUIT (Código Único de Identificación Tributaria) - tax identification number that must be valid within the Argentine tax system	Required

   Charge parameters:

   Parameter	Description	Required?
   merchant_payment_code	Unique merchant payment code	Required
   currency_code	Supported values ARS and USD	Required
   amount_total	Total amount to be charged	Required
   bank_details.account_number	Customer's CBU (Clave Bancaria Uniforme) - 22-digit bank account number that will be validated by the banking system	Required

3. Sample request

   Use the following example to initiate a DEBIN payment request.

   curl -X POST \
     --location 'https://sandbox.ebanx.com/ws/direct' \
     --header 'Content-Type: application/json' \
     --data '{
       "integration_key": "{{your_integration_key}}",
       "operation": "request",
       "payment": {
         "name": "{{customer_name}}",
         "email": "{{customer_email}}",
         "document_type": "CUIT",
         "document": "{{customer_document}}",
         "country": "ar",
         "payment_type_code": "debin",
         "bank_details": {
           "account_number": "{{customer_account_number}}"
         },
         "merchant_payment_code": "{{merchant_payment_code}}",
         "currency_code": "ARS",
         "amount_total": "1500.00"
       }
     }'

4. Sample response

   A successful request will return a response with the payment hash and initial status. The payment will remain in pending status until the customer authorizes the transfer.

   {
     "payment": {
       "hash": "{{payment_hash}}",
       "country": "ar",
       "merchant_payment_code": "{{merchant_payment_code}}",
       "order_number": "{{order_number}}",
       "status": "PE",
       "status_date": null,
       "open_date": "2024-12-06 20:18:45",
       "confirm_date": null,
       "transfer_date": null,
       "amount_br": "1500.00",
       "amount_ext": "1500.00",
       "amount_iof": "0.00",
       "currency_rate": "1.0000",
       "currency_ext": "ARS",
       "due_date": "2024-12-09",
       "instalments": "1",
       "payment_type_code": "debin",
       "pre_approved": false,
       "capture_available": null
     },
     "status": "SUCCESS"
   }

   Key response fields:

   The response includes several important fields that provide information about the payment request.

   • The hash field contains a unique identifier for tracking the payment throughout its lifecycle.
   • The due_date indicates when the transfer request will expire if not authorized by the customer.
   • The status field shows the current payment state, which will be "PE" (pending) initially and will change to "CO" (confirmed) or "CA" (canceled) based on customer action.
   
   
   At this stage, the payment will appear as pending (PE) in your

   EBANX Dashboardchevron_right

5. Monitor payment for status changes

   Asynchronous payment flow

   • DEBIN follows an asynchronous payment model where the initial request creates a pending payment that requires customer authorization.
   • The payment will remain in pending status while the customer has the opportunity to approve or reject the transfer through their banking platform. This process typically takes anywhere from a few minutes to days, depending on when the customer accesses their internet banking.

   Notifications

   • EBANX will send a notification whenever the payment status changes from pending to either confirmed or canceled.
   • Make sure your system is configured to receive and process these notifications properly, as they provide the definitive status update for DEBIN payments.
   Learn more about Payment Notificationschevron_right

   Status progression

   • The payment status will progress through the following states: initially "PE" (pending) when the transfer request is created, then either "CO" (confirmed) when the customer approves the transfer, or "CA" (canceled) if the customer rejects the transfer or the due date expires.
   • Once a payment reaches confirmed or canceled status, it cannot be changed.
   Learn more about Retrieving Payment Statuschevron_right

6. Congratulations!

   You have successfully integrated DEBIN.

   For more information, refer to the

   Direct API reference guidechevron_right

Resources

Use the following resources when testing in your sandbox environment.

API Reference

Click here to access detailed API documentation to integrate efficiently.

Click to explorechevron_right

Mock Customer Data

Click here to view mock customer data for testing and validating user flows.

Click to explorechevron_right

Error Codes

Click here to review common error codes to troubleshoot and resolve issues quickly.

Click to explorechevron_right

Still need help?

We hope this article was helpful. If you still have questions, you can explore the following options:

• Merchant support: Contact our support team at sales.engineering@ebanx.com for assistance.
• Not a partner yet? Please complete the Merchant Signup Form, and our commercial team will reach out to you.