Customer Alleges Payment Gateway Changed Bank Account Number
An Exness customer is alleging that a withdrawal intended for their own bank account was instead paid to another person after a payment gateway altered an incorrectly entered account number rather than rejecting the transaction.
The complaint, posted on Trustpilot on Sept. 3, identifies LuxPay as the payment gateway involved and includes Exness payment case number PMT0001896553.
The allegations have not been independently verified, and neither Exness nor LuxPay has publicly confirmed the circumstances described by the customer.
According to the reviewer, the problem began when they incorrectly entered an 11-digit local bank account number while requesting a withdrawal from Exness.
A normal validation failure might have resulted in the transfer being rejected and the funds returning to the trading account.
Instead, the customer alleges that LuxPay shortened or otherwise modified the account number to 10 digits without permission and subsequently processed the withdrawal.
The most serious part of the complaint is what allegedly happened next.
The reviewer claims the resulting transfer was credited to an entirely different person, rather than an account belonging to the Exness customer. The customer identified the recipient only as “ISTIQOMAH” and said they possess a LuxPay payment receipt showing the third-party beneficiary.
That document has not been independently examined, so it cannot currently establish whether the recipient information, payment routing or sequence described in the complaint is accurate.
The customer also said Exness support had responded by stating that the funds had already been sent, while the user was seeking an investigation into how the beneficiary details were processed.
Exness had not posted a public response to the review when the complaint was checked.
The allegation is particularly notable because Exness’s published payment policies take a strict position on third-party transactions.
The broker says accounts used for withdrawals must be registered under the same full legal name as the customer’s Exness account. Its general withdrawal rules state that a withdrawal will fail if the payment account belongs to someone else.
Exness’s client agreement goes further, stating that withdrawals will only be made to the client and that the company does not permit withdrawals to third parties or anonymous accounts.
Customers are also instructed to double-check information such as account numbers before submitting a transaction.
Those rules make the distinction between two potential errors important.
The first would be the customer’s admitted mistake in entering the wrong account number. In most payment systems, customers carry some responsibility for providing accurate beneficiary information.
The second question is whether the payment provider modified that information after submission and whether any mechanism checked that the resulting bank account belonged to the Exness customer.
If the account number was altered by the gateway and a payment was then sent to a beneficiary whose name did not match the Exness account holder, the case would raise a substantially different issue from an ordinary mistyped withdrawal.
It could point to weaknesses in field validation, beneficiary verification or the way information is passed between the broker, payment intermediary and receiving bank.
Exness says some of its withdrawals are processed automatically rather than being handled manually. Automation allows brokers to provide rapid withdrawals at large scale, but it also makes validation rules particularly important because incorrect information may move through a payment chain without a human checking it.
The company’s Personal Area records payment transactions and provides customers with transaction status information and invoice details. Payment-related cases can also be escalated through its support system.
Exness operates internationally through several regulated entities and offers regional payment methods depending on a customer’s country and account status. Individual payment routes can therefore involve outside banks, processors or local payment providers rather than Exness directly moving money through a single banking channel.
That makes assigning responsibility difficult without the transaction records.
It is not yet clear whether LuxPay received the 11-digit number exactly as entered, whether any formatting rule changed it, what beneficiary information accompanied the payment or which institution ultimately credited the receiving account.
There is also no independent evidence that the alleged recipient had any connection to the customer, Exness or the payment provider.
For now, the case remains a single unverified client complaint.
But the existence of a specific payment case number and the customer’s claim to possess a receipt identifying another beneficiary make it more concrete than a generic allegation that a withdrawal simply disappeared.
If the underlying documents support the account, the central question will not be why a mistyped withdrawal failed.
It will be why it allegedly succeeded.
A Wrong Number Should Not Quietly Become a Valid Payment
The customer openly admits making the first mistake.
That matters.
If someone enters an incorrect bank account number, a broker cannot reasonably be expected to know what number they actually intended to type.
But a good payment system should be designed around the assumption that customers will occasionally make mistakes.
There is a major difference between accepting exactly what a customer entered and automatically changing that information until it becomes a valid destination.
If the allegation is accurate, an 11-digit number that apparently could not be processed was transformed into a 10-digit number that could. That sounds like a small technical adjustment, but financially it could be the difference between a rejected transfer and money arriving in a stranger’s account.
The crucial question is therefore where validation occurred.
Was the field limited to 10 digits but allowed the customer to type 11? Did the payment gateway strip a digit according to a formatting rule? Did Exness transmit one number while the processor interpreted another? Or is the customer’s understanding of the receipt incorrect?
Those questions can only be answered from the transaction logs.
The beneficiary name is potentially even more important.
Exness tells customers that payment accounts must carry the same legal name as their trading account and explicitly prohibits third-party withdrawals.
If a transfer carrying a clearly different beneficiary name was nevertheless allowed through the payment chain, that would expose a gap between the broker’s customer-facing rule and the controls actually enforcing it.
However, name matching is not universal across banking systems.
Some payment rails route transfers primarily using account numbers and bank identifiers. A beneficiary name entered alongside them may be informational rather than a hard validation field. If the account number points to a valid account, the receiving bank may credit it even when the typed name differs.
That would not necessarily mean anyone deliberately bypassed an AML control.
It would mean Exness and its payment providers need safeguards before the payment reaches a banking system where recovery becomes difficult.
This is where the story becomes more interesting than a routine withdrawal dispute.
The relevant control is not simply anti-money laundering. It is payment integrity.
A broker promising that withdrawals can only go to the account holder needs enough validation to make that promise operationally meaningful.
That could involve verifying previously approved bank accounts, preventing unexplained modification of customer-entered details, comparing beneficiary names where the payment rail supports it and forcing manual review when fields do not validate cleanly.
The case is still missing the evidence needed to say those controls failed.
The customer’s receipt would be the key document. It should show the beneficiary, destination account information, amount, payment reference and processor details. Exness’s transaction record could then be compared with it to determine whether the account number changed between the withdrawal request and the final payment.
If both documents show that transformation, this stops being a story about someone typing a bank number incorrectly.
It becomes a story about how a financial system handled the error after it was made.