microsoft / microsoft/Dynamics365Commerce.Solutions

D365 does not pick the correct card type from Adyen

Open
#262 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
80
Forks
38
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the D365 POS and Adyen transaction comparison described in the issue, focusing on co-branded card data and the two card-data layers. The issue provides no version information, reproducible steps, sample, screenshots, or error details, so those must be established first. Done would mean D365 records both the UnionPay layer and the co-branded Visa, Mastercard, or Amex layer consistently with Adyen.

Written by the indexing model from the issue text.

Assessment

Domain
payments
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.