Last updated

About Electrum VAS

Value-added services (VAS) — also referred to as digital goods and services (DGS) — encompass a wide range of consumer products that are offered by service providers and sold through digital and in-store channels.

Electrum provides the technology for high-volume channels — such as a bank's mobile app or a retail chain's point-of-sale (POS) — to easily connect to a multitude of service providers and VAS aggregators. Electrum does not have any commercial with the service providers, so it is entirely up to our clients to build their VAS portfolio based on their preferred providers and business needs.

Digital or POS channels communicate with Electrum over a RESTful API and Electrum performs the following functionality:

  • Real-time transaction processing, including:
    • Routing transactions to the appropriate service provider
    • Load balancing and automatic failover accross multiple service providers
    • Orchestrating multi-leg transactions
    • Risk mitigation checks
  • End-of-day processing, including:
    • Automated file matching and reconciliation
    • Reporting and extracts
  • Operational tools, including:
    • Full transaction trace lookup
    • Alerts and monitoring
    • Service configuration

The main categories of VAS that we cater for are:

  • Account payments (also called bill payments)
  • Digital vouchers
  • Airtime and data (direct top-up and PIN-on-receipt)
  • Lotto
  • Money transfer
  • Prepaid utilities

Integrate with Electrum VAS services

If you are an existing client of Electrum, or a service provider looking to integrate a service via Electrum, you may access additional documentation describing the various services and how to integrate to them. Contact Electrum about how to gain access to these resources.

VAS Documentation

Product overviews and implementation guides for Value-added Services (login required)

API Reference

Navigate the left-hand menu to view and download the OpenAPI specifications used by our VAS services.

Note

The exact transaction flows and messaging requirements for each VAS service are described in the implementation guides (login required).