#WilliamD-payments
1 messages · Page 1 of 1 (latest)
If you want to accept payment on your account you'd want to use Payment Intents - if you want to use our standalone payment element (which has google/apple pay support) to collect payment information you can follow these docs: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements
Alternatively, if you want to use Stripe Checkout (which would be our own hosted page) you can take a look at https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=checkout
Is it possible to use my own UI for checkout and still be able to implement support for Apple and Google Pay? My platform runs a RESTful API and I plan to handle payments on my back-end using the API for Node
You can create your own UI, but we still recommend you use our elements in order to be PCI compliant
Okay, so what I need to do is:
- Create PaymentIntent as soon as the client requests to make a deposit into their virtual account
- Update PaymentIntent with payment instrument once the client has selected a payment method and provided the details
- Obtain payment status
Is that correct?
Let me add in a bit more detail:
- Create the Payment Intent as soon as the client requests to make the deposit
- Surface the Stripe element of your choice to collect payment information
- When they submit their info, you will confirm the Payment Intent
- You'll be notified of success/failure through a webhook, or you can retrieve the Payment Intent to check the status
Okay, thanks
The diagram in the docs for creating a PaymentIntent (server-side) mentions redirection (I assume 3D password/security), how does this happen serverside?
That part of the diagram is from the confirmation of the Payment Intent, not creation. This guide does confirmation client-side, not server-side
The title says "Create a PaymentIntent (server-side)"
Do I need to redirect the client to an external website for additional confirmation?
Sorry that's misleading - that diagram is meant to represent the whole payment flow. Creating the Payment Intent just covers the top part of that diagram
If you use stripe.confirmPayment then we handle that redirection/surfacing the modal to ask for authentication for you
I see. Is it possible to use confirmPayment server-side?
E.g. client sends payment instrument information to my server -> my servers sends payment details to Stripe API
Is there a specific reason you want to do this?
It is possible, but there are a number of limitations, and it is a more complicated flow
Okay, thank you for the information. I will then most likely use your client-side library to handle payment confirmation
👍 Glad to hear it!