This document provides a comprehensive overview of the Blink service architecture, including infrastructure components, integration points, and detailed user flows.
We are building Blink - a non-custodial stablecoin payments platform on the Stellar blockchain that enables both single and bulk payments via magic links tied to recipient emails and a wallet. Funds are locked in Soroban smart-contract escrow vault that generate yield until fund gets claimed by recipient. This makes stablecoin payments not only faster, but more programmable and useful.
The service leverages existing Bingtellar banking, settlement rails, KYC, and compliance frameworks to ensure secure and compliant transactions. Bingtellar infrastructure enables customers to send money with/across Africa using USDC and settlement is handled via the Stellar Network.
The goal:
“Every cross-border or person-to-person transfer on Blink temporarily earns yield until it’s claimed or refunded, powered by Stellar non-custodial, on-chain vault interactions.”
More info here about Blink, our vision and why we started building Blink: Blink Whitepaper v1
At the core of Blink architecture is a Stellar Soroban smart-contract escrow vault, integrated with a backend relayer service, a yield management layer, and an email-based claim portal.
When a sender initiates a money transfer (USDC on Stellar), the specified principal amount is locked into an escrow vault, the platform then issues a claimable transfer ****tied to the recipient’s email address and a unique claim URL.
While awaiting claim, the escrowed amount is programmatically ****deployed into yield-bearing pools and strategies (Blend capital pools ) through on-chain integrations (Defindex). The escrow vault accrues variable yield from these pools until the verified recipient claims the funds or until the sender cancels the transfer or the claim window expires i.e the yield management layer continuously tracks accrued returns and updates the vault’s balance in real time until recipient activates claim/withdrawal, then the Soroban contract automatically triggers settlement logic: the vault value is unlocked and yield is distributed per defined (sender/recipient split).