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.
Notifications are Payment type and Payment method agnostic and will be called for all transactions based on configured notification type. Transaction type is indicated by the transaction_type field in the notification.
Multiple notification channels can be configured and all will be triggered for each transaction based on configured notification type.
Select notification types corresponding to the Version of the API you are using, this API documentation is V1.

The use of a port number in the API Endpoint value is not allowed.

Notifications can be resent in the merchant portal by selecting transaction details 👁 for the applicable transaction and selecting 'Resend' for the applicable notification.

Request Paramters

Parameter	Description
transaction_id	Unique PayPaga assigned transaction identifier
status	New status for the transaction	Enum values: Approved - Payment provider successfully processed the transaction. Final successful state Declined - Payment provider declined the transaction during processing. Final failed state Error - Unexpected error during processing. Final failed state Failed - Unexpected error during processing. Final failed state Canceled - Payment provider cancelled the transaction. Final failed sate
merchant_id	Unique PayPaga assigned merchant identifier
transaction_type	Transaction type	Enum values: Payin - Pay In transaction Payout - Pay Out transaction
merchant_transaction_reference	Merchant supplied unique transaction identifier for correlation	Max length: 45 Pattern: ^[A-Za-z0-9-_]+
country_code	ISO 3166-1 Alpha 2 Country code where the transaction is being processed
currency	ISO 4217 alphabetic currency code of the transaction amount
payment_method_code	Payment method code
transaction_input	Original data provided by the merchant or end customer to PayPaga when initiating the payment
transaction_amount	Pay-In - Original transaction amount initiated expressed as a decimal amount in the currency major and minor unit
paid_amount	Pay-In - Amount actually paid by end customer expressed as a decimal amount in the currency major and minor unit
unsolicited_payment	Indicates whether the pay-in was automatically generated	Boolean: true if the transfer was received without a prior API-created transaction

PIX

{
"transaction_id": "20260813-1329-40cb-96b2-84e3d9deaa61",
"status": "Approved",
"merchant_id": "ea685a4e-eab4-4b3c-a42a-e012c076ea30",
"transaction_type": "Payin",
"merchant_transaction_reference": "fLqqCP2qHNlnNOsA",
"country_code": "BR",
"currency": "BRL",
"payment_method_code": "BNKTR",
"transaction_input": {
"document_number": "241.390.720-32",
"first_name": "First",
"last_name": "Last"
},
"transaction_amount": 58.83,
"paid_amount": 58.83,
"unsolicited_payment": false
}

Callback response:

Status code: 200
Body: Empty
Any other status code will be considered failed webhook request.

Retry Policy

PayPaga retries the notification using exponential backoff. The formula used is attempt ^ 4 + rand(±10%).

After all attempts have failed, a V1 Notification Failed event will be triggered to the configured channels with the payload.

To retrieve more details about the notified transaction, use the relevant Transaction Query API for the transaction type.