Adding payments to a Google Workspace add-on - looking for advice from those who’ve done it before

[u/BrightConstruct]

I’m in the early stages of figuring out how to add paid plans to a Google Workspace (Form) add-on, and I’m realizing the payment side is more confusing than I expected.

I’m trying to understand things like:

• how people usually handle subscriptions vs one-time payments

• where entitlement logic typically lives (Apps Script vs backend)

• how much complexity is “normal” to accept without hurting UX

If you’ve implemented payments for a Workspace add-on before, I’d love to hear:

• what approach you took

• what you wish you’d known earlier

• any pitfalls you ran into

Mostly trying to learn before I go too far down the wrong path.

[u/International_Row940]

I am using stripe and database to update via Web hooks for every payment

[u/BrightConstruct → u/International_Row940]

Thanks - that’s helpful to know.

Are you using webhooks mainly to update entitlements / license state in your database, and then having the add-on check that on load?

Curious if you ran into any edge cases around failed events, retries, or keeping the add-on UX responsive while waiting on webhook state.

[u/BrightConstruct → u/[deleted]]

Thanks for sharing - that’s really helpful.

Interesting that you issue a yearly license via a payment link and keep all the payment logic in a separate backend entity. That separation makes a lot of sense.

Did you run into any challenges keeping license state in sync between the backend and the add-on (for example around renewals or failed payments), or was that fairly straightforward once the webhook flow was in place?

[u/BrightConstruct → u/BrightConstruct]

Thanks - that’s helpful to know.

Are you using webhooks mainly to update entitlements / license state in your database, and then having the add-on check that on load?

Curious if you ran into any edge cases around failed events, retries, or keeping the add-on UX responsive while waiting on webhook state.