#jarrett_api

1 messages ¡ Page 1 of 1 (latest)

glacial cosmosBOT
#

👋 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/1234906303185551413

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

frail hinge
#

meant to share this instead of charge id req_HVhTwchSZ3RA5m

orchid pebble
#

Unfortunately that's actually passed to us from the card networks. Like, we have the exact same qualms as you and your customers do, because the card issuer/bank sends us vague decline codes that are often not even indicative of what actually caused the decline (e.g. they sometimes send generic decline codes for very specific types of declines like invalid expiration and funds not available).

frail hinge
#

But you guys have documentation with better messaging for what "invalid account" typically means

#

Like the docs say "The customer needs to contact their card issuer to check that the card is working correctly."

#

so I don't get why the message to the end user couldn't be some version of that adjusted to address the customer

#

instead of just "Invalid account.". the customer doesn't know what that means at all.

orchid pebble
#

Ahhhh, I see what you're saying now. What product are you using that's surfacing that error? Stripe Checkout? Payment Elements?

frail hinge
#

Payment Elements

#

that request was made i believe with confirmPayment

orchid pebble
#

You should be able to surface the error message yourself if you wanted to, no? Like, I thought Stripe sent a more helpful error message back to the client along with the more basic invalid_account code, but I could be misremembering.

#

Ahhh, okay I see. After testing a few of them, it looks like the error message is also fairly generic. I'm thinking this is probably for security to mitigate card testing, since if you could automate figuring out exactly what's wrong with someone's card, then that might give fraudsters a bit more to work with, but I'm not sure.

frail hinge
#

I mean, you guys surface other error messages that are totally obvious

#

like the card was declined

#

most other errors have an actually useful error message in the message value of the JSON response.

#

it's just this one that is oddly confusing. we take that message and display it to users for every other message.

orchid pebble
#

Yeah, that's a bit odd. I'm happy to flag it with the product team for you and see if they might be able to take a look