#mohanad_code
warm oliveBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1260870715217809492
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
terse estuary
Hi, let me help you with this.
What do you mean by "stopped" exactly? Do you have a screenshot?
idle hamlet
Hi @terse estuary
well, let me start from the back a little bit.
we had a release branch last March our tester made his smoke test and confirmed Gpay on Testing was visible ( we have a video of the process recorded )
but we didn't go live since production was not ready yet ( account provider issues )
anyway we tried to start with production steps a few weeks back and found out that Testing was not showing the Gpay option at all ( Tester is in UK and the card is from a UK bank )
we obv tried updating the sdk and going back to the Relesae branch as we suspected that Dev could be the problem but nothing ! Gpay just doesn't show up for us !
we went over many steps and shared Payment ID in the link to the bug on github and nothing really
here's how it looked for us back in March
terse estuary
I see that this PaymentIntent was created with a payment_method provided: https://dashboard.stripe.com/test/logs/req_NNisy7AI1JEHqu
Is it actually related to the integration on the screenshot?
Ok, I see the PaymentMethod was created on Android: https://dashboard.stripe.com/test/logs/req_VruAN3U3wiN5q7
Is it a requirement for you to collect the payment details before creating the PaymentIntent?
idle hamlet
could you elaborate on that part ?
terse estuary
There's a few ways to render the Mobile Payment Element - you can create a PaymentIntent on your backend with amount, currency etc. and then send a client_secret to the frontend to render the component: https://docs.stripe.com/payments/accept-a-payment?platform=android
Or, the way you do it currently, render the Mobile Payment Element with the amount, currency parameters, and after the customer provides their payment details, you create the PaymentIntent.
I was curious why you use the second approach.
idle hamlet
We have a third party provider ( clubspark ) that handles the payments and details of the clients. That's why we don't do the logic through our backend first
warm oliveBOT
terse estuary
I see that Google Pay is actually turned off in your Payment Method settings: https://dashboard.stripe.com/test/settings/payment_methods
I will need to understand better, how your relationship with Clubspark works. Could you elaborate please?
idle hamlet
I see that Google Pay is actually turned off in your Payment Method settings: <h...
Ok, I don't have access with the dashboard and it's owned and moderated by the provider ( clubspark )
but they said that Google pay was active as a paymen method !
Our relationship really is a bit of a partnership
The app handles the booking and other non financial matters. But, once it goes down to customers about to pay the transactions goes through the API's on Clubspark and they handle the dashboard and everything with Stripe.
terse estuary
Here's what I see, maybe they're looking at Live mode settings and not Test mode? These payments are happening in Test mode.
idle hamlet
OK, let me double check with them and get back to you @terse estuary 🙏