Troubleshoot Dynamics 365 Payment Connector for Adyen
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 IIS Hardware Station event logs first. You can find these logs found under the following nodes in the Microsoft Windows event log:
- Application and Services Logs > Microsoft > Dynamics > Commerce-ModernPOS
- 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 will contain a PSP reference number(PSP is the reference ID provided by Adyen used to uniquely identify each transaction). Provide this reference number when you contact Adyen support for help with specific transactions.
The EFT terminal ID isn't set
| Title | EFT Terminal ID is not set |
| Symptom | Payment authorization calls fail, and a hardware error occurs. An error message in the event log indicates that the EFT Terminal ID value isn't set. |
| Root cause | This issue can occur when the EFT POS Register Number field isn't set on the register or the IIS Hardware Station. It can also occur if the value is set but isn't correctly synced to the POS terminal. Finally, it can also occur when the value is cached. | Fix | Follow the instructions in Set up a Dynamics 365 register. Then run the 1070 and 1090 distribution schedules. If the issue isn't resolved, consider reactivating the Store Commerce app, because the value of the EFT POS Register Number field might be cached and might need to be reset. |
The Store Commerce app or IIS Hardware Station configuration isn't updated
| Title | Config is not updated |
| Symptom | Store Commerce app error: "Sign in Error. The initialization data couldn't be loaded." |
| Root cause | This issue can occur when the POS is redeployed but the dllhost.config file hasn't been updated. | Fix | Follow the instructions in Update the Store Commerce app or IIS Hardware Station configuration. Then end the dllhost.exe task on the Details tab in Task Manager, and reopen Store Commerce app. If you're using an IIS Hardware Station, reset IIS. |
Invoicing sales orders failed due to stale authorization
| Title | Capture failed due to stale authorization |
|---|---|
| Symptom | Invoicing sales orders fails with "Exception has been thrown by the target of an invocation. System.ArgumentNullException: Value cannot be null." The underlying error in the logs is "The following error occurred during the capture call - Dynamics 365 Payment Connector for Adyen: Error code Decline message Capture failed due to stale authorization." |
| Root cause | This error happens when an authorization older than the Authorization stale period (days) is sent to the payment connector for capture. |
| Fix | Ensure the value of Number of days before expired in Accounts receivable parameters, Credit Card is set to 1 less day than the value set in merchant properties for all channels and then retry invoicing. The recommended value for Authorization stale period (days) is 14 in Adyen merchant properties and 13 in Accounts receivables parameters. |
Additional resources
Dynamics 365 Payment Connector for Adyen overview
Set up Dynamics 365 Payment Connector for Adyen
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for