Payment blocks don't work for anonymous users

Support
1

Hi,

I built an agent with an Authorize Payment → Capture Payment flow and set it to Public with Anonymous Access enabled. Everything is configured correctly, but when I check the Errors panel, I get this message:

“Anonymous public usage is enabled. AI costs from payment-enabled workflows will be billed to your account since anonymous users cannot be charged directly.”

This means my payment gate is completely bypassed for anonymous users — which is the majority of my intended audience, since I’m sharing the agent via a public link to people who don’t have MindStudio accounts.

My setup:

  • Access: Public :white_check_mark:
  • Anonymous Access: Enabled :white_check_mark:
  • Cost Responsibility: Agent Owner :white_check_mark:
  • Authorize Payment block: $10.00, correctly connected :white_check_mark:
  • Capture Payment block: At end of flow :white_check_mark:
  • Everything looks right — the platform itself is flagging the limitation

My questions:

  1. Is anonymous payment collection planned/on the roadmap?
  2. What is the currently recommended workaround for charging non-MindStudio users?
  3. Is the only option right now to gate payment before the agent link (e.g. Stripe/Razorpay link → then redirect to agent)?

Would love an official answer on this. Thanks!

2

Hi @kirankri,

Thanks for the post!

  1. Anonymous payment collection isn’t on the public roadmap right now, but it’s logged as a feature request

  2. The recommended workaround is embedding. You host the agent on a paywalled page of your own website and handle billing through your own Stripe setup or payment plugin. Your users get a seamless experience without needing a MindStudio account or workspace balance. Here are two resources to get started:

  1. A Stripe link → redirect flow could work technically, but embedding gives you a much cleaner user experience and more control over the flow end-to-end. It’s the path most builders take for this use case.

Hope that helps!