#JDPT-charges
1 messages · Page 1 of 1 (latest)
It could be any number of things - for example, some of the requirements have thresholds for when they are triggered (like you've charged $3000+)
Even in test mode? The relative link that is appended to the error above, is that an API link?
"shield_action": "too_many_charges_for_current_state",
Could this be the reason?
Do you have one of the failling requests that I can take a look at?
req_05V5ezy5JG28TG
Ah, so I think the issue here is that this is with a Standard account, which can also be used as a standalone account and needs a lot of information even though it's only connected in test mode
But why has it started failing within the last 5 hours? We've been using the same logic for creating the account and charging it for months, and never had this issue before
I could try wiping our test data and see if that fixes it. Like you said maybe it's something to do with volume.
I'll check back on this in the morning, heading on 1am over here
I'll keep looking as well - the thread may get archived in the mean time, but feel free to ask us to reopen it in the main channel!
@tepid lake it's best to contact support for this overall too: https://support.stripe.com/contact
you also seem to do Destination charges on Standard accounts here which is a highly discouraged integration path too