#Cerbu
1 messages ยท Page 1 of 1 (latest)
Hi there!
Can you share the ID (req_xxx) of the failing API request?
https://support.stripe.com/questions/finding-the-id-for-an-api-request
yes sir!
req_1u2pZZHhSS7xtv
I am aware that these are credit card testers and I'm trying to block them
Ah ok, you can refer to this guide in order to prevent your integration from card testing:
https://stripe.com/docs/disputes/prevention/card-testing
yes I already followed that
I need a way to recreate this error in my test environment
You can refer to all test cards in this guide:
https://stripe.com/docs/testing#declined-payments
I think this card will help you get that error 4242424242424241
nope
that returns an error in the tokenization process
so before the request to create the customer with source happens
Yeah but you'll get the same error code incorrect_number at the end. That' the only option. You should be using PaymentMethods API instead of token and sources, these APIs are deprecated.
I know
The call it self is a backend call
so
this guy
for which I gave you the error
req_TMn50YHUF0wImP this request
for the tokenization went thru
but the other to create the customer faile
so there is a different validation method
I cannot get to the second validation because the tokenization is stoping me
if I use the 4241 card, the first validation from stripe elements stops me
from getting to the PHP part, where I actually create the customer
I think the tokenization is Luhn check, which does the credit card number sanity check
while the customer creation / source attach does it some other way ๐
can this be replicated on DEV someway ?
No.
๐ฆ
ok
thanks
then, I'll just add that check in the code and keep the fingers crossed ๐
and about migrating to the PayemntMethods API I agree, however the emergency right now is stopping the card testers
have a nice day!
Please, let me know if you have any other questions.