#emil - issuing and apple pay
brittle jolt
hey there, do you have an example of this failing recently? what sort of errors do you see?
and do you have an example of a successful one that was previously set up?
glossy wedge
yes here are the error messages that pop up on Apple Pay
glossy wedge
and do you have an example of a successful one that was previously set up?
do you need the Stripe Issuing card ID? i can send that
or the success screen with Apple Pay?
brittle jolt
To confirm, you're a developer for the company managing the issuing cards here?
glossy wedge
yes, we use Stripe Issuing api
brittle jolt
(just so i have the right context)
glossy wedge
yes, we use Stripe Issuing api. I am a developer from the company
brittle jolt
OK, and are you receiving the authorization requests for these attempts to set up the card?
glossy wedge
no, Apple Pay wallet works with an Apple developer certificate that Stripe maintains - see this page in Stripe settings https://dashboard.stripe.com/settings/issuing/digital-wallets (there's an application process that Stripe handles to approve on Apple Pay)
authorization attempts are not attempted by Apple Pay to verify the card, (Google Pay works like that but not Apple Pay)
brittle jolt
ah, thanks. looking at that.
Can you share the cardholder id for an example card here?
According to this: https://stripe.com/docs/issuing/cards/digital-wallets?platform=iOS#add-to-wallet-manually
the cardholder needs to have email or phone number set to receive the one time code to add the card. Is it possible the cardholder having issues having neither of those set?
glossy wedge
here is a card holder ID:
ich_1IxdGqPaPNsDAn4ByKDCHANt
and card ID: ic_1K70lZPaPNsDAn4B4zvhAdnu
all users have an email set on their cardholder information. It seems to not be sending the confirmation email/text even.
I think it's an issue with the Apple Pay wallet certificate/approved application. I feel like there must be some type of issue there as this suddenly happened since 2 days ago
brittle jolt
do you have an example of a card that worked successfully recently?
You should check your code though, i would have expected it to return eg a 400 if the signature failed
so you might be returning success even when the endpoint fails to receive the event properly
glossy wedge
here's an example of a card that worked:
ic_1K75OhL1IhhmDSAASP9aU2Ca on account acct_1HHq0cL1IhhmDSAA
brittle jolt
perfect thx
glossy wedge
so you might be returning success even when the endpoint fails to receive the ev...
with the manual Apple Pay wallet adds we don't actually receive any data back though
brittle jolt
and to be clear, this is still happening for you, it wasnt a transient error?
brittle jolt
@glossy wedge Is one of these a case you control for testing? I'm still looking into this but wanted to ask if removing the card and re-adding it makes sense. From the screen shots you shared its only asking for exp/cvc, not the card number, so it seems like that was possibly entered previously.
glossy wedge
this is still happening, but I actually had someone from Stripe reach out and I think I understand what caused this issue
we are working with someone directly at Stripe Issuing to set us up on a unique BIN range
apparently they accidentally set it live while we were testing. I believe these new card BINs are not set up to be approved with Apple Pay yet