Platforms · Software · Providers · Markets
The Malta Financial Services Authority (MFSA) has barred Trive shareholder Kasim Garipoglu from future roles requiring regulatory approval for 10 years and ordered him to sell his stake within six months. It has also directed Trive Financial Services Europe Limited to block activity entering or leaving client accounts, citing weaknesses in protecting client assets and reconciling records.
Shareholder approval status changes
The MFSA found Garipoglu no longer fit and proper for positions that require its approval. The restriction covers qualifying interests in Trive held through intermediaries as well as in his own name; he must dispose of them promptly, and no later than six months after the decision.
The Maltese action followed a Financial Conduct Authority (FCA) ban on Garipoglu working in UK financial services. The FCA said he had deliberately given it and other regulators misleading or false information, and found that he lacked honesty and integrity.
Client money controls remain central
The MFSA's measures against Trive started in September, when it stopped the firm taking on new clients until weaknesses in asset protection and account matching were addressed. It also required the board to approve transactions involving specified client accounts or client money and assets, with supervision in place.
The regulator sought records to verify that client funds held by liquidity providers were in the relevant accounts, and told Trive to give priority to moving money away from counterparties that did not satisfy regulatory requirements. On 24 September, it imposed an immediate block on transactions into and out of client accounts.
That restriction continues until funds are transferred to eligible counterparties or the MFSA rules otherwise. Finance Magnates reported that the notice does not give the sum affected or say any funds are missing. The decisions may be appealed before the Financial Services Tribunal within the period set by law.
Where this lands in the stack
For operations teams, the immediate question is how the restriction is enforced across account processing: which account types and payment routes are in scope, and what checks stop a blocked instruction from passing through a connected ledger or channel? The MFSA's order covers client-account activity in both directions, so the scope needs to be reflected in transaction controls and reconciliation workflows.
The remediation also depends on evidence from counterparties. What records will demonstrate that balances are held in the required accounts, who will verify transfers, and how will reconciliation resume? The notice gives no figure for affected client money, so the scale of the reconciliation work cannot be established from the order.
