#anxster

1 messages · Page 1 of 1 (latest)

novel raftBOT
vale dagger
#

On backend, before creating the PaymentIntent, you can pre-create a Customer and supply its Id to the PaymentIntent

frosty thunder
#

How does that control the visibility of the checkbox?

vale dagger
#

I think it will make the PaymentIntent has a Customer, then present the option to save. Could you try it?

frosty thunder
#

I will need speak to the backend team for that...
...but if the payment sheet is currently always saving the card, then the payment intent on BE must already have customer.

vale dagger
frosty thunder
#

Also, I am talking about "SetupIntent"

#

"PaymentIntent" is created after the sheet is closed, either with a new card or a saved card.

vale dagger
#

Yeah SetupIntent should behave the same

#

Um wait a min

#

You are using SetupIntent instead of PaymentIntent, right?

frosty thunder
#

yes, correct

vale dagger
#

Okie I know this. Because SetupIntent means you "intent" to save the card for future use anyway, so it doesn't have the Checkbox (it always save!) This is in contrast to PaymentIntent where it shows the checkbox based on condition (see this SO: https://stackoverflow.com/questions/74105664/how-to-get-the-save-card-details-option-from-stripes-paymentsheet)

frosty thunder
#

Ah, so in this case its not possible to show the checkbox, it WILL always save, right?

vale dagger
#

Yep

frosty thunder
#

Does stripe provide any guidance around shall we display the saved cards on our own app's screen, or just rely on the saved cards shown in stripe payment sheet?

fringe lantern
#

Hi! I'm taking over this thread.

#

That's up to you, but saved payment method should be automatically displayed in the PaymentSheet, so that's probably the simpler option.