#Gary4091-invoices

1 messages · Page 1 of 1 (latest)

runic kernel
#

Hello! Do you have an example customer you see this happening for? I'm surprised to hear this, since I wouldn't expect us (Stripe) to be creating cards for you automatically

#

@queen gate Please use the thread 👍

#

Copy-pasting the customer ID here as well to keep it in one place: cus_KWA6sbcXId29WX

queen gate
#

Sorry about this

runic kernel
#

No worries!

queen gate
#

cus_KWA6sbcXId29WX

#

First card has a ID=
pm_1KOlS9AAKiNY1vCoKkL8AzxF

#

and it was created using Stripe API from our web site

#

Second Card (the same card) was created when customer paid Stripe Invoice

#

src_1KOlf4AAKiNY1vCoR8MxgqsW

#

Third Card (the same card) was created when customer paid Stripe Invoice again

#

src_1KOlWcAAKiNY1vCoqdfvsLTU

#

All 3 cards are identical

#

If we send another Invoice for this customer, and customer enter the same card again in the invoice payment form, another record for the same card will be created

runic kernel
#

Ahhh, gotcha - so you're saying that when your customer is paying from the hosted invoice page they're entering in the same card details causing multiple cards to be created

queen gate
#

YES EXACTLY

runic kernel
#

Unfortunately, if you heavily rely on the hosted invoice page there isn't a great way to get the behavior you want. The hosted invoice page currently does not support re-using a previously saved payment method from that UI.

#

If you didn't use the hosted invoice page you could implement something that would give you more control over duplicates, or if you switched your invoices to collection_method: charge_automatically that would allow the invoice to be charged immediately with the default set for the customer (eliminating the need for them to go through the hosted invoice page again)

queen gate
#

We don't want to charge automatically because it reduce our security in case of dispute (No 3D Secure and other advatages of customer himeself making payment)