Understand the limitations and known issues if using Adyen payments.
Cardholder Verification Methods (CVM) Limits
Minimum payment amounts aren’t configurable within Modern POS or our CMS. They’re dependent on a variety of factors, such as payment networks and customer regions.
Refusal Reasons
Refusal reasons displayed in Modern POS as to why a transaction wasn’t completed are provided by the terminal. These reasons aren’t configurable in Modern POS or CMS.
Payment Reader Not Reading Chip
Make sure the card is inserted into the payment reader correctly. The end of the card with a metallic square has to be inserted into the payment reader.
Payment Terminal Topology
Prior to version 8.4.1, payment terminal topology can only be configured at the store level. Modern POS versions 8.4.1 and onwards added support to configure payment terminal configuration at register level.
Localization
The language presented in the terminal settings is determined by the Adyen console. The language isn’t configurable via Modern POS or CMS.
Funding Source
If the terminal has a network issue connecting to Adyen cloud, then funding sources won’t be returned to the POS. As a result, funding source attributes can be missing in TLOG for credit card payments performed in a terminal offline state.
Partial Payments
Adyen has the concept of Partial Payments, however we aren’t using it. Insufficient funds always result in a decline. You can find the risks and limitations here.
Store and Forward (SAF)
For Adyen terminals with cellular capability, offline (SAF), transactions exceeding configured limits attempt to go online for processing. If the device can’t reach Adyen servers, an error message displays: “”
For devices with 4G (ASM1, SF01), turn off 4G by asking Adyen support. Salesforce doesn’t support failover between Wi-Fi and cellular networks.