Docs/Operate your integration/Mainnet launch guide

Mainnet launch guide

Test wallet conversions with a small group, connect your points database, and open the integration to customers on Base.

GoalAdd wallet conversions to your existing loyalty program.

Start with one type of eligible point balance. Test converting points into wallet tokens and converting them back. Keep your existing customer login, points database, fraud checks, and support process.

Launch path#

01

Scope

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

02

Dry run

Run controlled Base Add to wallet and Add from wallet flows using disposable issuer and customer wallets.

03

Integrate

Connect your backend to signed issuance and redemption actions, then poll receipts before changing final brand-side state.

04

Launch

Open the integration to customers with clear instructions, a support process, and tested balance reconciliation.

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 and royalties until ownership is renounced.
  • Decide whether tokenized rewards can transfer, whether Add from wallet is open, and whether any expiry bucket is part of the launch scope.
  • Choose your operation ID strategy before launch. See Operation hash.
  • Create a Loyfin account, rotate an API key, and configure account-level webhook endpoints before wiring production traffic.
  • Use the session API with Loyfin Checkout, or embed the same customer-paid contract submission flow in your own app.

Dry run#

The web app uses Base. Use isolated local fixtures for failure scenarios; mainnet actions spend real funds. A brand engineer should complete one Add to wallet, one Add from wallet, one failed duplicate nonce, one expired deadline, and one polling-based confirmation before broad rollout.

Production checklist#

  • Confirm the production factory and event emitter 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.
  • Use webhooks as the default completion signal, and keep receipt polling as a reconciliation fallback. See Receipts and webhooks.
  • Prepare customer-facing copy for fees, expiry, transferability, Add to wallet, and Add from wallet. See Customer communication.

Public launch#

The current web deployment uses Base. Brands and integration partners should confirm the production addresses, choose issuer/admin custody, and launch with the smallest loyalty value that can be supported clearly.