Paying by proxy
A proxy is a mobile number, an email address, or a customer identifier that a person registers with their own bank. It stands in for their bank account number.
You can pay a customer using only their proxy. You never learn their account number, and they never have to give it to you.
Capture a proxy beneficiary
The customer must already exist as a counterparty. A proxy tells you a name, not a party — so you attach it to someone you already know.
- Open the counterparty’s Beneficiaries panel.
- Select Add Beneficiary — see adding a beneficiary.
- Choose the mobile, email, or customer-identifier type.
- Enter the proxy.
- Select Check name.
- Read the name back to the customer.
- Select Save.
The beneficiary is saved with no account number, because none was ever known.
Why you confirm the name
Mobile numbers get reassigned. An instant payment to a reassigned number cannot be recalled.
The scheme’s answer is a fact with a time, not a stored truth. So the name is checked twice: once when you capture the proxy, and again when the payment is sent.
| When the two names differ | What happens |
|---|---|
| At capture | The save is refused, and you see the name the scheme holds |
| At send | The payment is stopped, and you see both names |
If a payment stops this way, confirm with the customer who should be paid, then capture the proxy again.
When a payment is stopped
An instant rail caps how much it will carry. A proxy beneficiary has no account number behind the proxy, so a payment over the cap has nothing to fall back to.
The payment is still recorded. It appears in the account’s direct credits marked Stopped, with the reason under it. For example, a payment of R60,000.00 to a proxy on a rail capped at R50,000.00 reads:
No rail carries R60,000.00 to this account. The highest cap is R50,000.00.
If you select Approve on a stopped payment, the approval is refused with the same reason. Nothing is sent.
Change the payment’s bank account
If the reason is the rail, pay the same customer through a bank account a rail carries:
- Ask the customer for their bank details.
- On the stopped payment, select Change bank account.
- If their bank account is not listed, select Add bank details and capture it.
- Choose the bank account.
- Select Change bank account.
- Select Approve on the payment, which now shows Requested.
In the example, the ordinary bank transfer rail carries R60,000.00 with no cap. The change clears the reason, and the payment is approved as usual.
You can only choose a bank account that belongs to the same customer. If the customer’s account has no owner on record, the change is refused. Reject the payment and raise it again.
When the change would cost a different fee
The rail fee is fixed when the payment is raised. If the new bank account goes out on a rail with a different fee, the change is refused and names both fees. Reject the payment, then raise it again against the new bank account.
When the payer could not cover the rail fee
If the payer’s balance was short of the rail fee, the row says by how much. Funding the account does not release this payment, because no money was ever set aside for it. Approve and Change bank account are not offered.
- Fund the payer’s account.
- Select Reject on the stopped payment, and give a reason.
- Raise the payment again.
Rejecting a stopped payment
Rejecting closes a payment nobody can send. Where raising it had already taken the money from the balance, rejecting puts it back. That happens when the payment came from a maturity, a payout, or another end-of-day step rather than from you.
Nothing is lost and nothing stops. End of day carries on, and approving all of an operating entity’s payments leaves a stopped payment stopped. It waits for you the next morning in the screen you already open.
When a file fails to deliver
A payment can be approved and sent, and the file carrying it can still fail to reach the bank. The payment then shows Delivery failed, with the gateway’s reason. Retry the file from the operating entity’s submissions page.
Two ways a proxy appears
The same word covers two different facts, depending on which direction the money moves.
| Direction | What the proxy is |
|---|---|
| You pay someone | Their proxy is how you address them, and it is all you hold |
| Someone pays you | Your bank account is registered under one or more proxies |
Your organisation’s own bank accounts stay single records. You add proxies to them from the account’s own screen, alongside the account number.
Proxy types
| Type | What you enter |
|---|---|
| Mobile number | An international number, for example +27 82 123 4567 |
| Email address | The address registered with the scheme |
| Customer identifier | The identifier the scheme issued |
Mobile numbers are stored in international format, so the same number entered two
ways is recognised as one proxy. This follows the ISO 20022 proxy account type code
set — see the standards register row for
ISO 20022 — ExternalProxyAccountType1Code.
What your organisation configures
- Which addressing standards are allowed. Proxy capture only appears when your organisation permits it. An administrator sets this in settings.
- Which rails carry proxy payments, and their limits. A proxy payment goes out on an instant rail, and instant rails usually cap the amount.
- Whether the Proxy Payments feature is licensed at all.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.