Cards & Wallets · Values and codes
Response Codes and Messages
Below are the codes and messages you could receive in response to your requests, grouped by the part of the platform that returns them.
Generic response codes and messages
Below is a list of the codes and messages you could receive in response to your request. S100 indicates the transaction request was successful.
| Code | Message | Reason |
|---|---|---|
| V100 | {validation that was not passed} | The API request was not valid. |
| V101 | Unauthorised access | The client address was not configured in the client firewall. |
| V102 | – | The server-to-server address was not valid (Internal). |
| V103 | Access Denied | The connection API credentials do not have permission to use the specified installation. |
| V104 | Unsupported transaction type {transactionType} | The specified operation is not supported on this installation. |
| V105 | Missing related transaction / Related transaction was not found | Related transaction was not provided / not found / processed by other merchant. |
| V106 | Suspended transaction has expired | The suspended transaction has expired, so it could not be resumed. |
| V107 | Wrong transaction status for resume – transaction status = {transactionStatus} | This transaction cannot be resumed. |
| V108 | PaRes is not valid | This 3DS transaction cannot be resumed, the provided PaRes is not valid. |
| V109 | CV2 specified as a standalone field is not consistent with the value from the card lock token. | CV2 is received as a standalone field and in card lock token and the values are not consistent. |
| V216 | Card details update is not allowed. | Card details update is not allowed for card backed by network token. |
| V306 | CV2 is required on domain / CV2 is required on Merchant. | CV2 is configured as a required field and has not been provided. |
| V500 | Feature no longer available | The specified feature is no longer available |
| A102 | No account capable of processing this transaction | No suitable external account. |
| A103 | Transaction is not a valid related transaction of its parent | The related transaction for this operation was not valid for this operation. |
| A104 | Card brand not found | Details of the card could not be determined from the card data source. |
| A107 | The customer does not have an active default card registered | Customer doesn’t have a default card. |
| A108 | Specified customer not found | Card has no customer / Customer belongs to different Org Unit / Invalid merchant reference. |
| A109 | Specified card not found | The merchant card token is not found into the system. Used when updating/removing customers. |
| A401 | Customer not found | Customer not found |
| A146 | That merchant token could not be found. | Specified payment method not found |
| A110 | Transaction cancelled beacuse of POST_AUTH Callback failure | Transaction was abandoned because the post-auth callback failed with a technical error. |
| A111 | Transaction cancelled beacuse of pre AUTH Callback failure | Transaction was abandoned because the pre-auth callback failed with a technical error. |
| A144 | Postauth callback error; operation not cancelled | Error in processing post-auth callback.The related operation failed. Operations that have failed can not be reversed |
| A145 | Postauth callback error; operation not cancelled | Error in processing post-auth callback.The related operation was successful but can not be reversed. |
| U110 | Suspended for completion of authorisation | Suspended for completion of authorisation |
| U200 | Waiting for downstream authoriser to complete processing | Waiting for downstream authoriser to complete processing |
| A112 | invalid configuration expression | Invalid configuration in regards to expressions (Invalid expression supplied to the global 3dsecure). |
| A113 | Transaction rejected after Three D Secure enrolment | The ThreeDSecure enrolment failed but the process is enforcing 3d secure enrolement. |
| A114 | The transaction was rejected because 3DS authentication failed | The ThreeDSecure progressed but the transaction was not authenticated. |
| A115 | Card operation no longer valid after resume | The CCS has identified that a card operation is no longer valid after the transaction is resumed. |
| A116 | Card fraud checks failed | Transaction cancelled because of card fraud checks failure. |
| A117 | Card brand is not supported on this account | The card type could not be determined. It is not supported by the route. |
| A118 | The customer name is missing and is a required field. | The customer name is not provided. |
| A119 | The card has already been registered to a customer. | The card to be registered already exists. |
| A120 | Invalid gaming territories country conditions. | The transaction has failed Gaming territory management rules. |
| A121 | A valid MCC could not be determined. | |
| A122 | Max limit exceeded for active cards. | The max limit of active cards is reached and no new card can be registered. |
| A123 | Card is in deleted status. | The specified card is deleted. |
| A124 | {One or more validation errors} | The custom field value is invalid for the configured type. |
| A125 | Cannot process two concurrent secondary transactions that refer the same primary transaction | A secondary transaction is already processing for this transaction. |
| A126 | Duplicate transaction submitted | Duplicate transaction submitted |
| A127 | Invalid or unknown card lock token. | Specified card lock token is not recognized by the Tokenisation Service. |
| A128 | Tokenisation Service temporarily not available | The Tokenisation Service is temporarily unable to process tokenised payments. |
| A136 | Rejected by fraud rules service | The transaction request has been rejected due to a Fraud rule. |
| A137 | Failed to communicate with fraud rules service | Failed to communicate with fraud rules service |
| A138 | The card submitted for referral payout has not been used previously for an authorised payment | This functionality is currently not enabled on your account. |
| A147 | 3D Secure authentication result is not available at this time | Cannot resume the given 3DSv2 transaction; the authentication result is not yet available. Make sure that the cardholder has been redirected to the Access PaySuite 3D Secure Server, and has returned before attempting to complete the transaction. Check 3D Secure 2 for information on troubleshooting possible integration problems with the handover. In rare cases, this response may be received even if the process is complete, if the card issuer's ACS has not made the full results available to us. Re-trying the resume after a short delay may help; otherwise, contact us for support, especially if this problem persists. |
| A150 | Network tokenisation is disabled | Network tokenisation is disabled. |
| A151 | The selected route does not support network tokens | The selected route does not support network tokens. |
| A152 | Network token is {STATUS} | The following values indicate an inactive status: SUSPENDED, DELETED, EXPIRED. |
| A153 | Token cryptogram is not available | Token cryptogram is not available. |
| A400 | No such transaction | Provided transaction Id does not exist. |
| C101 | Cancelled by preauth callback | The Preauth callback returned a CANCEL response. |
| C102 | Cancelled by postauth callback | The post auth callback returned a CANCEL response. |
| C103 | Cancelled due to postauth callback error | Transaction cancelled by error when handling post-auth callback (e.g. a timeout or invalid response from the callback). |
| C104 | Cancelled due to preauth callback error | Transaction cancelled by error when handling pre-auth callback (e.g. timeout or invalid response) |
| C105 | Cancelled by request | Merchant cancelled suspended transaction |
| C107 | Payout Initialize has been successfully voided | Merchant cancelled Payout Initialize transaction |
| X201 | No processing routes are configured for this type of transaction | Internal error within the platform. |
| Failed to communicate with destination transaction processor | Exception from destination processor. | |
| X202 | Post Auth transaction void failed | The transaction mandated a VOID but this failed at the destination platform. The authoriser response contains an unsuccessful void response or does not contain a void response at all. |
| X203 | Unable to port registration data | The destination platform is not available. |
| X208 | Could not perform Three D Secure enrolment check | A general error occurred with the 3DS enrolment check. |
| X209 | There is no MPI configured for 3DS | MPI not configured on account. |
| X215 | Invalid transaction reference | Invalid or duplicate transaction reference. The request includes a reference used by a third-party supplier, and that third party has rejected it. |
| A139 | Three D Secure requirements not met | Transaction rejected because of configured 3DS liability shift requirements were not met. |
| E500 | Unknown error returned from card check | Checks to see if upon resume, a pending customer card service operation is valid. Checks that pending card entry is valid and repeats fraud checks. |
| Stored card details were not available for this suspended transaction | Appears when a resumed transaction occurs but the temporarily stored card details were not available. | |
| Unrecognised cv2avs string: {cv2AvsConstant} | Unrecognised CV2 AVS status. | |
| Internal Server Error | An internal error has occurred while processing the transaction. | |
| An unexpected error has occurred while processing. | ||
| Exception indicating that the 3DS enrolment status was missing. | ||
| General transaction management exception. | ||
| S100 | Accepted | When multiple reported transactions have been successfully submitted. The transaction has completed it’s desired goal. |
| Authorised | General transaction success code. The transaction has completed it’s desired goal. | |
| S101 | Customer fetched | General success code stating that a customer has been successfully returned. |
| S102 | Customer not found | Customer not found on Retrieve Customer Request. |
| S102 | Partial Failure | A report operation failed partially. |
| S103 | Payment method successfully removed | Payment method was successfully removed. |
| S104 | Payment method successfully updated | Payment method was successfully updated. |
| D100 | Declined by upstream processor | The platform or the authoriser declined the transaction. There can be useful guidance to the cause of the decline in processing.authResponse.gatewayMessage. |
| The transaction was refused because the country was prohibited as a result of territory management settings. | ||
| The transaction was refused because the maximum amount was exceeded as a result of velocity controls. | ||
| Payment declined by PayPal risk controls. | ||
| D101 | Transaction declined; Strong Customer Authentication required | The issuer declined the transaction; Strong Customer Authentication (SCA) is required, and has not been performed. If you can, re-try the transaction with 3D Secure 2. See 3D Secure 2 for more information. |
| D102 | Cardholder has advised their bank to stop this recurring payment. | The card holder has advised their bank to stop this recurring payment. Future repeats attempts are likely to be declined in the same way. |
| U100 | Suspended pending Three D Secure process | Transaction was suspended by 3DS enrolment processing. See redirect message in response, can only be resumed with a PARes message. |
| U101 | Suspended by preauth callback | Transaction was suspended by Preauth Callback. Transaction can be resumed to continue processing. |
| U102 | Suspended for replay by preauth callback | Transaction was suspended by Preauth Callback. Transaction can be resumed to continue processing. |
| R100 | Report Failed | Report Failed |
| T100 | Transaction expired by timeout | Transaction expired by timeout |
| B100 | Batch failed, see individual items for reasons | Batch failed, see individual items for reasons |
| B101 | Partial batch failure, see individual items for reasons | Partial batch failure, see individual items for reasons |
| A140 | General Risk Decline: Card velocity limit reached | Transaction rejected because of Risk Control Velocity checks failure |
| General Risk Decline: IP Address velocity limit reached | Transaction rejected because of Risk Control Velocity checks failure | |
| General Risk Decline: Card & IP Address velocity limit reached | Transaction rejected because of Risk Control Velocity checks failure | |
| A142 | General Risk Decline: CV2 requirements not met | Aborting transaction, pre-auth risk CV2 checks failed. |
| A143 | General Risk Decline: IP is negative listed | Risk controls found the IP address in a blacklist |
| General Risk Decline: Card is negative listed | Risk controls found the card in a blacklist | |
| C106 | General Risk Decline: {requirements not met} requirements not met | Transaction cancelled by platform risk controls. |
| V321 | Mobile SDK not available for you. | Mobile SDK not enabled on your account. |
Validation response codes and messages
| Validation Type | Code | Message | Reason |
|---|---|---|---|
| Authentication | V111 | UserId must be specified | Invalid API credentials. |
| Security Key must be specified | Invalid API credentials. | ||
| Installation | V112 | Installation must be specified. | Installation not provided in request |
| V113 | Invalid installation / Installation ID must be numeric | Installation id must be numerics only. | |
| Customer validation | V114 | Customer must be specified / Customer details must be specified. | Customer not specified on request |
| V115 | merchantRef or id must be specified. | merchantRef or id not specified on request | |
| V116 | merchantRef and id must not be specified together. | Both merchantRef and id specified on request | |
| V117 | Customer not found. | Customer specified in request not found | |
| Create customers validations | V118 | Customer name cannot be null. | Customer name cannot be null. |
| V119 | At least one name for the customer must be set. | At least one name for the customer must be set. | |
| Payment class validation | V123 | paymentClass should be specified. | paymentClass should be specified |
| Postal code validation | V124 | Invalid optional post code. | Invalid optional post code. |
| Callback URL validation | V125 | Invalid URL. | Callback url does not have a valid URL format. |
| General validation | V126 | Currency must be specified. | Currency must be specified. |
| V127 | Unrecognised currency {currencyType}. | Unrecognised currency | |
| V128 | CommerceType must be specified. | CommerceType must be specified. | |
| V129 | Amount must be specified. | Amount must be specified. | |
| V130 | Amount {amountValue} cannot be negative. | Amount cannot be negative. | |
| V131 | Amount {amountValue} exceeds the number of fractional digits {digitsNumber} permitted for currency {currencyType}. | Amount exceeds the number of fractional digits permitted for currency | |
| V132 | Amount {amountValue} exceeds the maximum number of non-fractional digits {digitsNumber}. | Amount exceeds the maximum number of non-fractional digits | |
| Acquiring limits validation | V171 | Requested amount exceeds single transaction limit of {singleTransactionLimit}. | The requested payment amount would cause you to breach a limit that was agreed as a condition of providing you with a merchant account facility. Contact our Risk team if you need to have these limits revised. |
| Requested amount exceeds remaining monthly transaction allowance of {remainingAllowance}. | |||
| Secondary transaction validation | V133 | Cannot {requestedTxnType} a transaction in a different currency ({requiredCurrency}) to the original {originalCurrency}). | Currency is different than that on the original transaction |
| V134 | Cannot perform a {requestedTxnType} against a {originalTxnType} transaction. | Secondary transaction type not valid for referenced transaction | |
| V135 | Cannot perform a {requestedTxnType} against an incomplete transaction. | Cannot perform a {requestedTxnType} against an incomplete transaction. | |
| V136 | Cannot perform a {requestedTxnType} against a failed transaction. | Cannot perform a {requestedTxnType} against a failed transaction. | |
| V137 | Cannot perform a {requestedTxnType} against an uncaptured transaction. | Cannot perform a {requestedTxnType} against an uncaptured transaction. | |
| V138 | Cannot perform a {requestedTxnType} against an already-captured transaction. | Cannot perform a {requestedTxnType} against an already-captured transaction. | |
| V139 | Cannot perform a {requestedTxnType} against an already-void transaction. | Cannot perform a {requestedTxnType} against an already-void transaction. | |
| V181 | Cannot perform a complete against a transaction that has had a failed capture transaction against it | Cannot perform a complete against a transaction that has had a failed capture transaction against it | |
| Nickname validation | V142 | Invalid nickname length ({nicknameLength}). Max number of permitted characters is 20. | Card nickname exceeds the max number of permitted characters (20). |
| Card detail validation | V144 | Expiry date should be MMYY. | Expiry date must match: MMYY format. |
| V145 | Start date should be MMYY. | Start date must match: MMYY format. | |
| V146 | startDate and clearStartDate can not be specified in the same request. | StartDate and ClearStartDate are both specified at the same time. | |
| V147 | Start date after expiry. | StartDate and Expiry are both specified and start date is after the expiry date. | |
| V148 | Issue number must be between 0 and 9. | Issue number must be between 0 and 9 | |
| V149 | issueNumber and clearIssueNumber can not be specified in the same request. | IssueNumber and ClearIssueNumber are both specified at the same time. | |
| Other validation | V150 | One payment method should be specified. | One payment method should be specified. |
| V151 | token should be set / cardToken must be specified | token should be set / cardToken must be specified | |
| V170 | Invalid order line ‘%s’, {specific validation not met}. | Invalid order line | |
| V324 | {fieldName} field cannot contain card number | Card number can only be provided in the designated field. | |
| Payment details validation | V152 | Address field exceeds max length. | Line 1 / Line 2 / Line 3 / Line 4 / City / Country / Postal Code / Region field length exceeds 255 characters. |
| V154 | Unrecognised address country code. | Address country code is not a valid country in the system. | |
| V156 | Cannot register a payment method for a guest transaction. | A payment method cannot be registered when a customer is not also being registered. | |
| Financial services validations | V153 | Invalid date of birth “{dateOfBirth}”, it must be in the format “yyyyMMdd”. | The date of birth must match: yyyyMMdd format |
Payment and authorisation response codes and messages
| Validation Type | Code | Message | Reason |
|---|---|---|---|
| Card details validation | V301 | No PAN provided. | Card number is not provided. |
| V302 | Invalid pan format: {maskedPan} / Card contains non-numeric characters / Invalid card number | Card number must be numeric only. | |
| V303 | Invalid pan length: {panLength} / Invalid card length ({panLength}) | Card number must be between 13 and 19 characters. | |
| V304 | expiryDate is null or empty | expiryDate is null or empty | |
| Payment details validation | V305 | Unknown card type, valid types are {listOfValidTypes}. | Payment card type must be one of: ELECTRON, MAESTRO, MC_DEBIT,SWITCH, SOLO, MC_CREDIT, VISA_DEBIT, VISA_CREDIT, AMEX, JCB, LASER, DISCOVER, DINERS. |
| Other validation | V307 | Only one payment method can be used at the same time. Trying to use card as well. | Only one payment method can be used at the same time. Trying to use card as well. |
| V308 | Only one payment method can be used at the same time. Trying to use cardToken as well. | Only one payment method can be used at the same time. Trying to use cardToken as well. | |
| V309 | Only one payment method can be used at the same time. Trying to use fromCustomer as well. | Only one payment method can be used at the same time. Trying to use fromCustomer as well. | |
| V310 | Only one payment method can be used at the same time. Trying to use payCash as well. | Only one payment method can be used at the same time. Trying to use payCash as well. | |
| V311 | No pan or card lock token provided. | No valid card lock token or card number specified. | |
| V312 | Either card lock token OR card number should be set. | Both card lock token and card number are specified. Only one is required. | |
| V313 | Card lock not available for you. | CardLock is not enabled on the account. | |
| V314 | Merchant has invalid credentials | Merchant has invalid credentials |
Refund response codes and messages
| Validation Type | Code | Message | Reason |
|---|---|---|---|
| Amount | V100 | Invalid Amount | Amount can not be zero. |
| V402 | Amount exceeds amount refundable | Amount exceeds amount refundable | |
| Transaction state | V403 | Cannot refund a cancelled transaction | Transaction to be refunded is already cancelled. |
Capture response codes and messages
| Validation Type | Code | Message | Reason |
|---|---|---|---|
| Amount | V100 | Invalid Amount | Amount can not be zero. |
| V501 | Amount exceeds the original pre-authorised amount | Amount exceeds the original pre-authorised amount | |
| V502 | Amount is less than the original pre-authorised amount | Amount is less than the original pre-authorised amount |
Cancel response codes and messages
| Validation Type | Code | Message | Reason |
|---|---|---|---|
| Amount | V100 | Invalid Amount | Amount can not be zero. |
| V601 | Amount exceeds the original pre-authorised amount | Amount exceeds the original pre-authorised amount | |
| V602 | Amount is less than the original pre-authorised amount | Amount is less than the original pre-authorised amount | |
| Transaction state | V603 | Cannot cancel a refunded transaction | Transaction to be cancelled is already refunded. |
Repeat response codes and messages
| Validation Type | Code | Message | Reason |
|---|---|---|---|
| Amount | V100 | Invalid Amount | Amount can not be zero. |
| Recurring Repeats | V704 | Original payment or authorisation not valid for a repeat payment | Original payment or authorisation not valid for a repeat payment |
Response codes specific for verify transactions
| Code | Message | Reason |
|---|---|---|
| V159 | The amount must not be provided for an account verification | Verify request sent not valid as it has amount included. |
| V160 | At least one verification option should be set for an account verification | Verify request sent not valid. |
| V165 | The currency must be provided for an account verification | Verify request sent not valid. |
Reporting response messages
| Validation Type | Message | Reason |
|---|---|---|
| Transaction details | Transaction report must be provided. | |
| Transaction details must be provided. | ||
| Transaction status must be terminal, pending is not allowed. | Transaction must not be in PENDING status. | |
| Amount | Amount {amountValue} cannot be negative. | Transaction amount must be a positive number. |
| Amount {amountValue} exceeds the number of fractional digits {currencyMinorUnitValue} permitted for currency {isoCurrencyCode}. | The transaction amount exceeds the number of fractional digits permitted. | |
| Amount{amountValue} exceeds the maximum number of non-fractional digits 16. | The specified amount exceeds the default maximum non-fractional length. | |
| Currency | Unrecognised currency {currencyType}. | Invalid currency. |
| Transaction manager | The transaction manager is not correctly specified: Unrecognised transaction manager{transactionManager}. | |
| The acquirer specified on the auth response is not correct: Unrecognised acquirer name {acquirerName}. | ||
| Payment method validation | Payment class could not be fetched into the system: Unrecognised payment class {paymentClassName}. | |
| Unrecognised card type {cardType}. | ||
| Unrecognised issuer country {issuerCountry}. | ||
| Unrecognised customer address country {countryCode}. | Customer address country is not a valid country. | |
| Unrecognised customer default currency {currency}. | Customer default currency is not correct. | |
| Unrecognised customer IP {ip}. | Customer IP is not in a valid format. | |
| Other validation | The number of requested report transactions exceeds the max number of allowed reported txns: {txnNumber} transactions reported.Maximum allowed number of reported |
Hosted response codes
Below is a list of the codes and messages you could receive in response to a hosted request.
| Code | Message | Reason |
|---|---|---|
| exception.authenticationFailure.noAuth | Authentication Failed | Authentication Failed. |
| exception.authenticationFailure.noPriv | Authorisation Failed | Authorisation Failed. |
| exception.cache.invalidResourcePath | Invalid Resource Path | Resource not found. |
| exception.config.noCustomerCardDomain | No customer-card domain configured | Customer-card domain not found for the installation. |
| exception.config.noReturnUrl | No return url provided | Return url not provided. |
| exception.error.amo | CSC Address match only | Fraud check fails for “address match only” rule. |
| exception.error.dcr | Daily card registrations | Fraud check fails for “daily card registrations” rule. |
| exception.error.mcr | Max card register | Fraud check fails for “max card register” rule. |
| exception.error.ndm | CSC No data match | Fraud check fails for “no data match” rule. |
| exception.error.nvd | Net balance | Fraud check fails for “net balance” rule. |
| exception.initialiseHosted.noCustomer | Customer not found | Customer ID provided could not be found. Applies to transactions and manage cards. |
| exception.installation.lookup | Invalid installation | The installation provided is not valid. |
| exception.landing.invalidFlow | Invalid flow provided | No flow specified or it is invalid. |
| exception.manageCards.noRegisteredCards | No cards registered | Exception for customer having no cards registered. |
| exception.manageCards.noRegisteredCards.message | Currently you have no registered cards which are available for manage cards. | Response message when there are no cards registered. |
| exception.manageCards.noValidCards | No cards active | Customer has no card active. |
| exception.payout.noValidCards | No valid cards for withdrawal | A Payout session can only be requested where the customer has a saved card. |
| exception.payout.noValidCards.message | Currently you have no registered cards which are available for withdrawal. | A Payout session can only be requested where the customer has a saved card. |
| exception.payout.noStoredPaymentMethods | No Valid Payment Methods for Withdrawal | The customer has no valid saved payment methods for withdrawal. |
| exception.request.newAccountPayoutEnabled | New account payout not available on version 1 skins. To make use of this feature, upgrade your skin | New account payout not available on version 1 skins. To make use of this feature, upgrade your skin. |
| exception.request.invalid.newAccountPayoutEnabled | Payouts with new payment methods are not enabled for this account | Payouts with new payment methods are not enabled for this account. |
| exception.permission.denied | Permission Denied | Request does not have have sufficient permissions to be processed. |
| exception.permission.denied.message | You do not have permission to perform that action | Response message for “permission denied” exception. |
| exception.resumeFailure.invalidSession | Session invalid for resumption | Session is not suspended therefore it can not be resumed. |
| exception.resumeFailure.noSession | No session found | Returned when: trying to resume a session that does not exist, an issue occurred trying to retrieve a session session was already expired or session was not found |
| exception.skin.installation | Skin specified in installation not valid | The skin status is not valid or initialising the resources from the skin has failed. |
| exception.skin.lookup | No skin configured | No skin is configured for the current merchant. |
| exception.skin.merchant.lookup | No merchant configured | Merchant could not be found. |
| exception.skin.request | Skin specified in request not valid | Returned when: the skin id is not provided skin is not found provided skin ID is not valid for the merchant |
| exception.skin.unusable | Skin not usable | The specified skin is not usable. Either the skin bundle or one of its resources is not readable. Contact Support to verify the stored skin data. |
| exception.skin.deleted | The skin with id {skinId} has been deleted so can no longer be used | The specified skin has been deleted so can no longer be used |
| exception.config.url.not.valid | Callback URL is not valid | The callback URL is not a valid URL. |
| exception.request.contentType | Content type {0} not supported. Content type application/json required. | The provided content type is not valid or missing. |
| exception.invalid.email | Email address provided is not valid | The email address provided in the request is not in a valid email format. |
| exception.request.resultPage | Results page not available on version 1 skins. To make use of this feature, upgrade your skin. | The feature requested is only availble if the hosted skin being used is version 2. See Skin Properties |
| exception.invalid.post.code | Post code provided is not valid | The post code provided in the request is not in a valid format. |
| exception.threedsecure.failure | 3D Secure Server failed to handover | When 3D Secure server returned overall status is not equal to: 00 or 03 or 04 See 3D Secure 2 |
| exception.invalid.negative.amount | Invalid negative amount | The amount provided in request is less than zero. |
| exception.invalid.fraction.digits.currency.amount | Amount exceeds the number of fractional digits permitted for currency | The amount provided in request exceeds the number of fractional digits permitted for currency. |
| exception.invalid.non.fractional.digits.amount | Amount exceeds the maximum number of non-fractional digits | The amount provided in request exceeds the maximum number of non-fractional digits. |
| exception.invalid.range.amount | Range incorrectly specified – minimum value larger than maximum value | When minimum value larger than maximum value. |
| exception.invalid.currency.code | Invalid currency | Invalid currency. |
| exception.invalid.amount.is.set | The amount must not be provided for an account verification | The amount is provided for an account verification. |
| exception.invalid.currency.not.set | The currency must be provided for an account verification | The currency is not provided for an account verification. |
| exception.invalid.country.code | Invalid country code | Invalid country code. |
| exception.invalid.country | Invalid country | Invalid country. |
| exception.invalid.order | Order details are not valid | Order details are not valid. |
| exception.invalid.financial.services.date.of.birth | Invalid date of birth – must be in the format “yyyyMMdd” | Invalid date of birth format. |
| exception.paymentMethod.noCustomer | Payment method can not be registered without customer | Customer details were not provided while registering payment method. |
| exception.request.content | Invalid Request Content | Request content is invalid. |
| exception.request.missing.transactionDetails | Transaction details must be provided | Transaction details not provided in request. |
| exception.request.invalid.acquirerPaymentMethod | At least one verification option should be set for an account verification | Verification option not provided for an account verification. |
| exception.request.invalid.skin.paymentMethod | The specified payment methods are not valid for the skin | The payment method provided in request is not valid for the skin. |
| exception.request.invalid.null.paymentMethod | The specified payment methods must not be null | Payment method not specified in request. |
| exception.request.no.valid.paymentMethods | There are no applicable payment methods specified | There are no applicable payment methods specified in request. |
| exception.request.missing.customerName | Customer name is required | Customer name is not provided. |
| exception.request.customFieldIllegalName | Custom fields do not have legal names: [fieldNames] | At least one custom field name is invalid, it may only contain alpha nmeric characters, underscore ‘_’, colon ‘:’ or hash ‘#’ |
| exception.request.customFieldNonUnique | Custom fields do not have unique names: [fieldNames] | Multiple custom fields have the same name |
| exception.request.customFieldLocatorNotRecognised | Custom field locator not recognised: [fieldNames] | At least one visible custom field has an invalid locator |
| exception.request.skinFieldNameMissing | Skin field name must be supplied | A skin field in the request does not have a name |
| exception.request.skinFieldValueMissing | Skin field value must be supplied | A skin field in the request does not have a value |
| exception.request.skinFieldFormatMissing | Skin field formant must be supplied | A skin field in the request does not have a format |
| exception.request.skinFieldValueNotValidJson | Skin field value is not valid JSON : [value] | A skin field with format application/json has a value that isn’t valid JSON. |
| exception.request.invalid.boletoConsumerRef | Missing or invalid consumer reference for Boleto | Missing or invalid consumer reference for Boleto. |
| exception.request.invalid.itauConsumerRef | Missing or invalid consumer reference for Itau | Missing or invalid consumer reference for Itau. |
| exception.request.invalid.bancoDoBrasilConsumerRef | Missing or invalid consumer reference for Banco do Brasil | Missing or invalid consumer reference for Banco do Brasil. |
| exception.request.invalid.qiwiSiteId | Invalid site ID for Qiwi | Invalid site ID for Qiwi. |
| exception.request.invalid.customPayPalBnCode | Providing a custom PayPal BN code has not been enabled on this account | Provided PayPal BN code has not been enabled on this account. |
| exception.request.invalid.santanderConsumerRef | Missing or invalid consumer reference for Santander | Missing or invalid consumer reference for Santander. |
| exception.request.invalid.webPayConsumerRef | Missing or invalid consumer reference for WebPay | Missing or invalid consumer reference for WebPay. |
| exception.request.invalid.bradescoConsumerRef | Missing or invalid consumer reference for Bradesco | Missing or invalid consumer reference for Bradesco. |
| exception.request.invalid.pseConsumerRef | Missing or invalid consumer reference for PSE (Pagos Seguros en Linea) | Missing or invalid consumer reference for PSE (Pagos Seguros en Linea). |
| exception.request.invalid.trustlyConsumerRef | Missing or invalid consumer reference for Trustly | Missing or invalid consumer reference for Trustly. |
| exception.request.invalid.oxxoConsumerRef | Missing or invalid consumer reference for Oxxo | Missing or invalid consumer reference for Oxxo. |
| exception.request.invalid.efectyConsumerRef | Missing or invalid consumer reference for Efecty | Missing or invalid consumer reference for Efecty. |
| exception.request.invalid.bancoDeOccidenteConsumerRef | Missing or invalid consumer reference for Banco De Occidente | Missing or invalid consumer reference for Banco De Occidente. |
| exception.request.invalid.redpagosConsumerRef | Missing or invalid consumer reference for Redpagos | Missing or invalid consumer reference for Redpagos. |
| exception.request.invalid.banamexConsumerRef | Missing or invalid consumer reference for Banamex | Missing or invalid consumer reference for Banamex. |
| exception.request.invalid.carullaConsumerRef | Missing or invalid consumer reference for Carulla | Missing or invalid consumer reference for Carulla. |
| exception.request.invalid.santanderCashPaymentConsumerRef | Missing or invalid consumer reference for Santander Cash Payment | Missing or invalid consumer reference for Santander Cash Payment. |
| exception.request.invalid.surtimaxConsumerRef | Missing or invalid consumer reference for Surtimax | Missing or invalid consumer reference for Surtimax. |
| exception.request.invalid.entercashConsumerRef | Missing or invalid consumer reference for Entercash | Missing or invalid consumer reference for Entercash. |
| exception.request.invalid.balotoConsumerRef | Missing or invalid consumer reference for Baloto | Missing or invalid consumer reference for Baloto. |
| exception.request.invalid.empresaDeEnergiaConsumerRef | Missing or invalid consumer reference for Empresa de Energia del Quindio | Missing or invalid consumer reference for Empresa de Energia del Quindio. |
| exception.request.invalid.scheduleOnPayout | Schedules cannot be created from payouts | Schedules cannot be created from payouts. |
| exception.request.invalid.scheduleOnVerifyWithoutAmount | A schedule cannot be created for a verify unless the schedule specifies at least one amount | A schedule cannot be created for a verify unless the schedule specifies at least one amount. |
| exception.request.invalid.scheduleWithoutContinuousAuthority | A schedule cannot be created unless the initial transaction is recurring or instalment | A schedule cannot be created unless the initial transaction is recurring or instalment. |
| exception.request.invalid.schedulerNotEnabled | The scheduler feature is not enabled for this account | The scheduler feature is not enabled for this account. |
| exception.invalid.address.containsPan | Address field cannot contain a card number | Card number can only be provided in the designated field. |
| exception.invalid.customer.name.containsPan | Customer Name field cannot contain a card number | Card number can only be provided in the designated field. |
| exception.request.invalid.astroPayCardConsumerRef | Missing or invalid consumer reference for AstroPay Card | Missing or invalid consumer reference for AstroPay Card. |
| exception.request.invalid.customerNoticeContent | Invalid customer notice content | Text contains malformed or non-permitted HTML elements – Customer Notice shows the current list |
| exception.request.invalid.customerNoticeSize | Customer notice content exceeds the maximum size limit {limit} | Text is longer than permitted (the count applies to all characters in the value, including HTML markup) |
CardLock response codes and messages
Below is a list of codes you could receive in an error handler (when using the JavaScript library) or in response to your request (when using the REST API).
| Code | Description | Explanation | HTTP Status |
|---|---|---|---|
| S00 | OK | Card details captured and a token has been issued Send the token to our payments API to continue processing | 200 |
| V00 | Bad request | One or more request elements were invalid; this is a catch-all used when no more detail is available REST API users: Review integration, ensure that requests are valid JSON with an appropriate Content-Type header, check field values against specification | 400 |
| V01 | Missing PAN | No PAN was provided in the request | 400 |
| V02 | Invalid PAN | PAN was not valid (must be 13-19 digits without spaces, etc.) Prompt the cardholder to re-enter the PAN | 400 |
| V03 | Invalid CVV | CSC was not valid (must be 3 or 4 digits) Prompt the cardholder to re-enter their CVV2/CVC2/CID/CSC | 400 |
| V05 | Missing publishable ID | No publishable ID was provided in the request | 400 |
| A01 | Unknown publishable ID | The publishable ID provided is not well-formed or not active Use a publishable ID value issued to you by Access PaySuite.Mobile SDK Users: Update the publishable ID from the merchant server (see mobile-specific guidance) | 401 |
| E00 | Service unavailable | Tokenisation service is not available Re-try the request after a short delay if feasible; if this persists, contact us | 500 |
| E01 | Internal error | An error occurred and no token could be issued; this may be temporary Re-try the request after a short delay if feasible; if this persists, contact us | 500 |
HTTP status codes are only applicable when using the JSON REST API. Any response code not listed here should be treated as an error; the message should provide more information.
Card Info client authorisation response codes and messages
Below is a list of the codes and messages you could receive in response to your request. S100 indicates the request was successful.
| Code | Message | Business Case |
|---|---|---|
| V320 | Card info not available for you. | Card Info functionality are not available for merchant |
Card Info library response codes and messages
Below is a list of the codes and messages you could receive in response to your request. S00 indicates the request was successful.
| Status | Code Message | Reason Message |
|---|---|---|
| FAILED | V00 | Access denied |
| FAILED | V02 | Access denied – client access token missing |
| FAILED | V03 | Access denied – client access token expired |
| FAILED | V04 | Missing partial PAN |
| FAILED | V05 | Invalid format partial PAN – must be digits only, length at least two |
| FAILED | V06 | SDK could not bind to specified element {elemId} |
| FAILED | E00 | Internal server error |
| FAILED | E99 | SDK’s call to CardInfo service timed out – endpoint {serviceEndpoint} |
Response codes for transactions using PayPal
| Code | Message | Reason |
|---|---|---|
| V179 | Merchant not configured for PayPal | The merchant is not configured for PayPal transaction processing. |
| Installation not configured for PayPal | The installation is not configured for PayPal transaction processing. | |
| V180 | Providing a custom PayPal BN code has not been enabled on this account. | This feature is not enabled on your account. |
| A131 | PayPal merchant authentication failure. | Invalid merchant credentials. |
| A134 | PayPal merchant authorisation failure. | You do not have the appropriate permissions to perform this transaction. |
| A135 | PayPal configuration issue | PayPal configuration issue |
| X210 | PayPal service currently unavailable | Unable to communicate with the PayPal service. |
| X211 | PayPal returned error. | Communication with PayPal returned an error. |
| X212 | PayPal timeout. | The Express Checkout session has expired. Token value is no longer valid. |
| X214 | PayPal user has not authorised. | Payment has not been authorised by the user. |
| PayPal user has not confirmed. | The customer has not yet confirmed payment for this Express Checkout session. | |
| PayPal transaction not completed. | The customer returned without completing the payment. | |
| U103 | Suspended by PayPal | The transaction was suspended by PayPal processing |
| U104 | Suspended for PayPal redirect retry | The transaction was suspended for PayPal session retry. |
| V157 | You may only cancel PayPal transactions that are in a suspended state | PayPal transaction is not in required status to be cancelled. |
| V708 | Cannot process recurring payments via PayPal | Cannot process recurring payments via PayPal |
Response codes specific for transactions using Visa Checkout
| Code | Message | Reason |
|---|---|---|
| V166 | Visa Checkout Call ID is required | Malformed request |
| V167 | Visa Checkout Call ID exceeds maximum length | Malformed request |
| V168 | Visa Checkout Call ID does not conform to the required format | Malformed request |
| V169 | Cannot use this currency with Visa Checkout | Malformed request |
| V801 | The Visa Checkout feature is not enabled for this account | Feature not enabled |
| A141 | Visa Checkout service unavailable | Error communicating with the Visa Checkout service |
Response codes specific to Apple Pay processing
Codes here may be received with messages not included in the examples below. In these cases, the description gives a broad outline of where the problem lies, and the message text should provide more detail.
| Code | Description | Message | Explanation |
|---|---|---|---|
| V190 | Apple Pay not enabled | Account not enabled for Apple Pay | Contact us to enable Apple Pay for your account. |
| V191 | Incorrect/unexpected merchant identifier | Apple Pay merchantidentifier does not match configuration | Make sure you’re using the correct applePayMerchantIdentifier; it needs to match the value we provided you with when enabling your account. |
| V192 | Domain validation error | Unsupported Apple Pay validation domain | The validationURL provided doesn’t match a known, trusted Apple domain. Make sure you’re passing the value obtained from the onvalidatemerchant function registered with the SDK. |
| Apple Pay site is not enabled for this merchant | The siteDomain provided doesn’t match one that we have registered with Apple for your account. Each domain in use needs to be activated. You can use different domains in MITE and live. | ||
| V193 | Invalid Apple Pay payment method data | Apple Pay data is not valid | The supplied data from Apple Pay isn’t valid; we can’t read or decrypt it, it’s been tampered with, or it’s not consistent between the SDK and the authorisation request. Make sure to pass through values as given, and note any specific guidance about encoding, etc. The currency and amount passed to the SDK need to match those passed in the transaction details for authorisation. |
| Apple Pay data invalid: Signature invalid | |||
| Apple Pay data invalid: Unable to decrypt | |||
| Apple Pay data invalid: amount or currency is null | |||
| Apple Pay amount and currency do not match with the amount and currency from transaction | |||
| One of Apple Pay paymentData or savedAccountToken required | Your API request is missing required elements, or contains multiple elements which can’t be used together. Check the API documentation and examples. | ||
| Provide one of Apple Pay paymentData or savedAccountToken, not both | |||
| Apple Pay requires both paymentData and paymentMethod to be provided |
Response codes specific for transactions using Optimize Standalone
| Code | Message | Reason |
|---|---|---|
| V100 | Status provided for task completion is invalid | The status provided in the complete request is not valid. It must be either ACCEPTED, REJECTED or FLUSHED. |
| V194 | Advice transaction {transactionId} not found | The transaction id specified does not exist or is not a standalone transaction. |
| V195 | Merchant notification url is missing | The queue merchant notification URL has no default installation value and has not been supplied in the request. |
| V196 | Missing transaction id | The mandatory transaction id has not been supplied in the request. |
| V197 | Task already in terminal state | The Queue task that is being updated is already in a terminal state so the action cannot be performed. This will only be returned when the requested status is different to the current status of the task. |
| V213 | Card Update was rejected for Card Token Payment on Advice mode | Cards cannot be updated in Advice mode transactions. |
| V214 | Unsupported payment method for Standalone Optimize | A payment method must be supplied in the API request. |
| V215 | Unsupported payment method source | The payment method source for a card transaction was not valid. Valid payment method sources are: VISA_CHECKOUT, PAYCASH, PAYPAL, PAYPAL_ONE_TOUCH, PPRO, METACHARGE, APPLEPAY, GOOGLEPAY, SECPAY. |
| V322 | Unknown card usage type, valid usage types are [CREDIT, DEBIT]. | The card usage type must be one of those specified. |
| V323 | Unknown card category, valid categories are [CREDIT, DEBIT, ELECTRON, COMMERCIAL, BUSINESS, CORPORATE, PURCHASING, SIGNIA, WORLD, FLEET, MAESTRO_INTL, MAESTRO_UK, MAESTRO_UK_DOM, LASER] | The card category must be one of those specified. |
| V802 | The Standalone Optimize feature is not enabled for this account | Feature not enabled |
| A137 | Failed to communicate with fraud rules service | The rules service is currently unavailable so we are are unable to provide you with a decision. |
| A400 | No such transaction | The queue task associated with the given transaction id does not exist. |