#chris-caffey-sunday_apple-pay-declines
flint sealBOT
👋 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/1344715150309068850
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
quick locust
Hi 👋
No, I don't think that is possible. AFAIK the MPAN generation occurs during the initial Payment Method creation process and involves both Stripe and your integration sending more details to Apple Pay to create the MPAN.
Saved payment methods using Apple Pay are only saved as a card Payment Method
lavish sequoia
Okay that's what I kind of figured. Our pre-existing Apple Pay PaymentMethods are most likely using DPANs due to our FE configuration and it is what it is.
thanks for responding @quick locust !
quick locust
Happy to shed what 💡 I can 🙂
You could add logic to save Apple Pay PMs with the MPAN details for recurring/off-session charges and, when you have an auth failure for saved Apple Pay PMS, bring those customers back on-session to go through that process.
lavish sequoia
yeah I figured that was the case, but we are trying to find a way to save our pre-exsiting methods from such a high churn rate. forcing the customer to come back to our website to update their payment method is another barrier to entry.
You stated that the method is saved as a card but that can't be entirely true can it? Our failure rates are much higher for apple pay cards than they are for normal cards. So there must be a difference still.
quick locust
Do you have an example Payment Method ID I could check?
lavish sequoia
Sure, here is one pm_1PLeCnGjO3bEFd6gyZYSzWMt
quick locust
For digital wallets (Apple & Google Pay) that are saved for later use, we don't store any relation to the digital wallet except where a DPAN is provided instead of the card's actual PAN.
pm_1PLeCnGjO3bEFd6gyZYSzWMt : type card
lavish sequoia
We have a lot of failures from Apple Pay based cards that respond with do_not_honor
quick locust
Do you have an example Payment Intent or Charge ID I could review?
lavish sequoia
pi_3QwyKSGjO3bEFd6g1BELsHtW
I mean it's a pretty high failure rate. We do not see this % on normal card payments
quick locust
Hmmm.... yeah we sent the data we had to the bank and that's how they responded.
lavish sequoia
Our only assumption is that we have been storing DPANs instead of MPANs. And these were generated 1+ year ago in a lot of cases and if a user has gotten the latest iPhone then their DPAN is effectively expired right?
quick locust
Yes, DPANs are both card & device specific
Damn, I try to hang onto my phone until it no longer gets security updates 😅
lavish sequoia
That is unfortunate 😩 . Do you have any other ideas of how to potentially save any of these payment methods moving forward without user intervention?
quick locust
Unfortunately no. Apple Pay made the decision a while ago to bias towards more active Customer involvement relating to payments through Apple Pay. They see the friction as a good thing.
But, with the development of Merchant Tokens (MPANs), they are offerring a way around that
It just requires a brand new Payment Method (that whole direct Customer action bias again)
lavish sequoia
That does sound like Apple. Well darn, definitely wish we had anticipated that before we starting accepted Apple Pay as a valid payment method option! Could have saved us some headache here heh
quick locust
Yeah, that sucks. Sorry about that!
lavish sequoia
That's okay, thanks so much for looking into this and helping out!
quick locust
Happy to help! It's why we're here