#sergey_05097

1 messages · Page 1 of 1 (latest)

prime hornetBOT
balmy thorn
#

Hello 👋
AFAIK PCI compliance is affected by sharing of PAN (raw card numbers etc)
If you're sharing the IDs you've generated on Stripe (like PaymentMethod ID, PaymentIntent ID etc) then it shouldn't affect your PCI compliance.

Also, sending amount from client-side is never a good idea as anyone can modify the request to change the amount to something else and if you're not validating the amount server-side then that'd be a severe bug

#

If you have an existing payment method then technically you can charge it in one go server-side, yes. The issuers may prompt for authentication anytime so you'd likely want to build a flow where your users can come back and authenticate the payment if necessary.

#

Namely, we are interested in whether we can send 1 request from the client to our server with the deposit amount and payment details (ID of the existing payment method or data on the new card and all required parameters)
I don't think we allow sending raw card information to the API. I'd recommend talking to our support team as there are many restrictions at play that our team won't be aware of. Support team can help put you in touch with the correct team for this

#

Lmk if that helps @ionic ember
https://support.stripe.com/?contact=true

Stripe: Help & Support

Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

ionic ember
#

thank you!