Handling verdicts

Switch on action to decide whether the account exists, and use recommendedAction to decide what the player gets: the full account, the account without the welcome bonus, an identity check, or nothing.

Last updated 2026-11-03

Switch on action

Switch on action: "allow" → create the account; "hold" → create it pending and store reviewId; "block" → reject the signup.

action	Your sign-up handler
`allow`	Create the account normally.
`hold`	Create the account as pending: no login, no welcome email, no bonus. Store the reviewId with it (live holds only). The hold is settled by a webhook or by polling; see Hold and review.
`block`	Refuse the sign-up. The reasons are written for your team; decide what, if anything, the player sees.

Use recommendedAction for the bonus

recommendedAction	Suggested handling
`allow`	Full account and welcome offer.
`allow_no_bonus`	The account is allowed (risk score 25 or more): create it, but withhold the welcome bonus or free bet until the player has a history with you.
`review`	Held for review: wait for the decision.
`require_kyc`	Sent on signup.approved when the hold had signals that call for it: activate the account, but ask for identity checks before any bonus or withdrawal.
`block`	Blocked, or rejected after review.

Errors and outages

Decide in advance what happens when InlineShield cannot answer. The shared snippets accept the sign-up (fail open) and log a warning; set INLINESHIELD_FAIL_CLOSED to true to reject instead.

401: your API key is wrong or revoked. Fix the configuration; the snippets reject.
402 QUOTA_EXCEEDED on /verify, or success: false with QUOTA_EXCEEDED on /siteverify: over the monthly quota. Treat it as unavailable.
429, 5xx, timeouts: unavailable. Retry later with Retry-After if you queue checks.

Every code: Errors and HTTP codes.

Keep the ids

requestId: store it with every account. It is how you send outcome feedback later.
reviewId: store it with a held account. The webhooks and the status call refer to it.