#diegus.
undone zodiac
chilly shard
Hello! If you're not PCI compliant you really can't be using this
dire geyser
then, how can I do it ? it's been working in QA
I mean, first news I have, I don't why it works in QA .
How can I solve this? what would be a workaround? how can I avoid that error?
chilly shard
It's working in QA because we allow it in test mode for users that were already trying it in test mode
But the expectation here is that before using it in live mode you HAVE to write in to support (https://support.stripe.com/contact) and prove that you are compliant
There's really now workaroudn here other than being PCI compliant or moving off of using raw card numbers entirely
dire geyser
Ok, according to the service response, it looks like I can add the credit card info via Stripe.js. Therefore, I could delegate payment method endpoint call to the mobile app SDK
Is that correct? will that solve this issue @chilly shard ?
chilly shard
I'm not sure exactly what you mean, but what the error message is describing is that you shouldn't be using/touching the raw number at all and you shouold be using stripe.js to collect all of that for you
dire geyser
I am talking about the endpoint response message :
{"status":402,"message":"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.","request_id":"req_bKIlPTbILDVerb","request_log_url":"https://dashboard.stripe.com/logs/req_bKIlPTbILDVerb?t=1698333512","type":"invalid_request_error"}
It seems that I can either use Stripe.js, the Stripe mobile bindings or Stripe Element
chilly shard
yup, we're saying the same things - stripe.js/our mobile library/stripe element colelct the payment details for you