#jose-luis-fernndez-ft25b_api

1 messages · Page 1 of 1 (latest)

deft flareBOT
#

đź‘‹ 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/1377361359703900252

đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.

plain beacon
#

According to the documentation, using Google Pay with Stripe Checkout doesn’t require any additional programming. However, I’m not sure how the token is passed or how the integration works under the hood.

Is there a complete example of a Stripe Checkout integration with Google Pay available on GitHub or elsewhere that shows the entire flow?

hasty pivot
plain beacon
#

Let me give you a bit more context: on our website, users visit, make a purchase, and then immediately receive access to content directly on the site — either an image or an access link.

In this case, would Google Play Billing still apply, or are we fine using just Stripe Checkout?

hasty pivot
#

My understanding is that you would not need to use Google Pay billing in this scenario (Web Payment and not an in-app payment) . As this is Google's policy you could check with them to get a definitive answer.

plain beacon
#

ok

#

I was reading the documentation on this page: https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=elements#apple-pay-and-google-pay

From what I understand about Google Pay, it typically returns a payment token that should be passed to Stripe. However, in the example code on that page, I don't see where the token is actually being handled or passed to Stripe — could you clarify how that works?

Also, I have a question regarding user management: is it strictly necessary to create and associate a persistent user account for each Google Pay transaction? In our current implementation, we create a new user for each transaction and do not store any persistent user data. However, over time, a single customer might make multiple purchases. Would this setup be compatible with Google Pay through Stripe, or would we need to implement a more persistent user identification system?

hasty pivot
#

We abstract away the token handling and a Payment Method is created for the transaction.

It's not needed to store persistent user data when using Google Pay.

plain beacon
#

So does that mean it's no longer necessary to implement a dedicated Google Pay or Apple Pay button?

Could you point me to a URL in the documentation that explains how to integrate them properly, or perhaps a GitHub repository with a full example?

#

Just to clarify, I'm currently using Stripe Checkout for the integration.

hasty pivot
#

https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=stripe-hosted#payment-methods

"You can enable Apple Pay and Google Pay in your payment methods settings. By default, Apple Pay is enabled and Google Pay is disabled. However, in some cases Stripe filters them out even when they’re enabled. We filter Google Pay if you enable automatic tax without collecting a shipping address.

Checkout’s Stripe-hosted pages don’t need integration changes to enable Apple Pay or Google Pay. Stripe handles these payments the same way as other card payments."

deft flareBOT
plain beacon
#

Okay, I see — so Apple Pay or Google Pay should appear as available payment methods in the Stripe Checkout UI when the user is redirected to the Checkout page, correct?

How can I test this? I’ve tried in sandbox mode, but those payment options haven't appeared for me during testing.

north sentinel
#

đź‘‹ stepping in here

#

Yep Google Pay and Apple Pay will show so long as you have them enabled in your payment method settings and you have a live card in your wallet.

#

When you are in test mode we swap out the live card for a test card during the flow so you aren't charged.

#

But you do have to have a live card for the buttons to show up.

plain beacon
#

What are the steps to add an active card in order to run tests with it?

north sentinel
#

Or your Apple Pay wallet on your iOS/Mac device

plain beacon
#

Ah, okay — I think I understand better now. The card needs to be added to Google Pay or Apple Pay first, and once that's done, the button should appear in the Stripe Checkout UI for the customer, right?

If that’s the case, and I need to switch to a test card, are the test card numbers provided by Stripe, or do they come from Google/Apple?

north sentinel
#

Yep

#

You don't do anything to switch to a test card

#

If you are in test mode (or using a sandbox) then we swap out your live card for a test card during the Google Pay/Apple Pay flow.

#

So nothing you need to do on your end.

plain beacon
#

Alright, I’ll give it a try.

plain beacon
#

I have one more question: if I wanted to implement the Google Pay or Apple Pay button directly on my site, would the integration be different?

The reason I chose to go with Stripe is because, according to Google Pay’s documentation, it mentions that a payment processor is still needed to complete the payment flow.

north sentinel