Get started
Meter and cap usage for a reseller customer

Engineering

Meter and cap usage for a reseller customer

FastYoke Engineering · 5 min read · Sep 22, 2026

  • Tutorial
  • Reseller
  • Billing

Audience: power users (Enterprise Platform) · Recipe: Meter usage, set your own retail markup, and let wallet enforcement cap a reseller customer.

What you'll build

By the end of this recipe you'll have a reseller customer whose metered usage is priced at your markup, rolled up into a statement you can turn into an invoice under your own name, and protected by an automatic floor: when that customer's prepaid balance runs low they get an alert, and if it hits zero their workspace suspends until they top up. You set the price. FastYoke does the metering, the roll-up, and the enforcement.

One thing to get straight up front, because it's the part people misremember: the "cap" here is not a spend ceiling you type into a box. There is no "stop this customer at $500 this month" field. The cap is a prepaid wallet — usage debits a balance, a low-balance alert fires while there's still runway, and a depleted balance auto-suspends the customer's tenants until it's credited again. It's a floor enforced by balance, not a monthly budget you set. Wire it up right and it does the job of a cap without pretending to be one.

Before you start

  • A channel-partner arrangement. The reseller billing surface lives in the partner portal, which is gated to organizations set up as a channel partner — the Enterprise Platform relationship, not a self-serve toggle. If you don't have partner-portal access yet, that's the conversation to have with us first.
  • At least one customer tenant provisioned under your organization, already generating some metered activity (a few transitions, an AI call, an outbound email — anything that meters).
  • Your own payment connection. To actually collect, you connect your payment account to the portal so invoices issue and settle through you, not through us. FastYoke uses the Vendara connector for this; you attach your own credentials once.

Steps

1. Set your retail markup with a rate card

Open the billing section of the partner portal and go to your rate card. Your rate card is how you turn FastYoke's wholesale metering into your retail price. You set a default markup multiplier that applies to every metered resource, then override it per resource type where you want a different margin — a higher multiple on AI usage, say, and a thinner one on plain transitions.

The multiplier is exactly what it sounds like: 1.0 passes wholesale through unchanged, 1.5 adds fifty percent, and anything up to a generous ceiling is allowed. Resolution is simple — a per-resource override wins, otherwise your default applies, otherwise it's 1.0. Save it once and every future metered event for your customers prices at your numbers.

This is the retail layer. Separately, FastYoke may have applied a wholesale discount to your organization — that's the number we set, and it sits underneath your markup. You don't manage that one; you mark up from it.

2. Fund the wallet and let metering run

Metering needs nothing from you to start — every metered event on a customer's tenant debits that customer's prepaid wallet balance automatically as it happens, and appends to an immutable usage ledger. Your job is to make sure the wallet has money in it. A customer tops up through a checkout flow that credits their balance; a platform grant can also credit it. Credits are append-only, so the funding history is always auditable.

Worth knowing: metering is a soft debit. A wallet is allowed to go negative — FastYoke will not fail a legitimate state transition just because the balance ran dry. Enforcement (the next step) is what turns "negative balance" into a consequence. That separation is deliberate: the customer's workflow never breaks mid-transition over a billing edge case.

3. Let enforcement cap the customer

You don't wire enforcement — it runs on its own, on a sweep, and it's the mechanism that makes "cap" real:

  • Low-balance alert. When a customer's balance drops under the alert threshold, FastYoke emails that org's admins with a link to top up. It fires once and re-arms only after the balance recovers, so nobody gets spammed.
  • Auto-suspend at zero. When a standard customer org's balance hits zero, its tenants are suspended with the reason recorded as wallet-depleted. That's the hard stop — the customer can't run up unbounded usage on credit.
  • Auto-unsuspend on credit. The moment the wallet is topped back into the positive, the suspension for that reason lifts automatically. No manual reinstatement.

Your own partner organization is treated differently: reseller orgs are alert-only and are never auto-suspended, so a low balance on your side is a heads-up, not an outage.

4. Turn usage into an invoice you send

Back in the portal's billing section, your statement is the live retail roll-up of your customers' metered usage, already priced at your markup. When you're ready to bill, generate an invoice — that freezes the amounts into an immutable record — and issue it. Because you connected your own payment account, the invoice goes out and settles through you. You can also set a billing profile so the line-item name your customer sees is your product's name, not ours.

Take it further

  • Reconcile before you bill. The portal exposes a reconciliation view alongside statements so you can check the retail roll-up against raw usage before you freeze an invoice.
  • Tune margin per resource, not per customer. Because markup is set by resource type, you can widen margin on the expensive resources (AI, external calls) and keep commodity actions cheap — one rate card, applied across your book.
  • Watch the whole book, not one account. As you take on more customers, a read-only view across the tenants you operate turns a low-balance alert into something you see before the customer calls you about a suspension.