Remediation with credits

Before using Pro remediation

Credits are useful for remediation only after WebRiskOps has report evidence, an eligible finding and a safe delivery mode. Upgrading before the report is ready can leave the account with capacity that cannot start a workflow yet. Use this page when a published report or Billing says Requires Pro, Credits exhausted or Remediation unavailable.

Confirm report eligibility

Follow the path `Reports → Published report → Automated fix workflow → Billing`.

1. Open /reports/{report} for the published report that contains the finding you want to fix. Result: the report page shows findings, quality gate status and the Automated fix workflow area.
2. Confirm the report is published and quality gates passed. Result: you do not spend credits on a draft, blocked or incomplete report.
3. In Automated fix workflow, select an eligible finding. Result: the selected issue count and estimated credit cost show what the workflow will reserve.
4. Read the plan and credit message beside the workflow action. Result: you know whether Pro, existing credits, safe access or ticket-only fallback is the next step.
5. If credits are required, open /billing while switched to the same account and read the Credits row. Result: you can compare remaining, reserved and used credits before checkout.
6. If no finding is eligible, do not upgrade yet; use report remediation guidance or Ticket-only fallback. Result: the next action matches report evidence instead of unused billing capacity.

Upgrade only when Pro is required

Use Billing only after the report has an eligible fix path. The Pro checkout route is `/checkout/pro` when Pro is available. Checkout can upgrade the subscription, but the workflow still waits for provider confirmation before it can reserve credits.

1. In Billing, read Locked feature and Upgrade trigger. Result: Pro appears only when remediation automation, team/client workflow or pooled capacity is the next useful step.
2. Use included credits first; upgrade only when the current plan is too small or Pro-only remediation is locked. Result: the purchase matches the report work you intend to start.
3. Click Upgrade only when the Pro card is enabled. Result: authenticated checkout opens for the subscription.
4. Finish provider checkout and return to Billing. Result: the credit balance may still show the old state while payment confirmation is pending.
5. Wait until Credit balance and renewal timing update. Result: the report workflow can reserve confirmed credits.

Use credits safely

Credits start tracked remediation work; they do not grant unrestricted production access or bypass report quality gates.

• Pro is the subscription step that includes generated remediation tasks, retests, team/client workflow and larger pooled credits.
• Credits remaining is the balance that can be reserved by a new eligible workflow.
• Reserved is already held by an in-progress or pending workflow and cannot start another fix.
• Used is completed usage history and cannot be reused.
• Eligible findings can become fix tasks.
• Ticket-only fallback can export or describe work when connected access is unavailable.
• Review-only patches still require customer approval before pull request creation.
• Retests can be requested after the customer applies or approves the change path.
• Unsafe access, missing evidence or unsupported scope stops the workflow even when credits exist.

Continue remediation or resolve blockers

When the report is eligible and credits are available, return to the published report and start the automated fix workflow. If the workflow cannot start, use the blocked state before upgrading.

• Requires Pro means remediation automation is locked behind Pro.
• Credits exhausted means available credits are empty after reservations and spent entries.
• No eligible finding selected means return to the report and choose a supported finding.
• Connected access unavailable means use [Ticket-only fallback](/docs/remediation/ticket-only-fallback) or connect safe access.
• Payment confirmation pending means wait on [Billing](/billing) until the ledger updates.