#jimin-PAN-error
agile elk
Hi there! Passing raw PANs is not a recommended flow. Are you aware of the PCI Compliance burdens involved?
neat island
What do you mean by raw PAN? I am using a third party tokenization API. What is the recommended way? Using Stripe js in the front end right?
agile elk
Sorry, raw PAN = raw credit card number which is sensitive data that we don't recommend that you handle. Yes using Stripe.js is the safe way to do it so that Stripe takes on the PCI burden.
neat island
So would it return the same error on production API too? Is there a way to bypass this during testing?
agile elk
If you are using a third party tokenization API and they are taking on the PCI burden then that is a bit different... but you should be aware of the implications involved. You can visit https://dashboard.stripe.com/settings/integration to bypass this error.
neat island
ok thank you!
Hmmm we've updated it, but it's still failing. Does it take some time to update?
agile elk
Are you getting the same error?
agile elk
Looks like you didn't flip the necessary toggle at the above page
You need to click on the "Show advanced options" button
And then flip the toggle and save
neat island
this right?
agile elk
Yes that looks correct.
neat island
hmm ok i'll wait a little and try again 🤷♀️