Skip to content

Commit cde4223

Browse files
authored
Merge pull request #10458 from haywoodsloan/8177-migrate-adyen-connector
AB#8177: Commerce troubleshooting migration - adyen-connector.md
2 parents 0618b0c + 2ff4680 commit cde4223

6 files changed

Lines changed: 101 additions & 3 deletions

File tree

Lines changed: 94 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,94 @@
1+
---
2+
title: Troubleshoot common issues in the Dynamics 365 Payment Connector for Adyen
3+
description: Learn how to troubleshoot common issues that affect the Dynamics 365 Payment Connector for Adyen.
4+
ms.reviewer: johnmichalak, Jiantong.Zhang, valitovgleb,v-shaywood
5+
ms.custom: sap:Payments\Issues with Dynamics 365 Payment Connector for Adyen
6+
ms.date: 10/15/2025
7+
---
8+
9+
# Troubleshoot Dynamics 365 Payment Connector for Adyen
10+
11+
This article provides troubleshooting guidance for common errors that affect the Microsoft Dynamics 365 Payment Connector for Adyen. The Dynamics 365 Payment Connector for Adyen facilitates communication between Microsoft Dynamics 365 Commerce (and associated components) and the Adyen payment service.
12+
13+
The Dynamics 365 Payment Connector for Adyen takes advantage of the device-agnostic [Adyen Terminal API](https://www.adyen.com/knowledge-hub/introducing-the-terminal-api). It supports all payment terminals that this application programming interface (API) supports. For a complete list of Adyen payment terminals, see [Adyen POS terminals](https://www.adyen.com/pos-payments/terminals).
14+
15+
## Invoicing sales orders fails because of stale authorization
16+
17+
### Symptoms
18+
19+
The process of invoicing sales orders fails and returns the following error message to the Commerce headquarters:
20+
21+
> Exception has been thrown by the target of an invocation. System.ArgumentNullException: Value cannot be null.
22+
23+
The following underlying error is also logged in the event log:
24+
25+
> The following error occurred during the capture call - Dynamics 365 Payment Connector for Adyen: Error code Decline message Capture failed due to stale authorization.
26+
27+
For more information about how to access the Commerce-specific event logs, see [Commerce component events for diagnostics and troubleshooting](/dynamics365/commerce/dev-itpro/retail-component-events-diagnostics-troubleshooting#find-commerce-specific-events-in-event-viewer).
28+
29+
### Cause
30+
31+
This error occurs if an authorization that's older than the **Authorization stale period (days)** property value is sent to the payment connector for capture.
32+
33+
### Solution
34+
35+
To resolve this issue, take the following steps:
36+
37+
1. In Dynamics 365 Commerce headquarters, go to **Accounts receivable parameters** \> **Credit Card**.
38+
1. Make sure that the **Number of days before expired** property is set to at least one day less than the **Authorization stale period (days)** property for each channel.
39+
1. You can configure the **Authorization stale period (days)** property in **Payment services**, **Hardware profiles**, and **Online stores**.
40+
41+
| Property | Recommended value |
42+
| ------------------------------------- | ----------------- |
43+
| **Authorization stale period (days)** | 14 days |
44+
| **Number of days before expired** | 13 days |
45+
46+
:::image type="content" source="./media/adyen-connector/authorization-stale-period.png" alt-text="The payment services configuration menu that shows the Authorization stale period in days highlighted":::
47+
48+
:::image type="content" source="./media/adyen-connector/days-before-expired.png" alt-text="The accounts receivable parameters menu that shows the Number of days before expired highlighted":::
49+
50+
1. Retry invoicing.
51+
52+
For more information about how to configure the payment connector for Adyen, see [Set up Dynamics 365 Payment Connector for Adyen](/dynamics365/commerce/dev-itpro/adyen-connector-setup#set-up-a-processor-for-new-credit-cards).
53+
54+
## EFT Terminal ID isn't set
55+
56+
### Symptoms
57+
58+
The following error is logged in Event Viewer:
59+
60+
> Hardware station an exception occurred when trying to open a payment device and begin a transaction.. Exception: System.ArgumentNullException: Value cannot be null.
61+
> Parameter name: terminalSettings.TerminalId
62+
63+
The Store Commerce app also displays the following error message to the point of sale (POS) user:
64+
65+
> There was an error communicating with the hardware station.
66+
67+
:::image type="content" source="./media/adyen-connector/hardware-station-config-error.png" alt-text="Message about a hardware station error":::
68+
69+
### Cause
70+
71+
This issue might occur in one of the following scenarios:
72+
73+
- You don't set the **EFT POS Register Number** field on the register or the IIS Hardware Station.
74+
- You configure the **EFT POS Register Number** value in Finance and Operations (F&O), but the Commerce Data Exchange (CDX) job for syncing data from F&O to the channel database hasn't run yet.
75+
- An outdated **EFT POS Register Number** is cached on the retail server.
76+
77+
### Solution
78+
79+
To fix this issue, follow these steps:
80+
81+
1. Follow the instructions in [Set up a Dynamics 365 register](/dynamics365/commerce/dev-itpro/adyen-connector-setup#set-up-a-dynamics-365-register).
82+
1. On the **Distribution schedule** page, run the **1070** and **1090** jobs.
83+
1. If the issue isn't resolved, consider reactivating the Store Commerce app. The previous value of the **EFT POS Register Number** field might be cached and have to be reset by reactivating the Store Commerce App.
84+
85+
## Related content
86+
87+
- [Dynamics 365 Payment Connector for Adyen overview](/dynamics365/commerce/dev-itpro/adyen-connector)
88+
- [Set up Dynamics 365 Payment Connector for Adyen](/dynamics365/commerce/dev-itpro/adyen-connector-setup)
89+
- [Dynamics 365 Payment Connector for Adyen FAQ](/dynamics365/commerce/dev-itpro/adyen-connector-faq)
90+
- [Payments FAQ](/dynamics365/unified-operations/retail/dev-itpro/payments-retail)
91+
92+
[!INCLUDE [Third-party information disclaimer](../../../includes/third-party-disclaimer.md)]
93+
94+
[!INCLUDE [Third-party contact disclaimer](../../../includes/third-party-contact-disclaimer.md)]
51.2 KB
Loading
60.4 KB
Loading
63.5 KB
Loading

support/dynamics-365/commerce/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,8 @@
6262
href: payments/refund-declined.md
6363
- name: Save for my next payment option doesn't appear
6464
href: payments/next-payment-link-not-appearing.md
65+
- name: Troubleshoot Dynamics 365 Payment Connector for Adyen
66+
href: payments/adyen-connector.md
6567
- name: Point of sale (POS)
6668
items:
6769
- name: Store Commerce app (POS) is suddenly deactivated

support/dynamics-365/commerce/welcome-commerce.yml

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ landingContent:
2828
- linkListType: how-to-guide
2929
links:
3030
- text: CDX download jobs can't be downloaded in a sandbox UAT
31-
url: data-synchronization/uat-cdx-broke-after-debug-aos.md
31+
url: data-synchronization/uat-cdx-broke-after-debug-aos.md
3232

3333
# Card
3434
- title: Development and SDKs
@@ -94,8 +94,10 @@ landingContent:
9494
- text: Refund on a return order is declined
9595
url: payments/refund-declined.md
9696
- text: Save for my next payment option doesn't appear
97-
url: payments/next-payment-link-not-appearing.md
98-
97+
url: payments/next-payment-link-not-appearing.md
98+
- text: Troubleshoot Dynamics 365 Payment Connector for Adyen
99+
url: payments/adyen-connector.md
100+
99101
# Card
100102
- title: Point of sale (POS)
101103
linkLists:

0 commit comments

Comments
 (0)