#sandyk-payment-method

1 messages · Page 1 of 1 (latest)

hexed lotus
#

The simple answer is: it's not very secure to send PII or raw PAns (card credentials) to your server before sending again to us, so the client-only method is preferred because it bypasses your server entirely. That was the way we used to do it years ago, but we eventually decided to try and migrate everyone to the more secure architecture.

ashen dust
#

Ok, that should've been obvious to me! 🤦‍♀️ Thanks.

is it possible to get the token on the client side so I can send the token to the server? From reading the PaymentIntent setup card docs, it seems like card creation is done only on the client side.

hexed lotus
#

No worries! This stuff can get fairly complex, so understanding it is not trivial.

is it possible to get the token on the client side so I can send the token to the server? From reading the PaymentIntent setup card docs, it seems like card creation is done only on the client side
You can get an ID which is attached to the Payment Method object. That ID is then used to perform payment method actions with Stripe. Usually this is sent back as a response after the Payment Method is created. If you're looking for a code overview of how this is done, this is the best resource for understanding what's under the hood: ~~https://stripe.com/docs/payments/quickstart~~

#

Err, woops. Hold on, that's not the right one