#canopus1io

1 messages · Page 1 of 1 (latest)

floral sundialBOT
tawdry bluff
#

Hello! Usually that means the card is on a denylist.

frosty sleet
#

as in the card has been blacklisted?

#

how does a card get on the denylist?

#

is it a stripe denylist?

tawdry bluff
#

Or it could be on a Stripe-wide list.

frosty sleet
#

I checked, all of those lists are empty

#

is this something that our merchant (connected account) should reach out to stripe support about resolving?

floral sundialBOT
tawdry bluff
#

Yeah, you should contact Stripe support for more info.

frosty sleet
#

we as the platform account? we have hundreds of connected accounts? that does not sound very scalable for us

void ingot
#

I'd still recommend talking to support about this for these errors. They may be able to work with you too for how you want to handle these going forward.

If your connected accounts are Express or Standard accounts they may be able to reach out, but it looks like your account is the one making these API calls as itself so it may be hard for them to get the relevant data to talk to support

frosty sleet
#

ahh, I see. thank you @void ingot and @tawdry bluff , I appreciate the help

#

actually, one more question about stripe logs

#

were there any recent changes to stripe logging, say starting October 1st?
reviewing our past logs, I noticed that there is a new attribute referrer which lists the domain

void ingot
#

I'd reccommend asking our support team about that quesiton as well. We know about the API and API changes but aren't as on top of the dashboard

frosty sleet
#

actually, its a new attribute in the POST request body for /v1/payment_methods api

#

so that would be your domain, no?

void ingot
#

Can you send me the ID of the request that you are looking at? I am not seeing that field in our API reference. Apologies, I thought you were talking about something new you were seeing in the dashboard UI

frosty sleet
#

req_zCqxT93mhJj2xc