One API for regulated money movement. Banks and fintechs plug in once and offer their customers on-ramp, off-ramp, and stablecoin transfers — across multiple licensed VASPs and PSPs.
Working with the regulators, vendors and standards that banks already trust
Three commitments shape every product decision at axe. They are written into our architecture, our licences, and our customer contracts.
SBP and PVARA Sandbox engagement, AML Act 2010 Reporting Entity registration, FATF Travel Rule from day one. The regulatory perimeter is the defining feature of the product, not an afterthought.
Bank-grade APIs, idempotent endpoints, append-only audit log, hash-chained ledger. We ship the SDK, the Postman collection, the OpenAPI spec, and a sandbox before the contract.
RAAST, 1LINK, and IBFT are the spine of every flow. Pricing in PKR, settlement to PKR, support and docs written for Pakistani engineering teams.
axe. is the orchestration layer. Custody and licences live with our partner VASPs and PSPs — not on our balance sheet, and not on yours.
Mobile app · KYC · ledger · end-customer touchpoint
No custody · no principal balance · append-only audit
PSPs hold the PKR licence — axe. never moves fiat.
VASP holds the licence and custody — axe. never holds crypto.
A single transaction can fan out to one fiat PSP and one crypto VASP, chosen at routing time from a pool that grows as more partners onboard.
Banks turn modules on as they need them. Most start with on-ramp and add transfers in month two.
Bank customer initiates a buy in your app. axe. quotes across every connected VASP, picks the best execution, and settles to the customer's wallet. PKR is debited via RAAST or IBFT. The customer sees your brand the whole time.
Customer sells held crypto from inside your app. axe. nets the trade across VASPs, hedges the exposure, and pushes PKR back to the customer's account through RAAST or IBFT. T+0 for retail, T+1 for institutional volumes.
Move USDT, USDC, or PYUSD between wallets — including between VASPs in different jurisdictions. Travel Rule payload assembled and exchanged automatically using IVMS 101. Failed counterparty exchanges are blocked at submission, not after settlement.
For each order axe. scores every counterparty on cost, depth, latency, and live uptime — then routes the leg to whichever path wins. When a VASP degrades, fail-over is automatic. The bank sees one consistent SLA.
Pre-submission KYT screening on every wallet and address. Sanctions, PEP, and adverse-media checks. Suspicious-transaction case management. SAR/STR templates aligned to FMU and SBP. Plug into your GRC stack or use ours.
Every settled order is reconciled against the corresponding line in the bank's ledger, the PSP's settlement file, and the VASP's daily file. Breaks surface in our admin console with a runbook attached. Exporters available in your accounting format.
Eight institution types we sell to. The integration surface is the same in every case.
Tier-1 and mid-tier banks adding regulated digital-asset products without a new licence.
Tech-native institutions where customer demand for crypto on-ramp is already loud.
Stock and asset-management firms expanding into digital assets alongside equities.
Stablecoin rails for inbound and outbound remittance — Gulf, UK, US, Europe.
Stablecoin holdings, hedging, and settlement across multi-country operations.
Existing aggregators and gateways adding crypto rails alongside fiat.
Digital-asset allocation, stablecoin yield, and tokenised products for private clients.
Exchanges and wallets expanding into Pakistan with regulated rails.
Liquidity, technology, and compliance — the three things every Tier-1 procurement committee will dig into. Each is purpose-built for a Pakistani regulated entity.
axe. routes across every licensed VASP we contract with — never holding crypto, always attributing each leg to a specific Order. The bank gets execution depth without owning custody.
Idempotent endpoints. HMAC signatures both directions. OpenAPI spec auto-generated from typed schemas. Sandbox parity with production. Status page public from day one.
SBP and PVARA Sandbox engagement underway, AML Act 2010 Reporting Entity registration in progress. SOC 2 Type II and ISO 27001 sequenced for the first 18 months. Travel Rule baked into the platform — not bolted on.
Pakistan is a top-three country by grass-roots crypto adoption. axe. is the only aggregator built natively for its rails.
Strategy notes, regulator timelines, and engineering deep-dives from the axe. team and our partners.
The PVARA framework opens a licensing pathway for VASPs but does not require banks to become VASPs themselves. We unpack the four operational implications.
Read more →A walk-through of how every axe. order is modelled as a Temporal workflow — and why the database is a projection, not the source of truth.
Read more →Where the threshold lands, how counterparty exchange works, and the four edge cases every Pakistani VASP and bank should design for now.
Read more →If yours is not listed, we'll send the spec and a regulator letter on request.
One call. We share the architecture, the integration plan, the regulator-facing memo, and a draft term sheet. If the fit is right, we walk away with sandbox credentials and an eight-week pilot path.