simon-wallets

[misty gust]

hi there! Not really, the way it works is there's a popup where the customer selects/enters their card information from Google/Apple Pay, you don't get access to the details or be able to charge them until after they complete that and the popup closes.

you might want to use auth-and-capture though : https://stripe.com/docs/payments/capture-later

so that you only authorise the amount when the customer is on the site and then capture it when/if you fulfill the order by creating the digital good

[tranquil ravine]

ok thanks.
"generate digital content" was maybe a bit misleading. So this is a process that might just take a second. But we are using a third party api for that and sometimes it was down. So we basically just don't want to charge the customer in the case an error occured.

I think this auth-and-capture is more like a deposit for a hotel room, right?

In the payment_intents api doc it look like the confirm property is what i'm looking for:
https://stripe.com/docs/api/payment_intents/create#create_payment_intent-confirm

But in the apple/google pay example there is no confirm call, even the property is not given, an the docs says its default to false

[misty gust]

yes, it's the same mechanism used for hotels. But you can authorise and capture a few seconds later. Or refund the authorsiation(which doesn't cost Stripe fees and is generally faster than a full refund) if something goes wrong

you don't need to confirm on the backend using that parameter. You confirm on the frontend : https://stripe.com/docs/stripe-js/elements/payment-request-button?html-or-react=html#html-js-complete-payment

you pass capture_method=manual on the backend when creating the PaymentIntent, and when it's confirmed on the frontend it will do an authorisation only instead of a full payment

[tranquil ravine]

ok, thank's for the detailed answer