#ozzy_best-practices

1 messages · Page 1 of 1 (latest)

half blazeBOT
#

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

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

#

⛔️ Stripe developers have stepped away for a short while

Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.

quasi geyser
#
  1. Is continuously cycling PaymentIntents while on the payment page acceptable?
  2. Should unused PaymentIntents be canceled or left in requires_payment_method state?
  3. Is there a recommended pattern for "always ready" NFC on payment screens?
  4. Are there rate limits I should be aware of for this use case?
half blazeBOT
flat crane
#

Hi! Looking into your query now. Give me a moment!

flat crane
quasi geyser
#

It’s semi attended product still as there will be someone there to assist

#

With these timeout logs happening, what’s the best way to make sure the PaymentIntents are captured correctly and still follow Stripe’s appropriate guidelines?

wide remnant
#

Hi @quasi geyser I'm also an engineer from Stripe, let me help you on this

#

I won't recommend continusly creating PaymentIntents, you'll eventually run into rate-limit problem as you scale.

#

I'd suggest having a trigger (i.e., a "PAY" button) on your application to create a PaymentIntent when your customer decides to pay

quasi geyser
#

Hi Jack,

Would it be possible to resume the same PaymentIntent if no one taps within the timeout window on Tap to Pay for Android? This would help us reduce the number of requests and stay within the rate limits however I don’t think we can reuse payment intends on tap to pay

wide remnant
#

You can reuse the same paymentIntent for payments. However, there's a variable upper bound limit on how many times a paymentIntent can be confirmed. After this limit is reached, any further call to confirm the paymentIntent will transition it to canceled state

quasi geyser
#

Do you know what the variable upper bound limit is?

#

Appreciate your help Jack

wide remnant
#

It's variable meaning it's different from time to time.