Demo · Simulated data and fictional banks. Features are in development.
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.
01
Near-field transport. Moves bytes between a phone and a terminal within 4 cm.
Hardware vendors
02
The protocol on top of NFC. Visa and Mastercard each have their own contactless profile. Nobody replaces this layer.
Card networks
03
Secure Element or Host Card Emulation. To the terminal they behave identically.
OEMs & processors
04
Till payments use a network token instead of the card number, and the design keeps card numbers off the device.
Visa VTS · Mastercard MDES
05
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
Provisioning API
Token requestor
Reli orchestrator
What we provide
Scheme tokenisation
Through the issuer's scheme membership, subject to approval
Bank / SACCO layer
Existing card programmes. RELI integrates. It does not replace them.
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.