Availibity of Processor reference by table

[rishabhwarner]

I also read the same on the Microsoft site.

It also mentioned that when using the Wallet feature with the Adyen connector, 

additional details like 'Authorization Code' and so on were also displayed on the UI

when you selected a single payment. But that these were not displayed on the statements.

 

Additionally, I read somewhere that this data from the Adyen connector (Processor reference, Auth code etc.) 

were stored in an XML file format in the database. 

Please refer https://www.linkedin.com/pulse/how-reconcile-adyen-vs-d365-fo-payment-transactions-patrick-mouwen

  | How to Reconcile Adyen vs D365 F&O Payment TransactionsD365 F&O/Commerce offers an out-of-box Adyen payment connector for use In-Store ("card present/card not present"), in Call centers or Online ("card not present"). When payments are physically captured through this connector, both 'sides' (Adyen and D365) capture 'evidence' for the physical transactiwww.linkedin.com -- | --

 

So I have some additional questions for you.

1. Does this 'saved as xml in database' thing also apply in our case?

2. If yes, could you please list out exactly what data are stored in the XML?
   Do these XML also contain the card details like the brand and co-brand names, last digits of the card number and so on?

We were thinking that if this XML files were also stored in our own instance of D365, then whether it was possible

to create some DB procedures to read the data from the XML and export it to some external tables.

So that the external tables would then contain the card details also, 

and thus we could then use that table for creating our Finance reports...

I also read the same on the Microsoft site.

It also mentioned that when using the Wallet feature with the Adyen connector,

additional details like 'Authorization Code' and so on were also displayed on the UI

when you selected a single payment. But that these were not displayed on the statements.

Additionally, I read somewhere that this data from the Adyen connector (Processor reference, Auth code etc.)

were stored in an XML file format in the database.

Please refer https://www.linkedin.com/pulse/how-reconcile-adyen-vs-d365-fo-payment-transactions-patrick-mouwen

How to Reconcile Adyen vs D365 F&O Payment Transactions

D365 F&O/Commerce offers an out-of-box Adyen payment connector for use In-Store ("card present/card not present"), in Call centers or Online ("card not present"). When payments are physically captured through this connector, both 'sides' (Adyen and D365) capture 'evidence' for the physical transacti

www.linkedin.com

So I have some additional questions for you.

Does this 'saved as xml in database' thing also apply in our case?
If yes, could you please list out exactly what data are stored in the XML?
Do these XML also contain the card details like the brand and co-brand names, last digits of the card number and so on?
We were thinking that if this XML files were also stored in our own instance of D365, then whether it was possible

to create some DB procedures to read the data from the XML and export it to some external tables.

So that the external tables would then contain the card details also,

and thus we could then use that table for creating our Finance reports...