DocsFallback
Fallback and the never block rule
PlannedNot every visitor can answer from a wallet yet. Ageseal tells your page why a check could not run, and you decide where to send the visitor next. The gate never blocks someone because of your plan limits.
When a visitor has no compatible wallet
A check can end without an answer. The browser may not have the Digital Credentials API, the visitor may have no wallet that holds an age credential, or they may close the picker. In each case Ageseal.check resolves with result: "unavailable" and a reason, and Ageseal does not bill the attempt.
Early on, wallet coverage is low, so plan for a real share of visitors to land here. Make the fallback a normal part of your flow, not an error page.
Plug in another check
Ageseal never processes the fallback. Send the visitor to any age assurance provider you already use, then continue as you would after a pass. The pattern is the same for every provider:
const r = await Ageseal.check({ key: "pk_test_9fK2", over: 18 });
if (r.result === "pass") {
await fetch("/age-ok", { method: "POST", body: r.token });
continueToCheckout();
} else if (r.result === "fail") {
showMessage("This purchase is only for people over 18.");
} else {
// unavailable: no wallet, cancelled, spend cap, network ...
// Keep r.reason for your own logs. It contains no personal data.
window.location.href = "/age-check/other?return=" + encodeURIComponent(location.pathname);
}failis a real answer: the wallet said the visitor is under the threshold. Do not send them to a weaker check.unavailableis not a refusal. It means Ageseal could not ask.- Whatever your fallback returns, record it on your side. Ageseal only counts hand offs, per reason.
The never block rule
Ageseal does not stop your visitors at the door because of a limit on your account. These rules apply to every paid plan:
- At your monthly allowance the gate keeps working. Extra checks are billed at your plan overage rate, and you get email alerts at 80% and 100% of the allowance.
- You never pay more in a month than the next plan up would cost.
- If you set a spend cap and it is reached, Ageseal stops spending and sends visitors to your fallback check. Spend caps are planned: the SDK will report
unavailablewith the reasonerrorand a code that names the cap. - Failed and abandoned attempts, such as a closed wallet or an error, are never billed.
- A signed result is reused for 30 days on the same browser without a new charge.
| Plan | Live checks included | Each extra check | Sites |
|---|---|---|---|
| Developer | 100 in total, then test mode only | None | 1 |
| Starter | 1,000 a month | €0.03 | 3 |
| Business | 4,000 a month | €0.025 | 10 |
| Growth | 12,500 a month | €0.02 | 20 |
| Enterprise | 150,000 a month | From €0.008 | Unlimited |
Prices are in euro and exclude VAT. They are planned and may change before launch. Current plans are on the pricing section of the home page.
Set a fallback URL
The fallback hook is part of Starter, Business, Growth and Enterprise. In the dashboard you set, per site, the URL visitors are sent to when no check can run, and you can set a spend cap under Billing. Ageseal warns you when a spend cap is on and a site has no fallback URL. On the Developer plan you handle fallback in your own code, as above.
What to watch
- The dashboard shows hand offs by reason, so you can see whether the share of visitors without a wallet is falling.
- Keep the fallback working all the time. It is also what protects you if a browser changes its wallet support.