PayPaga
  1. Transactions Status Notification
PayPaga
  • Introduction
    • Introduction
    • API Reference
    • 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 Out - Direct API Integration
    • Pay Out - Direct API Integration
    • Pay Out - Query Transactions
    • Pay Out - Payment Processing
  • Pay Out - Examples
    • Pay Out - Brazil
    • Pay Out - Mexico
    • Pay Out - Argentina (V2)
    • Pay Out - Colombia (V2)
    • Pay Out - Ecuador (V2)
    • Pay Out - Guatemala (V2)
    • Pay Out - Peru (V2)
  • Transactions Status Notification
    • Transactions Status Notification
  • Query Balance
    • Query Balance
  • Appendix
    • Transaction Status Definitions and Lifecycle
  1. Transactions Status Notification

Transactions Status Notification

The PayPaga platform provides Transaction Status Notifications that can be sent to a merchant defined API URL and/or to an email address list. Configuration of transaction status notifications is performed via the Developer's section of the Merchant Portal for each environment. The configuration uses a JSON format, the following is an example:
{
  "notificationActivation": {
    "email": true,
    "api": false
  },
  "apiEndpoint": "https://your-api-endpoint.com/your-webhook",
  "failedWebhookEmailList": [
    "user1@example.com",
    "user2@example.com"
  ],
  "notificationEmailList": [
    "user3@example.com",
    "user4@example.com"
  ]
}
WARNING
The use of a port number in the apiEndpoint value is not allowed.
The payload of the API call and email is as follows:
{
  "transaction_id": "XXXXX-XXXX-XXXX-XXXXX",
  "status": "Cmpleted",
  "merchant_id": "XXXXX-XXXX-XXXX-XXXXX",
  "transaction_type": "payin or payout",  
  "merchant_transaction_reference": "XXXXXXXX-XXXX-XXX"
}
Request Paramters
ParameterDescription
transaction_idUnique PayPaga assigned transaction identifier
statusNew status for the transaction
statusNew status for the transactionEnum values:
ApprovedPayment provider successfully processed the transaction. Final successful state
DeclinedPayment provider declined the transaction during processing. Final failed state
ErrorUnexpected error during processing. Final failed state
CanceledPayment provider cancelled the transaction. Final failed sate
transaction_typeTransaction typeEnum values:
PayinPay In transaction
PayoutPay Out transaction
merchant_transaction_referenceMerchant supplied unique transaction identifier for correlation
  • Max length: 45
  • Pattern: ^[A-Za-z0-9-_]+
RESPONSE:
Status code: 200
Body: Empty
Any other status code will be considered failed webhook request.
Request attempts:
Paypaga will attempt the notification request 3 times. If all attempts fail an email will be sent to the configured failedWebhookEmailList email list.
The first retry will occur after 30 seconds with backoff rate multiplier duplicating timeout for every attempt , for example:
First attempt FAILED
30 seconds later second attempt FAILED
60 seconds later third attempt FAILED, send email with Payload to failedWebhookEmailList
In order to retrieve more details about the notified transaction use the applicable ‘Transaction Query’ API relevant to the transaction type.
Previous
Pay Out - Peru (V2)
Next
Query Balance
Built with