FuzeMetrix integration rules
The IBA’s business rules for the FuzeMetrix (FM) integration — what FM-operated tunnels can rely on, what the IBA promises in response, and what flows are gated on currency. The technical contract (HMAC scheme, payload formats, exact endpoint shapes) lives in Tech docs → FuzeMetrix integration.
What the integration promises
Member validation at check-in. When a flyer checks in at an FM
tunnel, the tunnel sends the IBA the flyer’s member_id and IBA PIN,
and the IBA responds with their current standing — name, level,
currency status. That’s what stops a non-member from passing themselves
off as qualified.
That’s the headline job. Everything else either flows through other paths or isn’t yet integrated.
What the integration deliberately does NOT do
The IBA’s FM integration is narrower than the Convergence integration for USA tunnels:
- No custom booking links. FM tunnels don’t have member-specific pricing flows in the way Convergence does.
- No automatic logbook sync from FM bookings. Logbook entries from flights booked through FM tunnels happen through other paths — manual member entry, instructor-side logging — rather than the integration writing entries.
If FM expands to cover automatic logbook sync in future, the currency split rule applies — logbook entries are gated on flyer currency, not currency status alone.
Trust model
Even with the narrower scope, every payload between the IBA and an FM tunnel is signed using HMAC-SHA256 with a shared secret. Both sides verify the signature before acting. A request that fails signature verification is rejected without a hint about what was wrong — deliberately, to avoid leaking information to attackers.
The shared secret is rotated periodically; rotation is coordinated out-of-band with each FM tunnel.
Member identity payload
When the IBA returns a validated member, the payload includes:
- Identity — name, member_id.
- Standing — current
role_id, currency status (active / inactive), home tunnel. - Level — current flyer level (1–5) and any instructor / trainer / examiner / coach / military authorities the member holds.
What’s deliberately NOT returned:
- Logbook details (flight count, individual flights).
- Fees / payment status.
- Any PII beyond what the tunnel needs to confirm identity at the desk.
Sub-page
- Public-facing rules reference — original public reference for the FM integration including the four-task overview, currency-driven email triggers, and data-format conventions.