#sasor_api
buoyant kayakBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1392123062106984469
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
vocal fog
hi there!
how are you accepting payments? Checkout Session, Payment Element, something else?
cloud pagoda
hi !
We have a backend integration using the following API (https://docs.stripe.com/api/payment_methods/create), and then link to a customer. (attach to customer endpoint)
vocal fog
got it, but note that's not a recommended integration. if your goal is to save a payment method for later, then you should use SetupIntent + Payment Element.
and to answer your question, you can learn more about cvc check here: https://docs.stripe.com/disputes/prevention/verification#cvc-check
buoyant kayakBOT
cloud pagoda
I understand, but I’m still unsure why this issue only occurs with the Spain-based account. In previous integrations (with Stripe accounts outside of Spain), using a similar approach, we didn’t experience these problems.
That’s why I initially thought that, being a Spain-based account, there might be additional parameters required or perhaps card payment method registration requires more data.
Is there any API endpoint that allows us to explicitly trigger or enforce this verification or should we definitely go with the recommended integration instead??
nova zenith