> ## Documentation Index > Fetch the complete documentation index at: https://docs.prontiq.dev/llms.txt > Use this file to discover all available pages before exploring further. # Billing > How Prontiq credits, plan changes, invoices, and current-period usage work. 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. Manage your plan, payment setup, usage charges, and invoices. Contact Prontiq support for billing, invoice, or account questions. ## Key terms | Term | Meaning | | ---------------- | -------------------------------------------------------------------------------------------------------- | | Credit | Prontiq's billing unit for admitted API usage. Different endpoints can consume different credit amounts. | | Billing period | The time window used for current usage, plan allowances, and invoices. | | Current usage | Prontiq's near-real-time credit counters for admitted API work in the current period. | | Billing totals | Billing-period totals used for invoices and payment status. These can lag while events settle. | | Invoice | The final billing record showing charges, tax, payments, and adjustments for your organization. | | Pending plan | A plan change that has been accepted but is not yet the active plan shown by the console. | | Burst rate limit | Short-term traffic protection applied before a request is admitted for endpoint processing. | | Hard cap | A plan limit that rejects additional usage after included credits are exhausted. | ## 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 {/* Generated from BILLING_ENDPOINTS. Do not edit manually. */} | Endpoint | API path | Credits | | ------------------------------------------------- | --------------------------------- | ------: | | [Autocomplete](/api-reference/autocomplete) | `GET /v1/address/autocomplete` | 1 | | [Validate](/api-reference/validate) | `GET /v1/address/validate` | 1 | | [Enrich](/api-reference/enrich) | `GET /v1/address/enrich` | 3 | | [Reverse geocode](/api-reference/reverse) | `GET /v1/address/reverse` | 2 | | [Postcode lookup](/api-reference/postcode-lookup) | `GET /v1/address/lookup/postcode` | 1 | | [Suburb lookup](/api-reference/suburb-lookup) | `GET /v1/address/lookup/suburb` | 1 | For response headers and implementation details, see the [Credits guide](/guides/credits). For traffic protection behaviour, see [Rate Limits & Quotas](/guides/rate-limits). ## 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. | Term | What it means | | -------------- | ----------------------------------------------------------- | | Usage | Near-real-time credit counters for admitted API work. | | Billing totals | Billing-period totals used for invoices and payment status. | | Invoice | The final billing record for a billing period or charge. | 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: | Plan shape | Meaning | | -------------------- | -------------------------------------------------------------- | | Free | No paid commitment. You receive the Free credit allowance. | | Included-credit plan | A paid plan with a fixed credit allowance each billing period. | | Pay As You Go (PAYG) | Usage is billed after your available credits have been used. | 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 | Current plan | Timing | What happens | | ---------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Free | Now | You pay the first billing period now. Any unused Free credits carry over, the new plan credits are added, and a new billing period starts. | | Smaller included-credit plan | Now | You pay the full new plan price now. Unused credits carry over, the new plan credits are added, and a new billing period starts. No refund is issued for unused time on the previous plan. | | PAYG | Now | Accrued PAYG usage is invoiced immediately. You pay the full new plan price, and the new plan credits start fresh. | ### Moving down or back to Free | Current plan | Timing | What happens | | --------------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------- | | Larger included-credit plan | Period end | Your current plan and credits continue until the billing period ends. The smaller plan starts at rollover. No refund is issued. | | Included-credit plan | Period end | Your current paid plan and credits continue until the billing period ends. Free credits apply at rollover. No refund is issued. | | PAYG | Now | Accrued PAYG usage is invoiced immediately, and Free credits start fresh. | ### Moving to PAYG | Current plan | Timing | What happens | | -------------------- | ------ | ---------------------------------------------------------------------------------------------------------------------- | | Free | Now | There is no monthly charge today. Any unused Free credits are used before PAYG billing begins. | | Included-credit plan | Now | Any unused included credits are used before PAYG billing begins. No refund is issued for unused time on the paid plan. | ### Cancelling | Current state | Timing | What happens | | -------------------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------- | | Included-credit plan | Period end | Your current paid plan and credits continue until the billing period ends. Free credits apply at rollover, and API keys keep working. | | PAYG | Now | Accrued PAYG usage is invoiced immediately. Free credits apply immediately, and API keys keep working. | | Scheduled change | Now | The scheduled change is removed. Your current plan continues. No money or credits move. | 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.