#ludongming_error
ember scaffoldBOT
👋 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/1294140838687014984
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
stone summit
Hmm what do you mean by pulled up
slender stone
clientSecret： pi_3Q8Z4hIC1xDAOwlv1Mw4jevo_secret_uf0t67xqkZBcxqigiUSWckpnT
The information above is the data used for Apple Pay payment
stone summit
Do you use PaymentElements?
slender stone
Hello, are you still there
stone summit
Yes. Can you elaborate on your question?
slender stone
The frontend SDK I am using is confirmPlatformPayment under @ stripe/strip react native.
What I mean is that the front-end retrieves the payment parameters and calls the confirmPlatformPayPayment API to invoke the payment control, but the payment control fails to invoke it
ember scaffoldBOT
low summit
can you call isPlatformPaySupported and see what it returns? https://stripe.dev/stripe-react-native/api-reference/index.html#isPlatformPaySupported
slender stone
The isPlatformPaySupported api was called before the payment method was selected
It's like this, the user reported that the first subscription was normal, but the second time they couldn't use Apple Pay, but bank card payments were normal.
red crystal
Hi @slender stone I'm taking over this thread. So your customer is able to to pay the first invoice that generated by the subscription. Can you tell me more about the "second time they couldn't use Apple Pay" ? If it's the subscription's collection_method is charge_automatically, Stripe would automatically charge your customers using the previously saved card, there's no need to ask your customer to confirm the payment again through your app.
slender stone
clientSecret： pi_3Q8Z4hIC1xDAOwlv1Mw4jevo_secret_uf0t67xqkZBcxqigiUSWckpnT
"subscriptionId": "sub_1Q8Z4hIC1xDAOwlvUNhuahl0"
The above are payment parameters. Do you need them on your end
red crystal
pi_3Q8Z4hIC1xDAOwlv1Mw4jevo is associated with the first invoice that sub_1Q8Z4hIC1xDAOwlvUNhuahl0 generates. And I don't see any payment confirmation request for this payment
Anyway, we have a billing integration doc for react-native, https://docs.stripe.com/billing/subscriptions/build-subscriptions?platform=react-native&ui=elements#react-native-apple-pay and it has a section about Apple Pay. Can I suggest you to go through it?
slender stone
It's like this, the front-end received the parameters required to invoke the control, but the payment control was not invoked on the user side. I would like to ask if your backend records the reason for this failure
It is normal for bank cards to trigger payments, but Apple Pay has failed to trigger
red crystal
No I don't see any logs. Do you see any error from confirmPlatformPayPayment ?
https://stripe.dev/stripe-react-native/api-reference/modules/PlatformPay.html#ConfirmPaymentResult should contains an error object if there's one
slender stone
We have not recorded any logs regarding the failure of confirming PlatformPayment call