Webhook Status Codes
Range | State ID | Name | Description | State Type | Shared with Merchant in Redirect? | Shared with Merchant in Callback? |
---|---|---|---|---|---|---|
1XXX | 1XXX range is for Transaction initialization with mPoint or PSP | |||||
1001 | Transaction Initialize | If the user left the payment on the payment selection page, then that transaction will be in the Initiate state. | Transaction State | ✅ | ||
1009 | Transaction Initialize with PSP | For an APM/ wallet payment, if the user left the payment process after the APM payment confirmation page or from the card selection page of the wallet, then the transaction will be Initialize with PSP state. | Transaction State | ✅ | ||
1041 | Payment Pending | |||||
2XXX | 2XXX range is for Authorization and Post Authorization | |||||
2000 | Payment Accepted | After the payment is completed successfully and the third-party provider confirms the same through the back-end calls, then the transaction moves into Authorize state. This state indicates that the transaction was successful. | Transaction State | ✅ | ✅ | |
2001 | Payment Captured | There are two type of capture process Auto Capture - After Authorization capture trigger automatically by CPD or PSP. In this case transaction move in capture state immediately after authorization. Manual Capture - Merchant capture transaction manually from Vision system. | Transaction State | ✅ | ✅ | |
2002 | Payment cancelled | Transaction State | ✅ | ✅ | ||
2003 | Payment Refunded | Transaction State | ✅ | ✅ | ||
2010 | Payment Reject/Fail | If the transaction is failed because of any reason then that transaction move in Reject or fail state. This state indicates Transaction is failed. | Transaction State | ✅ | ✅ | |
2011 | Payment Decline | For capture, refund, and cancel failures. Note: In the future, there will be a separate state for each operation failure. | Transaction State | ✅ | ✅ | |
2012 | Cancel Failed | ✅ | ||||
2013 | Refund Failed | |||||
2014 | Payment Request Failed | |||||
2015 | Payment Request Expired | |||||
2201 | Payment Partially Captured | |||||
2202 | Payment Partially Cancelled | |||||
2203 | Payment Partially Refunded | |||||
4XXX | 4XXX is for session states | |||||
4001 | Session created | Whenever any payment is create it will be in session created state. Any session remain in this state if None of the transaction within this session is successfully yet and session is not expired. If redirect request contain this state as session state means there no any successful transaction in session. Consumer service needs to check the state of individual transaction to detailed information of failure. Base on the failure reason and retry configuration, can retry the payment.` | Session State | |||
4010 | Session Expired | If a session is completed (failed/successful) within the configured time, then the session moves into the Session Expired state, and consumer service cannot perform any authorization against the same session. | Session State | ✅ | ||
4020 | Session Failed | If fraud is detected for any transaction within a session or if one of the transactions has failed and the payment retry is not configured for a client, then the session immediately moves to the Session Failed state. | Session State | ✅ | ||
4021 | Session Failed - Maximum Attempt | Session State | ✅ | |||
4030 | Session Completed | The entire payment amount is authorized/captured from one or multiple transactions and the session moves to the Session Completed state. After the session is completed, consumer service cannot perform more authorizations against the session. | Session State | ✅ | ||
4031 | Session Partially Completed | As soon as one of the transaction is authorized/captured successfully session move into partially completed state. | Session State | |||
4039 | Session Already Completed | Information State |
Updated 3 months ago