Unknown block type:
SchoolHeaderUnknown block type:
SchoolNavForex Back Office
Wallets, payments and the ledger behind every account
Why the back office
Where the money
actually moves
Everything that comes in or goes out lands in one ledger — and leaves a reference behind it.
-
A wallet per client
Money arrives in the client’s wallet first and is moved to a trading account from there, so a deposit is never stranded against the wrong account and a client with four accounts still has one balance to look at rather than four to add up.
-
Deposits that clear themselves
Card, bank, UPI, e-wallet and crypto payments post against the client the moment the provider confirms them. Nobody watches an inbox for a payment notice, and nobody types an amount into a second system to make the first one agree.
-
Withdrawals on rules, not favours
A withdrawal follows the approval rule set for its size and its client — documents checked, limits applied, second sign-off where the amount asks for it. The operator who released it is on the record, and so is the one who declined.
-
Transfers and adjustments
Internal transfers between a client’s own accounts, credits, bonuses and manual corrections all go through the same ledger as everything else. There is no side book, which is the only reason the numbers stay comparable.
-
Reconciliation with something to match on
Each movement carries the provider’s own reference alongside ours, so a statement from the gateway and a report from the back office line up on a shared key rather than on an amount and a hopeful guess at the date.
-
Fees where they belong
Gateway charges, spread markup, commission and partner rebates are worked out on the movement itself rather than bolted on at month end — so what a desk earned on a deposit is known on the day the deposit happened.
The rails it speaks
Every method, one ledger
Clients fund the way their country funds. The back office does not care which one they picked.
-
Cards
Visa and Mastercard through your own acquirer, with the authorisation, the capture and the refund all sitting on the same client record.
-
Bank transfer
Local and international wires, matched on the reference the client quotes rather than on a name that rarely arrives spelled the way you hold it.
-
Local rails
UPI and the domestic methods a region actually uses, because the cheapest deposit is the one the client already knows how to make.
-
Crypto
Stablecoin and coin deposits with the confirmation count you set, converted at the rate held on the movement so the ledger never drifts.
-
E-wallets
Skrill, Neteller and the rest, added as another gateway rather than another system, and reconciled on the same key as everything else.
-
Manual entry
The payment that arrived some other way still gets recorded properly — posted by an operator, against a rule, with the trail an audit will ask for.
The back office
Close the day without a spreadsheet
Balances, movements, fees and partner rebates come off the same ledger, so the report and the screen never disagree.
- A wallet per client
- Gateway references kept
- Approval limits per operator
- Fees worked out on the day
Questions about the ledger
Before you move the money
What a finance team usually wants settled before it runs client funds through a new back office.
-
Your own. The merchant accounts, the acquirer relationships and the rates you have negotiated stay yours — the back office connects to them and settles into your accounts, not through ours. Cards, bank transfer, UPI and the local methods your region uses, e-wallets and crypto can all run side by side, and adding another provider later is a configuration rather than a rebuild, so a new market does not have to wait on a release.
-
Through the client’s wallet. The payment posts to the wallet the moment the provider confirms it, and the client moves it to whichever trading account they want — or the desk does it for them. Keeping the wallet in the middle is what stops a deposit landing against the wrong account, lets a client with four accounts see one balance instead of four, and gives a withdrawal somewhere to sit while its approval runs.
-
Per operator, and per amount. A withdrawal follows the rule set for its size: documents checked, the limit on the operator applied, and a second sign-off required above whatever figure you decide needs one. Limits sit on the person rather than the department, so somebody covering a colleague on leave never quietly inherits a larger one. Every release and every rejection is written against the operator who made it.
-
Every movement keeps the provider’s own reference next to ours. That is the whole trick: a gateway statement and a back-office report then match on a shared key instead of on an amount and a guess at the date, which is where most of a finance team’s month end actually goes. Fees, spread markup, commission and partner rebates are calculated on the movement itself rather than assembled afterwards, so the day’s figure is final on the day.
-
Yes, and the rate is held on the movement. A client can hold wallets in more than one currency and fund an account in a different one, with the conversion recorded at the rate that applied when it happened rather than recalculated later from a rate that has since moved. Reporting rolls everything up into your base currency for the desk while each client still sees the number they actually paid.