Important Considerations

Instant Transfers in Argentina allow end users to send funds directly to a CVU/CBU, both inside and outside of a checkout flow.
This behavior is expected and inherent to Instant Transfers (CBU/CVU) in Argentina.
PayPaga has built a transaction matching logic to cover the majority of use cases. However, there are known situations where an incoming payment cannot be matched to an existing pay-in previously created via the API.
Matching logic is configured on a per account basis and dependant on orchestration configuration.

---

Unmatched or Unplanned Payments

You may receive incoming transfers that cannot be matched to a previously created 'Pending' transaction in the following situations:

Scenario	Description
Unmatched payer	The payment is initiated by the expected customer, but the payer identification (CUIL/CUIT) does not match the one provided when the transaction was created
Unsolicited payment	The end user performs a transfer without creating a prior transaction, sending funds directly to your assigned CVU/CBU
Expired transaction	A transaction was created but expired before the transfer was completed
Third-party payment	The payment is initiated by a different person or legal entity than the customer defined in the original transaction, even if the amount or reference matches

Important
You cannot currently reject or automatically refund unsolicited payments.
Once funds are received in your assigned CVU/CBU, the pay-in is considered approved and reflected accordingly.

---

System Behavior for Unmatched Payments

When an incoming transfer cannot be matched to an existing pending transaction (including cases where a previous transaction exists but is already expired), the system behaves as follows:

Step	Behavior
Pay-in creation	The system automatically creates a new pay-in
Approval	The pay-in is instantly approved based on the received funds
Notification	You are notified via your configured webhook notifications

As a result, you may receive a successful pay-in notification for a transaction that you did not explicitly create beforehand via the API.

---

What You Should Consider

If you integrate Instant Transfers (CVU/CBU), you should take the following into account:

• Do not assume that every approved pay-in originates from a transaction you previously created.
• Always rely on webhooks and reports as your source of truth for successful payments.
• Ensure your system is capable of handling unsolicited/third-party payments. Note that unsolicited/third-party payments are not supported for Forex and Crypto industries.

This behavior is expected and inherent to Instant Transfers (CBU/CVU) in Argentina and must be considered as part of your integration logic.

---

Required Fields

Field	Description	Validation
first_name	First name	Length >= 2 <= 50, RegEx ^\p{L}*(?:[ '-]\p{L}+)*$
last_name	Last name	Length >= 2 <= 50, RegEx ^\p{L}*(?:[ '-]\p{L}+)*$
document_number	CUIL/CUIT	RegEx ^(20|23|24|25|26|27|30|33|34)(-?\d{8}-?\d|\d{8}\d)$ Must be valid CUIL/CUIT (length/format/check digit)

Optional Fields

Field	Description	Validation
bank_code	Bank identifier code	One of the bank identifier codes listed below

Bank Identifier Code

Name	Code
Mercado Pago	mercado_pago
Ualá	uala
Naranja X	naranja_x
Personal Pay	personal_pay
Brubank	brubank
Prex	prex
Lemon	lemon
Galicia	galicia
Santander	santander
BBVA	bbva
Banco Provincia	banco_provincia
Banco Nación	banco_nacion
ICBC	icbc
Macro	macro

User Experience

Logos for primary banks can be displayed to enhance the user experience as per the PayPaga demonstration site.
Logos can be sourced from the Assets in the documentation Appendix

Expiry

Initiated transactions that are not completed, transition to an Expired state after 72 hours.
The instructions to the payer encourage payment within 3 hours.

Response Fields

Field	Description
reference	Payment reference code generated for this transaction. Including it in the transfer's payment concept can help match the incoming payment, though matching is primarily done via the payer's document number (CUIL/CUIT).
bank_account	CVU/CBU account number the payer must transfer the funds to.
beneficiary	Name of the receiving account holder (Razón Social), when configured for your account.
alias	Alias of the receiving CVU/CBU account, when configured for your account.

Payment Instructions

1. Open your banking app or digital wallet.
2. Look for the "Transfer to CVU/CBU" option and paste the CVU/CBU number provided in the response.
3. Confirm the payment details and complete the transfer.

Important
The CUIL/CUIT of the person initiating the payment must match the CUIL/CUIT registered with the bank, otherwise the payment will not go through.
Transfer the exact amount to the provided CVU/CBU.

Spanish:

1. Abre tu app bancaria o billetera digital.
2. Busca la opción "Transferir a CVU/CBU" y pega el número de CVU/CBU.
3. Confirma los datos del pago y completa la transferencia.

Importante
El CUIL/CUIT de quien inicia el pago debe coincidir con el CUIL/CUIT del banco, de lo contrario, el pago no se efectuará.
Transfiere el importe exacto al CVU/CBU proporcionado.

When configured for your account, the response may also include beneficiary (receiving account holder name / Razón Social) and alias (receiving account alias) to help the payer verify the destination account.