PERFORMANCE & PRICINGSMART IDENTITY CACHE

Smart Identity Cache & Billing

Accelerate recurring identity lookups to sub-15ms and slash verification costs by up to 60% with Verixa's automated identity caching engine.

How Smart Cache Works

In high-volume applications (e.g., loan repayments, repeat user transactions, or multi-step onboarding), users often trigger multiple verification checks for the same identity record (NIN, BVN, or Bank Account).

STEP 1: FIRST QUERYCACHE MISS

Live Upstream Query

When an identity is verified for the first time, Verixa routes the request to authorized upstream verification registries. The verified payload is stored in Verixa's tenant-isolated in-memory Redis cache with a 30-day retention window. Billed at standard live rate (₦50).

STEP 2: REPEAT QUERIESCACHE HIT

Sub-15ms Cache Delivery

Subsequent queries for the same NIN, BVN, or account within 30 days are served instantly from cache memory without querying upstream registries. Billed at up to 60% discounted rates (₦20 for NIN/BVN, ₦5 for NUBAN).

Live vs Smart Cache Rate Schedule

Smart Cache savings are applied automatically to all Starter, Growth, and Enterprise accounts.

Service	First Lookup (Live Miss)	Cached Lookup (Cache Hit)	Client Savings	Latency
BVN Verification	95 NGX (₦95.00)	38 NGX (₦38.00)	60% OFF	<15ms (Cache) vs ~140ms
NIN Verification	125 NGX (₦125.00)	50 NGX (₦50.00)	60% OFF	<15ms (Cache) vs ~160ms
CAC Company Verification	120 NGX (₦120.00)	48 NGX (₦48.00)	60% OFF	<15ms (Cache) vs ~220ms
Bank Account (NUBAN)	Free (₦0.00)	Free (₦0.00)	100% Free	<15ms (Cache) vs ~80ms

Identifying Cached Responses

Verixa returns audit metadata in the standardized response envelope. When a query hits cache, meta.cached is set to true, along with the timestamp of the original verification.

Standardized Cache Hit Response Payload

{
  "status": "success",
  "data": {
    "nin": "11234567890",
    "first_name": "CHIDERA",
    "last_name": "OLUTOLA",
    "gender": "male",
    "residence_state": "Lagos"
  },
  "meta": {
    "cached": true,
    "cached_at": "2026-10-01T14:22:10.450Z",
    "provider": "verixa_smart_cache",
    "upstream_provider": "primary_gateway",
    "referenceId": "vx_cache_8f19a02d41ba",
    "cost_ngx": 20,
    "latency_ms": 12,
    "environment": "live"
  }
}

Forcing a Fresh Live Lookup (Cache Bypass)

If you need to guarantee that data is re-queried directly from upstream verification registries (for example, during annual AML re-kyc reviews), include the X-Bypass-Cache: true HTTP header.

Bypassing Cache with X-Bypass-Cache

curl -X POST https://api.verixaid.com/v1/verify/nin \
  -H "Authorization: Bearer vrx_live_9f83a8f1e2..." \
  -H "X-Bypass-Cache: true" \
  -H "Content-Type: application/json" \
  -d '{"nin": "11234567890"}'

Data Isolation & NDPR Compliance

Verixa Smart Identity Cache is strictly tenant-isolated. Cache entries are partitioned by organization ID, ensuring that no client ever accesses records queried by another company. In accordance with the Nigeria Data Protection Act (NDPR), identity cache records are encrypted at rest and automatically purged when their TTL expires.