Credits

Before using credits

Credits are account-owned allowance for eligible automated work: scans, retests, report work and Pro remediation automation. They belong to the billing account, not to a person, browser session or unrelated client workspace. Use this page when Billing shows a credit balance, renewal timing, an upgrade trigger or a blocked workflow message such as Credits required or Payment confirmation pending.

Read credit balance

Follow the path `Billing → Current plan → Credits → Renewal`.

1. Open /billing while signed in to the account that owns the project you want to scan. Result: Billing shows the account-specific billing email, subscription badge and credit state.
2. Read Current plan and Credits. Result: you know how many credits remain for scans, retests, report work and eligible remediation.
3. Check Included credits and Renewal. Result: you know whether to run now, wait for the monthly reset or upgrade.
4. Read Reserved or Used only when they are visible. Result: in-progress work and past usage do not look like available capacity.
5. If Credits is 0, read the upgrade trigger and renewal timing. Result: you do not retry work that the billing gate will block.
6. If Credits is greater than 0, return to the project and start the scan from Actions. Result: the product spends credits from the same account that owns the project.

Upgrade or wait for renewal

Use the upgrade trigger only when the billing account is correct and the next plan unlocks the work you need. A browser return page is not enough; credits become usable only after provider confirmation reaches WebRiskOps.

1. In Billing, read Current plan, Credits, Locked feature and Upgrade trigger. Result: you know whether Basic, Plus or Pro is the next useful step.
2. Choose Basic for one small project, Plus for more capacity plus monitoring/retests, or Pro for pooled team/client/remediation work. Result: the plan matches the work without adding another purchase type.
3. Click Upgrade only when the next plan is enabled. Result: authenticated checkout opens with the selected subscription.
4. Finish provider checkout. Result: Billing may still show the old balance while payment confirmation is pending.
5. Return to Billing and wait until Credit balance and renewal timing update. Result: the next private workflow can use confirmed credits.

Understand credit use

Credits are the single customer-facing allowance for eligible automated work.

• Public quick scans and public previews use the Free preview allowance, not paid subscription credits.
• Unsupported targets do not consume credits because the workflow must stop before scan execution.
• Credits remaining is the count that can start eligible work.
• Reserved is held for in-progress or pending work and is not available to another run.
• Used is past usage and cannot be reused.
• Restored credits can appear after a failed scan path when the workflow returns the reserved credit.
• One account cannot spend another account's credits.

Continue or fix blocked credit state

When credits are available and Project Pages are ready, continue to [Run the first scan](/docs/getting-started/run-first-live-audit). If Billing or the project still blocks the scan, use the blocked state to choose the next action.

• Credits required means the selected workflow needs available credits, an active subscription or approved trial before it can run.
• Credits exhausted means the account has no available credits after reservations and spent credits.
• Payment confirmation pending means checkout happened but the credit ledger has not been updated.
• Plan does not include this scan means choose a different plan or reduce the scan request.
• Wrong account means switch to the account that owns the credits.