Billing

Billing in Prontiq is based on credits. Credits are the usage unit consumed by admitted API work. Your signed-in console shows the current plan, usage, payment actions, invoices, and any pending plan change for the active organization.

​

Key terms

​

What counts as billable usage

A request becomes billable after it passes API-key authentication, product access checks, burst-rate limits, and plan/quota enforcement, and Prontiq accepts it for endpoint processing. Requests rejected before admission do not consume credits. This includes missing or invalid API keys, products not included in your plan, burst-rate-limit rejections, and hard-cap quota rejections. Once admitted, a request may consume credits even if endpoint processing later returns a validation error, no match, or an API error. If you believe credits were consumed incorrectly during an incident, contact support.

​

Endpoint credit costs

For response headers and implementation details, see the Credits guide. For traffic protection behaviour, see Rate Limits & Quotas.

​

Usage and billing totals

Usage appears in Prontiq first. Billing totals and invoices can take a few minutes to catch up while billing events settle. Use the Usage page for recent activity and the Billing page for plan, invoice, and payment state.

​

Changing plans

Plan changes are predictable. Before you confirm, the console shows whether the change happens now or at the end of the billing period, what you pay now, and what happens to your credits. There are three plan shapes: If a change needs a verified payment method and your organization does not have one yet, the console asks you to set one up before accepting the change. These rules always apply:

• API keys are not revoked by plan changes.
• Self-service plan changes do not issue refunds.
• Immediate upgrades keep unused credits and add the new allowance.
• Downgrades from included-credit plans wait until the billing period ends, so you keep what you already paid for.
• Leaving PAYG happens immediately, and any accrued PAYG usage is invoiced at that point.
• If you already have a scheduled change and confirm a different one, the old scheduled change is replaced.

​

Moving into an included-credit plan

​

Moving down or back to Free

​

Moving to PAYG

​

Cancelling

Some changes are not accepted because the result would be unclear. For example, you cannot switch to the same plan, move between equivalent included-credit plans, or move to an included-credit plan where price and credits do not move in the same direction.

​

Invoices and payment state

Invoices show the final billing-period charges, tax, payments, and any adjustments for your organization. The invoice is the source of truth for the amount due. The console shows invoice and payment status. Available actions depend on the invoice or payment state, such as paying an invoice or updating a payment method. Request handling still follows the active plan enforcement policy. Billing notifications are sent to the organization contact configured for billing or administration.

​

Closing an organization

Closing an organization disables its API keys and stops new usage under that organization. It does not erase prior invoices, unsettled usage, or payment obligations. If the organization has unpaid invoices, an active paid plan, or unsettled usage, support may need to resolve those before closure completes.

​

Billing support

If you need help with billing, invoices, account access, or plan questions, raise a support ticket through Featurebase.