Docs/Build guides/Pilot launch guide

Pilot launch guide

A practical launch path for brands tokenizing selected loyalty value from sandbox testing to production pilot.

GoalMove from existing loyalty stack to a controlled tokenization pilot.

Loyfin pilots should start with one clear onramp and one clear offramp. Keep the brand's CRM, points database, customer auth, fraud checks, support, and fulfillment in place; use Loyfin for the selected loyalty value that should become tokenized and redeemable onchain.

Launch path#

01

Scope

Choose one existing loyalty balance, campaign, expiry rescue, credit, perk, or reward bucket to tokenize.

02

Sandbox

Run Base Sepolia issuance and redemption using a disposable issuer, relayer, and customer wallet.

03

Integrate

Connect your backend to signed issuance and redemption actions, then poll receipts until issuer webhooks are available.

04

Pilot

Move to Base mainnet with a small customer cohort, clear customer copy, and a support/reconciliation runbook.

Decisions#

  • Choose the issuer wallet or multisig. The issuer is the permanent brand identity and signs issue/redeem actions.
  • Choose the admin owner. The owner controls metadata, royalties, and capability flags until ownership is renounced.
  • Decide whether tokenized points can transfer, whether redemption is open, and whether any expiry bucket is part of the pilot.
  • Choose your operation ID strategy before launch. See Operation hash.
  • Decide whether your app will use the signed API plus Loyfin relayer, submit contract transactions directly, or run its own relayer.

Sandbox#

Non-production environments should use Base Sepolia. A brand engineer should complete one issuance, one redemption, one failed duplicate nonce, one expired deadline, and one polling-based confirmation before moving to production.

Production checklist#

  • Confirm the production factory, event emitter, and USDC addresses in Contract addresses.
  • Move admin owner to the intended multisig before opening broad access.
  • Store signed operations internally with operation hash, customer ID, loyalty ID, amount, expiry bucket, status, and support reference.
  • Poll receipts until issuer webhooks are available. See Receipts and polling.
  • Prepare customer-facing copy for fees, expiry, transferability, and redemption. See Customer communication.

Get access#

The verified brand pilot is intake-based so we can review the loyalty program, integration path, issuer/admin setup, and launch timeline before production use. Start from Get access.