#kishankumar
dapper veldt
terse nebula
You should migrate to Elements: https://stripe.com/docs/payments/elements
compact ginkgo
we also thought of this. but we got a mail where it s mentioned that our integration doesn't comply with certain RBI guideline especially saving of cards and we have to update it before 31 march.
In this short notice we cant implement Elements.
thats why we are thinking of submitting PCI form
terse nebula
Attaining PCI compliance will take a lot longer than migrating to Elements
compact ginkgo
ok can you please suggest how much time it can take ?
and is there any way that we can use our own custom payment flow like using our own form to save card and our own component to make payment ?
terse nebula
Not something we here have any experience with. Some vague details here:
If you continue to send card details directly to our API, you’ll be required to upload your SAQ D annually to prove your business is PCI compliant. SAQ D is the most onerous of all the SAQs, with over 40 pages of requirements you must implement to remain PCI compliant. Migrate to client-side tokenisation of card information if you want to substantially reduce the scope of your PCI compliance.
https://stripe.com/docs/security/guide
compact ginkgo
and is there any way that we can use our own custom payment flow like using our ...
can you please suggest on this ?
terse nebula
It's not possible, no
compact ginkgo
ok