Payment Notifications
Each time a payment is completed, a notification is sent to the URL configured for such purposes in the PAYMENTS MODULES.
Payment notifications can have the following two result values:
| Result | Description |
|---|---|
| ok | Payment was succesfully processed |
| ko | The payment could not be processed correctly or has been left pending. |
Incorrect payments
The reasons can be diverse but the most common are that the user has not completed the payment process, that he does not have enough balance to make the payment, that he has entered incorrect data in the payment form or that the payment provider has rejected the request.
Pending payments
When a payment is pending, a new notification with the same access code of the initial notification can be received, but with result "ok", in case the payment becomes successful.
Reference of parameters that are sent in notifications:
| Parameter | Type | Description |
|---|---|---|
| uid | numeric | Value that identifies the user account |
| mid | numeric | Value that identifies the module referenced in the access |
| country | text | Country Code (ISO 3166-2) |
| price | numeric | Price paid by the user |
| currency | text | Payment currency code (example: USD) |
| code | text | Payment identification code |
| Mail of the user who paid | ||
| result | text | Transaction Result Value (ok, ko) |
| ucode | text | Text defined by user account |
| type | text | Payment method used in the transaction |
| mode | text | If this parameter is received, the payment was made from the test environment. Only valid value is "debug". |