Demo · Simulated data and fictional banks. Features are in development.

Tap uses a token.
Send uses a name.

Two products on one embed. Merchant tap is contactless. A send to a name is paid over Visa Direct or Mastercard Send, with PesaLink as the fallback. RELI never holds the money.

  1. 01

    Radio — NFC

    Near-field transport. Moves bytes between a phone and a terminal within 4 cm.

    Hardware vendors

  2. 02

    Contactless

    The protocol on top of NFC. Visa and Mastercard each have their own contactless profile. Nobody replaces this layer.

    Card networks

  3. 03

    Card emulation

    Secure Element or Host Card Emulation. To the terminal they behave identically.

    OEMs & processors

  4. 04

    Tokenisation

    Till payments use a network token instead of the card number, and the design keeps card numbers off the device.

    Visa VTS · Mastercard MDES

  5. 05

    Provisioning — Reli

    Android HCE first. Apple Pay and Google Wallet on the roadmap, subject to approvals.

    Through the issuer's scheme membership, subject to approval

await Reli.tap.enable({
  issuer: bank.bin,
  cardRef: existingDigitalCard.id,
  channels: ["hce"],
});

await Reli.handle.claim({ personId, handle: "wanjiku" });

await Reli.send.toHandle({ fromCard, handle: "amani", amountKes: 2000 });

Issuer SDK

Lives in their app

  • Native iOS / Android
  • Flutter / RN plugins
  • Headless REST

Provisioning API

Token requestor

  • Push provisioning
  • Lifecycle
  • Device bind

Reli orchestrator

What we provide

  • HCE
  • Alias directory
  • Visa Direct / Mastercard Send

Scheme tokenisation

Through the issuer's scheme membership, subject to approval

  • Visa VTS (planned, via the issuer)
  • Mastercard MDES (planned, via the issuer)

Bank / SACCO layer

Existing card programmes. RELI integrates. It does not replace them.

  • Vision Plus
  • Way4
  • T24 / Finacle
  • Mobile app backend
  • KYC

Visa, Visa Direct, Visa Token Service, Mastercard, Mastercard Send, MDES, Apple Pay, Google Wallet, M-Pesa, PesaLink, PesaLink ID, T24, Vision Plus and Way4 are trademarks of their respective owners. We name them only to describe our integration approach and compatibility, and this implies no partnership, certification or endorsement. Product screens and illustrations are indicative, and the features described are in development.