#notdpr - Payment Problems

1 messages · Page 1 of 1 (latest)

somber finch
#

HI 👋

#

that's a lot of text, give me a sec to catch up

#

First question:

failures on the initial on-session payment when creating a subscription
what kind of failures are these?

bright beacon
#

We see the message "The bank returned the decline code transaction_not_allowed." or "The bank returned the decline code do_not_honor.

somber finch
#

Yeah unfortunately that isn't something we can control and I don't think it's related to 3DS authentication

#

India has some of the most complex financial regulations that I've come across

bright beacon
#

Yes, it's a big problem. They don't seem to do 3DS in many cases

somber finch
#

Indeed. And that is entirely up to the bank.

bright beacon
#

Our "last hope" is that maybe the full-on Stripe Payment Element will have better success on these initial on-session payments.... can you comment on that...

Also, the Stripe-hosted payment form at invoice.hosted_invoice_url seems to have better rate of success (when we manually send the India customer that link). Is there something that makes this form work better?

And, is it using the Payment Element?

somber finch
#

Unfortunately I cannot comment specifically on which interfaces provide higher conversion. The hosted invoice page does make use of the Stripe payment element

bright beacon
#

Ok, but it sounds like if we implement the Payment Element, then we'd at least be doing the same as Stripe does on the hosted form

somber finch
#

That is true which may improve conversion for you

bright beacon
#

Thanks for your help!