#beeeeeeeeeeee2
1 messages · Page 1 of 1 (latest)
Is there a reason why you're using dangerouslyGetFullCardDetails=true? if you collect raw credit card numbers, you become subject to the full PCI compliance standards. In your case this means you’d have to submit a SAQ D form to prove that you are PCI compliant [0]. It’s a 40 page form and typically, not a headache most companies want to be dealing with.
[0] see https://stripe.com/docs/security/guide#validating-pci-compliance under "API Direct" as this is what your integration would be classified as.
i just talked to a coworker who was doing the web implementation and they mentioned i could use the "createPaymentMethod" to avoid the problem i'm having of the credit card details input being unmounted before the user reaches the executePayment screen. so i'll try that before we are forced to open a new legal department to handle this 😆