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

Duplicate card #736

Open
yoobi opened this issue May 24, 2021 · 4 comments
Open

Duplicate card #736

yoobi opened this issue May 24, 2021 · 4 comments
Labels

Comments

@yoobi
Copy link

yoobi commented May 24, 2021

General information

  • SDK/Library version: Javascript V3 SDK + Java SDK
  • Environment: Sandbox
  • Browser and OS: Chrome Version 90.0.4430.212 (Official Build) (x86_64) // MacOS. 10.14.6

Issue description

I'm using drop-in UI for my payment, I'm displaying the card layout with registered card of the user, I've notice that the user can save multiple times the same card (image1) but it is displayed only once in the the UI (image2).

Image 1

Screenshot 2021-05-24 at 18 29 57

Image 2

Screenshot 2021-05-24 at 18 33 22

Unfortunately there is a bug because when I delete the card used via the UI, the same card appear again and I have to delete it again probably because the first deletion was on 46w4cqg and the second is for kdkv3yb.

The important issue is that if a user paid 20 times and each time the same card was saved he has to delete it 20 times via the UI which is not acceptable for a user-friendly UI.

drop-ui

Question:
Do you have a solution to avoid inserting the same card over and over again ?
Or delete all the duplicate cards of the user at the same time ?

@BotanAtomic
Copy link

I have the same issue..

@crookedneighbor
Copy link
Contributor

We have a task in our backlog to allow you to specify if you do not want to de-duplicate cards for cases like this. Will update here when the task is complete.

@yoobi
Copy link
Author

yoobi commented May 26, 2021

Ok cool, do you know when it'll be push to production ?

@crookedneighbor
Copy link
Contributor

No, there are no timelines for a resolution for this issue. We'll update this issue when any new information is available.

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

No branches or pull requests

4 participants