Understand when an assessment uses enterprise credits and how to reconcile usage.
GOFA configures the enterprise's enabled services, credit grants, grant expiry, and per-service credit rates. These are enterprise settings, not fixed values in the API contract. Confirm the agreed configuration with GOFA before acceptance or load testing.
For an enterprise configured with test-credit accounting:
| Event | Effect |
|---|---|
| Create an Inquiry or issue an eligible session | No assessment charge. |
| Start a service attempt | Reserve the credits needed for that assessment. |
| Recoverable failure or pause | Release the reservation; no successful-assessment charge. |
| Save a successful result | Settle the usage once for the Inquiry. |
| Read a result, return to your site, or refresh | No additional assessment charge. |
An abandoned attempt's reservation is bounded by its lease and can be reclaimed when that lease expires. It is not a permanent successful usage entry. Do not assume simply closing a tab immediately completes every cleanup action.
If there are insufficient available credits or the service is disabled, a new attempt cannot proceed. A launch URL being created successfully is not a guarantee that credits or capacity will still be available when the user starts.
The Hosted Flow's test label means it is a test assessment, not a monetary charge. Test-credit balances and usage can still change. Some GOFA test workspaces are unmetered; use a workspace with credit accounting explicitly configured when verifying deduction and release behavior.
A grant's start and end dates are configured when it is issued. Do not assume all grants last one year or that unused credits never expire. Rates and credits for a particular commercial agreement must be confirmed separately.
Open Usage & billing to review the enterprise balance and service usage. Use the usage history to inspect individual entries and their Inquiry references. Match each completed assessment by Inquiry ID. A retry in the same Inquiry should not create a second settled entry.
Customer filters apply to the relevant detail view; the enterprise balance is still organization-wide. Home reports assessment activity, while usage history reports settled credit usage. Created tasks, incomplete attempts, and completed chargeable assessments are different quantities and need not have equal counts.
A large credit balance does not raise requests per minute or simultaneous scan
capacity. A 429 is a traffic/capacity condition, not a request to buy more credits.
See Errors and limits.