Integration Planned

BrandForge for Stripe Billing

Sell BrandForge from any Stripe-native SaaS stack with full subscription and metering sync.

Stripe-native

First-class

Metered

Ready

84

Languages

Full lifecycle

6 events

What this integration does

How BrandForge fits Stripe Billing

Stripe-native provisioning

Subscription created in Stripe, BrandForge account provisioned via webhooks. No middleware, no cron jobs.

Direct API integration

Uses Stripe restricted keys and BrandForge webhooks. Nothing sits between the two APIs.

White-label to your customers

Customers see your domain, logo, colours, and SSL. The BrandForge name never appears.

Metered billing support

Track usage in BrandForge, meter to Stripe, and bill customers by volume where the model calls for it.

How it works

From cart to brand kit

  1. Customer subscribes in Stripe

    Any Stripe-hosted checkout or your own can create a BrandForge subscription.

  2. Stripe webhook fires

    customer.subscription.created triggers BrandForge to provision the account.

  3. Brand kit is generated

    The customer lands in your white-labelled BrandForge instance.

  4. Lifecycle syncs both ways

    Subscription state, invoice paid, and payment failed events all sync in real time.

Technical details

Under the hood

Integration type
Direct API + Stripe webhooks
Authentication
Stripe restricted key + BrandForge API key
Provisioning events
create, suspend, unsuspend, terminate, upgrade, downgrade
Webhook events
customer.subscription.updated, invoice.paid, invoice.payment_failed
Module location
BrandForge partner portal
Data direction
Bi-directional. Stripe is the source of truth for subscription state.
Setup

Setup

A handful of steps to go from install to first sale.

  1. Register interest

    Let us know you want it so we prioritise the build.

  2. Create products in Stripe

    Map each BrandForge tier to a Stripe product and price.

  3. Add BrandForge webhook

    Point BrandForge webhooks at the URL shown in your partner portal.

  4. Add Stripe restricted key

    Enter a Stripe restricted key in the partner portal so BrandForge can query subscription state.

  5. Enable and go live

    New Stripe subscriptions provision BrandForge accounts automatically.

Who this is for

Who this is for

Agencies and SaaS-native resellers who bill customers directly through Stripe and want to add AI branding as a subscription product without adopting a hosting billing platform.

Requirements
  • Stripe Billing account
  • Ability to issue Stripe restricted keys
  • BrandForge partner plan (any tier)
  • Public HTTPS endpoint for webhooks
Common questions

Integration FAQ

When will Stripe Billing integration be live?

It is planned. Register interest and we prioritise the build based on demand from Stripe-native partners.

Does it support metered billing?

Yes. BrandForge can report usage back to Stripe so you can bill customers on volume where the model calls for it.

Is the customer experience white-labelled?

Yes. Customers see your domain, logo, colours, and SSL. The BrandForge name never appears.

Can I use Stripe Checkout or my own?

Both. The integration works with any Stripe-hosted or self-hosted checkout that creates subscriptions.

How does billing work?

You bill your customers through Stripe as you already do. BrandForge invoices you monthly at wholesale for active subscriptions.

Who handles customer support?

You handle L1 with your customers. BrandForge handles L2 and L3 platform issues for partners.

Ready?

Stripe Billing for BrandForge

Register interest so we prioritise the build. Stripe-native, metered-ready, free for partners.

  • Stripe-native
  • Metered billing
  • Free for partners
  • Webhook-driven