#khadim-yaseen_api
lethal sapphireBOT
đ 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/1291652879135936594
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
oak loom
Can you share with me the ID of paymentIntent that was declined due to reasons rather than insufficient funds?
violet zealot
Yes Sure
pi_3Q5lgrED5xkfDv2c06oSwFRc
The above intent if from the payment request button flow
And this is from the payment element flow:
pi_3Q52bUED5xkfDv2c1bI77GPF
oak loom
https://dashboard.stripe.com/events/evt_3Q5lgrED5xkfDv2c0MDT10L0
https://dashboard.stripe.com/events/evt_3Q52bUED5xkfDv2c1ed0Hc2n
You can listen to charge.failed events, and check the charge's outcome.seller_message to understand more about the payment failure.
https://dashboard.stripe.com/settings/billing/automatic there's a "Manage failed payments" in your Dashboard settings, you can also enable the option to sends emails to customers to update failed card payment methods
I don't think there's a problem with your integration. Card declines are normal and you just need to handle them properly.
violet zealot
I understand card decline can be normal.
But I happen to have more failure rates.
I need to confirm If this is totally from the bank side or the issue could be on my end that's why the card is getting declined for most of my subscriptions?
oak loom
Both these two declined are issuer_declined, meaning they were both declined by the issuer.
violet zealot
ON the documentation
Even though This error says issuer_declined
But its in the Invalid API section
And for this intent I have the same error:
pi_3Q52bUED5xkfDv2c1bI77GPF
Is it possible that the issue could be on my end that's why bank is declining the payments more times than usual?
oak loom
We don't have insights on what makes an issuer decide to decline a payment.
And sometimes the issuer could return a totally unrelated decline reason to mitigate card testing
violet zealot
Okay can you PLEASE have a look at flow of events if the flow of events is correct for these two customers?
Payment Element Flow:
cus_Qvnoyk6ErFmHCT
Payment Request Button:
cus_QwYPDgkXzrVPzn
oak loom
You should share with me the PaymentIntent ID
violet zealot
Actually I want you to check the flow of events
https://dashboard.stripe.com/events?related_object=cus_Qvnoyk6ErFmHCT
oak loom
So I checked the logs. You created a customer, and used a setupIntent collect a payment method. After that you create a subscription, followed by a subscription schedule to manage it.
I don't see problems with this flow
lethal sapphireBOT
violet zealot
Can you please check this flow as well. This is a different flow for Payment Request Button:
https://dashboard.stripe.com/events?related_object=cus_QwYPDgkXzrVPzn
long hawk
well you're using the "PaymentMethod attach" API which I'd generally never recommend doing, PaymentMethods should be attached by confirming an Intent instead.
if this is a flow for starting a subscription the recommended integration is https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements
violet zealot
Can this be the reason for higher payment failures I get?
long hawk
I don't know, possibly
violet zealot
well you're using the "PaymentMethod attach" API which I'd generally never recom...
Actually I am using Payment request button in this flow for Apple pay / Google PAy.
I am required to use this function and this returns the payment Method
Which I attach to the customer and the create the subscription
paymentRequest.on('paymentmethod', function(ev) {
handlePaymentMethodReceived(ev.paymentMethod);
ev.complete('success');
});