The announcement
Thunes announced on 1 October 2026 that Absa Group selected it as a strategic multicurrency clearing partner. The collaboration builds on Absa Global Pay in South Africa and supports a broader cross-border payments strategy across Africa and international markets. The release emphasizes foreign exchange, liquidity and multiple payment rails. It does not provide a complete customer-level list of live corridors, delivery times or prices, which buyers should confirm for their own requirements.
NXBits analysis: a corridor is more than a destination
A payment provider's reach is often described by the number of markets it can connect. An operator needs a more detailed view. A supported corridor combines a sending entity, currency, beneficiary type, destination, payment route and set of conditions. Availability in one combination does not automatically establish availability in every other combination involving the same country. This is particularly important when a product serves both businesses and individuals.
Our interpretation is that multicurrency clearing can be useful when it makes these combinations easier to operate and explain. The customer wants to know the amount delivered, the cost and the likely arrival time. Behind that answer sit choices about funding, conversion, routing and local delivery. A broad partnership becomes operationally valuable when the provider can make a dependable promise for a specific payment.
Make the foreign-exchange quote understandable
A business sending money abroad should be able to identify the sending amount, conversion rate, explicit charges and expected recipient amount. It should know when the quote expires and which conditions could change the final outcome. This is a product requirement as well as a financial one. A technically efficient route can still disappoint a customer if the amount received differs from what the interface appeared to promise.
The treasury team should also understand how the provider manages a delay between quoting and execution. Different arrangements can create different exposures or restrictions. Buyers need the applicable terms rather than an assumption based on a headline exchange rate. When comparing providers, they should use the same transaction type and timing, including any charges or operational steps needed to make the funds usable at the destination.
Liquidity planning should follow actual demand
Cross-border activity is rarely uniform throughout a day or across a month. A business may have concentrated supplier payments, payroll cycles or seasonal flows. Funding arrangements should reflect those patterns. An operator can map when it needs money in each destination and compare that requirement with its replenishment options. Better planning can be as valuable as adding another payment connection.
A provider evaluation should include what happens when demand exceeds a prefunded amount or a usual funding route becomes unavailable. Teams should establish whether limits are visible, how additional capacity is requested and what the customer sees while the request is handled. A fallback route should be assessed for cost and availability under the same difficult conditions, rather than assumed to be interchangeable with the primary route.
Local delivery needs local evidence
A payment marked sent in one system may still be awaiting a destination-side action. The customer needs a status that reflects that stage. Operators should ask what confirmation they receive from the local route, how beneficiary information is checked and how returned or rejected payments are reported. These details determine whether a support team can explain an outcome with confidence.
Testing should use the actual beneficiary types the business intends to serve. A bank account payout and a mobile-wallet payout may require different identifiers and customer guidance. Teams should validate data collection, amount limits and recovery procedures for each selected route. A successful test in one market should not become a blanket assumption about every other destination shown on a coverage map.
Connect the payment to the business record
For a company paying overseas suppliers, a clear remittance record can matter almost as much as the transfer itself. The supplier needs to know which invoice has been paid, and the sender needs a record it can reconcile. Operators should preserve useful references across the route and explain any restrictions on the information delivered with a payment. Missing context can create manual work at both ends.
This also affects exception resolution. A returned amount should remain linked to the initiating instruction and the relevant customer obligation. Fees and conversion differences need an explanation in the records. A good operating service helps finance teams close that loop without reconstructing the payment from emails. That capability should be included in procurement questions and tested before substantial payment volume is committed.
What buyers should ask next
The next practical step is to request a current matrix for the specific corridors a business needs, including currencies, beneficiary types, limits, cutoffs, funding conditions and reporting. Buyers should discuss support coverage and escalation ownership where several organizations participate in the route. The agreement should make clear which delivery statements are commitments and which are estimates subject to local conditions.
We would judge the collaboration through the quality of those route-level outcomes. Wider connectivity is meaningful when it produces more predictable payments, clearer charges and a manageable process for exceptions. The October announcement provides a direction for Absa's cross-border strategy. Operators can use it as a prompt to examine how effectively their own provider connects liquidity, foreign exchange and local delivery into a service customers can trust.
Sources and further coverage
Follow our b2b payments coverage and read the editorial policy. Corrections and correspondence: info@nxbits.com.
Cover: AI-generated conceptual illustration for NXBits Payments News; not a photograph of an actual event.