#sankyo_api
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/1361250027095457792
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
hi there!
I want to know this case is one of the rare case cards you mentioned?
which "rare case" are you referring to?
I don't see anything unusuall here. it's juts the bank who declined the payment becasue the card didn't have enough funds.
Hi,
which "rare case" are you referring to?
[this test card case ](#1344603386762367079 message)
I don't see anything unusuall here. it's juts the bank who declined the payment becasue the card didn't have enough funds.
How can I know that?
in the reponse you see decline_code: "insufficient_funds".
Oh, I see.
Thanks for your help.
Sorry, I entered wrond Request ID.
The right Request ID is req_y4Nffjb5vEAzDd .
How about this one ?
here you tried to do an on-session payment, but the bank request 3DS, which can happen. so that's something your code needs to handle.
We seem to create the off-session payment intent, but the on-session payment intent created?
this code
payment_intent = ::Stripe::PaymentIntent.create(
{
amount:,
currency:,
customer:,
capture_method: `manual`,
metadata: option[:metadata],
off_session: true,
confirm: true
}
)
no, this create an off session payment. but then the bank decided that 3DS was required. so your code needs to handle this (tell the customer to come back to your website/app, and re-confirm the PaymentIntent while the customer is on session). this is totally normal.
So, for this card, we need to implement handleNextAction process?
yes, but this can happen for any card, not just this card.
This error rarely occurs on our service, but does it occur with normal frequency?
again, it's up to the bank. so yes it can happen. but no idea how frequently.
OK, thanks for your help. I try to implement handleNextAction