VeloraPay Technologies Business Plan — Technology, data & product architecture

Section 10 · 10 of 23

Technology, data & product architecture

VeloraPay’s platform is engineered as a cloud-native, API-first system designed for reliability in low-connectivity environments and for rapid multi-country deployment. Technology is the largest single line in the use of funds (R120 million) because the platform is the product.

Core infrastructure

  • Cloud-native architecture hosted on AWS, enabling elastic scale across markets without capital-intensive data-centre build-out.
  • API-first ecosystem so that payments, lending, POS and analytics interoperate and third parties can integrate.
  • PCI-DSS compliance as the security and certification baseline for card acceptance.
  • AI fraud detection monitoring the transaction flow in real time for anomalies and scheme-fraud patterns.

Platform capabilities

  • Offline transaction capability to keep merchants trading through connectivity gaps — essential in informal and rural markets.
  • Multi-wallet and multi-currency support for cross-border merchants and regional settlement.
  • Real-time reconciliation giving merchants and the Company an accurate, live financial position.
  • AI underwriting scoring merchants for credit on their own transaction history, continuously re-rated.

Data as the strategic asset

The proprietary asset VeloraPay accumulates is not the hardware but the longitudinal record of merchant transactions. This data underpins three defensible capabilities: credit underwriting that banks cannot replicate for the same merchants; fraud models that improve with volume; and merchant insights that raise engagement and retention. As hardware inevitably commoditises, this data layer is where durable competitive advantage resides — the same conclusion the market leader has reached in pivoting from devices to an AI-driven business platform.

Analyst flagTechnology delivery risk is front-loaded

R70 million of platform capitalisation is modelled in FY2027, driving heavy early amortisation and contributing to the fully-loaded net loss in the ramp years (Section 15). A delayed or over-budget core build would both defer revenue and worsen early cash burn. Investors should confirm the engineering plan, team and third-party dependencies before close.