Replies: 2 comments 6 replies
-
@lbk9 unfortunately it is quite impactful what you need to do: https://stripe.com/en-se/guides/pci-compliance . The fact that you use non certified screen components for handling card data is already sufficient enough request PCI compliance. Thats why we heavily (and also Stripe) advise against using it. I think Stripe can advice more precise about what you need to do. I was able to convince my company to use the payment sheet which offers less customisation but we do not need to do the paperwork. https://stripe.com/docs/security/guide |
Beta Was this translation helpful? Give feedback.
-
Is the CardField PCI compliant? Is the PaymentSheet able to generate paymentMethodIDs and confirm payment intents? If so I may look to switch over to it. |
Beta Was this translation helpful? Give feedback.
-
Because of the ongoing issues with your CardField on Android I have to use the
CustomCardPaymentScreen
implementation from your example app. Your documentation does not say what PCI Compliance questionnaire is required to be completed for the flutter package, mobile SDK does not cover it.Am I right in thinking that as long as I do not store any card details I do not need complete a questionnaire? If so then this is a non-issue as I make use of your API to generate payment methods and confirm payment intents.
Beta Was this translation helpful? Give feedback.
All reactions