Error Codes

4. Error Codes

4.1 Fraud Status Codes

The following table lists status codes that can be returned in the redirect from HPP against fraud_status_code.

CodeTypeDescription
3010Pre-Fraud Check InitiatedPre-Fraud Check Initiated.
3011Pre-screening result
- Accepted
The pre-auth fraud check was “accepted” and no further fraud screening will be done.
3012Pre-screening fraud service unavailableSystem error from fraud check service.
3013Pre-screening result
- Unknown
An unknown error.
3014Pre-Screening fraud Result
- Review
The fraud check was REVIEW.
3015Pre-screening result
- Rejected
The pre-auth fraud check service was in REJECTED and no further payment processing will be done.
3016Pre-screening Connection Failed - RejectedPre-screening connection failed – rejected.
3100Post Fraud Check requiredPost fraud check required.
3111Post-screening Result

- Accepted
The post-auth fraud check was ACCEPTED.
3112Post-Screening Result

- Unknown
System error from fraud check service and therefore, manual review will be required.
The payment will not be refunded or cancelled.
3113Post-screening Fraud Result - ReviewThis state indicates an unknown error.
3114Post-screening Result

- Rejected
The fraud check was REVIEW and hence manual Review will be required.
The payment will not be refunded or cancelled.
3115Post-screening Result

- Rejected
The fraud check was REJECTED. The payment will be refunded or cancelled.
3116Post-screening Connection FailedVelocity could not connect to fraud check service and therefore, manual review will be required. The payment will not be refunded or cancelled.

4.2 Transaction Status Codes

The following table lists possible status codes that can be returned in the redirect from HPP against state_id.

CodeTypeDescription
1041Payment PendingWhen 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.
2000AuthorizedThe payment has been successfully authorized by the PSP.
2001CapturedThe payment has been successfully captured by the PSP.
2010Captured
Rejected
The payment was rejected by the PSP or Acquirer.
2011DeclinedThe payment was declined by PSP / Acquirer while performing capture.
2000CancelThe payment was cancelled.
5000ValidationThe validation failed.
20163D verification failed3D verification with MPI failed.
2017Authorization not attempted due to rule matchedAuthorization not attempted after successful 3D verification due to rule matched.

4.3 Cancellation/Timeout Status Codes

The following table lists possible status codes that can be returned in the redirect from HPP in specific cancellation/time out scenarios.

CodeTypeDescription
409SESSION_TIMEOUTHPP session timeout
410CANCELUser cancels without attempting a payment. Cancellation by customer is implemented via (via Button ‘Back' or 'Cancel’) and confirmation popup.
411PAYMENT_INCOMPLETE_CANCELUser cancels after back-end interaction (after an error is thrown on the HPP).