Flymebase.

Methodology and security

Trace the rate. Bound the access.

A number becomes useful when its source, age, rounding and ownership are explicit.

Daily reference data

Flymebase stores USD-based snapshots from Frankfurter. Publication schedules and banking holidays affect source dates. The normalized snapshot includes a content hash; it is never relabeled as a real-time price.

A stale snapshot remains inspectable. New conversions using stale reference data are rejected according to the administrator’s age policy.

Every quote retains

  • Original decimal amount and currency pair
  • Converted amount and half-up rounding
  • Source type, date and snapshot identifier
  • Creation and expiry timestamps
  • Ownership and idempotency fingerprint

Controls that match the workflow

IDENTITY

IAMC-connected accounts

Account registration, sign-in and remembered-device PIN use IAM Central. Customer login does not grant platform administration.

ACCESS

Tenant-owned credentials

Keys are generated server-side and stored as hashes. Download once, then rotate or revoke from your workspace.

CONFIG

Encrypted integration secrets

IAMC, Elpixe and payment settings are project-owned database records. Dashboard documents never carry plaintext credentials.

Billing is a separate policy

The USD/IDR operating policy is administrator-published with revisions. It is not a claim about the market rate. Invoices freeze the source USD amount, FX policy, payable IDR amount and purchased plan revision.

Deployment responsibilities

Public deployments need HTTPS, secure cookies, supervised workers, restricted database access and verified backup restoration. Local sandbox payments do not prove public callback reachability or a production availability SLA.

If a key is exposed, revoke it immediately. Activity and administrator audit views provide operational event metadata for review.