API Status Codes
<initialize-payment> Codes
<initialize-payment> CodesThe following table provides information about the codes that you can receive after you initialize a payment.
| Code | Description |
|---|---|
| 1 | Client ID / Account does not match. |
| 2 | Invalid client ID |
| 3 | Unknown client ID |
| 4 | Client disabled |
| 11 | Undefined account |
| 12 | Invalid account |
| 13 | Unknown account |
| 14 | Account disabled |
| 53 | Amount is more than pending amount. |
| 400 | Wrong operation: initialize. |
| 401 | Authentication Failed. |
| 415 | Invalid XML Document. |
| 1002 | Internal database error - Unable to create a new Transaction. Contact [email protected] |
| 1003 | Internal database error - Unable to insert new message for Transaction. Contact [email protected] |
| 1004 | Internal database error - Unable to update Transaction. Contact [email protected] |
| 4021 | Payment failed: You have exceeded the maximum number of attempts. |
| 4039 | Payment session is already completed. |
<authorize-payment> Codes
<authorize-payment> CodesThe following table describes the codes you can receive after you request to authorize a payment.
| Code | Description |
|---|---|
| 1 | Undefined client ID |
| 2 | Invalid client ID |
| 3 | Unknown client ID |
| 4 | Client disabled. |
| 11 | Undefined account. |
| 12 | Invalid account. |
| 13 | Unknown account. |
| 14 | Account disabled. |
| 24 | The selected payment card is not available. |
| 26 | Undefined password. |
| 27 | Password is too short; min length is 6 characters. |
| 28 | Password is too long; max length is 50 characters. |
| 29 | Password contains invalid characters ‘or’ |
| 31 | Authentication failed. |
| 32 | Authentication failed – Next invalid attempt will delete the account. |
| 33 | Authentication failed – Account deleted. |
| 34 | Authentication rejected by the single sign-on server. |
| 35 | User account not found. |
| 36 | A timeout occurred while communicating with the single sign-on server. |
| 37 | Mobile number not verified. |
| 38 | Unable to perform single sign-on due to invalid Security Token or Authentication URL. |
| 39 | User account disabled. |
| 41 | Undefined card ID. |
| 42 | ID for the stored card is too small, min value is 1. |
| 43 | Stored card not found. |
| 43 | Insufficient balance on voucher. |
| 44 | Stored card disabled. |
| 45 | Voucher and Redeem device-ids not equal. |
| 48 | Voucher payment temporarily locked. |
| 51 | Insufficient balance on e-money account. |
| 52 | Amount is more than pending amount. |
| 53 | Amount is more than pending amount. |
| 59 | Authorization type not supported for the transaction. |
| 79 | An unknown error occurred while retrieving payment data from third-party wallet. Card has been blocked. |
| 90 | The connection timed out while authorizing the payment with the PSP. |
| 92 | Authorization rejected by PSP / Acquirer. |
| 99 | Unknown PSP / Acquirer. |
| 100 | Payment authorized using a stored card/Invoice. |
| 101 | Payment authorized using e-money account. |
| 102 | Payment authorized using loyalty account. |
| 103 | Authorization already in progress. |
| 400 | Wrong operation: authorization. |
| 401 | Authentication Failed. |
| 404 | Transaction with ID:<Transaction ID>. |
| 415 | Invalid XML Document. |
| 1002 | Internal database error - Unable to create a new Transaction. Contact [email protected]. |
| 1003 | Internal database error - Unable to insert new message for Transaction. Contact [email protected]. |
| 1004 | Internal database error - Unable to update Transaction. Contact [email protected]. |
| 2000 | Payment authorized. |
| 2009 | Payment authorized and card stored. |
| 2010 | Authorization Declined or Rejected |
<capture> Codes
<capture> CodesThe following table provides information about the codes that you can receive after you send a Capture request.
| Code | Description |
|---|---|
| 1 | Client ID / Account does not match. |
| 400 | Invalid request |
| 401 | Authorization failed. |
| 415 | Invalid XML Document. |
| 500 | Internal Error. |
| 997 | Capture not supported. |
| 998 | Network error. |
| 999 | Declined. |
| 1000 | Transaction captured successfully. |
<refund> Codes
<refund> CodesThe following table describes the codes you can receive after you send a Refund request.
| Code | Description |
|---|---|
| 1000 | Transaction refunded successfully. |
| 1001 | Transaction cancelled successfully. |
| 1100 | Refund Initiated. |
| 9400 | Invalid request. |
| 9502 | Bad gateway. |
| 9500 | Internal sever error. |
Other Codes
| Code | Category | Type | Description |
|---|---|---|---|
| 1001 | Payment | Payment Initialized with Velocity | The payment transaction is created in the Velocity database. |
| 1009 | Payment | Payment Initialized with PSP | The payment processor responsible for authorizing the payment has been initialized. |
| 1991 | Callback | Merchant Callback Constructed | The callback to the merchant application sent to callback-url has been constructed. |
| 1992 | Callback | Callback Connected | The connection with the merchant callback URL is established. |
| 1993 | Callback | Callback Connection Failed | The connection with the merchant callback URL failed. |
| 1990 | Callback | Callback Accepted | The merchant system returned an HTTP 200 OK and received the callback. |
| 1995 | Callback | Callback Rejected | The merchant system returned an HTTP $XX/5XX Error and rejected the callback. |
| 2000 | Payment | Authorized | The payment has been authorized successfully by the PSP. |
| 2002 | Payment | Cancelled | The authorized payment has been cancelled successfully by the PSP. |
| 2003 | Payment | Refunded | The captured payment refunded successfully (full / partial) by the PSP. The manual operation / delayed refund - pending states, initiated. |
| 2008 | Payment | Payment via Stored | Initialized payment with a stored card. |
| 2009 | Payment | Authorized and Card Stored | The payment has been authorized successfully by the PSP and the card stored on a successful authorization. |
| 2001 | Payment | Captured | The payment has been captured successfully by the PSP initiated for refund. |
| 2010 | Payment | Rejected | The payment was rejected by the PSP or Acquirer need more granular states - message tbl front end can continue handling the generic state. |
| 20109 | Payment | Rejected sub state on timeout | Issuer down time; SDK returns this to the Velocity core. |
| 20108 | Payment | Rejected sub state on timeout | PSP down time; SDK returns this to the Velocity core. |
| 2011 | Payment | Declined | The payment was declined by the PSP / Acquirer while performing capture, refund, or cancel. No Vision impact; however, all declines have common state 2011. |
| 4020 | Session | Session Failed | The session failed or declined. One or more transactions in the session failed. |
| 4021 | Session | Session Failed | The session failed (maximum attempt exceeds). One or more transaction attempts failed. |
| 4030 | Session | Session Complete | The session completed successfully. The transactions in the session are complete and successful. |
| 4031 | Session | Session Partial | The session was partially completed. One or more transactions in the session were incomplete. |
Additional codes:
| Code | Description |
|---|---|
| 0 | Payment not made. |
| 200 | Request validated and accepted by back end. |
| 400 | Request rejected by back end because of validation error. |
| 401 | Authentication required. |
| 403 | Access denied. |
| 415 | Message transmitted in an unknown format or by using an unsupported content type. |
| 500 | Velocity server error. |
| 502 | PSP returned an unknown error. |
| 504 | A timeout occurred while communicating with the PSP. |
| 1003 | Card expired. |
| 1005 | Invalid card number. |
| 1011 | Invalid card name. |
| 1012 | Invalid card address. |
| 1013 | Invalid card date of birth. |
| 1014 | Card is inactive. |
| 2007 | Payment processed. |
| 2019 | Payment duplicated. |
| 2084 | Card not found. |
| 4030 | Payment success. |
| 40031 | Partial payment success. |
Updated 5 months ago
