#yuliana_decline-support

1 messages · Page 1 of 1 (latest)

tepid roseBOT
#

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

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

velvet ferry
#

👋 Hi Yuliana, do you have an example request ID demonstrating this behavior?

molten geode
#

Hi,

Yes, here is an example demonstrating the issue:
– Initial tokenization request (failed on /v1/customers): cgi_iMdAYrFkTWZSQgge
– Subsequent attempt processed as sale instead of recurring: cgi_h50QThtaePPEm15Y

Let me know if you need a successful flow for comparison.

velvet ferry
#

Our request ID's typically start with req_ and can be found under your logs in the dashboard. Not familiar with any objects that begin with cgi

tepid roseBOT
wheat whale
#

yuliana_decline-support

molten geode
#

Sorry, I'll try to find a right id in a moment

wheat whale
#

@molten geode when you attach a card to a Customer we run a card validation on it and the bank can declione it, it's fairly common and normal

molten geode
#

Thanks for the clarification - understood that card validation and bank declines during attachment are expected.

Given this behavior, could you please advise on the recommended handling on our side:
– should we retry attaching the card to the Customer after a short delay, or
– should such cards be treated as not eligible for recurring payments?

For reference, the example request ID is req_ynLZFFwMGX8eZJ.

Thanks.

wheat whale
#

Really your code should basically never use this in the first place. This has been discouraged and deprecated for years now.

If you are collecting card details now for a future payment (no payment immediately) you should use the SetupIntents API instead

#

It does look like you're using a really old integration with card Sources (src_123) when the newer APIs have been live for over 7 years now. Highly recommend investiging in upgrading your integration

molten geode
#

Got it, thanks. I understand the recommendation to use SetupIntents and I’ll pass this to our dev team to plan an integration update.

For the current implementation, could you please confirm the best-practice handling when the card validation fails during attachment (bank decline), so we can apply the correct logic on our side?

wheat whale
#

the bank rejected the card, retrying immediately won't help. It could work the next day or the next week. So I'd treat it as any normal decline, show an error to the customer and ask them to call their bank or try again

molten geode
#

Thank you!