Billing and credits

A paying developer manages money for a subscription in your API Portal. Recurring plans show a Billing tab with invoices and a link to the Stripe customer portal, usage plans show consumption, and prepaid plans top up a credit balance on the team. Request logs are a separate, optional view. What a developer sees depends on the plan and on their billing access.

Where does a developer see billing for a subscription?

On a recurring paid subscription, the subscription has a Billing tab. It shows the billing cycle, the next invoice date, the pricing details, and an invoice history. A button opens the Stripe customer portal, where the developer manages payment details directly.

Each invoice opens in Stripe through a per-invoice link. The Open Stripe Customer Portal button sends the developer to Stripe to update their card, see receipts, and manage the subscription's payment details.

When is the Billing tab hidden?

The Billing tab appears only when the subscription bills on a recurring plan and the member can read billing. It is hidden in several cases, so not every developer or every subscription shows it.

• The plan is free, contract, or prepaid. These plans do not bill a recurring invoice, so there is no Billing tab. Prepaid plans use the team's Credits tab instead.
• The subscription is still pending, waiting for approval.
• The member does not have at least Read-only billing access in the team.
• Your team activated the subscription from the dashboard without a payment processor, so no Stripe subscription exists.

A member needs Read-only or Full billing access to see the Billing tab. Managing payment in the Stripe customer portal is a developer action in Stripe, not gated further in your portal.

What does consumption show?

On usage-based and overage plans, the subscription shows how much has been used in the current billing period. It appears under the subscription's billing view. Free and flat-fee plans show no consumption, because there is nothing metered to display.

Consumption needs a Stripe subscription, so it follows the same recurring-plan condition as the Billing tab. See Anatomy of a plan for how a plan's revenue model sets which view applies.

How does a developer top up prepaid credits?

On a prepaid plan, the team carries a credit balance instead of recurring invoices. The team's Credits tab shows the balance and lets a developer add to it by creating an invoice. The team draws down the balance as it calls your paid APIs.

1. The developer opens the team and goes to the Credits tab.
2. They see the remaining balance, shown per currency, and a list of credit lines.
3. To add credit, they pick a currency and an amount, then create an invoice.
4. The portal opens a Stripe hosted invoice. Once it is paid, the credit becomes active.

Each credit line shows its amount, type, invoice number, created date, status, and expiry. A credit is Active, Pending, or Void. An invoiced credit stays pending until the invoice is paid, then turns active. Creating a top-up needs Full billing access in the team.

Can a developer see request logs?

When your portal enables usage reporting, a subscription has a Logs tab. It lists recent requests for that subscription, so a developer can confirm their calls are landing and check status codes. The Logs tab is separate from billing and does not depend on the plan being paid.

The log table is sortable and shows one row per request:

Where to next