#connor_amex-decline
1 messages ¡ Page 1 of 1 (latest)
đ 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/1294067065119965184
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- connor_api, 6 days ago, 15 messages
connor_amex-decline
@obsidian anchor I'd recommend discussing with our support team why Amex doesn't work on your account. It's often due to a problem with MCC or the connected account being blocked from using Amex
Ah interesting! I saw others had an issue with where their Connect Account was "based" out of in the test env, will pull at that thread
yeah looks like the connected account's MCC is forbidden for amex so that's your issue
Cool cool, thank you!
Oh, one thing, in production we accept AMEX all the time with this MCC on the Charges API. Would something about Payment Intents change that?
It should not. But are you sure you understand that this isn't about your own MCC but the connected account's MCC? You use on_behalf_of so the info of the connected account are what's pulled and maybe you have used that MCC randomly just for that account?
It's a good theory, I checked to make sure the MCC is in line with what our production Connected Accounts use
Gotcha then the next step would be to chat with our support team to get to the root of this: https://support.stripe.com/contact