Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

D365 does not pick the correct card type from Adyen #262

Open
rishabhwarner opened this issue Mar 18, 2024 · 0 comments
Open

D365 does not pick the correct card type from Adyen #262

rishabhwarner opened this issue Mar 18, 2024 · 0 comments

Comments

@rishabhwarner
Copy link

rishabhwarner commented Mar 18, 2024

Other Development Issue

Summary

**Hello MS team,

I want to raise an issue with you that we are having in D365.
We are using D365 as our point of sale with Adyen as the Payment gateway.

When co-brands card i.e., UnionPay co-branded as Visa/ Mast/ Amex are used on the D365 POS, D365 captures the payment method as UnionPay card.
When we compare the transactions across Adyen and D365, we see differences. We did our analysis with MS and Adyen support analyst.
The analysis revealed that Adyen store 2 layers of card data i.e., UnionPay as layer 1 & Visa/ Master/ Amex as Layer 2, on the other hand D365 only store Layer 1 i.e., UnionPay. Hence, when comparing the total number of Visa/ Master/ Amex transaction in D365 w.r.t. Adyen and it does not match, as Adyen shows more than D365.
We’re hoping Microsoft can add this feature to D365 i.e. store both the layers of card data. UnionPay as layer 1 & Visa/ Master/ Amex as Layer 2

With Cobranded cards on the rise, we suspect this issue to escalate quite rapidly.

We are happy to come on a call or share any more details if needed.
**
A clear description of what the issue you're experiencing. Please provide as much information as possible so we can best assist you with this issue.

Version and Error Info
Commerce SDK Component:
Component Version:
Commerce SDK Version:
Exception/Error Details:

Reproducing the Issue

Link to GitHub repo/solution where the issue is reproducible:

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Run command '....'
  4. See error

Screenshots

Please include any screenshots that would help us understand the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant