PayPaga
  1. Pay In - Argentina
PayPaga
  • Introduction
    • Introduction
    • API Reference
    • Environments
    • Payment methods
    • Errors
    • Standard Codes and Values
  • Authorization
    • Authorization
    • OAuth 2.0 Token Generation
  • Pay In - Direct API Integration
    • Pay In - Direct API Integration
    • Pay In - Payment Options
    • Pay In - Payment Processing
    • Pay In - Query Transactions
  • Pay In - PayURL Integration
    • Pay In - PayURL Integration
    • Pay In - Create PayURL
  • Pay In - Examples
    • Pay In - Argentina
      • Pay In - Instant Transfers
        POST
    • Pay In - Brazil
      • Pay In - PIX
    • Pay In - Chile
      • Pay In - Bank Transfer
    • Pay In - Colombia
      • Pay In - Dale
      • Pay In - Daviplata
      • Pay In - Efecty
      • Pay In - Gana
      • Pay In - Movii
      • Pay In - Nequi
      • Pay In - PSE
      • Pay In - RappiPay
      • Pay In - ReFacil
      • Pay In - Susuerte
      • Pay In - Western Union
    • Pay In - Ecuador
      • Pay In - Bemóvil
      • Pay In - Deuna
      • Pay In - Mi Negocio Efectivo
      • Pay In - Omniswitch
      • Pay In - Banco Pichincha
      • Pay In - Rapi Activo
      • Pay In - Western Union
    • Pay In - El Salvador
      • Pay In - Banco Agrícola
      • Pay In - Banco Cuscatlán
      • Pay In - Puntoxpress
    • Pay In - Guatemala
      • Pay In - BAM Efectivo
      • Pay In - BAM Transferencia
      • Pay In - Banco Industrial
      • Pay In - Akisi Pronet
    • Pay In - Mexico
      • Pay In - Pay With Cash
      • Pay In - SPEI
    • Pay In - Peru
      • Pay In - BBVA
      • Pay In - BCP
      • Pay In - BCP Efectivo
      • Pay In - Cell Power
      • Pay In - KasNet
      • Pay In - QR Interoperable
      • Pay In - Plin
      • Pay In - Yape
  • Pay Out - Direct API Integration
    • Pay Out - Direct API Integration
    • Pay Out - Query Transactions
    • Pay Out - Payment Processing
  • Pay Out - Examples
    • Pay Out - Argentina
    • Pay Out - Brazil
    • Pay Out - Chile
    • Pay Out - Colombia
    • Pay Out - Ecuador
    • Pay Out - Guatemala
    • Pay Out - Mexico
    • Pay Out - Peru
  • Transactions Status Notification
    • Transactions Status Notification
    • Pay In - Instant Transfers
  • Query Balance
    • Query Balance
  • Appendix
    • Transaction Status Definitions and Lifecycle
    • Assets
  1. Pay In - Argentina

Pay In - Instant Transfers

POST
/payment

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.


Unmatched or Unplanned Payments

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

ScenarioDescription
Unmatched payerThe 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 paymentThe end user performs a transfer without creating a prior transaction, sending funds directly to your assigned CVU/CBU
Expired transactionA transaction was created but expired before the transfer was completed
Third-party paymentThe 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:

StepBehavior
Pay-in creationThe system automatically creates a new pay-in
ApprovalThe pay-in is instantly approved based on the received funds
NotificationYou 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.
  • Make sure your internal systems can correctly handle unsolicited payments.

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

FieldDescriptionValidation
first_nameFirst nameLength >= 2 <= 50, RegEx ^\p{L}*(?:[ '-]\p{L}+)*$
last_nameLast nameLength >= 2 <= 50, RegEx ^\p{L}*(?:[ '-]\p{L}+)*$
document_numberCUIL/CUITRegEx ^(20|23|24|25|26|27|30|33|34)(-?\d{8}-?\d|\d{8}\d)$ Must be valid CUIL/CUIT

Optional Fields

FieldDescriptionValidation
bank_codeBank identifier codeOne of the bank identifier codes listed below

Bank Identifier Code

NameCode
Mercado Pagomercado_pago
Ualáuala
Naranja Xnaranja_x
Personal Paypersonal_pay
Brubankbrubank
Prexprex
Lemonlemon
Galiciagalicia
Santandersantander
BBVAbbva
Banco Provinciabanco_provincia
Banco Naciónbanco_nacion
ICBCicbc
Macromacro

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.

Request

Header Params

Body Params application/json

Examples

Responses

🟢200Success
application/json
Body

🟠400Bad Request
🔴500Server Error
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request POST '/payment' \
--header 'Authorization;' \
--header 'Content-Type: application/json' \
--data-raw '{
  "transaction_id": "20251028-1319-425e-b6e6-6ef9eb963110",
  "payment_method_code": "cvu",
  "country_code": "AR",
  "currency": "ARS",
  "transaction_total": 1000,
  "merchant_transaction_reference": "abc4561698162696828",
  "transaction_fields": [
    {
      "name": "first_name",
      "value": "Barão"
    },
    {
      "name": "last_name",
      "value": "Praça"
    },
    {
      "name": "document_number",
      "value": "20084908488"
    }
  ]
}'
Response Response Example
200 - Success
{
  "transaction_id": "20251028-1319-425e-b6e6-6ef9eb963110",
  "transaction_payment_mode": "ASYNCHRONOUS",
  "payment_method_reference": "129916",
  "message": "Transaction Successfully",
  "version": "0.1",
  "next_steps_detail_instructions": [
    {
      "type": "label",
      "key": "payment_method",
      "label": "Metodo de Pago",
      "description": "cvu"
    },
    {
      "type": "label",
      "key": "main_instructions",
      "label": "Instrucciones",
      "description": "Transfiere el monto exacto al CVU/CBU proporcionado para completar tu pago."
    },
    {
      "type": "label",
      "key": "reference",
      "label": "Referencia",
      "description": "WDCMRMNPBE4CG"
    },
    {
      "type": "label",
      "key": "bank_account",
      "label": "CVU/CBU",
      "description": "50053763000179"
    }
  ]
}
Previous
Pay In - Examples
Next
Pay In - PIX
Built with