#rooter
1 messages · Page 1 of 1 (latest)
Do you have the ID of a request (req_123) where you got this error?
sec
And also of a time that you didn't if possible?
For the $4000 limit, it sounds like you may be specifying payment_method_types in which case our API will error out if one of those PMs is not available for the charge. With automatic payment methods you should see the behavior where AfterPay simply does not show up in the payment element
A request ID for the shipping address error would be helpful as well. Appreciate the info
Automatic payment methods are not an option. I don't even know what the max values are for each financing option. This is not a good experience.
So, this time it decided to work over $4000, but I got the address error: pi_3N6EM8DQzp6p2Ds21NR4yusv
but half the time it blocks me for being over $4000
"Amount must be no more than $4,000.00 usd" req_3eQYb83xFfZjdn
All I did was reload the page and try again
We have the limits for afterpay here. Though interestingly it lists the US limit as $2,000 https://stripe.com/docs/payments/afterpay-clearpay#collection-schedule
Will check in to that $4000 error in a moment
Yeah, I thought it was $2000 as well, but I also thought stripe would just hide the option. It seems silly to have to check it on my end for each financing option.
The shipping address error is from confirming the payment intent. So that is after the user chose AfterPay as a finance option right? https://dashboard.stripe.com/test/logs/req_pNLIIFLHVFQykx
For manually specifying the payment methods that is what you will have to do unfortunately. I can put in a feature request for this but at the moment that is what the API requires
Yes, half the time the payment intent is created successfully, but I immediately get the other error.
Do you know the max amounts for Affirm and Klarna?
Not seeing those amounts in the equivalent docs for those payment methods. Will check in to them
I am going to consult a colleague on the intermittent error for those payment intents. As you noted those are the same parameters twice
The inconsistent error behavior appears to be a bug. We are still looking in to this and I will get back to you with more details