Response codes

The first two characters in the response code from RapydGateway are listed on this page. Any additional characters returned should be omitted as they are only for monitoring purposes. For example, a common response code is 05-I and is listed below as 05. Retries
Retries should be kept to a minimum in all cases, but should never be attempted when Merchant advice code is either 01, 05 or 06.
The merchant advice code returned in the response should be used to determine the retry policy. Available Merchant advice codes can be seen on the bottom of this page.
Failure to follow these suggestions can result in fines. Response codes 00, 85 and 10 mean that the transaction was successful. Please note that this list of response codes is not exhaustive and only represents the most commonly encountered response codes. Any code not listed in the table below should be treated as an error code.

Acquirer reject and error codes

Code	Reason
A0	User cannot be authenticated or action was not authorized.
A1	Invalid Card acceptor identification code (MerchantXID).
A2	Invalid Category code.
A3	Invalid Terminal ID or Device ID.
A4	Invalid message ID.
A6	Invalid card expiration date.
A7	Invalid message UTC.
A8	Invalid Currency (TransCurrency or OriginalTransCurrency value is invalid or field is not allowed for TransType).
A9	Invalid Amount (TransAmount or OriginalTransAmount value is invalid or field is not allowed for TransType. TransFee invalid or not allowed for CategoryCode).
AA	Invalid Message type.
AB	Invalid Transaction type.
AC	Invalid Card type.
AD	Invalid 3DSecure data (e.g. CAVD missing or wrong length).
AE	Transaction rejected - wrong CardVD value (CVC2/CVV2).
AF	Invalid Card verification data.
AG	Invalid address verification data (AVSPostalCode or AVSStreetAddress).
AH	Invalid Cashback amount.
AJ	Invalid Card (wrong issuer BIN or inactive BIN range).
AO	Invalid Transaction xid.
AT	Invalid token data.
AI	Invalid Additional Data.
AK	Invalid Transaction date.
AL	Invalid Card sequence number.
AN	Invalid Transaction time.
AM	Invalid Terminal capability/type.
AP	Invalid Authorization code.
AQ	Invalid Track 2.
AZ	Invalid Character(s) in Input Data (not covered by any of the codes above). Can apply to MessageCode, TransactionId, LifeCycleId, TransitIndicator, MerchantVerificationValue or Mastercard Wallet Identifier.
AY	Unexpected error.
AR	Invalid 3DSecure electronic commerce fields.
AS	Invalid Icc data.
AV	Connection to Visa EU/Mastercard is temporarily unavailable. Resending after several seconds/minutes prevents a high load on the network.
AW	Time-out (authorization host received no response from Visa/Mastercard). Resending after several seconds/minutes prevents a high load on the network.
AX	Invalid Parameter.
A5	Card details not found with the information provided.
F0	Invalid format of payment facilitator id

Transaction related reject codes

Code	Reason
T0	Unable to locate previous message.
T1	Previous message located, but the reversal data are inconsistent with original message.
T2	No action taken (authorization already finalized).
T3	Duplicate transaction.
T4	Unable to confirm online pin.
T5	Initiation reason missing or invalid.
T6	Initiator missing or invalid.
T7	Dynamic Currency Conversion (DCC) not allowed on card.
T8	SCA exemption failed validation or exemption not allowed on transtype.
T9	TransStatus not allowed for transaction.
TA	Unsupported BIN.
TB	Acquirer declined SCA exemption.
TC	Transaction being reversed was declined by the acquirer. No need to reverse.
TD	Balance inquiry request must contain a zero amount.
TE	Invalid receiving account bin for OCT.
TG	Missing mandatory values for MoneyTransfer.

Merchant related reject codes

Code	Reason
M0	Merchant ID not found.
M1	Merchant account closed.
MJ	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MI	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MH	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
ME	Sub-merchant account closed.
M2	Terminal ID not found.
M3	Terminal closed.
M5	Invalid currency.
M4	Invalid category code.
M6	Missing CVV2/CVC2.
M7	CVV2 not allowed.
M8	Merchant not registered for Verified by Visa/Secure Code.
M9	Merchant not registered for Amex.
MY	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MZ	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MA	Transaction not permitted at terminal.
MB	Agreement and terminal are not related.
MC	Invalid processor ID.
MD	Invalid merchant data (Name, City or Postal Code).
MF	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MG	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MK	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
ML	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MM	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MN	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MO	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MP	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MQ	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MR	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MS	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MT	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MU	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MV	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MW	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.
MX	Reserved for future use, however, processors/merchants should be prepared to receive them and interpret them as declined. Rapyd may introduce new codes with short notice if necessary.

Processor/Rapyd related response codes

Code	Reason
AU	Acquirer unavailable.
B2	Unable to fetch virtual card data.
B3	Unexpected error when fetching virtual card data.
B4	Initiator or initiator reason does not match with the virtual card found.
B5	Merchant initiated virtual cards are not allowed to perform this operation.
P1	Merchant initiated transactions can not be authorized with 3dSecure data.
P4	Cavd validation failed for SCA card where full authentication was requested.
PN	Payout is not allowed to merchant.
PP	Processing communication error.
Q1	Origin host name could not be retrieved or it's not allowed.
Q2	Payment can not be completed because call to payment system failed.
Q3	Sending of success payment notification failed for the provided webhook endpoint.
Q4	Cardholder was not successfully 3DSecure authenticated.
Q5	Gift cards can not be 3D secure authenticated.
Q6	Token amount and currency value are not equal with values from request.
Q7	Payment was reversed since virtual card creation was unsuccessful.
S2	Merchant data was not found.
S3	Unexpected error occured when fetching merchant data.
UB	It is not possible to get updated account for this bin at this time.
UD	Account was found but insufficient card data was provided.
UI	Internal Service Error while updating account.
UM	Transaction ID and Transaction Date must be supplied for Rapyd issued cards.
UN	No updated account was found for the given card number.
V2	The ResponseDescription may vary depending on the error that occurred. Please check the text for further information. Resending after several seconds/minutes prevents a high load on the network.
V3	Card was not fully authenticated and therefore virtual card can not be created.
X1	DCC approved.
X2	DCC Transaction not allowed to Cardholder.
X3	DCC Cardholder currency not supported.
X4	DCC Exceeds time limit for withdrawal (too late).
X5	DCC Transaction not allowed to terminal equipment.
X6	DCC not allowed to merchant.
X7	DCC Unknown error.
P3	Unexpected error when performing payment.
3X	This card falls under the SCA (Strong customer authentication) mandate and 3D Secure authentication is required.
V1	Success creating/fetching merchant virtual card.
RX	There was a problem with the virtual card payment batch and was forced to retry later. PAYOUT can not be retried in virtual card payment batches under any circumstances. This is a rare case and there is a chance that the payout is actually complete but authorization data was not saved properly with the transaction. When receiving this response code we recommend the merchant contacts Rapyd immediately before taking further action.
Q8	Decryption of Google Pay token was successful. Please proceed with Card verification followed by Card payment.
Q9	Decryption of Google Pay token was unsuccessful. Please verify token and try again.

Get batch report response codes

Code	Reason
D1	Success response code.
D2	Batch report is not yet available for this batch ID. Please try again later.
D3	The batch with this batch ID has been deleted.
D4	The batch with this batch ID has been created from incoming batch file, saved to our database and is awaiting transaction authorization. A batch usually does not have this status for a long time, but it can be delayed in case of extreme traffic or communication problem.
D5	The batch with this batch ID has not yet been finalized and is being prepared for the transaction authorization process.
D6	The batch with this batch ID is currently undergoing the transaction authorization process. Rapyd authorization process is usually very fast and so the batches do not have this status for very long. In case there is a problem then the batch will pause the authorization process for a time before retry, during that time the batch will hold this status.
D7	The batch with this batch ID has expired. The system never managed to create or finalize the batch properly, and so it was marked as expired after a few days of inactivity. In the rare case this happens we suggest to merchants to try creating the batch again.
D8	A batch file has been received by our system and will soon be validated and (if successfully validated) converted into an actual batch that is due for transaction authorization.
D9	The batch file has been successfully converted into an actual batch that is due for transaction authorization.
D0	The batch file has been successfully validated and will soon be converted into an actual batch that is due for transaction authorization.
DA	A batch (converted from a validated batch file) has been successfully saved to our database.
DB	A batch (converted from a validated batch file, and successfully saved to the database) has been successfully submitted for transaction authorization.
DC	There was a problem converting the incoming batch file into an actual batch. Please contact Rapyd support for more information.
DD	The batch file is invalid and can not be converted into an actual batch for transaction authorization. Information on why the batch failed will be delivered to the merchant notification email and/or webhook.
DE	The was a problem when submitting a batch for transaction authorization. Please contact Rapyd support for more information.
DF	The batch was successfully converted from a batch file to an actual batch, but there was a problem saving the batch to our database. Please contact Rapyd support for more information.
DG	There was an communication error between Rapyd internal systems, please try again later or contact Rapyd support if the problem persists.
DH	No batch with this batch id was found. Please make sure you have entered the correct batch id.
DI	The merchant agreement number provided does not have permission to access this batch. Batch reports can only be accessed with the merchant agreement number they were created with. Make sure you have the correct API key.

3D Secure response codes

Code	Reason
C1	3DSecure verification was a success.
C2	3DSecure verification failed, merchant is not enrolled in 3DSecure.
C3	3DSecure verification failed, unable to validate card.
C4	3DSecure verification failed, could not determine card type.
C5	3dSecure MPI is unreachable at the moment, please contact Rapyd support for more information or try again later. Resending after several seconds/minutes prevents a high load on the network.
C6	3dSecure authentication request was rejected by MPI, please contact Rapyd support for more information.
C7	3dSecure MPI returned insufficient data to proceed with authentication, please contact Rapyd support for more information or try again later.
C8	The card does not support 3DSecure.

Push/Pull Funds response codes

Please note that these codes are the ones that are push/pull funds specific and not an exhaustive list. All other response codes in this document can be returned when pushing/pulling funds.

Code	Reason
O1	Card type could not be determined.
O2	Push/Pull funds payment is not supported for Amex cards.
O3	The transaction timed out. Wait an appropriate amount of time and then call the query endpoint.
O4	The API detected a duplicate transaction. Use query endpoint to get details of the original transaction.
O5	The message contains an invalid Primary Account Number (PAN).
O6	Unexpected error. Please contact Rapyd support.
O7	Successfully queried information about transaction.
O8	Merchant is not correctly set up for using PushFunds. Please contact Rapyd support for more information.
O9	SenderData is required for this transaction.
OA	RecipientData is required for cross-border transactions.
OB	Merchant not allowed to pull or push funds
OD	The transaction type is not supported for this card type.
OE	No transaction is found for the specified input parameters. Original transaction can be sent again via Push Funds endpoint.
OF	This card does not support domestic money transfers
OG	This card does not support cross border money transfers
OH	This card does not support domestic gambling payouts
OI	This card does not support cross border gambling payouts
OJ	This card does not support domestic non money transfers
OK	This card does not support cross border non money transfers

Response codes for Visa transactions

Code	Reason
N0	Force STIP.
N3	Cach service not available.
N4	Cashback request exceeds Issuer limit.
N7	Decline for CVV2 failure.
N8	Transaction amount exceeds pre-authorized approval amount.
P2	Invalid biller information.
P5	PIN change/unblock request declined.
P6	Unsafe PIN.
Q1	Card authentication failed. Or offline PIN authentication interrupted.
R0	Stop Payment Order.
R1	Revocation of Authorization.
R3	Revocation of All Authorizations.
XA	Forward to issuer.
XD	Forward to issuer.
Z3	Unable to go online.
00	Approval.
01	Refer to card issuer.
1A	Additional customer authentication required.
02	Refer to card issuer, special condition.
03	Invalid merchant or service provider.
04	Pickup card.
05	Do not honor.
06	Error.
07	Pick up card, special condition (other than lost/stolen card).
10	Partial Approval.
11	V.I.P Approval.
12	Invalid transaction.
13	Invalid amount (currency conversion field overflow) or amount exceeds maximum for card program.
14	Invalid account number (no such number).
15	No such issuer.
19	Re-enter transaction.
21	No action taken (unable to back out prior transaction).
25	Unable to locate record in file, or account number is missing from the inquiry.
28	File is temporarily unavailable.
39	No credit account.
41	Pickup card (lost card).
43	Pickup card (stolen card).
46	Closed account.
51	Insufficient funds.
52	No checking account.
53	No savings account.
54	Expired card.
55	Incorrect PIN.
57	Transaction not permitted to cardholder.
58	Transaction not allowed at terminal.
59	Suspected fraud.
61	Activity amount limit exceeded.
62	Restricted card (e.g. in Country Exclusion table).
63	Security violation.
64	Transaction does not fulfill AML requirement.
65	Activity count limit exceeded.
70	PIN Data Required.
75	Allowable number of PIN-entry tries exceeded.
76	Unable to locate previous message (no match on transaction ID).
77	Previous message located, but the reversal data are inconsistent with original message.
78	'Blocked, first used' - Transaction from new cardholder, and card not properly unblocked.
79	Transaction reversed.
80	Visa transactions: credit issuer unavailable. Private label: invalid date.
81	PIN cryptographic error found (error found by VIC security module during PIN decryption).
82	Negative Online CAM, dCVV, iCVV, or CVV results or offline PIN authentication interrupted.
85	No reason to decline a request for Account Number verification, address verification or CVV2 verification.
86	Cannot Verify PIN.
91	Issuer unavailable or switch inoperative (STIP not applicable or available for this transaction). Resending after several seconds/minutes prevents a high load on the network.
92	Financial institution or intermediate network facility cannot be found for routing. Resending after several seconds/minutes prevents a high load on the network.
93	Transaction cannot be completed; violation of law.
94	Duplicate transaction.
96	System malfunction. Resending after several seconds/minutes prevents a high load on the network.

Response codes for MasterCard transactions

Code	Reason
00	Approved or completed successfully.
01	Refer to card issuer.
03	Invalid merchant or service provider.
04	Capture card.
05	Do not honor.
06	Error.
08	Honor with ID.
10	Partial Approval.
12	Invalid transaction.
13	Invalid amount.
14	Invalid card number.
15	Invalid issuer.
30	Format error.
41	Lost card.
43	Stolen card.
51	Insufficient funds/over credit limit.
54	Expired card.
55	Invalid PIN.
57	Transaction not permitted to cardholder.
58	Transaction not permitted to acquirer/terminal.
61	Exceeds withdrawal amount limit.
62	Restricted card.
63	Security violation.
65	Additional customer authentication required (formerly: Exceeds withdrawal count limit).
70	Contact Card Issuer.
71	PIN not changed.
75	Allowable number of PIN-entry tries exceeded.
76	Invalid/nonexistent 'To Account' specified.
77	Invalid/nonexistent 'From Account' specified.
78	Invalid/nonexistent account specified.
79	Lifcycle related.
81	Domestic debit transaction not allowed.
82	Policy related.
83	Fraud/Security related.
84	Invalid authorization life cycle.
85	Not declined (Valid for all zero amount transactions).
86	PIN validation not possible.
87	Purchase amount only, no cash back allowed.
88	Cryptographic failure.
89	Unacceptable PIN.
91	Authorization system or issuer inoperative. Resending after several seconds/minutes prevents a high load on the network.
92	Unable to route transaction. Resending after several seconds/minutes prevents a high load on the network.
94	Duplicate transaction detected.
96	System error. Resending after several seconds/minutes prevents a high load on the network.

Response codes for Amex transactions

Code	Reason
00	Approval.
1A	Additional customer identification required.
05	Do not honor.
10	Partial Approval.
13	Invalid amount.
14	Invalid account number (no such number).
30	Format error.
54	Expired card.
55	Incorrect PIN.
75	Allowable number of PIN tries exceeded.
91	Issuer unavailable. Maybe retried. Resending after several seconds/minutes prevents a high load on the network.
96	System error. Resending after several seconds/minutes prevents a high load on the network.

Response codes for Apple Pay register merchant and get session

Code	Reason
W0	Success
W1	Error registering Apple Pay merchant.
W2	Error getting Session from Apple Pay.

Merchant Advice Codes

Additional information, if available, for the merchants on when and how to retry a declined transaction.

Code	Reason
01	Do not try again
02	Try again later
03	Update account information
04	Retry using authentication
05	Suspected fraud, do not try again
06	Payment cancellation, do not try again
07	Merchant does not qualify for product code
08	Retry after 1 hour
09	Retry after 24 hour
10	Retry after 2 days
11	Retry after 4 days
12	Retry after 6 days
13	Retry after 8 days
14	Retry after 10 days
15	The issuer recognizes the product as a consumer non-reloadable prepaid card
16	The issuer recognizes the product as a consumer single-use virtual card number
17	Token requirements not fulfilled for this token type
18	Negotiated value not approved
19	Sanctions Scoring Service: Score Exceeds Applicable Threshold Value
20	Consumer multi use virtual card (Mastercard use only)

Common Address Verification Result codes

Code	Reason
X	Street address and 9-digit ZIP code both match
Y	Street address and 5-digit ZIP code both match
A	Street address matches, but both 5-digit and 9-digit ZIP Code do not match
W	Street address does not match, but 9-digit ZIP code matches
Z	Street address does not match, but 5-digit ZIP code matches
N	Street address, 5-digit ZIP code, and 9-digit ZIP code all do not match
U	Address information unavailable. Returned if non-US. AVS is not available or if the AVS in a U.S. bank is not functioning properly.
R	Retry - Issuers System Unavailable or Timed Out.
E	AVS data is invalid
S	U.S. issuing bank does not support AVS