Trial credits
for a new signup

Every verify response comes back with a grant: what share of your trial this signup gets, and how many credits that works out to.

Decision trace

How it works

1. Set a trial

   Choose full credits, limited share and what a challenge requires.

2. Read the grant

   Every verify response includes share, credits and requires.

3. Apply it once

   Your backend owns the balance. Seed credits from the returned grant.

API

Example request and response. Keep the secret on your backend.

POST https://nolgard.com/v1/verify
Content-Type: application/json

{
  "secret": "SITE_SECRET",
  "token": "BROWSER_TOKEN",
  "account": { "id": "user_123" }
}

// Example: configured 100-credit trial
{
  "decision": "limit",
  "grant": {
    "share": 0.2,
    "credits": 20,
    "requires": null
  }
}

Limits

• Allow gives share 1. Limit uses your limited share, default 0.2. Challenge, shadow and block give share 0.
• Credits are rounded down. Configure a nonnegative whole-number trial up to 1,000,000,000 credits. Without a configured credit total, credits is null; use share with your own trial size.
• Challenge requirements are step-up or payment, unless your policy chooses block. Nolgard does not process payments or maintain your credit ledger.
• After step-up, the default grant remains limited. Choose full explicitly if passing should give someone the entire trial.
• Observe mode returns the full allow grant. Inspect wouldGrant before changing enforcement.

Related

• Repeat accounts
• Step-up
• Spend guard