sttl is a technology infrastructure company operating across African corridors.
We provide the technical and operational infrastructure that regulated sending partners use to run merchant payout programmes across African markets. Local provider relationships, routing, exception handling and reconciliation are managed within our infrastructure, on their behalf.
Reaching merchants across African markets means building relationships most sending partners should not need to build.
Every market has its own local providers, formats and timing. That knowledge takes time to accumulate and ongoing effort to maintain. We hold it so our partners don't have to.
Local provider relationships are costly to establish
Onboarding, integrating and maintaining relationships with local providers across multiple markets takes time, legal groundwork and operational effort that most sending partners cannot justify at scale.
Every market operates differently
Formats, cut-off windows and outcome reporting vary widely by market. Without accumulated local knowledge, failures are hard to anticipate and harder to resolve.
Reconciliation does not travel well
Matching instruction data against confirmed outcomes across multiple markets becomes a manual exercise that grows in complexity with every corridor added.
Partners submit an instruction. We manage everything that follows.
Local provider selection, routing, monitoring, exception handling and reconciliation are handled by us. Partners receive a normalised outcome regardless of what took place in the market to produce it.
Instruction submitted
The sending partner submits a payout instruction through a single, consistent operational interface. No local market knowledge is required on their side.
Sending partnerValidated, routed, monitored
We validate and normalise the instruction, select the appropriate local provider for that market, monitor progress and manage any exceptions that arise.
sttl · coordination layerLocal processing takes place
The appropriate local provider processes the instruction on its own rails, under its own permissions and controls. Partners are not party to this layer.
sttl · managed on your behalfNormalised outcome returned
A structured confirmation with full reconciliation data is returned to the sending partner in a consistent format, regardless of how many markets were involved.
Sending partnerThe operational layer, run on your behalf.
We maintain local provider relationships, integrations and operational knowledge across African markets. Sending partners access the coverage through us, without the relationship overhead.
Routing decisions are made on the sending partner's behalf, informed by real corridor and market behaviour, so more instructions reach a confirmed outcome on the first attempt.
A single, normalised status model is returned to the sending partner across every market: received, in progress, confirmed, exception. No need to interpret what different markets sent back.
Failures and delays are identified and worked through defined playbooks on our side. Partners receive an updated outcome status rather than a problem to investigate.
Structured reconciliation files are produced in a consistent format regardless of which markets or local providers were involved, with no manual assembly required.
We sit between sending partners and the local layer by design.
Sending partners should not need to build or maintain local provider relationships to run merchant payout programmes across Africa. That complexity is ours to manage. Local providers retain full control of their own processing; we ensure the connection works cleanly from the sending side.
What we are
- A software, operations and coordination layer
- A single operational interface for regulated sending partners across African markets
- The layer that manages local provider relationships on behalf of our partners
- Routing, monitoring, exception handling and reconciliation, handled end to end
What we are not
- We do not process payments or operate local rails
- We do not hold, move or control funds
- We do not replace or compete with local providers
- We do not present ourselves as a regulated financial entity
Operational knowledge across African markets.
We have accumulated working knowledge of how each market operates: local provider behaviour, timing, failure patterns and reconciliation standards. That knowledge is applied on our partners' behalf rather than passed to them to manage.
Market knowledge, held by us
Formatting requirements, timing windows, retry behaviour and outcome standards across each market, so sending partners do not need to learn them.
Route-quality intelligence
An evolving picture of how each market performs, used to direct instructions where they are most likely to reach a confirmed outcome.
Exception handling
Known failure patterns are recognised and resolved through defined playbooks on our side, before they require action from the sending partner.
Consistent reconciliation files
Structured reporting outputs in a single format regardless of how many markets were involved or which local providers processed the instructions.
Local provider management
We maintain operational relationships with local providers across African markets. Sending partners benefit from the coverage without the relationship overhead.
Governance and reporting
Transparent activity logs and reporting available to partners and, where required, to local providers for their own oversight purposes.