Field Codes and Message Formats
Resources and details referenced.
Parameter Values
HMAC - Message Authentication Code
Message Authentication Code
The Message Authentication Code (hmac
) is calculated by creating a SHA512 hash comprising the following input fields in the listed order:
Parameter | Required |
---|---|
clientid | Yes |
orderid | Yes |
amount | Yes |
country | Yes |
mobile | No |
mobile-country | No |
No | |
deviceid | No |
salt | Yes |
FX - Exchange Service ID
Exchange Service ID
The table below shows the type of exchange services that can be applied to a transaction (used in service_type_id
).
ID (XY) | Service (X) | Opt/Not Opt (Y) |
---|---|---|
11 | DCC | Opt |
12 | DCC | Not opt |
21 | MCP | Opt |
22 | MCP | Not opt |
31 | External MCP | Opt |
32 | External MCP | Not opt |
41 | PCC | Opt |
42 | PCC | Not opt |
Response Codes
Fraud Status Codes
Fraud Status Codes
The following table lists status codes that can be returned in the redirect from HPP against fraud_status_code
.
Code | Type | Description |
---|---|---|
3010 | Pre-Fraud Check Initiated | Pre-Fraud Check Initiated. |
3011 | Pre-screening result - Accepted | The pre-auth fraud check was “accepted” and no further fraud screening will be done. |
3012 | Pre-screening fraud service unavailable | System error from fraud check service. |
3013 | Pre-screening result - Unknown | An unknown error. |
3014 | Pre-Screening fraud Result - Review | The fraud check was REVIEW. |
3015 | Pre-screening result - Rejected | The pre-auth fraud check service was in REJECTED and no further payment processing will be done. |
3016 | Pre-screening Connection Failed - Rejected | Pre-screening connection failed – rejected. |
3100 | Post Fraud Check required | Post fraud check required. |
3111 | Post-screening Result - Accepted | The post-auth fraud check was ACCEPTED. |
3112 | Post-screening Fraud Service Unavailable | System error from fraud check service and therefore, manual review will be required.The payment will not be refunded or cancelled. |
3113 | Post-Screening Result - Unknown | This state indicates an unknown error. |
3114 | Post-screening Fraud Result - Review | The fraud check was REVIEW and hence manual Review will be required.The payment will not be refunded or cancelled. |
3115 | Post-screening Result - Rejected | The fraud check was REJECTED. The payment will be refunded or cancelled. |
3116 | Post-screening Connection Failed | Velocity could not connect to fraud check service and therefore, manual review will be required. The payment will not be refunded or cancelled. |
Hosted Payment Page -Transaction Status Codes
Hosted Payment Page -Transaction Status Codes
The following table lists possible status codes that can be returned in the redirect from HPP against state_id
.
Code | Type | Description |
---|---|---|
1041 | Payment Pending | When Velocity starts a payment with a provider and waits for the confirmation about payment, mPoint logs this state. This state is useful for offline payment methods, where the payment is processed on Velocity and waiting for the offline provider. |
2000 | Authorized | The payment has been successfully authorized by the PSP. |
2001 | Captured | The payment has been successfully captured by the PSP. |
2010 | Rejected | The payment was rejected by the PSP or Acquirer. |
2011 | Declined | The payment was declined by PSP / Acquirer while performing capture. |
2002 | Cancel | The payment was cancelled. |
5000 | Validation | The validation failed. |
2016 | 3D verification failed | 3D verification with MPI failed. |
2017 | Authorization not attempted due to rule matched | Authorization not attempted after successful 3D verification due to rule matched. |
Hosted Payment Page - Cancellation/Timeout Status Codes
Hosted Payment Page - Cancellation/Timeout Status Codes
The following table lists status codes that can be returned in the redirect from HPP in specific cancellation/timeout scenarios.
Code | Type | Description |
---|---|---|
409 | SESSION_TIMEOUT | HPP session timeout |
410 | CANCEL | User cancels without attempting a payment. Cancellation by customer is implemented via (via Button ‘Back' or 'Cancel’) and confirmation popup. |
411 | PAYMENT_INCOMPLETE_CANCEL | User cancels after back-end interaction (after an error is thrown on the HPP). |
Updated 5 months ago