A Revolut customer says a technical problem prevented them from closing a profitable WTI crude oil CFD position on September 22, leaving the trade exposed for roughly 90 minutes before it could finally be exited at an alleged loss of approximately $5,300.
The allegation was published on Reddit on September 24 by a user who said Revolut subsequently acknowledged that there had been a technical problem on its side and was investigating the financial impact to determine whether compensation was appropriate.
Those claims have not been independently verified. Revolut has not publicly commented on the specific dispute, and no execution logs, order IDs or sufficiently clear screenshots establishing the sequence of events are publicly available.
More importantly, a search for other reports from the same September 22 period did not identify a fresh cluster of Revolut customers describing the same inability to close CFD positions. The available evidence therefore supports treating this as an individual execution dispute rather than evidence of a platform-wide CFD outage.
Trader Says Profitable WTI Position Became Uncloseable
According to the Reddit post, the customer had an open WTI CFD position that was showing a profit when they attempted to close it.
The user claims the close did not execute because of a technical problem. Around an hour and a half later, they said normal functionality returned, but crude oil had moved sufficiently against the position that closing it resulted in a loss of roughly $5,300.
The trader says screenshots show the attempted closure, the error encountered, the position when it was eventually exited and conversations with Revolut support.
According to the customer, Revolut told them that the issue originated on its side, that the case had been escalated as a high priority and that the financial impact was being assessed to determine possible compensation. The trader said they were initially told to expect an answer within one business day but had not received a substantive resolution when the Reddit post was published.
Without the underlying correspondence, however, it is not possible to establish exactly what Revolut acknowledged. A support agent confirming that a technical problem occurred would not necessarily establish that the entire $5,300 subsequent loss was caused by that failure or that Revolut had accepted liability for it.
The distinction resembles other recent broker execution disputes, where a trader’s description of the financial outcome provides the starting point but order timestamps and actual execution data are necessary to determine what happened.
September 22 Did See Other Revolut Service Problems
There is some independent evidence that Revolut experienced technical disruption on September 22, but it does not establish that CFD trading was affected.
Third-party services that archive Revolut’s official status information recorded several incidents that day, including problems involving transfers and identity verification. One recorded transfer incident lasted more than five hours.
No corresponding public incident has been identified specifically naming CFD trading or the inability to close leveraged positions.
That means the broader outages cannot currently be used as corroboration of the Reddit user’s execution claim. They establish only that other Revolut services experienced disruption on the same date.
The distinction matters. DaveFinances previously found a similar need for caution when XTB users reported platform and chart problems without evidence establishing a system-wide trading outage.
In other cases, multiple independent complaints can materially strengthen the evidence. A single customer report and a cluster of customers describing the same failure during the same time window are very different stories. That is why earlier reviews of broker complaint patterns have distinguished isolated reports from genuinely recurring problems.
Revolut’s Own Execution Policy Makes the Logs Critical
Revolut’s current European CFD execution documentation provides a useful framework for testing the allegation.
The company says that when it acts as principal for CFDs it is the execution venue and direct counterparty to customer transactions. Its policy says CFD orders should be handled fairly and promptly, with accurate timestamps covering order receipt and execution.
Revolut also says it monitors execution latency and applies price-tolerance, requote and slippage controls symmetrically.
Its CFD terms nevertheless make clear that submitting an order does not guarantee execution. Markets can move rapidly, liquidity can change and an order may ultimately execute at a different price. Revolut also maintains records of orders that are executed or rejected.
Those records are particularly important here because the allegation is not simply that the customer received an unfavorable price.
The user claims they tried to close the position and could not.
If Revolut’s logs show a valid close instruction reaching the trading system while the position was profitable, followed by a technical rejection or prolonged failure to process the request, that would provide significantly stronger evidence for the customer’s case.
If no close order reached the execution system, the dispute becomes more complicated because the investigation would then need to establish whether an application failure prevented the instruction from being transmitted in the first place.
Similar questions arise whenever traders lose access to functionality while positions or funds remain exposed. The financial consequence can continue changing while the technical problem is being resolved.
A 90-Minute Failure Matters Much More in Leveraged Markets
The size of the alleged loss may sound surprising given the relatively short period involved, but 90 minutes can be an extremely long time in a leveraged CFD position.
WTI was already moving sharply around September 22. Crude futures extended a multi-session decline that day, with CME commentary describing a fifth consecutive losing session and a drop of more than 14% across the stretch.
CFDs magnify the consequences because the customer does not need to fund the full notional value of the underlying exposure. A relatively modest movement in crude can therefore produce a much larger percentage change in the capital committed to the trade.
That is why platform availability is not simply a user-experience issue for active traders.
If someone cannot open a settings page for 90 minutes, it is inconvenient. If someone cannot close a leveraged oil position for 90 minutes while the market is moving rapidly, the financial exposure continues changing every second.
Brokerages increasingly understand that distinction. eToro’s upcoming phased migration to a rebuilt trading application, for example, highlights how even planned technology changes need to minimize disruption to customers with live positions.
The $5,300 Figure Is Not Automatically the Compensation Figure
This is where the dispute becomes more complicated than calculating the difference between the profitable position and the eventual loss.
If a technical fault is established, the next question is what would probably have happened without it.
The requested close price matters. So does the exact timestamp, available bid or ask, position size, prevailing spread and whether Revolut actually received the instruction.
A trader saying, “I wanted to close here,” is different from a timestamped order reaching the execution system at that moment.
This evidence-first distinction also appears in disputes where brokers allegedly remove trading profits. DaveFinances’ coverage of an Ultima Markets customer dispute similarly centered on identifying the actual trades and contractual basis behind the financial adjustment rather than treating the customer’s final balance as sufficient evidence by itself.
For the Revolut customer, the strongest possible case would therefore combine screenshots with server-side records showing the attempted close and contemporaneous WTI pricing.
This Becomes a Bigger Story Only if More Traders Surface
Right now, this is an unusually detailed complaint, but it is still one complaint.
That limitation matters.
The trader says Revolut has acknowledged a technical issue. There were independently recorded Revolut service incidents on September 22. WTI was moving sharply enough that a leveraged position could change significantly during a 90-minute window.
But none of those facts proves there was a wider CFD execution outage.
The missing evidence is another trader.
If additional Revolut CFD customers independently report that they could not close positions during the same period, particularly if their screenshots show matching timestamps or error messages, the story changes substantially. At that point, the question would no longer be whether one customer’s order failed. It would be whether a common execution problem affected a group of leveraged traders.
There is precedent for user reports becoming more meaningful once functionality problems begin appearing across multiple accounts. Recent coverage of tastytrade customers receiving different levels of platform functionality showed how repeated independent reports can reveal an operational issue that is not obvious from a public status page alone.
For now, Revolut’s execution logs are more valuable than another support message.
They should show whether the attempted close reached the platform, when it arrived, whether it was rejected, what reason was recorded and what prices were available at the relevant moments.
If those records support the customer’s account, the $5,300 dispute becomes a concrete test of how Revolut compensates traders when a platform failure allegedly prevents them from controlling live market risk.
If the records do not, the case may remain an individual disagreement over what happened inside the application.
Either way, the evidence needed to resolve it should exist down to the timestamp.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape.