Where the money lands
Every payment settles to one merchant, and which one depends on who is being paid. ePay never pools them: a merchant sees only its own payments.
Whose merchant
| Who pays whom | Kuploy Cloud | Leeram Business |
|---|---|---|
| An organisation pays you for its plan | Your merchant | Your tenant revenue merchant |
| A customer pays an organisation | The organisation's own merchant, through the Payment Gateway service in its app | The organisation's own merchant, through Pay now on its invoice |
The second row is the organisation's money, not yours. It settles to that organisation and is intentionally absent from anything you see.
Funds settle into the mobile-money and card accounts registered with the providers on the gateway. Your deployment never holds funds — it starts the checkout and listens for the outcome.
On Kuploy Cloud, Admin → Finance is a read-only view of your own merchant's payments. See Payment Gateway → Finance.
How your deployment is told
When a payment reaches a final state, ePay sends the deployment a signed notification, and the deployment checks the signature before acting on it. A notification that isn't acknowledged is retried.
You don't wire anything for your own products — they receive and act on these themselves:
- Kuploy Cloud moves the organisation's plan to active when its payment succeeds. See Payment Gateway.
- Leeram Business activates, renews, marks past due or cancels an organisation's subscription as the events arrive, and records an invoice payment when a customer's Pay now succeeds.
An organisation's own app is different: its developers choose where notifications go and verify them themselves — see Payment Gateway Service → Reacting to webhook events.
The full notification reference — its body, signing and retries — is on ePay's merchant docs, which need an invite to read.