Skip to main content

What is Thiqwave

Thiqwave is B2B2B non-custodial cross-border payment infrastructure for the MENA region and beyond. Licensed businesses (banks, PSPs, fintechs) use it to collect funds in one currency, convert them, and settle to a beneficiary in another currency or rail — programmatically, through a single API.

You integrate Thiqwave; your end-users are served through your product. Thiqwave is infrastructure, not a consumer app.

The hub-and-spoke model

Every payment is a journey from source to destination, routed through a Thiqwave settlement hub:

  Source (pay-in)            Thiqwave hub              Destination (payout)
───────────────── ──────────── ───────────────────
Fiat (AED, SAR, Collect → screen → Fiat (INR, PKR, PHP,
USD, EUR, …) convert → settle … 150+ countries)
via Open Banking, ┌───────────────┐
virtual IBAN, ───▶ │ Collection │ ───▶ Stablecoin (USDT, USDC)
instant rails │ Compliance │ to any EVM / supported
│ FX + Settlement│ wallet
Stablecoin (USDT/USDC) ───▶ │ Payout │ ───▶ Fiat bank account
from any wallet └───────────────┘

The hub is rail-agnostic: the code does not hard-code currencies, chains, or providers. Corridors, assets, and networks are configuration, so new routes light up without API changes on your side.

What Thiqwave is

  • A settlement control plane: create participants, request quotes, move money, reconcile, and audit — all via API and the partner console.
  • Multi-rail: fiat-to-fiat, fiat-to-stablecoin, stablecoin-to-fiat, and stablecoin-to-stablecoin.
  • Compliant by default: every flow runs KYB, sanctions/PEP screening, and (for stablecoin legs) wallet screening before any money moves.
  • Auditable: every money movement is a stateful, idempotent workflow with a recorded trail.

What Thiqwave is not

  • Not a consumer wallet or remittance app.
  • Not a crypto exchange or broker.
  • Not a speculative trading product.
  • Not a custodian of your private keys — Thiqwave never holds your signing material.

Where to go next