#xathieur-unsafe-processing
1 messages · Page 1 of 1 (latest)
What is the error message?
Error: Your payment was declined for the following reason: 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."
I want to enable unsafe processing
Read all of those and if you are happy and agree, check all and continue
I believe they must all be checked
Thanks
No problem
Please be sure to understand that PCI compliance is shifted to being your responsibility if you go down this route.
Which one applies to your situation?
Which ever one best suits your situation
two of them apply
I had tried enabling this but the error still occurs
Any thoughts?
What can you see when you go to https://dashboard.stripe.com/settings/integration
you're probably mixing up accounts then like you enabled it one account but you're using the API keys of another.
also really, you should almost never do this.
are you PCI certified and in a position to submit a SAQ D https://www.pcisecuritystandards.org/documents/SAQ_D_v3_Merchant.pdf document to us every year?
not if you integrate according to our docs.
what are you trying to do, why are you making an API call with raw card details? What guide are you following exactly?
I can fix this error by enabling something, the fix is here: https://dashboard.stripe.com/settings/integration but after that, there is a risk credit card info
like you said, is there anyway to do with without risking the info like you said earlier?
or what do you think @warm coral
no, the fix is to not send raw card numbers.
you should start with https://stripe.com/docs/payments/accept-a-payment and integrate that way(using our frontends like Checkout or Elements), it does not involve sending card numbers or having the same PCI implications or needing to enable that setting.
Ohhh, I am setting this up on an e-commerce site
Is this possible by following this link, and integrating that way?
what guide are you following or what is this e-commerce site exactly?
Absorb is the company
it says . Stripe is recommending that users make use of their tokenization integration options, so that the merchants don't have to handle credit card numbers at all.
yep indeed, we do recommend that.
it also says depending on how your account was created, you may receive an email from Stripe noting that you need to enable either tokenization or “Unsafe Processing”,
i get the unsafe processing, do you think i created it wrong
well I think that Absorb should not be using an integration that requires you as the user to enable that option.
do you have a link?
are we talking about https://support.absorblms.com/hc/en-us/articles/231697987-Configuring-eCommerce ? or something else
ah ok yes, I see that language in their setup guide PDF, I suppose that's what you're looking at?
ideally that platform would not integrate that way, but if you trust them to handle the card details then it's ok to enable that setting in your Stripe account.
as I mentioned, it should work if you enabled it. Most likely you activated it on the wrong Stripe account for example if you have multiple, they would be my guess.
Yes that is
What i was looking at
So @warm coral it works when I enabled it, but I was just scared about the credit card info
I was wondering if there is anyway around it
if you use that plugin it seems like they require you to enable this since it's how they've built their integration, maybe there's a way to avoid it or they have a new version that uses tokenization, you'd have to ask them.
if you have concerns about the PCI implications of their solution I'd suggest you reach out to their support team.
Thanks Karl i appreciate it