How credit programmes work
1
Create a non-cash programme
In the programme form, choose Non-cash rewards and describe the reward (e.g. “50 credits
per referred customer”).
2
Define the delivery amounts
- Credit label — the unit, e.g.
ai_creditsorfree_days. - Referee bonus — credit the new signup receives (0 = none).
- Free user reward / Paid user reward — what the inviter earns depending on the referred user’s tier.
3
Connect a fulfilment backend
Credit can only be delivered once you connect a backend (see below). Until then, grants are
recorded as earned but not delivered.
earned → delivered, or
revoked if refunded or blocked for self-referral). Grants are
idempotent, and refunds revoke them just like cash commissions.
Fulfilment connectors
Set up delivery under Configuration → Integrations → “5 · Credit fulfilment”. Choose a driver and map where credit lands:
Config fields include the users table, the match column (how to find the user), the credit column,
and driver-specific values (database, base ID, webhook). Credentials are encrypted. Use Test
connection to confirm it’s healthy before going live.
Most non-technical setups use Supabase or Airtable directly; teams that want full control
use the Webhook driver and apply the credit in their own code.
The Credits dashboard
Open Affiliate program → Credits to monitor delivery:- Stat cards: Awaiting delivery, Delivered, Delivery issues, Blocked (self-referral).
- A table of Inviter, Kind, Amount, Status and Earned-at.
API & webhooks
Credit grants are also available programmatically:- List grants and balances:
GET /api/v1/credits. - Mark a grant delivered:
POST /api/v1/credits/{id}/mark-delivered. - Subscribe to
credit.earnedandcredit.deliveredwebhooks.
Drive referrals from inside your product
The referral widget and API turn every signed-in user into a referrer automatically.

