Note
The Retail Interest Group by Dynamics 365 Commerce has moved from Yammer to Viva Engage. If you don't have access to the new Viva Engage community, fill out this form (https://aka.ms/JoinD365commerceVivaEngageCommunity) to be added and stay engaged in the latest discussions.
This article provides troubleshooting guidance for common issues related to the Microsoft Dynamics 365 Payment Connector for Adyen. For an overview of the Dynamics 365 Payment Connector for Adyen, see Dynamics 365 Payment Connector for Adyen overview.
POS payment terminals
General issues
For all general issues, you should always consult the Store Commerce app or Internet Information Services (IIS) Hardware Station event logs first. You can find these logs found under the following nodes in the Microsoft Windows event log:
- Windows Logs > Application > Filter Current Log
(On the Event sources drop-down list, select Microsoft Dynamics - Store Commerce.) - Application and Services Logs > Microsoft > Dynamics > Commerce-Hardware Station
Failing payment transactions
When payment transactions aren't successfully processed through the Adyen payment terminal, the corresponding error messages in the Dynamics 365 POS contain a payment service provider (PSP) reference ID. The PSP reference ID is provided by Adyen to identify each transaction. Provide this reference ID when you contact Adyen support for help with specific transactions.
The EFT terminal ID isn't set
For troubleshooting guidance on this issue, see EFT Terminal ID isn't set.
Invoicing sales orders failed due to stale authorization
For troubleshooting guidance on this issue, see Invoicing sales orders fails because of stale authorization.
Additional resources
Dynamics 365 Payment Connector for Adyen overview
Set up Dynamics 365 Payment Connector for Adyen