#ArjunB - Charges to Payment Intents
1 messages · Page 1 of 1 (latest)
Hello! Can you provide more details about the specific thing that's blocking you? I'm not sure I understand your question as-is.
You can configure a Payment Intent to set up Payment Methods for future use with setup_future_usage, is that what you're asking about?
no.
the above the statemnt is correct , right?
Stripe saves if i added a CC on their end
with PI (Payment Intents )
there is nothing on the merchant side..
Not sure I understand. Can you provide more details?
Which statement are you asking about?
Stripe saves if i added a CC on their end
with PI (Payment Intents )
there is nothing on the merchant side
Who or what does "their" refer to?
When a paymentMethod is created with a PaymentIntent, a charge is made with the PaymentMethod.
IF "setup_future_usage" is set to true, and a customerId is also set, then the PaymentMethod is saved to a customer on whichever account the paymentIntent was created on
Also, if a SetupIntent is used, and a customerId supplied, then a PaymentMethod will be attached to the customer without creating a charge. If the SetupIntent was created with "offline_usage" (check the syntax in the API documents), the PaymentMethod can later be used for "offline" charges - without the customer present. These charge attempts may still be required by the bank to pass 3DS verification, so your code needs to be ready for that.
Which account (Platform or Connected) the SetupIntent or PaymentIntent is created on depends on the type of charges & type of accounts involved.
so i have apple pay , how that will be saved?
i am seeing wallets here https://stripe.com/docs/payments/payment-methods/overview
(I don't actually work for Stripe) - wallets appear to PaymentMethods as CC, so there's no separate flow for them once created as PaymentMethods