#NewtReyes
1 messages ยท Page 1 of 1 (latest)
Hi ๐ just to clarify, are you looking to use a physical reader to save a tapped payment method, or are you trying to save a payment method that was provided by a customer tapping their payment method to your iPhone?
We would like to save it and later on use it, if possible at all.
Apologies for not being precise, I was looking for clarity on whether you plan to use one of our physical terminal readers to save payment methods as seen in this flow (this flow does not support saving wallet payment methods):
https://stripe.com/docs/terminal/features/saving-cards/overview
Or if you were referring to processing payments using just an iPhone and our Terminal SDK via our new approach:
https://stripe.com/en-gb-us/terminal/tap-to-pay-on-iphone
We will be implementing both
Our present understanding is that option 1 (Apple Pay) won't allow us to save the credit cards but we are not sure about option 2 (iPhone's Tap to Pay)
Gotcha, I'm not sure either off-hand either and will need to consult with teammates.
Thank you, Toby
While I do that, my suspicion is that they can't be saved based to align with the behavior discussed here about Apple Pay payments likely being declined when reused for anything other than Subscriptions:
https://stripe.com/docs/apple-pay?platform=web#recurring-payments
Thank you for your patience, my teammates have confirmed that you cannot save wallet based payment methods for reuse.
Ok
Thank you, Toby
Now, does that mean I can't use SetupIntents at all or is it that if I use a SetupIntent, then the Payment Method generated can only be used for a single transaction?
From what I am reading, it looks like Apple Pay will only support PaymentIntents (https://stripe.com/docs/apple-pay)
No mention of SetupIntents in that page.
On the other side, Google Pay seems to support both according to this: https://stripe.com/docs/google-pay
You can use Setup Intents with Terminal, the guide for that can be found here:
https://stripe.com/docs/terminal/features/saving-cards/save-cards-directly
Sorry, I'm getting a little confused as the screenshots you're sharing seem to be from our guides related to accepting Google Pay or Apple Pay payments through a mobile application, rather than via a Terminal integration.
I am sorry about the confussion
That's probably because I am confusing things in my head too
Sorry about that
๐
All good!
Let's go back a couple of steps to get this untangled
So, we are building a mobile app for processing payments that will be used by "in the field" users that will be charging customers. This is not an app that will be downloaded by customers but an app that will be used by "in the field" employees. Ex Pizza Delivery guy
Does that make sense?
It does
Awesome
Now, we are working with the Terminal SDK to allow them to swipe / tap cards to charge those cards.
We would like to also support Apple Tap to Pay
On top of that, we were wondering if there is any way to use Google Pay / Apple Pay to charge customers from this app (Pizza Delivery guy app) without the customer having to download an app on their mobile devices.
Does that make sense?
Yes it does, and as far as I know that is possible.
Awesome
Then let's tackle each case separately, if that is OK with you.
Let's start with Tap to Pay
Is there any documentation on how to use the Terminal SDK to support Tap to Pay?
IMPORTANT: We would like to save the CC as a Payment Method for future use using Setup Intents if possible at all.
On this point, if you want to process a payment from the app then I do not believe a Setup Intent is the right approach.
That may very well be the case.
The reason we have been using SetupIntents for capturing Credit Card information is because we need the Credit Card information to calculate the right Application Fee when creating the PaymentIntent.
So, our process is usually this:
- Create SetupIntent
- Capture CC as payment method using SetupIntent
- Based on the CC info, calculate Application Fee.
- Create and Capture PaymentIntent using calculated ApplicationFee and Payment Method.
Does that make sense?
Yup, and my understanding is that will work fine for cards, but that it may not work for wallets.
Awesome
I believe this guide does the best job of walking through the flow of using a Setup Intent with Terminal to save payment method details:
https://stripe.com/docs/terminal/features/saving-cards/save-cards-directly
And that you would combine it with these guides, specific to setting up Tap to Pay on iPhone functionality, to leverage that feature:
https://stripe.com/docs/terminal/payments/setup-reader/tap-to-pay-on-iphone
https://stripe.com/docs/terminal/payments/connect-reader
Hi. Stepping in for Toby as they have to step out. Let me ask a colleague about this. Will get back to you
Yep just confirmed SetupIntents can be used with Tap to Pay
Awesome
Thank you, @small fjord
Now, we would also like to support Google Pay and Apple Pay
Let's start with Google Pay. Just to make sure we are on the same page, the question is this: Is there any way to use Google Pay to charge customers from this app (Pizza Delivery guy app) without the customer having to download an app on their mobile devices?
IMPORTANT: We would like to save the CC as a Payment Method for future use using Setup Intents if possible at all.
You're talking about tap to pay? Wallets (Google Pay, Apple Pay, etc) aren't supported unfortunately as my colleague toby mentioned
Yep just confirmed SetupIntents can be used with Tap to Pay
I think with this, I am all set with Tap to Pay.
Now, for Google Pay: am I correctly understanding things when I say that from what you are telling me Google Pay (Wallet) does not support setup intents?
Actually, maybe we should go back a little. What we are building is a Terminal App (Ex. Pizza Delivery Guy app).
This app will be installed in the Pizza Delivery Guy mobile phone. Is there any way to charge a CC that's in the customer's Google Pay Wallet from the Pizza Delivery Guy's mobile phone app?
Is that even possible?
(sorry, I have never used Google Pay)
Gotcha. No I don't think there is an easy way to do that. Unless you can have them display a qr code or something that the customer will scan on their phone where they can check out on their device. The issue is they need to be signed in to their Google account on the device where payment is being made for google pay to work
Google pay won't work with tap to pay
Yeah
that's what I thought too
So, let's say we generate a QR code, they scan it and that takes them to some webpage.
In that webpage, we could use this to continue with the process, right? https://stripe.com/docs/google-pay
Yeah, specifically the Web tab of that guide
So you'd end up using Elements, Checkout, or Payment Request button