Our payment terminals are able to accept credit and debit cards from the following card schemes:
|Global Credit||Local Credit||Global Debit||Local Debit|
|American Express||Alliance Data (ADS)||JCB||Bancontact|
|Discover||Hipercard||Visa Debit||Carte Bancaire|
Not all of these cards are available in all regions. See our full Payment Methods offering for detailed information.
Before you begin
Before you begin integrating a payment method, make sure you have:
Perform card entry on your terminals using either magnetic swipe reader (MSR), EMV chip, or contactless via NFC. All card entry methods are supported without additional integration.
If all card entry methods fail, you can use manual keyed entry (MKE) to manually enter the card details.
The presence of the card holder is still required for MKE. Use MOTO payments if you need to support transactions where the card holder is not present.
Credit and debit cards can require a cardholder verification method (CVM) when used in a payment terminal. Verification is commonly with a personal identification number (PIN) or shopper signature. Support of all CVMs does not require any additional integration effort by default. For more information, see Cardholder verification methods.
Personal Identification Number
The shopper is prompted to enter their Personal Identification Number (PIN) into the terminal. Subsequently the PIN gets verified either offline with the chip on the card or online with the card issuer. Contactless transactions above CVM limit always require online verification.
The shopper is prompted to provide their signature either on the touch screen of the terminal or on the printed transaction receipt. It is your responsibility to verify the signature of the shopper with the signature on the card or another form of identification.
For Terminal API, the terminal always approves the signature.
If you want to implement a manual signature check on the cash register, proceed as follows:
- Retrieve CapturedSignature data from the PaymentResponse.
- Make sure the cash register software shows a prompt to check the signature.
Your staff then checks the signature:
- If a signature is approved, no action is necessary.
- If a signature is declined, the payment needs to be refunded.
In this scenario, we recommend delaying auto-capture of payments on the Adyen payments platform to prevent unnecessary reservation or transfer of funds. To configure this, refer to Delayed capture.
All credit and debit cards follow the same payment flow. You can read more about this in our make a payment documentation.
Transaction routing and refunds
Adyen terminals support both Credit and Debit cards. Depending on transaction routing, a Debit card may either be processed over a Debit network like Maestro, Interac, and Pulse, or over a Credit network like MasterCard and Visa. All Credit networks are dual-messaging meaning that we are able to trigger a referenced refund against an existing transaction. Some Debit networks however are single-messaging meaning that a referenced refund cannot be performed and that the refund must be done by inserting the card into the terminal.
As a result, it is important to keep track of the
paymentMethodVariant at the time of the transaction. This field returns the network over which the transaction was routed and which can be used to determine the allowed refund method. Keep in mind that the routing is independent of the funding source of the card. For example, a debit card can be processed via a credit network. The best way to determine whether the card itself is a credit, debit, or prepaid card is via the
fundingSource. Keeping track of the
fundingSource along with the
paymentMethodVariant allows you to determine both the type of card and the routing so it can be refunded appropriately.