Infrastructure · Pan-African rails

One API. Every African rail.
You keep custody.

Tranzra is a non-custodial payment switch and liquidity router for Africa. One harmonized API surfaces every collection and disbursement rail available through your own provider relationships — bring your credentials, we orchestrate the rest.

Intelligent routing scores available paths in real time. Automatic failover retries on the next viable route without you changing a line of code. A unified reconciliation view tells you exactly what settled, where, and when.

Money never touches Tranzra. No custodial account, no pooled float, no PCI scope creep. You route; you reconcile; you own the relationship.

BYOC · non-custodial · integer minor-unit amounts · idempotent by design

http
# 1 — get a quote for the best available route
POST /v1/quotes
Content-Type: application/json

{
  "capability": "collection.mobile",
  "country": "KE",
  "currency": "KES",
  "amount_minor": 1250000,
  "counterparty": { "type": "msisdn" }
}

# → 200 OK — Tranzra returns the scored route and fee estimate.


# 2 — initiate the collection on that route
POST /v1/collections
Content-Type: application/json
X-Idempotency-Key: idem_7f2a9c1e-3b4d-48a2-bc50-6f0b2e1c9f3c

{
  "capability": "collection.mobile",
  "country": "KE",
  "currency": "KES",
  "amount_minor": 1250000,
  "counterparty": {
    "type": "msisdn",
    "ref": "+254712345678"
  }
}
Routing engine

Smart routing across your provider network

Tranzra evaluates every provider credential set you have configured and selects the best available path per intent. When a path degrades or fails, it falls over automatically — no webhook, no config change, no downtime.

Rail Country State
Safaricom STK KE
Primary
Airtel Money UG
In-flight
MTN MoMo GH
Degraded
Flutterwave NG
Standby
Relworx MoMo TZ
Primary
Pesapal KE
Unavailable

Illustrative only. Actual routes reflect your configured provider credentials.

Scored routing

Each available path through your provider credentials is scored on current health, capability match, and historic reliability. The highest-scoring route is selected per intent.

Automatic failover

If the selected route fails at the provider level, Tranzra immediately retries on the next viable path — same idempotency key, transparent to your integration.

Idempotent by design

Every intent carries an idempotency key. Duplicate submissions within the window return the original outcome. Safe retries, no duplicate charges.

Custody model

Money never touches Tranzra

You bring your own provider credentials (BYOC); we orchestrate routing, idempotency, and reconciliation visibility. Your settlement, your provider contract, your float — always.

Non-custodial by design

Money never touches Tranzra. There is no pooled float, no custodial account, and no PCI Card Data Environment in scope. Funds move directly through your own provider relationships.

Bring your own credentials (BYOC)

You supply your provider API credentials; Tranzra stores them encrypted and uses them only to route your intents. Your contract, your settlement, your provider relationship — we orchestrate.

Append-only orchestration log

Instead of a custodial ledger, Tranzra keeps an append-only orchestration and audit log per intent. Every state transition — submitted, in-flight, settled, failed — is immutable and queryable.

Reconciliation visibility

Reconciliation is framed as a question: did the provider confirm what Tranzra routed? The answer, per intent, is always available — with the raw provider reference and timestamp — so your books close cleanly.

No PCI CDE, no double-entry ledger

Because Tranzra never holds or moves funds on its own behalf, it does not operate a card data environment and has no need for a custodial ledger. Compliance obligations stay with the provider and the tenant, exactly where they belong.

Pricing

Infrastructure pricing, not transaction clipping

Tranzra charges for API infrastructure — routing calls, not a percentage of money moved. Your provider fees stay between you and your provider.

What you pay for

Routing API calls Metered per intent routed through Tranzra.
Quote lookups Included in the base API call count.
Webhook delivery attempts Retries within the delivery window included.
Reconciliation queries Querying the audit log is included.

What you do not pay for

Per-transaction percentage Tranzra does not clip a fee on transaction value — it charges for infrastructure calls, not for money moved.
Float or custody fees No funds touch Tranzra, so there is nothing to charge float on.
Provider pass-through Provider costs (MDR, settlement fees) stay between you and your provider, unchanged.

Volume-based and enterprise plans available

Pricing is negotiated per tenant based on anticipated routing volume and rail mix. Contact us to discuss a plan that reflects your actual infrastructure needs.

Tranzra is currently in private access. Pricing is confirmed at onboarding. No credit card required to start a sandbox integration.