#binodkafle

1 messages · Page 1 of 1 (latest)

neon pathBOT
magic summit
#

Can you share an example?

queen ivy
#

You mean failing payment intent id?

magic summit
#

Yes

queen ivy
#

pi_3NpjrCD5KYFi3zJG1CmspwS5

#

pi_3NoJkeD5KYFi3zJG0R4z9jlF

#

pi_3NoJduD5KYFi3zJG1n0VcHVI

#

pi_3NWtgnD5KYFi3zJG07LsbVoE

#

pi_3NpjrCD5KYFi3zJG1CmspwS5

#

pi_3NWtfDD5KYFi3zJG10JiGoQL

magic summit
#

Looking at just the one example

#

I looked at pi_3NpjrCD5KYFi3zJG1CmspwS5 and it seems the bank just declined the payment. Nothing seems off with your integration

queen ivy
#

Just asking, isn't it unusual for the bank to decline these payments if nothing seems off with the integration. For eg. billing_details of the payment is always null. Is it possible that setting the correct information for name will improve the payment success rate?

magic summit
#

isn't it unusual for the bank to decline these payments if nothing seems off with the integration
Not particularly no. Banks can, and do, decline payments for any number of reasons. In most cases the customer can resolve the issue by speaking to the bank

Is it possible that setting the correct information for name will improve the payment success rate?
Specifically what information? We only send specific information with the payment across the networks in cases where we think it'll imporve auth rates

queen ivy
#

Specifically what information?
I mean billing_details in the payment methods and charges section

"billing_details": {
    "address": {
      "city": null,
      "country": "JP",
      "line1": null,
      "line2": null,
      "postal_code": null,
      "state": null
    },
    "email": null,
    "name": null,
    "phone": null
magic summit
#

But in the example payment I looked at the bank didn't do an AVS check so likely not the cause of the decline

queen ivy
magic summit
#

Hmm, that's not really the case here as no authentication was requested. They're just straight up declines