Betaglia builds the identity infrastructure layer that enables regulated financial institutions to resolve identities, authenticate intent, and route transactions with verifiable auditability across existing payment rails.
Betaglia operates beneath the application layer, providing the identity primitives that regulated institutions require to function at scale.
Betaglia operates at the transaction volumes that regulated financial institutions require, without performance degradation under load.
Betaglia does not maintain a public sales process. Infrastructure engagements begin with a structured briefing.
A structured set of modular services that financial institutions deploy individually or in combination, integrated into existing core banking, payment switching, and compliance infrastructure.
Each module is independently deployable and exposes a consistent API surface.
Real-time alias-to-account resolution. Maps PayTag identifiers, phone numbers, national IDs, and account numbers to verified entities. Sub-15ms P95 latency.
Multi-factor identity verification engine. Orchestrates biometric, document, and database verification across configurable rule chains without storing raw biometric data.
Distributed identity graph. Maintains the canonical mapping of aliases, verified identities, and institution relationships with conflict resolution and merge detection.
Structured consent management that captures, versions, and surfaces consent records against a regulatory-compliant schema. Audit-ready at point of capture.
Rail-agnostic transaction routing that selects optimal settlement paths across NIBSS, interbank, and mobile money rails based on identity resolution and availability.
Real-time fraud decisioning using behavioral signals, device intelligence, and transaction velocity. Returns a structured risk score with explainable factors.
Immutable, tamper-evident audit trail for every identity decision, consent event, and routing outcome. Structured for regulatory examination and legal discovery.
Betaglia does not replace existing infrastructure. It integrates as an identity layer beneath current systems.
Synchronous JSON/HTTPS API with OpenAPI 3.1 specification. Suitable for real-time transaction flows requiring sub-second identity resolution.
Asynchronous event delivery via Kafka-compatible consumers. Identity events, audit records, and routing outcomes delivered to institutional event buses.
Client libraries for Java, Python, and Node.js. Handles authentication, retry logic, and response parsing. Available for private distribution to integration partners.
For institutions with data residency requirements. Betaglia infrastructure deploys within institution-controlled environments under a managed operations model.
Platform evaluations are conducted under NDA with a Betaglia infrastructure engineer and a solutions architect.
Deployed configurations for specific institution types and regulatory environments.
Betaglia integrates with existing core banking systems to provide identity resolution and verification without requiring account number changes or customer re-enrollment.
Betaglia Resolve maintains a continuously updated mapping between aliases (phone numbers, PayTags, national IDs) and verified account identifiers. Resolution occurs before transaction initiation, not during settlement.
Betaglia Trust Engine evaluates transaction risk using behavioral signals, identity confidence scores from Resolve, and velocity rules. Returns a structured risk object with explainable factors that integrate with existing fraud review queues.
Betaglia Audit captures every identity decision, consent event, and routing outcome in an immutable, tamper-evident log. Export interfaces for CBN, NDIC, and custom regulatory reporting are included in the standard deployment.
// Resolve a PayTag to a verified account
POST /v1/resolve
Authorization: Bearer {institution_token}
X-Institution-ID: inst_Hd9KxBv...
{
"alias": "@temizee",
"alias_type": "paytag",
"context": {
"intent": "credit",
"amount": 50000,
"currency": "NGN"
}
}
// Response
{
"resolved": true,
"identity": {
"id": "idn_9kTm3X...",
"confidence": 0.998,
"account_ref": "acct_enc_Q9..."
},
"latency_ms": 11
}
National-scale identity infrastructure that operates as a shared utility across member institutions, without centralizing identity data at the apex bank.
Betaglia's federated architecture enables a central bank to define identity standards and audit requirements while institutions retain ownership of their customer data.
Identity resolution without centralizing PII at the apex institution.
Standardized alias schema across participating institutions.
Structured audit exports designed for supervisory examination.
Full infrastructure deployment within central bank data perimeter.
Central bank and regulatory engagements are handled by Betaglia's infrastructure team directly, under a structured NDA process.
Briefings cover architecture, data residency options, audit interfaces, and deployment timelines.
Betaglia integrates with switching infrastructure to provide identity resolution at the point of transaction initiation, before settlement routing.
Resolve identities across institution boundaries without requiring bilateral agreements between each institution pair.
Route transactions across NIBSS NIP, USSD, mobile money, and real-time gross settlement systems based on identity resolution outcomes.
Identity objects are structured to align with ISO 20022 message formats, supporting migration paths and cross-border payment schemes.
Identity verification and alias resolution for agent-assisted and self-service mobile money environments operating at population scale.
Betaglia Verify supports agent-initiated identity verification workflows, including document capture, liveness checks, and BVN/NIN cross-referencing, within a constrained mobile network environment.
Identity resolution available via USSD session context, returning verified identity objects that can be consumed by existing USSD transaction flows without requiring smartphone access.
Production documentation is available to integration partners under NDA. This reference covers the public API surface.
All API requests are authenticated using Bearer tokens issued to the institution. Tokens are scoped to specific products and carry expiry claims.
Authorization: Bearer <institution_token>
X-Institution-ID: inst_<id>
X-Request-ID: <idempotency_key>
Content-Type: application/json
Complete documentation, including request and response schemas, error codes, SDK references, and integration guides, is available to verified integration partners.
The architecture decisions that determine how Betaglia behaves under load, failure, and regulatory examination.
Platform status across all infrastructure components. Updated continuously.
Betaglia separates identity from account. A single verified identity may be associated with multiple accounts across multiple institutions. Aliases resolve to the identity layer, not directly to accounts.
This architecture enables cross-institution resolution without requiring institutions to share account data. The institution of the receiving account receives only an encrypted account reference after identity confirmation.
{
"identity_id": "idn_...",
"verified_at": "ISO8601",
"confidence_score": 0.998,
"aliases": [
{ "type": "paytag", "value": "@temizee" },
{ "type": "phone", "value": "enc_..." }
],
"account_refs": [
{ "institution": "inst_...", "ref": "acct_enc_..." }
],
"consent_refs": ["cns_..."]
}
Security is implemented at every layer of the stack, not as a perimeter control.
All identity data encrypted using AES-256. Encryption keys managed via HSM, rotated quarterly. PII fields use field-level encryption with institution-scoped keys.
TLS 1.3 minimum for all API communication. mTLS enforced for institution-to-infrastructure connections. Certificate pinning recommended for SDK deployments.
No implicit trust between internal services. All service-to-service communication authenticated and authorized against a centralized policy engine.
Audit log entries are cryptographically chained. Any modification to a historical record invalidates the chain, detectable at the next verification interval.
Performance targets are commitments, not aspirations. They are measured across all production traffic and reflected in the service agreement.
Betaglia supports institution-controlled data residency for institutions with regulatory requirements restricting cross-border data transfer.
The platform is designed for regulated financial environments, where downtime has direct operational and compliance consequences.
All production services operate across multiple availability zones simultaneously. No single-region dependency for any resolution or verification flow.
Under partial failure, services enter defined degraded modes rather than failing open or closed. Degradation state is surfaced to the institution in real time.
Betaglia operates under a formal compliance program aligned with the regulatory requirements of the financial institutions it serves.
Betaglia builds identity infrastructure for regulated financial systems. The company spent years operating infrastructure before entering the public market. That period produced the architecture, data model, and operational practices that now support institutional clients.
Financial infrastructure earns its standing through performance and availability, not through marketing. Betaglia's design principle is that the infrastructure should be indistinguishable from the institution's own systems, composable with existing core banking, payment switching, and compliance infrastructure without requiring replacement of it.
Betaglia Identity Infrastructure is currently deployed across Nigeria, powering the identity layer for FLEX, a live payment network with active users, and extending into the FLEX partner ecosystem including eDryv, where IDaaS serves as the underlying verification and routing infrastructure. Geographic expansion follows regulatory readiness, not market opportunity.
Betaglia does not compete with the institutions it serves. The company builds what institutions need to function, not what institutions sell.
Every system is built assuming regulatory examination. Audit completeness and data integrity are not features; they are requirements.
Infrastructure earns trust through performance and availability, not through marketing. Betaglia does not publish case studies. Institutions evaluate the system.
Betaglia does not maintain an inbound sales process. Infrastructure engagements begin with a structured briefing conducted by the infrastructure team.
Betaglia engagements begin with a structured briefing. Select the engagement type below. All enquiries are reviewed by the infrastructure team within two business days.