aeo_api | Stripe Developers | Page 1

strong blazeBOT Mar 9, 2026, 4:39 AM

#

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

📝 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_api, 3 days ago, 15 messages
aeo_webhooks, 5 days ago, 19 messages
aeo_best-practices, 6 days ago, 9 messages

#

split siren Mar 9, 2026, 4:40 AM

#

for reference, I'm using server driven mode with s700

sinful grove Mar 9, 2026, 4:40 AM

#

Hi! Give me moment to look into this.

split siren Mar 9, 2026, 4:41 AM

#

thank you

sinful grove Mar 9, 2026, 4:59 AM

#

You mentioned you are using setup_future_usage so I am assuming you are using PaymentIntent. It is not possible to disable tap payments on Terminal. But can I confirm if your concern is about wallet tokens being non-reusable?

If so, when your customer taps with Apple Pay / Google Pay and setup_future_usage: "off_session" is set on the PaymentIntent, a generated_card will be created.

But do take note that Ssaved mobile wallets can only be re-used for off_session payments such as those initiated by you for your customers or future subscription [0].

[0] https://docs.stripe.com/terminal/features/saving-payment-details/save-after-payment?terminal-sdk-platform=server-driven#mobile-wallets-considerations

split siren Mar 9, 2026, 5:53 AM

#

i was afraid of this answer. thanks, but that really complicates matters. do you know if this is a feature that has been requested? or in process?

sinful grove Mar 9, 2026, 5:57 AM

#

I am not sure if this has been requested or is on the roadmap. I can provide a feedback to our internal team. Could you provide more details on your use case for this request?

split siren Mar 9, 2026, 6:02 AM

#

basicily, i have a custom pos, and our clients sometimes sell memberships... but they also, just sell whatever else. so saving a payment method is a normal part of our flow... i store references to stripe customer / saved payment methods on my side, and present them to customer at the appropriate times. when setting up a membership (which we control billing through our software), i want to make sure I am collecting a "real" card, and not a mobile wallet, so that the saved payment method can be run in "off_session" or "on_session" when the customer is checking out for themselves. we currently provide messaging to our clients to not accept those payment types, and to "dip" only, but messaging only goes so far, and inevitably people will not follow the rules... I'm just looking to restrict the terminal from accepting tap payments, so that I am sure that the saved payment method will be reusable in all of our use cases.

#aeo_api