Accept IFR Lock — Business Onboarding

Standard Operating Procedure for onboarding new builder businesses into the IFR Benefits Network.

Step 1: Initial Contact & Eligibility

Minimum Requirements

• Legal business registration (sole proprietor, LLC, GmbH, etc.)
• Willingness to define IFR lock requirements; 1,000 IFR is the current first-party starting baseline, not a protocol-wide hardcoded minimum
• Smartphone or tablet for QR scanner
• Agreement to follow this onboarding guide and the exclusion criteria below (there is no separate terms document)

Exclusion Criteria

The following categories are excluded from the IFR Benefits Network:

• Gambling, tobacco, or weapons businesses
• Businesses without a physical or digital location
• Blocked entities (sanctioned individuals or organizations)

Step 2: Technical Setup

Option A: Hosted Solution (Recommended)

The fastest way to get started. No technical knowledge required.

1. Open seller mode in the live IFR Benefits app and connect the owner wallet
2. Create the business profile, add a broad public service area such as a city, region or Online, and keep its Business ID. Never enter a street address.
3. Add products or services and configure benefit rules, including the accepted IFRLock or TIME_ONLY CommitmentVault source (see Step 3 below)
4. Authorize expiring checkout-operator wallets when staff need point-of-sale access
5. Bookmark the business checkout URL on the point-of-sale device

Option B: Self-Hosted (For Developers)

For businesses that want full control over the verification flow.

1. Clone the Benefits Network repository:

   git clone https://github.com/NeaBouli/inferno.git
   cd inferno/apps/benefits-network

2. Install dependencies and configure environment:

   cd backend && npm ci
   cp .env.example .env
   # Edit .env: CHAIN_ID, RPC_URL, SELLER_AUTH_DOMAIN, contract addresses,
   # ADMIN_SECRET and DATABASE_URL (no Business ID or API key is needed here)

3. Start the backend server:

   npm run dev
   # Server runs on http://localhost:3001

4. Start the frontend:

   cd ../frontend && npm ci
   npm run dev
   # Frontend runs on http://localhost:3000

5. Verify the lock check endpoint works:

   curl http://localhost:3001/api/health
   # Expected: { "status": "ok", "chainId": <configured CHAIN_ID> }

Step 3: Tier Configuration

Configure the discount tiers your customers can access based on their IFR lock amount. You may also require a separate minimum IFR balance that remains free in the customer wallet. These are recommended starting values — you can customize them for your business.

Step 4: Cashier Staff Training (5 Minutes)

The QR Flow

This customer-presented pass is the recommended flow. The compatible seller-issued QR flow remains available when the seller needs to start the checkout. In both flows, the cashier applies the displayed discount and completes the sale as usual.

What Cashier Staff Does NOT Need

• No crypto knowledge required
• No handling of customer tokens or private keys
• No blockchain understanding
• No contract-address entry during checkout
• No special hardware — any device with a camera works

Current Seller App Flow

• Seller chooses business categories and adds products or services.
• Seller defines discount rules by minimum IFR locked in IFRLock.
• Recommended: customer creates a private short-lived pass; seller scans it and binds the selected rule.
• Customer reviews the exact seller, product, discount, locked-IFR threshold and any optional wallet-held IFR threshold in the original tab, then signs the checkout proof.
• Compatible alternative: seller creates a short-lived rule-bound checkout QR that the customer scans and signs.
• The customer proof redeems the checkout once when the signature matches the claimed wallet, a fresh on-chain read is eligible and the seller who opened the checkout is still authorized. Seller sees REDEEMED (or REJECTED, with the checkout left open) and applies the configured benefit. There is no separate seller redeem step.
• Since the customer-privacy migration of 11 October 2026 the backend stores no customer wallet address or customer history; it keeps a merchant checkout record (shop, offer terms, status, times, lock source, self-redemption flag, the seller wallet that opened it). IFR does not enforce per-customer redemption limits; a seller that needs them enforces them in its own systems. See the migration runbook.
• Registered pilot partners may later receive PartnerVault rewards, paid in IFR only for verified checkout redemptions, valued in EUR, within a fixed budget set by a Governance proposal. Rewards are not active yet.

Step 5: Go-Live Checklist

This checklist covers the hosted seller path. The open, read-only self-check needs none of these steps.

• Business registered in the hosted seller app (self-service, signed with the owner wallet; there is no approval step)
• Discount tiers configured (at least one tier active)
• Scanner URL bookmarked on POS device(s)
• Test scan performed with a known locked wallet
• Cashier staff briefed on the four-step customer-pass flow
• Business signage or sticker placed at point of sale (optional but recommended)
• Support contact saved for troubleshooting

Step 6: Ongoing Operations

Monthly Checks

• Review discount redemption stats in your business dashboard
• Adjust tier thresholds if needed (e.g., seasonal promotions)
• Ensure POS device software is up to date
• Verify scanner URL is still bookmarked and accessible

Support Channels

• Technical issues: Open an issue on GitHub
• Business inquiries: Contact via X / Twitter (@IFRtoken)
• Integration help: See the Integration Guide for developer documentation

FAQ for Businesses