Back office & approvals
Approved by the right people. Booked exactly once.
Deposits, withdrawals, credit, bonuses and corrections are requests. Approving takes a fresh authenticator code, the two-person rule lives in the database, and the bridge writes every operation down before it sends it to MT5.
Back office & approvals: the rules
Who can approve, and when.
- 01
Every kind of money movement
Deposit, withdrawal, and credit, bonus or correction, in or out. Approving takes a fresh authenticator code, good for 5 minutes on that sign-in only.
- 02
Maker-checker in the database
You can approve your own request only while it, plus your own requests and approvals for that client over 24 hours, stays within the brand's threshold: 1,000 USD unless you set another.
- 03
Two people for large portal money
A portal deposit or withdrawal above the threshold needs two different people. The first approval sends nothing: the request shows "1 of 2 approvals".
- 04
Other currencies take two
A request in any currency other than the brand's own always needs a second person.
- 05
A 14-day block
Whoever changed a client's email, or sent them a sign-in link, can't approve that client's portal money for 14 days.
- 06
Nothing rewritten
No role can delete or rewrite a ledger entry, a request or an account. A correction is a new request, approved like any other.
Second approval
What "approved" means here.
A 48,500 USD withdrawal from the portal, above a 1,000 USD threshold. Watch who can approve it, who can't, and when it finally moves.
Requests: waiting for approval
ExampleA 48,500 USD withdrawal from the portal, above the brand's 1,000 USD threshold. Sofia Marchetti gives the first approval with a fresh code, and nothing is sent. Omar Haddad can't approve: he changed the client's email 3 days ago. Daniel Whitford gives the second approval, which sends it to MT5, where it is booked once.
Needs a person
When the bridge can't be sure, it stops and asks.
An approved operation carries its own reference to MT5, like Deposit #7F3K9QX2M4PA. If the answer is lost, the bridge looks for the reference before it sends again, 3 sends at most. What it still can't settle within 24 hours comes here, with what to look for in MT5. Every answer takes a code and a note, and no answer sends anything again.
- "Check again" looks at MT5 once more
- "It was booked as deal N" is checked on the server first
- "Close" ends it, with your reason on record
The ledger
Every booked operation, its deal ticket and approver.
What the queue approved and the bridge booked, line by line. It is the side reconciliation checks against MT5 each day, and no role can edit or delete a line of it.
- The MT5 deal ticket on every line
- Who approved it, and when
- Corrections as new requests, never edits
Back office & approvals: questions
Straight answers.
Can an administrator approve their own large withdrawal?
No. The two-person rule is in the database, so no role can step around it. Above the threshold, a portal withdrawal needs a second, different person.
What happens if MT5 doesn't answer a deposit?
The operation is already recorded with its reference. At least a minute later the bridge searches the account's deals for it, and sends again only once it is proven absent, 3 sends at most. Unsettled after 24 hours, it goes to Needs a person.
Can we set our own threshold?
Yes, per brand. The default is 1,000 USD.
Where to next
Approved, booked, then checked.
Every line in the ledger is matched to MT5 by deal ticket once the server day is over. A mismatch waits for a name.