Appendix A

Adyen Fault Cases

FC1) “5 001 - ApplePay token amount-mismatch”

A mismatch occurred between the amount in the payment request and the amount in the
ApplePay token due to a rounding problem. A one cent difference is detected where the
payment request amount is, e.g., 72.20, while the amount in the ApplePay token is 72.21.

FC2) “110 - BankDetails missing” (1)

Due to missing response data from a third party payment method, recurring payments for
a specific bank and payment method are failing. In this case Adyen resorts to a backup
mechanism, which is unsuccessful and causes an internal error.

FC3) “110 - BankDetails missing” (2)

Bank details are required when storing details for shopper payouts in case there is no credit
card information supplied. The bank details are missing in the request, hence this error is
returned.

FC4) “131 - Billing address problem (City)”

The city name is a required field of the billing address. This value is not supplied.

FC5) “134 - Billing address problem (Country 0 invalid)” (1)

The country code should be a valid value ISO 2-character country code. This error is re-
turned because the value is missing.

FC6) “134 - Billing address problem (Country 0 invalid)” (2)

The country code should be a valid value ISO 2-character country code. This error is re-
turned because it does not conform to the standard.

95
A. A DYEN FAULT C ASES

FC7) “135 - Billing address problem (StateOrProvince)”

A valid 2-character abbreviation for the state or province is required for the United States
and Canada. This value was not supplied causing this error.

FC8) “132 - Billing address problem (Street)”

The street name is a required field of the billing address. This value is not supplied.

FC9) “128 - Card Holder Missing”

The name of the card holder is required field. In case this value is missing this error is
returned.

FC10) “0 - Configuration Problem mpiImplementation”

3D secure authorize calls require a payment authorization response from the issuer and a
payment session identifier. Requests that do not contain these values fail with this error.

FC11) “800 - Contract not found” (1)

This error occurs when one attempts to disable a shopper contract that has been disabled in
the past. The reference associated with the contract thus not found.

FC12) “800 - Contract not found” (2)

This error is caused by an internal database replication delay. When a recurring contract is
created it takes a few minutes to be replicated to the slaves. If the contract is requests before
replication the request fails with this error.

FC13) “800 - Contract not found” (3)

Attempting to use a recurring contract in combination with a payment method that does
not support recurring payments results in this error. At the moment of writing Bancontact
does not support this functionality there causing errors for merchants attempting recurring
Bancontact payments.

FC14) “0 0 - Could not read XML stream..”

The values are not URL-encoded causing a failure in the XML parsing. The ampersand sign
should be URL-encoded as ‘&amp,

FC15) “0 - Couldn’t parse expiry year”

The expiry year, which is part of the credit card information, cannot be parsed to an integer.
This happens when it contains letter or other non-digit characters. E.g., ‘20/2 cannot be
parsed, in contrast to the likely intended ‘2012.

96
FC16) “103 - CVC is not the right length”
The credit card CVC code is not the expected length. Generally the code consists of three
digits, with American Express cards being the exception with four digits.

FC17) “0 - CVC is required for OneClick card payments”

The credit card CVC code is required for OneClick card payments for which the credit card
details are already stored. This value is however missing in the request.

FC18) “0 - Double processing”

This error occurs when a 3D authorize request is submitted more than once. The request
has already been processed, hence an error is returned.

FC19) “172 - Encrypted data used outside of valid time period” (1)
The timestamp included is outside the valid time range. The timestamp is generated for the
end user, but the end user takes too long to initiate the request.

FC20) “172 - Encrypted data used outside of valid time period” (2)
The timestamp included is outside the valid time range. Either the timestamp is off by a
mistake on the server side, or the request is sent in for processing too late.

FC21) “0 - Expiry month not set”

The expiry month of the credit card is required in an authorization request. The value
is missing in the request. This error most often occurs in case all credit card details are
missing. This is because the expiry month is validated first.

FC22) “0 - Expiry month should be between 1 and 12 inclusive”

The expiry month should be a value between 1 and 12. The value in this case is lower than
1 or higher than 12, causing this error.

FC23) “0 - Expiry year should be a 4 digit number greater than 2000”

This error occurs when the expiry year of the credit card is not higher than 2000. When the
shopper does not fill in this year, some merchants default to 0, causing this error to occur.

FC24) “0 - iDEAL communication error”

The select iDEAL bank is not available. This can be because of planned maintenance or a
temporary connection problem.

97
A. A DYEN FAULT C ASES

FC25) “0 0 - internal Configuration Problem mpiImplementation”

3D secure authorize calls require a payment authorization response from the issuer and a
payment session identifier. Requests that do not contain these values fail with this error.

FC26) “903 - Internal error” (1)

This error is caused by a configuration mistake. The configuration key, required for install-
ments, is not found.

FC27) “903 - Internal error” (2)

For airlines additional airline data can be enabled to capture flight information such as the
leg data. This error is thrown when airline leg data is missing.

FC28) “903 - Internal error” (3)

Invoice payment requests require order lines and an invoice number. This error is returned
when either is missing.

FC29) “137 - Invalid amount specified” (1)

Captures are used to transfer money from one credit card account to another. The amount
specified for a capture request has to be higher than zero. A problem with this error occurs
when the amount is zero.

FC30) “137 - Invalid amount specified” (2)

Adyen offers the functionality to initiate a recurring contract by means of a zero amount au-
thorization call. However, the minimum amount of iDEAL transactions is one cent, causing
this error when a zero amount authorization call is made.

FC31) “137 - Invalid amount specified” (3)

An amount is invalid when it is below zero or higher than a specific limit. Transaction
requests containing an out of range amount result in this error.

FC32) “137 - Invalid amount specified” (4)

A refund request requires an amount higher than zero. Zero amount refund requests fail
with this error.

FC33) “101 - Invalid card number”

The supplied credit card number does not validate. It is either not the right length or does
not validate against the Luhn formula.

98
FC34) “153 - Invalid CVC”
The CVC code does not validate. In this case it contains non-digit characters, which are not
allowed.

FC35) “116 - Invalid date of birth”

For Open Invoice transactions the shopper has to be at least 18 years of age. This error is
returned if the shopper is younger.

FC36) “161 - Invalid iban” (1)

The IBAN supplied for the transaction does not have a valid length. The maximum length
is 34, but depends on the country.

FC37) “161 - Invalid iban” (2)

The country code supplied in the payment request has to match the country code of the
IBAN. In case of a mismatch this error is returned.

FC38) “161 - Invalid iban” (3)

The IBAN is required for SEPA Direct Debit transaction. This error is returned when the
IBAN is missing.

FC39) “901 - Invalid Merchant Account” (1)

In order for a merchant to capture an amount from a shoppers account Adyen requires the
merchant account to be included in the request. In case this field is missing the request is
rejected with this error.

FC40) “901 - Invalid Merchant Account” (2)

In order to process on Adyens platform the merchant account needs to be active. In this
case an inactive account is used to process payments, resulting in an error.

FC41) “901 - Invalid Merchant Account” (3)

To process payments the supplied merchant account has to exist. Requests result in an error
when an invalid account is used.

FC42) “105 - Invalid paRes from issuer” (1)

3D secure authorize calls require a payment authorization response from the issuer and a
payment session identifier. This error is returned when Adyen tries to process the payment
with the issuer, which is unable to process their own payment authorization response.

99
A. A DYEN FAULT C ASES

FC43) “105 - Invalid paRes from issuer” (2)

3D secure authorize calls require a payment authorization response from the issuer and a
payment session identifier. This error is returned when the merchant fails to forward the
valid payment authorization response and payment session identifier.

FC44) “906 - Invalid Request: Original pspReference is invalid for this environment!”
Adyen provides a test environment for its customers to test their integration with test pay-
ments. Payment references in the production environment are invalid in the test environ-
ment, and vice versa. This error is returned when a merchant attempts to use a payment
reference of a different environment.

FC45) “109 - Invalid variant”

Credit cards come in different variants. Some variants are a subtype of another variant.
For instance, the Mastercard commercial premium credit card is a subvariant of the regular
Mastercard card variant. An error occurs when the payment contains a credit card or one
variant which is not a sub(variant) of the variant supplied in the variant field.

FC46) “100 - No amount specified”

Payment requests such as authorize, capture and refund require an amount. This error is
returned when the amount is not supplied.

FC47) “0 - No InitialPspReference provided”

The status of iDEAL payments can be checked by sending in the payment reference in
combination with issuer information. A signature is required so that the request can be
verified. When the signature is not valid this error is returned.

FC48) “113 - No InvoiceLines provided”

Open Invoice requests require invoice lines with details about the purchased items. When
these lines are omitted this error is returned.

FC49) “10 - Not allowed” (1)

API endpoints have to be configured, before they can be used. When a Point of Sale con-
figured account tries to use the ecommerce endpoints an error is returned indicating that the
request is not allowed.

FC50) “10 - Not allowed” (2)

A merchant has to be PCI Level 2 certified to handle credit card information. Only then
they can use certain request fields for the credit card. Else they have to encrypt the card data

100
on the client side and send the data in an encrypted blob. Merchants that are not certified
and attempt to use the former method receive this error.

FC51) “167 - Original pspReference required for this operation” (1)

For modification action such as capture, cancel and refund a valid reference to the autho-
rization is necessary. In this case the merchant sends in invalid references.

FC52) “167 - Original pspReference required for this operation” (2)

For modification action such as capture, cancel and refund a reference to the authorization
is necessary. The merchant in this case neglects to send in this reference.

FC53) “905 - Payment details are not supported”

An acquirer configuration is needed to do a transaction in a specific currency using a specific
payment method. If this configuration is missing or incorrectly set up, then payments for
these combinations will fail with this error.

FC54) “907 - Payment details are not supported for this country/ MCC combination”
(1)
A Merchant Category Code (MCC) is a classification used to describe the services or type
of products offered by that merchant. Depending on this classification accepting payments
in certain countries is not allowed, and payments are rejected with this error message.

FC55) “907 - Payment details are not supported for this country/ MCC combination”
(2)
Adyen doesnt support payments in certain countries. Payments attempted in these countries
are rejected with this error.

FC56) “803 - PaymentDetail not found” (1)

The merchant in this case attempts to disable a contract that does not exist. This situation
occurs when the references to contracts are not properly managed or the contract has been
disabled in the post.

FC57) “803 - PaymentDetail not found” (2)

The merchants attempts to authorize a payment using a recurring contract that has been
disabled, updated or removed in the past. The contract can no longer be found, hence this
error is returned.

101
A. A DYEN FAULT C ASES

FC58) “0 - Please supply paymentDetails”

To authorize a transaction payment details are required. This error is returned when no
payment details are in the request.

FC59) “0 - Recurring requires shopperReference”

Recurring payments require the shopper reference field to be included, although optional
for normal payment requests. This error is returned when merchants neglect to send in the
shopper reference.

FC60) “130 - Reference Missing”

A merchant reference, created by the merchant, is used to uniquely identify payments. This
value is required for all payment authorization and this error is returned if missing.

FC61) “174 - Unable to decrypt data” (1)

For non-PCI certified merchants Adyen offers a client-side encryption library that encrypts
credit card information before submitting it via the API. In case requests are submitted with
an empty encrypted data field the system is unable to decrypt the data, hence returning this
error.

FC62) “174 - Unable to decrypt data” (2)

Credit card information encrypted in the shoppers browser is to be decrypted by Adyen. In
a limited number of cases this encryption fails with an internal exception, causing this error
to be returned.

FC63) “102 - Unable to determine variant”

To determine how to process a transaction Adyen determines the payment method variant
from the supplied card number. When the card number is invalid this process fails, causing
this error to occur.

FC64) “175 - Unable to parse JSON data”

This error occurs when the encrypted data containing credit card details cannot be parsed to
JSON after decryption. This can happen when a shopper maliciously alters the data before
it is encrypted in the browser.

FC65) “138 - Unsupported currency specified” (1)

A payment request requires the currency to be specified. When the value is omitted the
request cannot be processed and this error is returned.

102
FC66) “138 - Unsupported currency specified” (2)
SEPA Direct Debit recurring payments can only be processed in euros. Although initiating
the contract can be done in different currencies, not being aware of the currency restriction
for subsequent payments can cause this problem.

FC67) “0 0 - validation expired, pspReference=****************”

For Direct e-banking payments a session validity of 30 minutes is set. Requests that are
processed outside the valid timeframe are rejected with this error.

FC68) “0 0 - ” (1)
This request fails because the merchant sends in the amount value of a payment request as
a floating point number, instead of an integer. The API fails to respond properly and returns
an empty message.

FC69) “0 0 - ” (2)
The merchant in this case tries to process a 3D secure payment request multiple times,
which results in an error. The API does not handle the error well resulting in an empty
response.

103