#ben-equimine_declines-radar-pans
misty pendantBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1423347266324004874
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
errant hollow
Here is an example of the .csv files we have tried uplaoding into the Stripe Default Allow list:
cursive rapids
Raw Payments API
What do you mean by this. We don't have a Raw Payments API in our API reference
And I cannot use the link you shared. If you have a Charge or Payment Intent ID that corresponds to this failure, please provide that
errant hollow
one moment please
its the raw card data APIs - we had to have Stripe support enable it
and here is the charge ID: ch_3SCjceAUMWrO4Kke0r1ux0l3
cursive rapids
Okay you are providing raw PANs (card numbers) and yes that requires a higher level of scrutiny
errant hollow
Yes - but I'm not sure what we're missing - some charges are going through but the majority - like what I linked above - are being falsely blocked due to card testing
cursive rapids
Unfortunately there isn't anything I can do about why these charges are blocked. You will need to write in to Support. This doesn't appear to be an integration issue.
errant hollow
Yea We have had the ticket open for two weeks with no resolution so our account manager asked me to post here 🙁
cursive rapids
I was able to look up the Charge and the API request and check our logs. You are making a valid API request
errant hollow
Yea, but its still being blocked due to card testing even though we're initiating it...the only thing that we've tested and that has worked has been manually adding the fingerprint to an allow list
But THEN the issue is that the bulk upload via .csv is failing....I added an example excel of what we're trying to upload
this would just be a "bandaid" until we fix the live payment issues
getting this error when we upload - but support can't tell me what I need to change in my .csv to make it work
cursive rapids
Unfortuantely, these aren't subjects I can help with here
errant hollow
Oh ok
cursive rapids
We focus on debugging issues with user's API integrations but we cannot assist with declines and how to remedy your current situation. I apologize if your account manager mistook either what the problem was on your end or what help we can provide
errant hollow
No worries, appreciate you trying. Would someone here be able to help with figuring out why the upload to the allow list isn't working?
we're dead in the water right now :/
I assume its just something wrong with the format etc?
cursive rapids
I think so. The error message says there is an unexpected parameter (expires_at) but I don't see that in the CSV you posted. Although that could be Discord formatting
errant hollow
The .csv I sent JUST has the fingerprints, so column headers etc. I've attempted to add them based on support feedback I've gotten but the upload simply sees the column headers as values (which fail)
So no column headers*
cursive rapids
Makes sense
errant hollow
using this process:
Any ideas? If we can enable this.....it would at least be a stop-gap for the payment failing because we would retry many of them
cursive rapids
Unfortunately we also don't deal with dashboard functionality. If you wanted to try using the API for this you could use this API endpoint: https://docs.stripe.com/api/radar/value_list_items
errant hollow
Do you know what its expecting though for that "Expires_at" parameter?
cursive rapids
I have no idea honestly. If you look at the documentation for the Value List Items API, that isn't a parameter.
errant hollow
Uhg - its annoying because its giving me this error when I'm using Stripe's own upload tool....
ok, well thank you. Appreicate you trying to help
cursive rapids
Uhg - its annoying because its giving me this error when I'm using Stripe's own upload tool....
Yeah I get that! Honestly, it's why I prefer to develop almost entirely directly with the APIs and my own code
But it's hard when you just want to get something working
misty pendantBOT