#Alan Tse
1 messages · Page 1 of 1 (latest)
It should allow you to not specifying payment method type, if you are not passing confirm = true
I am happy to look closer if you can provide the request id req_xxx, can see from https://dashboard.stripe.com/test/logs
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
req_Z04ulgEXseANMe
but i want to set the returnurl ,if i don't set the comfirm, the return url can't be set
req_uEcK0CT9haWdn3 there is another request without paymentmethodtype=card.
@still stump Whether applepay googlepay front-end comfirm backend paymentintent does not need to comfirm?
confirm means you need to have a customer payment method beforehand. You can't confirm without a payment method (we need something to charge)
so i can do not set the comfirm item
The ideal flow is to create Payment Intent on backend (without confirm=true), passing its client_secret to frontend then use frontend to confirm
Ok, so our backend doesn't need to call the comifrm interface anymore?
- don't need to pass
confirm: truein the parameter
so, if i dont pass comfirm:ture, i just comfirm in the frontend and dont need to call this api https://stripe.com/docs/api/payment_intents/confirm in the backend?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Yep