Connect to Banks Through One Consistent API
CharrgSwitch gives fintech wallets and payment platforms a consistent way to connect to supported banks. Use its APIs for supported account inquiries, transfers, wallet top-ups, and bank transaction routing, while bank-specific connections are handled behind the integration layer.
Simplify the bank-by-bank integration challenge
CharrgSwitch separates your client-facing integration from the implementation requirements of each supported bank. A common API receives the request, the routing layer identifies the appropriate bank connection, and a bank-specific adapter handles the institution's integration.
This structure supports transactions within a bank and between supported banks. It also allows additional bank connections to be added behind the common API, reducing the need to rebuild client integrations each time the supported network expands.
Core capabilities
Bank connectivity that can grow with your platform
How It Works
Connect your platform. Integrate with the CharrgSwitch client-facing API for the bank services agreed with LEOGC.
Submit the bank-service request. Your platform provides the required account, transaction, and authorization information for the requested operation.
Route through the bank adapter. CharrgSwitch selects the supported bank connection and applies that institution's integration requirements.
Return the bank-service result. Your platform receives the result for use in its customer or operational workflow.
Available functions depend on the connected bank, the enabled integration, and the required customer authorization. Confirm supported banks and transaction types with LEOGC before defining your launch scope.
Frequently Asked Questions
What is the difference between CharrgSwitch and PulseConnect?
CharrgSwitch connects directly to supported banks through bank-specific adapters. PulseConnect provides access through the Bank of Sierra Leone central switch. They are distinct LEOGC products.
Does every connected bank support every function?
No. Account inquiries, transfers, wallet services, and authorization requirements depend on the capabilities enabled for each bank.
Will every new bank require a separate client integration?
CharrgSwitch is designed to keep the common client API stable while bank-specific adapters handle individual integrations. Newly enabled services and requirements are confirmed with LEOGC.
Build the Bank Connections Your Platform Needs
Share your target banks and account-service or payment workflows. Our team will confirm the supported functions and integration approach.