JamesJGoodwin

[wanton saddle]

Yep! I'd recommend looking at the Stripe Payment Element. We have a quickstart tutorial linked in this page along with other helpful mentions: https://stripe.com/docs/payments/payment-element

[full valve]

Hmm, I was talking more about the backend part of the work. We already have a credit card form on the UI, but it's unclear what to do with credit card details when the user typed it in and clicked "Submit". The way I see it:

1. We should pass the credit card details (number, expiry, security code) to our backend
2. Our backend should create a charge with Stripe by passing card details down to Stripe
3. Stripe should return a redirect url:
   a) to our success page if no 3DS supported by card issuer or bank
   b) to 3DS page and then to our success page after 3DS challenge completed

But I'm not sure whether this approach is safe or not so I wanted to read more about it in the docs.

[wanton saddle]

1. We should pass the credit card details (number, expiry, security code) to our backend
   This is incorrect. The reason I recommended Payment Element is because it submits everything from the client, since you should never pass CC details to your own server

[full valve]

What's the difference between passing down card details to my backend and passing down card details to Stripe backend? It is both done through the same client network.