#NewtReyes

1 messages ยท Page 1 of 1 (latest)

errant sparrowBOT
maiden kelp
#

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?

obtuse shadow
#

We would like to save it and later on use it, if possible at all.

maiden kelp
#

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

Use your Stripe Terminal integration to collect card details for online reuse.

Accept in-person contactless payments using an iPhone and the Stripe Terminal SDK โ€“ from physical cards to digital wallets โ€“ without extra hardware.

obtuse shadow
#

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)

maiden kelp
#

Gotcha, I'm not sure either off-hand either and will need to consult with teammates.

obtuse shadow
#

Thank you, Toby

maiden kelp
#

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

Allow customers to securely make payments using Apple Pay on their iPhone, iPad, and Apple Watch.

#

Thank you for your patience, my teammates have confirmed that you cannot save wallet based payment methods for reuse.

obtuse shadow
#

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)

Allow customers to securely make payments using Apple Pay on their iPhone, iPad, and Apple Watch.

#

No mention of SetupIntents in that page.

maiden kelp
obtuse shadow
#

I am sorry about the confussion

#

That's probably because I am confusing things in my head too

#

Sorry about that

#

๐Ÿ˜œ

maiden kelp
#

All good!

obtuse shadow
#

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?

maiden kelp
#

It does

obtuse shadow
#

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?

maiden kelp
#

Yes it does, and as far as I know that is possible.

obtuse shadow
#

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.

maiden kelp
obtuse shadow
#

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:

  1. Create SetupIntent
  2. Capture CC as payment method using SetupIntent
  3. Based on the CC info, calculate Application Fee.
  4. Create and Capture PaymentIntent using calculated ApplicationFee and Payment Method.
#

Does that make sense?

maiden kelp
#

Yup, and my understanding is that will work fine for cards, but that it may not work for wallets.

obtuse shadow
#

Awesome

maiden kelp
obtuse shadow
#

ok

#

Got it

#

Then, can you confirm that SetupIntents can be used with Tap to Pay?

small fjord
#

Hi. Stepping in for Toby as they have to step out. Let me ask a colleague about this. Will get back to you

small fjord
#

Yep just confirmed SetupIntents can be used with Tap to Pay

obtuse shadow
#

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.

small fjord
#

You're talking about tap to pay? Wallets (Google Pay, Apple Pay, etc) aren't supported unfortunately as my colleague toby mentioned

obtuse shadow
#

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)

small fjord
#

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

obtuse shadow
#

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.

small fjord
#

Yeah, specifically the Web tab of that guide

obtuse shadow
#

Yes

#

Got it

small fjord
#

So you'd end up using Elements, Checkout, or Payment Request button

obtuse shadow
#

That makes a lot of sense

#

Awesome

#

that clears it all up from my side, @small fjord

#

thank you so much!!!