#pingproxies

1 messages · Page 1 of 1 (latest)

tough basaltBOT
cinder wharf
olive mural
#

We show the user a list of their payment methods to pay an invoice with, these are ones which are saved for future use. However, sometimes the user clicks through anyways and tries to pay the invoice with a card that was already saved / a duplicate was previously detached leading to the error, not sure if our team is missing something but it seems reducing the problem to no occurrences is nearly impossible since there is a large element of user decisions which we can't control.

Its happening quite a lot which is why we are contacting, we only have around 1,000 active customers and yesterday we had 10 occurences so quite a high incidence rate.

#

@cinder wharf

cinder wharf
#

large element of user decisions which we can't control.
Yes correct, if the user want to re-enter their card despite they have it already saved, there is nothing to do in this case.

#

As each time they enter their card details, a new PaymentMethod will be created

olive mural
#

Damn, thats a shame. Any plans on changing this or any solution in the works? In 2019 a dev on the Github said that you are working on a more elegant solution

#

@cinder wharf

cinder wharf
#

Please don't use mentions, I'm monitoring your thread.

#

As I shared previously with you, you can collect and save the payment method of a customer using SetupIntent or PaymentIntent with future usage, but if the customer decides to enter their card details again, there is nothing to do, you need to use all their attached payment methods

olive mural
#

Understood, and apologies for the @. Out of interest, is there a way to get a users saved cards displayed to them on an invoice page? When we create an invoice, Stripe sends them the payment link and it doesn't show them their saved cards, meaning that there is a very high liklihood if they go through that path, they will enter a same card and run into the error.

cinder wharf
#

Wait, I don't think that by entering the same card they'll get taht error

tough basaltBOT
olive mural
#

We aren't able to see the exact card info they enter but we've spoken to clients via support tickets and also tried to recreate the issue. Here are some examples where we think it has happened:

Sample request IDs:

req_CM7B98hRbK4pr9
req_xfe7ItbsLBHQLy
req_m3UywZ3zh6xYsG
req_dKYmaunylmRNRS