#Reflixez88
distant wolf
unkempt sable
Do you have a request ID for one of these transactions?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
sand coral
Yes that example is: https://dashboard.stripe.com/logs/req_r5YKNrIEu1hgOf
unkempt sable
Looking into this now
sand coral
thank you!
just for comparison, this is the log for a successful Apple Pay rebill payment for the same user exactly 1 month ago: https://dashboard.stripe.com/logs/req_hzApHidf4IzLTV
unkempt sable
Thanks for that additional context. I'm working with a colleague to see if there's anything we can advise, as it appears as an issuer decline, which complicates the troubleshooting process a bit.
sand coral
hmm got it thanks, but it might be an issuer decline because the card is being manually passed in by Recurly instead of using the Apple Pay payment ID that already exists (e.g. trying to manually use their underlying card instead of Apple Pay)?
unkempt sable
That's correct. It seems like the best course of action would be to (1) contact Recurly and see if they are seeing this happen for their other users, and then (2) open a Stripe support thread to have someone keep an eye on the decline rates for Apple Pay in case this is an upstream error.
sand coral
understood, so most likely this is a Recurly technical configuration issue right?
unkempt sable
We believe that is the case as the alternative seems to be that Apple Pay is erroneously declining charges and you're the first person to report it (https://www.apple.com/support/systemstatus/)
Unfortunately my tooling and visibility beyond that is very limited.
sand coral
got it thanks!