Cross-border payments and bills for businesses in 10 countries

Businesses trading across Sub-Saharan African markets struggled to convert currencies and pay overseas partners. Buying foreign exchange through a bank and then arranging a separate transfer delayed trade settlement.

The challenge was to connect those steps in one understandable journey while respecting the steps required by the underlying payment gateways.

If businesses can convert currency and send cross-border transfers from one Swiftpoint account, they can settle trade with fewer handoffs and less repeated sign-in.

An integrated journey should also make the relationship between the amount sent and the amount received easier to understand before the payment is authorised.

My contribution was turning payment-gateway requirements into a user journey, and designing account access that reduced interruptions during payment and transfer.

Currency conversion and cross-border payment become one connected Swiftpoint experience, with single sign-on carrying businesses through to settlement.

The transfer amount, conversion rate, fees and recipient amount appear together before authorisation, so businesses can judge the payment before committing.

A gateway-informed transfer design with single sign-on supporting continuity through the payment process, aimed at less effort when settling cross-border trade.

Impact is assessed through fewer handoffs, fewer repeated sign-ins and shorter completion time. Any “best rate” claim would need a defined comparison of quotes and total cost.

Cross-border transfer design means connecting the user's commercial goal with the steps of the payment infrastructure. The gateway review and single sign-on work addressed the continuity of that journey.

Next, I'd test whether businesses understand both the cost of conversion and the progress of settlement — especially when a transfer can't complete immediately.

People moved between apps to pay different bills, then went back to each service to find their payment records. The task was fragmented and it was hard to see what had been paid and how much had been spent.

Product research also found incomplete payment coverage, network delays and difficult first-time interactions. The design had to consolidate services without making the payment page harder to navigate.

If people can choose different bill types from one curated payment page and keep the records in Swiftpoint, they'll spend less time switching apps and hunting for payment information.

Organising those records into a spending view should also help people understand where their bill money goes over time.

My focus was the connection between bill selection, payment and tracking: organising the payment page and shaping how people move from paying a bill to reviewing their records. This built on three months of broader payment research.

Supported bill categories sit on one curated payment page, so people choose the service they need inside Swiftpoint, with one shared payment experience.

Payment records and spending analysis complete the experience, helping people revisit transactions and understand where their money has gone.

The shipped product includes a Pay bills entry point and transaction records within the shared payment platform; this direction extends it toward consolidated bill management and spending analysis.

The target is completing multiple bills five times faster with a useful spending log. Claiming it requires timed task evidence and a check that the spending view matches the payment records.

The feature connects two parts of bill management: making a payment and understanding it afterwards.

Next, I'd check that adding more services keeps navigation clear, and that people can explain their spending without piecing records together from different apps.