#alex_best-practices

1 messages · Page 1 of 1 (latest)

austere voidBOT
#

👋 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/1337527791431712799

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

potent tide
#

It also sounds like mobile wallets do not yield a generated_card which is a bit of a blocker as well. But also seeing there is a beta program to use mobile wallets to get a generated_card..?

regal tundra
potent tide
#

I've written to that email to see about enabling that.

regal tundra
#

Sounds good!

potent tide
#

Is there any other way to save a payment method from a mobile wallet? we're currently using tap to pay to create a payment intent with capture method manual to delay it somewhat.

We're open to using other terminal devices if that makes the difference, like the S700.

regal tundra
#

Is your account based in the US?

potent tide
#

Canada

regal tundra
potent tide
#

ok, so that's our best bet, even considering the option of developing on the S700 terminal?

regal tundra
#

Yes

potent tide
#

any limitations or things we should know about the S700 option? I have a colleague who is keen on it but I suspect the development effort might prove prohibitive.

regal tundra
#

I do not know of what limitation you may be referring to

potent tide
#

I'm referring to things like: getting a unit to develop on, modifying our existing android app to be compatible, having all of our app updates going through a Stripe review process.

None of those are blockers per se but may mean we don't release anything for the S700 in a timely manner.

Otherwise, in terms of limitations, it seems like we could use setup intents linked to a customer and save the "card-present" payment method to that customer with the S700, will that work for mobile wallets or we'll be back to the same issue of only being able to create a payment intent with capture method manual when it comes to mobile wallets?

#

I'll mention that our app relies on the camera as well, which is listed as not officially supported on the S700.

regal tundra
#

Let me get grab a teammate to help with the question on S700 as I do not have that deep of expertise there

#

As for the difference between setup intents vs payment intents with setup_future_usage..

#

The first one is used when there is no payment/ charge when you collect the payment method details

#

The second one is used when you want to save the payment method details used on the first charge for a later time

potent tide
#

oh I see ok, so in our case we would use setup intent as there is no sale event at the time we receive the payment method

#

ok thanks, should I continue watching this thread for information on the S700 or is it better if someone from the terminal team emails me?

raven gale
#

Hello 👋

regal tundra
#

I'm trying to get someone to jump in this thread now.

raven gale
#

I believe you're referring to needing devkit device for development?

potent tide
#

hi Hanzo, yes that's one element

raven gale
#

Gotcha. We only allow development on DevKit devices yeah. They run a different firmware compared to production S700s

potent tide
#

yes, I recall trying to request one but it wasn't the most straightforward process. what's the canonical way to secure a dev kit?

raven gale
#

Going back to saving wallet payment methods question

potent tide
#

then yeah my other questions that would come before that:
want to confirm:

  1. we will likely have to modify our existing react-native android application to be compatible with the S700
  2. our app relies on camera access, do you have any sense for the camera support, it's listed as not officially supported
  3. every update to our app has to go through a stripe review process
  4. can we save mobile wallets for charging later on an S700 or are we back to payment intents API with capture method manual
raven gale
potent tide
#

ok right, so still the same beta program regardless of S700 or Tap to Pay for saving mobile wallets for future use.

raven gale
#

we will likely have to modify our existing react-native android application to be compatible with the S700
Yeah, Apps on Devices is a bit different so would require changes

our app relies on camera access, do you have any sense for the camera support, it's listed as not officially supported
Officially, it is still in experimental phase. So we don't block you from using it but we can't really provide any support in case things don't work 100% of the times. I believe you can still try to include the camera permission in your app and give it a try..

every update to our app has to go through a stripe review process
That's correct. There are ways you can bypass that while testing but otherwise we do require review of app updates on production readers

can we save mobile wallets for charging later on an S700 or are we back to payment intents API with capture method manual
The beta feature mentioned above would work with S700 once you're approved, yes.

#

ok right, so still the same beta program regardless of S700 or Tap to Pay for saving mobile wallets for future use.
Yes

potent tide
#

ok great thanks that's very helpful context

raven gale
#

Happy to help! 🙂
Anything else I can help with?

potent tide
#

Our ideal experience is to capture a payment method from physical payment cards as well as mobile wallets, that we attach to a customer, that we can in turn:

  • recognize on future interactions
  • charge off-session
#

given those requirements, if there a terminal or other workflow you're aware of that will already do that (available in Canada, ha)? or, essentially, the path forward of updating our MCC to be a rental and applying to the save mobile wallet beta program is the best path forward.

#

and, when it comes to recognizing the user, using the fingerprint of the payment method to correlate

raven gale
potent tide
#

ok, yes the setup intents workflow is the one I'm referring to.

#

ok great, thanks for your help with that, yes I've got some emails going back and forth with support to update the MCC and I've just sent one to request access to the beta. appreciate the help from you both!