Wallet-as-a-Service infrastructure for bank-grade digital-asset payments.
En3 builds modular Wallet-as-a-Service infrastructure for banks, fintechs, payment providers, remittance companies, and regulated digital-asset payment products in emerging markets. The public GitHub organization documents the integration surface, reference client experiences, sandbox API contracts, control-plane concepts, and deployment boundaries while keeping production security-sensitive systems private.
| Repository | Purpose | Status |
|---|---|---|
| en3-docs | Architecture, integration, security, and deployment documentation. | Public documentation |
| en3-api-spec | OpenAPI, AsyncAPI, webhook schemas, and mock sandbox contracts. | Public sandbox contract |
| en3-wallet-sdk | TypeScript SDK examples for En3 sandbox APIs. | Public SDK artifact |
| en3-web-wallet | White-label web wallet reference app documentation and mocks. | Reference app |
| en3-mobile-wallet | React Native reference mobile wallet documentation and mocks. | Reference app |
| en3-admin-console | Wallet Control Plane reference console with mock data models. | Reference control plane |
| en3-reference-bank | End-to-end mock bank stablecoin wallet scenario. | Reference implementation |
| en3-chain-integrations | Sandbox chain adapters and network configuration examples. | Integration examples |
| Layer | Public explanation | Private boundary |
|---|---|---|
| Cryptographic Core | Key-management boundaries and custody deployment patterns. | Production MPC/TSS, signing orchestration, key-share operations, and HSM integrations. |
| Wallet & Account Layer | Wallet, address, balance, and transaction API contracts. | Production ledger, wallet state engine, and account reconciliation internals. |
| Wallet Control Plane | Organizations, IAM/RBAC, policies, approvals, and audit trails in reference form. | Production policy enforcement and administrative control systems. |
| Payment Operations Layer | Stablecoin flow, treasury, sweeping, and reconciliation concepts using mocks. | Treasury execution, live settlement operations, and production payment infrastructure. |
| Compliance & Monitoring Layer | KYT, sanctions, and address-risk adapter concepts. | Real vendor integrations, rules, case logic, and customer-specific compliance operations. |
| Client & Integration Layer | SDKs, webhooks, web wallet, mobile wallet, and reference bank flows. | Customer deployments, private endpoints, and production partner integrations. |
| Deployment Layer | SaaS, hybrid, on-prem signer, bank-hosted key share, BYO custody, and HSM blueprints. | Real infrastructure, environment configs, and deployment runbooks. |
| Public artifacts | Private by design |
|---|---|
| API specifications, webhook schemas, mock requests, and SDK examples. | Production cryptography, signer orchestration, and key-management internals. |
| Reference web, mobile, admin, and bank workflows. | Production policy engine, ledger, risk logic, treasury execution, and customer deployments. |
| Architecture, security-boundary, and deployment-pattern documentation. | Internal deployment configs, private endpoints, vendor integrations, and operational runbooks. |
| Sandbox chain configuration examples. | Production RPC credentials, customer nodes, allowlists, and infrastructure secrets. |
The first wave of public artifacts is intended to help partners and technical diligence teams understand how En3 thinks about API-first wallet infrastructure, client integration, control-plane workflows, mock payment operations, and deployment flexibility. These repositories are not production custody systems.
Production cryptography, signing orchestration, policy enforcement, risk logic, ledger infrastructure, treasury execution, compliance vendor integrations, and customer deployments remain private by design. Public repositories should not contain secrets, private infrastructure details, real customer data, or production operational material.
Use the public repositories to review the intended integration surface, reference workflows, product boundaries, and architecture model. Detailed production reviews, security assessments, deployment architecture, and customer-specific material should be handled through private partner channels.