Scan credits

Before using scan credits

Scan credits are account-owned allowance for eligible private live audit runs. They belong to the billing account, not to a person, browser session or unrelated client workspace. Use this page when Billing shows a scan-credit balance, a top-up option, or a blocked scan message such as Scan credit required or Payment confirmation pending.

Read scan credit balance

Follow the path `Billing → Billing account status → Credit balance → Latest ledger`.

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. In Billing account status, confirm the account name and Available credits. Result: you know which account balance will be checked before scan start.
3. In Credit balance, find the Scan credits row and compare Avail, Res and Spent. Result: only Avail can start another eligible private scan.
4. Read Latest ledger for recent scan-credit grants, reservations, spent entries or restored credits. Result: you can explain why the available count changed.
5. If Avail is 0 and Credit top-ups are available, continue to the top-up steps on this page. Result: you do not retry a scan that the billing gate will block.
6. If Avail is greater than 0, return to the project only after scope is accepted and start the live audit from the project page. Result: one scan credit can be reserved and later consumed by that run.

Top up scan credits

Use a scan-credit top-up only when the billing account is correct and Billing shows checkout as available. A browser return page is not enough; the ledger changes only after provider confirmation reaches WebRiskOps.

1. In Billing, scroll to Credit top-ups. Result: the available top-up cards show credit type, quantity, price label and checkout state.
2. Choose the top-up whose credit type is Scan credit. Result: you do not buy automated-fix credits or another credit type by mistake.
3. Click Top up credits when the button is enabled. Result: authenticated checkout opens with the selected top-up.
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 Latest ledger show the new scan-credit grant. Result: the next private scan can use the confirmed credit.

Understand reservations and spending

Scan credits move through the ledger as the product reserves, consumes or restores capacity for eligible private scans.

• Public quick scans and public previews do not consume private scan credits.
• Unsupported targets do not consume credits because the workflow must stop before scan execution.
• Avail is the count that can start another eligible private scan.
• Res is held for an in-progress or pending scan and is not available to another run.
• Spent is ledger history 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 Avail is greater than 0 and scope is accepted, continue to [Run the first live audit](/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.

• Scan credit required means the selected workflow needs an available scan credit, active subscription or approved trial before it can run.
• Scan credit exhausted means the account has no available scan 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.