PayPaga
  1. Transactions Status Notification
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
    • 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. Transactions Status Notification

Pay In - Instant Transfers

Note
For Instant Transfers (CVU/CBU), callbacks are the source of truth for payment approval.
An Approved status does not guarantee that the paid amount matches the originally requested amount, nor that the transaction was previously created in our system.
Callback Request Parameters
ParameterDescriptionDetails
transaction_idUnique PayPaga-assigned transaction identifier—
statusCurrent transaction statusEnum values:
- Approved — Payment successfully processed (final success state)
- Declined — Payment declined during processing (final failure state)
- Error — Unexpected processing error (final failure state)
- Canceled — Transaction canceled by the provider (final failure state)
transaction_typeTransaction typeEnum values:
- Payin — Pay-in transaction
- Payout — Pay-out transaction
merchant_transaction_referenceMerchant-defined transaction identifier used for correlation- Max length: 45
- Pattern: ^[A-Za-z0-9-_]+
transaction_inputOriginal data provided by the merchant or end customer to PayPaga when initiating the payment
Examples
—
processing_outputData verified during payment processing
Examples
—
transaction_amountAmount originally requestedFor unsolicited pay-ins, this value is system-defined and matches the paid_amount field
paid_amountAmount effectively receivedFunds credited to the assigned CVU/CBU
unsolicited_paymentIndicates whether the pay-in was automatically generatedtrue if the transfer was received without a prior API-created transaction

Callback Examples#

Underpayment
Overpayment
Unsolicited Payment
{
    "transaction_id": "20250516-1036-4c6e-9340-1d7769e556ae",
    "status": "Approved",
    "merchant_id": "50249f9c-2e0b-4d6a-bd44-0a9207b508dc",
    "transaction_type": "payin",
    "merchant_transaction_reference": "XXXXXXXX-XXXX-XXX",
    "country_code": "AR",
    "currency": "ARS",
    "payment_method_code": "CVU",
    "transaction_input": {
        "document_number": "20123456786",
        "first_name": "Jon",
        "last_name": "Snow",
        "bank_code": "mercado_pago"
    },
    "processing_output": {
        "account_number": "5111184511100013648681",
        "document_number": "20123456786",
        "first_name": "Jon",
        "last_name": "Snow"
    },
    "transaction_amount": 1000,
    "paid_amount": 900,
    "unsolicited_payment": false
}
Callback Response
Status code: 200
Body: empty
Any other status code is treated as a failed webhook request.
Retry Policy
PayPaga attempts the notification up to 3 times. If all attempts fail, an email is sent to the configured failedWebhookEmailList with the payload.
The first retry occurs after 30 seconds. Each subsequent attempt doubles the wait time. Example:
First attempt: failed
30 seconds later: second attempt failed
60 seconds later: third attempt failed, email sent to failedWebhookEmailList with the payload
To retrieve more details about the notified transaction, use the relevant Transaction Query API for the transaction type.
Previous
Transactions Status Notification
Next
Query Balance
Built with