Bank or exchange house
Move money between licensed institutions and deliver each payment where the customer already banks, from your sending market or ours.
Value, measured your way: settlement time, pre-funding avoided, Travel Rule completeness, amount landed versus amount sent.
Fund the corridor without a nostro, where the approved settlement model and partner liquidity allow.
KPI: settlement time.
Reduce corridor pre-funding where the approved settlement model and partner liquidity allow.
KPI: pre-funding avoided.
The account or wallet they hold, or a basic phone where they hold neither.
KPI: amount landed versus amount sent.
camt.053, camt.054, MT940, BAI2, CSV.
KPI: Travel Rule completeness.
The same sending institution, one more leg at the receiving end.
Integration is by API or by batch file, whichever your operations already run. Nothing changes in your core: you send as you send today, and Saleem carries the leg beyond the account.
The three states below come from Saleem's partner mapping, which is research and not partnerships or commitments. Whichever describes you, the addition is the same: reach past the account.
Add stablecoin settlement and feature-phone reach.
Add wallet, payments and last-mile reach.
Use Saleem as the mobile payment layer.
The structure, not the numbers.
You pay for the platform, you keep the customer, Saleem is the rail.
The five questions a diligence team asks, answered.
API or batch file, whichever suits your operations. No core banking change is required, and the connection is scoped with your team before anything is built.
Licensed partners perform regulated money movement, custody, conversion and payout as required in each jurisdiction. Saleem provides instruction validation, screening orchestration, routing, records and reconciliation under the agreed operating model.
Recipient balances are to be held by a licensed custodian and accessed through Saleem's interfaces; keys do not sit on the handset. This is the target operating model at launch.
Value settles on the network and the regulated token you permit: dirham payment tokens under the CBUAE regime and dollar tokens recognised by the ADGM FSRA. The recipient never handles a token, and neither does your customer.
You keep your customer and your regulated relationship. Saleem does not stand between you and the person who banks with you.
Each regulated activity is performed by the appropriately licensed entity in the relevant jurisdiction; the final responsibility map is agreed per corridor.
Every payment returns to you per recipient, in the formats your operations team already reads: camt.053 and camt.054, MT940, BAI2 and CSV.
Six client surfaces are built and demonstrable against mocked services. The production backend, licensed-partner connections and independent security testing remain pre-launch work.
Six client surfaces are built and demonstrable against mocked services. The production backend, licensed-partner connections and independent security testing remain pre-launch work.
Tell us which corridor you serve today and where your reach stops, and we will scope the partner role and the integration around it.