
Collect and Settle Payments for International Merchants
How a PSP uses FiveWest to collect, hold, convert, and settle across borders
Challenge
The situation
A payment service provider settles funds on behalf of international merchant clients, collecting payments from local customers, then paying merchants out in the currency and jurisdiction they operate in.
The typical flow might look like this: a local customer pays into the PSP's collection account. The PSP holds those funds until the next settlement cycle. Funds are sent to a bank or Forex broker to convert into the merchant's settlement currency. The merchant is paid out, and when a customer needs a refund, that has to be processed too.
In practice, that means a different provider for each step: one to collect, another to convert, and sometimes another to pay out. Each relationship comes with its own onboarding, reconciliation, and support queue when something goes wrong. Every additional provider is another point where a payment can be held up. Funds sitting in transit or awaiting the next settlement cycle earn nothing. And when payout delays happen, it's the merchant relationship that takes the damage.
FiveWest
The solution
FiveWest replaces the fragmented chain with one licensed infrastructure stack:

ZAR Collections
the PSP collects customer payments in ZAR via Open Banking, or EFT under FiveWest's Third-Party Payment Provider licence. No dependency on a local banking relationship the PSP would usually have to source and maintain itself.

FiveWest Earn
collected funds don't have to sit idle between collection and settlement. They can be held in an Earn account and generate yield while awaiting the next payment cycle, turning float into working capital instead of dead time.

OTC Desk
when it's time to settle, funds convert into the merchant's currency of choice at an all-in institutional rate, with no need to route through multiple banking hops to get there.
The PSP decides, at the point of settlement, whether to convert immediately or hold and earn, FiveWest supports either without adding a step. One relationship and a flow that moves at the speed the merchant expects.

