#ad1122
tight frost
Not familiar with OmniPay. Can you share a payment ID from your Stripe account? pi_xxx or ch_xxx?
tight frost
Of course, nobody can do anything with that ID without your API keys
crude rock
perfect, the ID I shared is for successful payment
tight frost
Do you have an example for one that is failing?
crude rock
ch_3LYzGfCLTmtPGc6N1bO82JWv
tight frost
I have my suspicions for the reason, just want to confirm
crude rock
this one failed
tight frost
And this is consistent for larger amounts?
It shows as a generic decline, which could be true and the bank are just declining it for whatever reason
Or if its a broader pattern across multiple cards/customers, then it could be 3DS/auth related
And that integration you have is using (older) Stripe APIs that can't facilitate those authentication flows
crude rock
we just tested 3 to 4 customers and they all declined
ch_3LYz7TCLTmtPGc6N1mHto7q8
ch_3LYzDSCLTmtPGc6N1FT062UE
can we bypass fraud flag / settings on Stripe
tight frost
You cannot, no. It's a request from the bank/issuer not us. We're just facilitating the collection for the info
crude rock
Ok and Is it mandatory to create customer in Stripe to charge large payments?
someone told me that Stripe require extra information from customer to accept large amounts
tight frost
Usage of Customer objects aren't mandatory no. They're just recommended if you're regular processing payments from the same users (you can save payment methods that way)
tight frost
someone told me that Stripe require extra information from customer to accept la...
Well it always helps to collect and provide as much info as possible that we can send to the bank (CVC, address, etc): https://stripe.com/docs/disputes/prevention/verification
crude rock
Usage of Customer objects aren't mandatory no. They're just recommended if you'r...
No we just make one time payment form customer, we sold event tickets, One Time Payment only
tight frost
But that doesn't need to be done with a Customer object, you'd just provide those fields via other means
crude rock
But that doesn't need to be done with a Customer object, you'd just provide thos...
other means? like metadata?
tight frost
Well if you were using one of our payment UIs (like Checkout or Elements) then they provide the fields to capture ZIP, CVC etc
crude rock
okay
I am using stripe.js which provides me cvc, exp date and zipcode to capture
will see Checkout and Elements
tight frost
I am using stripe.js which provides me cvc, exp date and zipcode to capture
Yep, but ultimately that's not the issue
I suspect the issue is you (or OmniPay) is using the Charges API which doesn't support 3DS/authentication: https://stripe.com/docs/payments/charges-api
So those payments which the bank wants to authenticate, we just mark as a decline as the API can't handle them
You should switch to Payment Intents (w/ Elements) or use Checkout (my recommendation)