Transaction Call Back Request
10. Transaction Call Back Request
The transaction status along with additional transaction information is posted to the callback URL configured for a merchant. There are two callback requests posted to the URL where the status codes indicate the following:
Code |
Description |
Invalid amount |
For example, 0.01. |
Missing mandatory request field |
For example, element 'card': The attribute 'type-id' is required but missing. |
The following parameters are sent in the callback:
Field |
Mandatory |
Description |
mpoint-id |
Yes |
This is the transaction/@id generated during initialize step. |
session-id |
Yes |
Internal session ID. |
orderid |
Yes |
This is the transaction/@order-no in the initialize request, like PNR. |
status |
Yes |
Transaction status code indicates successful or failure. |
mobile |
Yes |
If present in the transaction requests, same will be returned. |
amount |
Yes |
Transaction amount. |
Fee |
Yes |
Default is 0. |
currency |
Yes |
Transaction code. |
language |
Yes |
If present in the transaction requests, same will be returned. |
operator |
Yes |
If present in the transaction requests, same will be returned. |
Note: For details about transaction call back, refer to the Velocity Callback Request to the Merchant Integration Guide.
Updated 6 months ago