#Cerbu

1 messages ยท Page 1 of 1 (latest)

warm basinBOT
plucky fable
next atlas
#

yes sir!

#

req_1u2pZZHhSS7xtv

#

I am aware that these are credit card testers and I'm trying to block them

plucky fable
next atlas
#

yes I already followed that

#

I need a way to recreate this error in my test environment

plucky fable
next atlas
#

nope

#

that returns an error in the tokenization process

#

so before the request to create the customer with source happens

plucky fable
#

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.

next atlas
#

I know

next atlas
#

yes, but I get that error code in the front end

#

I need it in the backend ๐Ÿ™‚

plucky fable
next atlas
#

I don't get to the backend

#

because the tokenization error kills the process

plucky fable
#

I meant to Stripe APIs.

#

which can be done from a backend too

next atlas
#

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 ?

warm basinBOT
plucky fable
next atlas
#

๐Ÿ˜ฆ

#

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!

tropic jacinth
#

Please, let me know if you have any other questions.