#josh_applepay-mpan
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/1489270827957485648
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- josh_paymentelement-applepay, 14 hours ago, 25 messages
- josh-unger_unexpected, 6 days ago, 12 messages
Hey hanzo this one is a little tricky. Let me know if all that makes sense.
Hello
Yeah with Stripe.js, you won't pass timing as a parameter. You'd rather configure the paymentRequest under applePay parameter when you create the Element as show in our docs
With regards to verifying if you have MPANs, Sigma is one way - https://docs.stripe.com/apple-pay/merchant-tokens?pay-element=web-pe#merchant-token-auth-rate-monitoring
Let me see if we expose this on the Payment Method object somewhere
Yup that is what we have done and still seeing the issue.
You mean the data isn't showing up in your sigma results?
Gotcha. I don't see any params on the Payment Method or the Charge object in the APIs that expose the token type unforunately.
If you have an example payment method/charge, I'm happy to look internally to see if I can find anything
That would be super helpful. Transaction is pi_3THl1yACfRnI7ss51B8aF0WQ
okay yeah I do see the correct MPAN identifier associated with the card that was used to pay for this PaymentIntent
Unfortunately, this is not something you can self-serve via the API or the dashboard today
Thanks for checking! I'm confused why Recurly then has the token wrong. Can you check this old transaction pi_3Rk9VJACfRnI7ss51SygHvOS? This was the transaction we originally did on Recurly + Apple Pay. Is there anything different between the two other than the obvious amount?
Hmm I don't see an MPAN associated with the card used for that PaymentIntent
Huh. Can you verify pi_3TH5rtACfRnI7ss51zIRF4eh also please?
I see an MPAN on the card used with the above PaymentIntent
To clarify, my team won't know anything about how recurly handles Apple Pay <> MPAN integration (I know you shared some docs but it's somewhat outside our scope of expertise)
So I can't say for certain why some cards are not getting merchant tokens
Since you're integrated through recurly, maybe they can help provide more context on that
Yeah totally we'll also follow up with Recurly as well.
Backend developer question - is it possible to query the MPAN on our end through the API of the payment intent?
Unfortunately, no. We don't have any APIs that let you do that. I believe this is an Apple restriction
Using sigma is the only way to know if the card token type was an MPAN or not