8

When a customer uses an Adyen connector on POS and needs to identify the relationship between cash and carry transactions and the Adyen reference, they must search through HQ transactions for each payment individually. This involves navigating to Store Transactions > Payment Transactions > Payment Authorization Token and sorting through 25,000 characters to find the tender reference. This reference is then used to match the transaction with the Adyen tender reference field, confirming that the transaction is the same on both Dynamics and the Adyen portal.


Another issue is that this search only works one way. If a customer requests the receipt number or sales order number, they can retrieve the relevant information. However, if they only have the tender reference number, they cannot search D365 for this number. This is particularly relevant in chargeback cases, where a charge appears in Adyen but no corresponding transaction is found in D365. Without manually reviewing every sale record for the store on that day, the customer cannot confirm whether this was a problematic transaction. This is similar to the situation with ECOM, where the data sent to Adyen includes an authorization number for the payment in D365.


The request is to implement a quicker way to identify the Adyen reference in the Dynamics user interface, ideally in an individual field, using the receipt or transaction ID.


Thanks!

STATUS DETAILS
New