Your brand.Our offline rails.
A wallet, a console, an SDK and an API that run inside your ledger.
Two layers, one integration
Reliability first. Guaranteed offline acceptanceon top.
Reliability layer
Keeps every transaction safe through connectivity loss, whatever the payment method underneath.
- Durable local queue on the device
- Idempotent signed transaction envelopes
- Automatic retry with back-off
Reference app (white-label PWA)
A progressive web app with a wallet mode for payers and a merchant mode for acceptance. Partners can ship it under their own brand or use it as a template for their own apps. It is not a consumer brand.
- Offline Vault and overdraft balance
- Pay, request and scan with the camera
- Merchant queue with sync status
Partner Console
Where risk, finance and operations teams see what is happening and configure how it behaves.
- Outstanding offline exposure and pending sync
- Reconciliation and settlement
- Fork alerts with the two conflicting signed payments
- Country Pack and limit configuration
REST API v1 and webhooks
Issue allowances, accept synced payments and receive events in your own systems. Your ledger stays authoritative.
- Idempotent requests
- Signed webhook events
- Hosted ledger or external ledger
SDKs
Embed offline payments in your own app. The Web SDK is available now. Native SDKs will use the hardware keystore on each platform.
- Web SDK
- Android (planned)
- iOS (planned)
- USSD / SIM (planned)
Non-custodial by design
Your licence. Your funds.Our rails.
PayVault is a technology service provider. It is not a bank or a wallet. It never holds customer funds.
The partner
- Holds the licence and the customer relationship
- Holds the funds and the ledger
- Does KYC and sets limits
- Sets overdraft terms and fees
PayVault
- Runs the offline protocol and SDKs
- Reconciles and detects forks
- Operates the risk pool and guarantee
- Produces settlement batches
Pilot metrics we measure
What the console tracks duringa pilot.
These are the measures we agree with each partner up front. They describe what we track, not results we have achieved.
- Share of transactions affected by connectivity loss
- Recovery after reconnect
- Duplicate rate
- Reconciliation accuracy
- Median time to settle
- Transaction loss
- Offline fraud, bounded by policy
- Integration time
No results are published yet. We will share figures only from real pilots, with the partner's agreement.