How we protect data, merchants and money.

Encryption at rest and in transit, isolated roles, verified webhooks, licensed identity checks and an append-only audit trail.

At rest
AES-256-GCM
In transit
TLS, SSL to the database
Roles
Isolated JWT secrets
Admin
TOTP two-factor
Audit
Append-only, hash-chained
Disclosure reply
Within 48 hours

One repayment, six checks.

Before a repayment touches a loan balance, it passes every gate in order. One failed check and it never reaches the ledger.

The same layers protect loans, disbursements, identity and admin actions. Each is listed below.

Fig 1One repayment, six checks
Repayment webhook arrives from the payment provider
  1. 1
    SignatureHMAC-SHA512, compared in constant time
    Stops: Forged webhooks
  2. 2
    SourceSender IP checked against the provider's ranges
    Stops: Spoofed senders
  3. 3
    Freshness2-minute timestamp window, 7-day nonce memory
    Stops: Replays
  4. 4
    AmountCross-checked with the payment provider's API
    Stops: Tampered amounts
  5. 5
    WriteRow-level lock, idempotent, decimal precision
    Stops: Double counts and races
  6. 6
    RecordAppend-only audit log in a hash chain
    Stops: Silent edits
Recorded against the loan
Every inbound payment-provider webhook takes this path before any repayment is recorded.

Controls, by layer.

Encryption

Encrypted at rest

AES-256-GCM, protecting confidentiality and integrity.
  • Paystack secret keys, lender-managed and never visible to Floatra admins
  • Bank account numbers, stored encrypted and shown masked
  • BVN and phone numbers, encrypted, plus SHA-256 hashes kept for lookup
  • Mandate references and identity documents
Authentication

Per-role isolation

Each user type has its own signing secret, so one role's token can't reach another.
  • Platforms and lenders: API key exchanged for a JWT
  • Merchants and agents: OTP by SMS or WhatsApp, rate limited
  • Admins: TOTP two-factor in production
  • Revocation by Redis blacklist on key rotation or deactivation
Webhooks

Verified before processing

Every inbound payment-provider webhook is checked.
  • HMAC-SHA512 signatures, constant-time comparison
  • Source IP checked against provider ranges
  • Replay protection: 2-minute timestamp window, 7-day nonce deduplication
  • Amounts cross-checked with the provider API before a repayment is recorded
Identity

Verified before any credit

BVN and NIN through Smile Identity, with biometric face matching.
  • Auto-accept at 80% confidence and above
  • Manual document review from 60% to 79%
  • Auto-reject with fraud logging below 60%
  • Watchlist screening; explicit consent before biometrics
Money

Financial controls

Built so balances and limits can't race.
  • Row-level locking on every financial write
  • Idempotent loan creation and repayment recording
  • Overpayment protection with decimal precision
  • Exposure caps checked atomically in the transaction
  • Retryable and fatal disbursement errors told apart
Audit

Append-only trail

Loan creation, status changes, repayments, admin actions and consent grants, in a hash chain with advisory locks.
  • Every loan outcome writes an immutable decision record
  • Seven-year retention marker, per CBN expectations
Infrastructure

Hardened by default

Containers and headers locked down.
  • Docker containers running as non-root
  • Strict CSP, HSTS (1 year, preload), X-Frame-Options
  • CORS limited to HTTPS origins in production
  • Redis-backed distributed rate limiting
  • Graceful shutdown and multi-instance event bridge
Data protection

NDPA and NDPR

A Data Protection Impact Assessment is complete for biometric verification.
Disclosure

Found a vulnerability?

Email security@floatra.com. Every report is taken seriously, with a reply within 48 hours.

Questions about security?

Ask for sandbox access and see how the controls behave in practice, or write to security@floatra.com.