#waleed.bin.khalid
1 messages · Page 1 of 1 (latest)
Hello what is the error that you are seeing?
Also are you using a token object literally named "Token"? Those are for legacy flows, if you are just starting out now you should use one of our newer APIs
I have backend in node js
where I am using stripe.tokens.create api to create token
it is sending me this error
Sending credit card numbers directly to the Stripe API is generally unsafe. To continue processing use Stripe.js, the Stripe mobile bindings, or Stripe Elements. For more information, see https://dashboard.stripe.com/account/integration/settings. If you are qualified to handle card data directly, see https://support.stripe.com/questions/enabling-access-to-raw-card-data-apis
Yep, generally you will want to collect card info on the client-side with Stripe.js. If you create tokens with raw card details on your server, you will have much higher PCI regulatory requirements on you.
Are you just starting out coding your integration? Or are you working with an existing integration that uses tokens?
existing integration that is uses token
actually scenario is we have card scan and auto fill functionality
that is why I have used create token api instead of stripe element
so If I will use stripe element, stripe element will not allow me to auto fill right ?
Correct. I think we have card scanning options in our mobile SDKs but not Stripe.js if you are just doing a website
so what I can do now
You will likely need to reach out to our support team and describe your usecase, they may be able to help you handle raw PANs on this account https://support.stripe.com/?contact=true
Find help and support for Stripe. Our support site 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.
I am guessing that you are getting this error on a new account? It sounds like the existing one may already have this enabled
yup this is the new account
Sounds good, talking to support will be the way forward then. That same code should work but accounts are not able to process raw PANs by default
if they allow me to process raw PANs then I will be able to tokenize my card using api just ?
Yep, the code shouldn't need to change. It is more of a permissions issue