#aprilsp

1 messages · Page 1 of 1 (latest)

ruby smeltBOT
shell tiger
#

There's a hard limit of 200 payment methods per customer

#

Why do you have so many of the exact same payment method attached?

#

You should code your integration to re-use payment methods not create duplicates

pliant palm
#

That's what I'm asking - does entering in the same card multiple times automatically create a new payment method instead of reusing the one saved on the Stripe customer? Our test automation runs every night and tries to simulate a new customer. We have an option to save the card to the account but that's for testing an existing user.

shell tiger
#

Yeah

#

If it's a returning customer, you should display their existing cards to them to select one

#

Having them enter the same card each time (and also passing customer id) causes duplicates

pliant palm
#

Ok I understand now thank you

#

Can we reuse cards on the customer with payment intents?

shell tiger
#

yeah

pliant palm
#

I could be mistaken but doesn't this require opt in from the customer to save the details? What if the customer refuses and reaches 200+ purchases without allowing us to save the payment method?

shell tiger
#

You'd need to start deleting payment methods then

#

detaching