#aeo_api
mossy hazelBOT
👋 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/1479293114891112621
📝 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.
- aeo_webhooks, 2 days ago, 19 messages
- aeo_best-practices, 2 days ago, 9 messages
- aeo_unexpected, 6 days ago, 51 messages
spice fable
Hey! The allow redisplay option can be specified on either Stripe.Terminal.ReaderProcessConfigOptions or Stripe.Terminal.ReaderCollectConfigOptions as seen in this section here:
https://docs.stripe.com/terminal/features/saving-payment-details/save-after-payment?terminal-sdk-platform=server-driven&lang=dotnet#collect-payment-method
fallen bough
awww man. thanks. trying now.
seemed to work.. is there a different message that shows on the terminal, similar to the web, like "you authorize blah blah to use this payment in the future" i didn't see that when I just tested
spice fable
For the terminal flow, you have to ensure consent youself as a merchant as seen in this section here:
https://docs.stripe.com/terminal/features/saving-payment-details/overview#compliance
You’re responsible for your compliance with all applicable laws, regulations and network rules when saving a customer’s payment details.
Add terms to your checkout flow that state how you plan to save payment method details and allow customers to opt in.
Some example patterns include a "Save my payment method for future use" checkbox (e.g., on an app screen, POS UI)
fallen bough
interesting.. ok.. thanks. not sure how that is supposed to work when a customer is checking out.. but ok.
spice fable
It really depends on how you want your customers to navigate through the flow. One example I can think of is to display a UI on your POS (point of sale) device that collects consent from the customer. Once consent is obtained, send the request to your backend to collect and process the payment method.
fallen bough
i guess, but most of my clients are not using a "customer facing" version of our pos... its intended for employee use..
i guess I could do something with like "set_reader_display".... but that doesn't actually collect anything..
spice fable
Or you could use: https://docs.stripe.com/terminal/features/collect-inputs instead
Readers: Stripe Reader S700/S710 and BBPOS WisePOS E
With Terminal smart readers, you can display input forms and collect information from your customers.
Set reader display is mainly for showing cart details: https://docs.stripe.com/api/terminal/readers/set_reader_display