Response Codes

The tables below outline all of our response codes and messages for our API and HPP solutions.

Search for response codes by code, error message or category:

Response Code	Response Message	Description
1	Transaction Success	Transaction has been authorised successfully.
11	Pending	Your `account_updater` / `pay_out` request is pending. You will receive the final outcome via webhook notification.
101	Declined	The customer's bank is unwilling to accept the transaction. The customer will need to contact their bank for more details regarding this generic decline.
102	Error:Invalid Parameters	One or more required values were not provided. Make sure requests include all required parameters.
103	Error:Invalid or Inactive MID Info	This error generally occurs when you use invalid MID credentials to process payments. More often than not it's because QA credentials are being used to target production or vice versa. However, it could indicate a connectivity or setup issue. Contact support@acquired.com for more information.
104	Error:Invalid or Unsupported Transaction Type	You have attempted to process a `transaction_type` that may be misspelled, contains invalid characters or has not been configured on your account. Please contact support@acquired.com.
105	Error:Invalid or Unsupported Currency	There may be an issue with the configuration of your account for the currency you are attempting to process. Contact support@acquired.com for more information.
106	Error:Invalid or Unsupported Card Type	The card type which the cardholder is using to process their transaction has not been configured to be accepted on your account or is unsupported by our gateway. Contact support@acquired.com for more information regarding this issue.
107	Error:Incorrect Hash String	The `request_hash` generated in the request message does not match the hash value on our side or there is an issue with your hash calculation. Please refer to the necessary integration documentation or contact support@acquired.com for more information.
108	Blocked:Unauthorized Merchant IP Address	As a safety precaution, we block any traffic that originates from any IP address that is not whitelisted on your account. If you are receiving this error, please contact support@acquired.com.
109	Error:Invalid timestamp	There is an error with the `timestamp` in your request message - please check this parameter for the issue.
110	Error:Invalid merchant_order_id	The `merchant_order_id` provided contains invalid characters or is the incorrect length.
111	Error:Invalid Company Info or Company Level Post Not Supported	There is an issue with the `company_id` or the `company_mid_id` values being passed through in your request. Please contact support@acquired.com for more information regarding this.
112	Error:Can Not Find Qualified MID for Company Level Post	There is an issue with the `company_mid_id` value being passed through in your request. Please contact support@acquired.com for more information regarding this.
151	Blocked:Max MID Amount Reached	The maximum amount configured for the MID you are attempting to process through has been reached. Contact support@acquired.com if you are receiving this error.
152	Blocked:Max MID Post Reached	The maximum number of posts configured on your MID has been reached and any further traffic processed against this MID will be blocked. Either update the MID details in your request to another or contact support for help in resolving this issue.
153	Blocked:Max Monthly MID Reached	The maximum amount successfully processed for this month via this MID has been reached. Contact support@acquired.com if you are receiving this error.
154	Blocked:Max Monthly MID Post Reached	The maximum number of posts against this MID for the month has been breached and any further transactions processedagainst this MID will be blocked. Either update the MID details in your request to another or contact support@acquired.com to help resolve this issue.
155	Blocked:Max Daily MID Amount Reached	The maximum amount permitted to be processed on a daily basis has been breached for this MID. Any further transactions processed against this MID will be blocked for the rest of the day. Either update the MID details in your request to another, wait until tomorrow to continue processing or contact support@acquired.com for help in resolving this issue.
156	Blocked:Max Daily MID Post Reached	The maximum number of posts permitted to be processed on a daily basis has been breached for this MID. Any further transactions processed against this MID will be blocked for the rest of the day. Either update the MID details in your request to another or contact support@acquired.com for help in resolving this issue.
157	Blocked:Max Single MID Amount Reached	The maximum amount (per transaction) configured on this MID has been breached. Reduce the amount that you are trying to process in future transaction attempts or contact support@acquired.com for help in resolving this issue.
158	Blocked:Min Single MID Amount Not Reached	The minimum amount (per transaction) configured on your MID has not been breached. Increase the amount that you are trying to process in future transaction attempts or contact support@acquired.com for help in resolving this issue.
159	Blocked:Max Daily Refund Count Reached	The maximum number of refunds (per day) configured against this MID has been breached. Any further refund attempts processed against this MID will be blocked for the rest of the day. Please contact support@acquired.com for help in resolving this issue.
160	Blocked:Max Daily Refund Amount Reached	The maximum amount you can refund (per day) has been breached against this MID. Any further refund attempts processed against this MID will be blocked for the rest of the day. Please contact support@acquired.com for help in resolving this issue.
161	Blocked:Max Montlhy Refund Count Reached	The maximum number of refunds you can refund (per month) has been breached against this MID. Any further refund attempts processedagainst this MID will be blocked for the rest of the month. Please contact support@acquired.com for help in resolving this issue.
162	Blocked:Max Monthly Refund Amount Reached	The maximum amount you can refund (per month) has been breached against this MID. Any further refunds attempted via this MID will be blocked. Please contact support for help in resolving this issue.
170	Blocked:Max IP Daily Post	The maximum number of posts (per day) from the same IP address has been breached against this MID. Any further attempts originating from the same IP address will be blocked for the rest of the day. Either update the MID details in your request to another, wait until tomorrow to continue processing or contact support@acquired.com for help in resolving this issue.
171	Blocked:Max IP Monthly Post	The maximum number of posts (per month) from the same IP address has been breached against this MID. Any further attempts originating from the same IP address will be blocked for the rest of the month. Either update the MID details in your request to another, wait until next month to continue processing or contact support@acquired.com for help in resolving this issue.
172	Blocked:Max Email Daily Post	The maximum number of posts (per day) from the same email address has been breached against this MID. Any further attempts from the same email address will be blocked for the rest of the day. Email Daily Post configured on your MID has been reached and any further payments processed through this MID with the same email address in the request will be blocked for the rest of the day. Either update the MID details in your request to another, wait until tomorrow to continue processing or contact support@acquired.com for help in resolving this issue.
173	Blocked:Max Email Monthly Post	The maximum number of posts (per month) from the same email address has been breached against this MID. Any further attempts from the same email address will be blocked for the rest of the month. Either update the MID details in your request to another, wait until next month to continue processing or contact support@acquired.com for help in resolving this issue.
174	Blocked:Max Phone Daily Post	The maximum number of posts (per day) from the same phone number has been breached against this MID. Any further attempts from the same phone number will be blocked for the rest of the day. Either update the MID details in your request to another, wait until tomorrow to continue processing or contact support@acquired.com for help in resolving this issue.
175	Blocked:Max Phone Monthly Post	The maximum number of posts (per month) from the same phone number has been breached against this MID. Any further attempts from the same phone number will be blocked for the rest of the month. Either update the MID details in your request to another, wait until next month to continue processing or contact support@acquired.com for help in resolving this issue.
201	Error:Invalid cardnumber	You have attempted to process a payment with an invalid `cardnumber`. Please ask the customer to correct their payment information and re-attempt the transaction - if the decline persists, the customer will need to contact their issuing bank.
202	Error:Card Type/Number Mismatch	The card type selected does not match the `cardnumber` provided. An example of this might be a Visa card type has been selected but a Mastercard `cardnumber` provided.
203	Error:Invalid cardcvv	The customer entered in an invalid `cardcvv` value or made a typo when inputting their card information. Have the customer attempt the transaction again – if the decline persists, the customer will need to contact their bank.
204	Error:Invalid or Expired cardexp	The card’s expiration month is incorrect. Check the expiration date or use a different card.
205	Error:Invalid cardholder_name	The `cardholder_name` parameter provided contains invalid characters or is too long. Please check the request message.
206	Error:Invalid billing_street	The `billing_street` parameter provided contains invalid characters or is the incorrect length.
207	Error:Invalid billing_city	The `billing_city` parameter provided contains invalid characters and / or is the incorrect length.
208	Error:Invalid billing_state	The `billing_state` parameter provided contains invalid characters and / or is the incorrect length.
209	Error:Invalid billing_zipcode	The `billing_zipcode` parameter provided contains invalid characters and / or is the incorrect length.
210	Error:Invalid billing_country_code_iso2	The `billing_country_code_iso2` parameter provided contains invalid characters and / or is the incorrect length.
211	Error:Invalid billing_phone	The `billing_phone` parameter provided contains invalid characters and / or is the incorrect length.
212	Error:Invalid_email	The `billing_email` parameter provided contains invalid characters and / or is the incorrect length.
213	Error:Invalid_fname	The `customer_fname` parameter provided contains invalid characters and / or is the incorrect length.
214	Error:Invalid_lname	The `customer_lname` parameter provided contains invalid characters and / or is the incorrect length.
215	Error:Invalid Amount	The `amount` parameter submitted in the request is incorrectly formatted, contains invalid characters and / or is the incorrect length.
216	Declined:Invalid AVS	The customers issuing bank has declined the transaction based on the AVS outcome.
217	Declined:Incorrect PIN	The pin code entered by the cardholder is incorrect. N / A to ECOM / MOTO payments.
218	Declined:Payment Account Not Found	The customer no longer has an account with the bank which they / you are trying to process the payment through. Please contact the customer and ask them to provide different payment details.
219	Error:Invalid customer_dob	The `customer_dob` parameter provided contains invalid characters and / or is the incorrect length.
220	Blocked:MCC Data Required	If your MCC code is 6012, 6051 or 7299 you are required to pass through certain data fields in every request - `customer_lname`, `customer_dob` and `billing_zipcode` - please ensure you are passing these values within the request and re-try. These MCC's relate to credit-related activities - if you are unsure what your MCC is, please contact support@acquired.com.
221	Error:Invalid shipping_street	The `shipping_street` parameter provided contains invalid characters and / or is the incorrect length.
222	Error:Invalid shipping_street2	The `shipping_street2` parameter provided contains invalid characters and / or is the incorrect length.
223	Error:Invalid shipping_city	The `shipping_city` parameter provided contains invalid characters and / or is the incorrect length.
224	Error:Invalid shipping_state	The `shipping_state` parameter provided contains invalid characters and / or is the incorrect length.
225	Error:Invalid shipping_zipcode	The `shipping_zipcode` parameter provided contains invalid characters and / or is the incorrect length.
226	Error:Invalid shipping_country_code_iso2	The `shipping_country_code_iso2` parameter provided contains invalid characters and / or is the incorrect length.
227	Error:Invalid shipping_phone	The `shipping_phone` parameter provided contains invalid characters and / or is the incorrect length.
228	Error:Invalid shipping_email	The `shipping_email` parameter provided contains invalid characters and / or is the incorrect length.
229	Error:Invalid billing_street2	The `billing_street2` parameter provided contains invalid characters and / or is the incorrect length.
230	Error:Invalid customer_ipaddress	The `customer_ipaddress` parameter provided contains invalid characters and / or is the incorrect length.
231	Error:Invalid subscription_type	The `subscription_type` parameter provided contains invalid characters and / or is the incorrect length and therefore does not match those offered by our system.
232	Error: MID Does Not Support Subscription	The `original_transaction_id` value for this transaction was processed without any recurring functionality. Please contact support@acquired.com.
233	Error:Original Transaction Not Subscription or Not Approved	The original_transaction_id value for this transaction was processed without any recurring functionality. Please contact support@acquired.com.
234	Error:Subscription Initialization Info Failed	There is an issue with your initial transaction (INIT). Please contact support@acquired.com.
235	Error:Subscription Info Retrieval Failed	There has been an issue with your request message - please contact support@acquired.com.
236	Error:Subscription Info Update Failed	There has been an issue with your request message - please contact support@acquired.com.
251	Declined:Fraudulent	The card used in this transaction has been flagged as Fraudulent by the issuing bank. Please re-try the payment with a different card.
252	Blocked:Card Blacklisted	The `cardnumber` attempted is on your blacklist. If you want to let this payment go through, please contact support@acquired.com.
253	Blocked:Phone Blacklisted	The customer’s phone number attempted is on your blacklist. If you want to let this payment go through, please contact support@acquired.com.
254	Blocked:Email Blacklisted	The customer’s email address attempted is on your blacklist. If you want to let this payment go through, please contact support@acquired.com.
255	Blocked:IP Address Blacklisted	The customer’s IP address attempted is on your blacklist. If you want to let this payment go through, please contact support@acquired.com.
256	Blocked:BIN Blacklisted	You have attempted to process a card that is blocked on your account. Please contact support@acquired.com.
257	Blocked:Fraud Risk Score Exceeded	Authorisation request has been rejected by your fraud solution.
258	Blocked:Fraud Check Unavailable	You have attempted to process a card that is blocked on your account. Please contact support@acquired.com.
261	Error:Invalid Original Transaction ID, Type or Status	There is an issue with the `original_transaction_id` used in your request. Please contact support@acquired.com.
262	Error:Order ID Already Processed and/or Approved	The `merchant_order_id` value passed through within the request message has already been processed. Please ensure that the `merchant_order_id` used is unique.
263	Error:Original Transaction Already Settled, can not Void	The transaction you are attempting to VOID has already settled. Please process a REFUND request instead.
264	Error:Original Transaction Not Settled Yet, can not Refund	The transaction you are attempting to REFUND has not yet settled. Please process a VOID request instead.
265	Error:Original Transaction too old, can not Void, Capture or Refund	The transaction you are attempting to VOID / CAPTURE or REFUND is too old. Please arrange for an alternative method of payment with your customer.
266	Error:Original Transaction Amount Exceeded for Refund	Your Acquired.com account is not set up to refund amounts higher than the original transaction amount. Contact our Support team for information on how to enable this.
267	Error:Original Transaction Already Captured	The submitted transaction appears to be a duplicate of a previously submitted transaction and was declined to prevent charging the same card twice for the same service.
268	Error:Original Transaction already Voided	The charge you’re attempting to void has already been voided. Update the request to use the ID of a charge that has not been voided already.
269	Error:Original Transaction Not Found	We were unable to locate the original transaction ID which you are attempting to process a recurring payment against. Update your original_transction_id to match one that can be found in our database.
270	Blocked:Max Refund Count Reached	Based on your configuration, you have processed the maximum number of refunds. Please contact support@acquired.com.
271	Error:Original Transaction Already Refunded	The charge you’re attempting to refund has already been refunded. Update the request to use the ID of a charge that has not been refunded.
272	Error:Capture Amount Greater Than Original Authed	You have attempted to CAPTURE more funds that you have authorised against the customers account. Please check the `amount` parameter within your request message.
273	Error:Partial Capture of Auth Not Allowed	You have attempted to CAPTURE less than you have authorised against the customers account. Please check the `amount` parameter within your request message.
274	Error:This Merchant Order ID is Being Processed	The `merchant_order_id` is currently being processed and you have duplicated the request message.
275	Blocked:Original Transaction Already ChargedBack	The charge you’re attempting to refund has been charged back. Check the disputes documentation to learn how to respond to the dispute.
276	Error:Original Transaction is Being Updated	The `original_transaction_id` used in your request message is still being processed. Please re-attempt at a later time.
277	Blocked:Cancellation Requested	The customer requested the cancellation of a recurring transaction or subscription – reach out to them for more information.
301	Declined:Insufficient Funds	The account did not have sufficient funds to cover the transaction amount at the time of the transaction – subsequent attempts at a later date may be successful.
302	Blocked:Max Amount Exceeded	The maximum amount set to be processed on your MID has been reached and as a result has been rejected. Either reduce the amount you are trying to process, or contact support for help in resolving this issue.
311	Blocked:Max Attempts Against Card Exceeded	You have reached the maximum number of authorised or declined attempts to process against any single card which has been configured on your account and, as a result has been rejected. Contact support for help in resolving this issue.
312	Blocked:Max Attempts Authorised Card Exceeded	You have reached the maximum number of authorised attempts to process against any single card which has been configured on your account and as a result has been rejected.
321	Declined:Revocation of Order by Cardholder	The cardholder has ordered their issuing bank to decline all future attempts by the merchant. Contact the customer and ask them to contact their bank to remove the block, update their billing details to a new card and cancel the user’s subscription and subsequent attempts against the card.
322	Blocked:Cardholder Cancellation	The customer requested a cancellation of a single transaction – reach out to them for more information.
323	Declined:Restricted Card	The customer's card issuer has declined the transaction as the credit card has some restrictions. The customer should use an alternate credit card, or contact their bank.
324	Declined:CVV Failure	The customer entered in an invalid security code or made a typo in their card information. Have the customer attempt the transaction again – if the decline persists, the customer will need to contact their bank.
325	Declined:Card Expired	Card is expired. The customer will need to use a different payment method.
351	Blocked: 3DS Failed	The customer's bank declined the transaction because a 3D Secure authentication was not performed during checkout. Have the customer authenticate using 3D Secure, then attempt the authorization again.
401	Declined:Fraudulent	The card payment has been declined by the customer’s issuing bank as fraudulent. Please contact the customer to retrieve alternative card details.
402	Declined:Lost or Stolen Card	The submitted card has expired or been reported lost and a new card has been issued. Reach out to your customer to obtain updated card information.
403	Declined:Suspected Fraud	The customer’s bank suspects fraud – recommended to reject the transaction.
404	Declined: Fraudulent Bank Block	The card payment has been declined by the customer’s issuing bank as fraudulent. Please contact the customer to retrieve alternative card details.
405	Blocked:BIN Filter (Type)	A BIN filter configured on your account has blocked the transaction, in this case on a card type level i.e. VISA, Mastercard etc. For more information please see here.
406	Blocked:BIN Filter (Level)	A BIN filter configured on your account has blocked the transaction, in this case on a card level i.e. Prepaid, Corporate etc. For more information please see here.
407	Blocked:BIN Filter (Country)	A BIN filter configured on your account has blocked the transaction, in this case on a Country level i.e. United Kingdom, South Africa etc. For more information please see here.
408	Blocked:BIN Filter (Bank)	A BIN filter configured on your account has blocked the transaction, in this case on a Bank level i.e. Natwest, Barclays etc. For more information please see here.
501	Pending:Card Enrolled	The cardholder is enrolled for 3-D Secure, continue to redirect them to the ACS page.
521	Blocked:3DS Invalid Action	There is an issue with your 3-D Secure request message. Please send any information you have to the support team.
522	Blocked:3Ds - Invalid PaRes	The `PaRes` parameter is invalid. Please send information you have on this transaction to the support team.
523	Blocked:3DS Invalid XID	The `XID` parameter is invalid. Please send information you have on this transaction to the support team.
524	Blocked:3DS Invalid CAVV	The `CAVV` parameter is invalid. Please send information you have on this transaction to the support team.
525	Blocked:3DS Not Active	3-D Secure is not active on your account. Please contact support@acquired.com.
526	Blocked:3DS Card Not Enrolled	The card which your customer is attempting to pay with is not enrolled for 3-D Secure. Please contact the customer and ask them to try with another card or for them to contact their bank and have them enroll the card in the 3-D Secure program.
527	Blocked:3DS Unable to Verify Enrollment	We are currently unable to establish whether your customer’s card is enrolled for 3-D Secure. Please re-attempt the payment.
528	Blocked:3DS ACS URL Unavailable	The customer’s issuing bank is currently unable to re-direct your customer to their authentication page to complete the 3-D Secure process. Please re-attempt the payment.
529	Blocked:3DS Invalid Response	We received an invalid response from the customer’s issuing bank and are unable to complete 3-D Secure authentication. Please re-attempt the payment.
530	Blocked:3DS Password Failure	The customer entered in an incorrect 3-D Secure password and as such, this transaction is declined.
531	Blocked:3DS ACS Failure	There is an issue with the customer’s issuing bank authentication page, we would recommend to re-attempt the payment at a later time.
532	Blocked:3DS Unavailable	The customer’s issuing bank is currently unable to authenticate their customers using 3-D Secure, we would recommend to re-attempt the payment at a later time.
533	Blocked:3DS Fatal Error	An error has occurred during the 3-D Secure v1 process and the cardholder can't be authenticated. Please try again.
534	Blocked:3DS Original Transaction Not 3DS	For gaming customers, if you want to process a CREDIT request sometimes the first time you store the card you will need to use 3-D Secure. If you didn't you will get this response code back.
540	SCA: Failed	EMV 3-D Secure was attempted but the cardholder failed to authenticate themselves.
541	SCA: Not Successful	EMV 3-D Secure was attempted but sadly hasn't been successful this time. Ask the customer to try with a different card.
542	SCA: Issuer Rejected	EMV 3-D Secure has been attempted but the issuing bank has rejected the authentication request. Ask the customer to try with a different card.
550	SCA Field (field_name)	There is an issue with one or more of the fields in your request, you will find the field name(s) in the response_message field.
565	SCA Required	Soft Decline - Strong Customer Authentication is required. Please resubmit the transaction using EMV 3DS. For more information see our Soft Decline guide.
901	System error	Something has gone wrong on our side, we apologise. Please try to process again and if the problem continues reach out to support.
902	System error:Networking error	Something has gone wrong on our side, we apologise. Please try to process again and if the problem continues reach out to support.
903	System error:HTTP error	Something has gone wrong on our side, we apologise. Please try to process again and if the problem continues reach out to support.
904	System error:DB error	Something has gone wrong on our side, we apologise. Please try to process again and if the problem continues reach out to support.
905	System error:Post to bank timeout	We got your request and passed it on to the bank but sadly never heard back from them. Our alerting has let us know and we'll get in contact with them. If the problem persists please reach out to support to let us know.
906	System error: Encryption failure	Something has gone wrong along the road to making your transaction as secure as possible. Our internal alerting has let us know and we're working to fix the problem, but you should just try again it is probably a once off.
907	System error:Too Many Simultaneous Transactions	It is incredibly unlikely but you may have exceeded our recommended throughput, please contact support.
908	System error:Invalid Issuing Bank Response	The response we received back from the bank didn't look right. Don't worry, it generated an alert in our system and we're looking into the reason. We recommend trying again, if the problem persists contact support.
909	System error:Invalid Acquirer Response	The response we received back from the Acquirer didn't look right. Don't worry, it generated an alert in our system and we're looking into the reason. We recommend trying again, if the problem persists contact support.
999	System Maintenance	A well run service needs routine maintenance. Without regular system maintenance, updates would go uninstalled, bugs would go unsquashed, patches would go … unpatched. We sincerely apologize if you're encountering this error without having received prior notice. You can view the status of our various systems by clicking here.