Coinbase is facing a second fresh customer report in which a transaction-risk restriction allegedly pushed an established user into an identity-verification process that repeatedly rejected valid documents, raising questions about what happens when the exchange’s security controls and account-recovery system fail at the same time.
A user posting Sept. 14 said their Coinbase account had been fully verified for more than five years before they attempted to withdraw funds to a bank account. According to the customer, Coinbase classified the transaction as suspicious and locked the account.
The user was then instructed to complete identity verification to regain access.
That is where the reported problem changed.
The customer said they repeatedly submitted both a driver’s licence and an ID card, but Coinbase’s verification system rejected the documents with a message saying the photos were not clear. The user said the same problem occurred through both a web browser and Coinbase’s mobile app despite the documents being clearly visible.
The customer further alleged that support told them a manual review was unavailable and that the automated verification system had to accept the documents before the account could be unlocked.
Coinbase Support responded publicly on Sept. 14 and asked the customer to send a Modmail containing any existing case number so the issue could be examined further.
The allegation has not been independently verified, and Coinbase has not publicly confirmed why the bank withdrawal was considered suspicious or whether the customer’s documents met its verification requirements.
Second User Described a Similar Sequence Two Days Earlier
The Sept. 14 report closely resembles another complaint posted in Coinbase’s support thread on Sept. 12.
In that case, a customer said Coinbase locked their account after they attempted to send USDC to a wallet they had personally authorized using their passkey and two-factor authentication. The customer said they had successfully sent funds to the same wallet through Coinbase on previous occasions.
After the restriction, the user said they attempted Coinbase’s account-recovery and identity-verification process more than four times using both a valid driver’s licence and passport. The documents allegedly continued to fail.
The customer supplied case number 27501418 and asked for escalation to Coinbase’s Account Security or Account Recovery team for manual review.
Coinbase Support subsequently asked that customer to send a Modmail as well so the company could review the account status and verification attempts.
Two complaints are not evidence of a platform-wide verification malfunction. There is no current evidence showing that large numbers of Coinbase customers are encountering the same problem.
But the similarity between the cases creates a narrower issue worth watching: a security control may be functioning as designed when it stops a transaction, only for the customer to become stuck in the recovery mechanism required to reverse that restriction.
That type of problem differs from the prolonged compliance investigations recently reported by customers at other exchanges. A Bybit customer recently said a $21 withdrawal triggered restrictions on roughly $25,000 after an address previously accepted by the exchange was later classified as high-risk.
Coinbase Says Restrictions Can Require Additional Verification
Coinbase’s own support documentation confirms that account restrictions can be imposed because of potential security issues and that customers may be required to complete additional verification before restricted activity is restored.
The company says account-restriction reviews typically take up to 10 business days, although individual cases can take longer.
Coinbase also specifically acknowledges that identity-verification failures occur.
Its troubleshooting guidance tells customers to ensure their personal information matches their identification, use clear photographs without glare, try another browser or the mobile app and wait between repeated attempts.
More importantly for these complaints, Coinbase says some upload errors can trigger a cooldown before another document can be submitted and that Coinbase Support cannot bypass that cooldown.
Another Coinbase help page says customers who remain unable to verify their identity after several attempts should contact support to initiate a manual review.
That makes the precise support route in the Sept. 14 case important. If the customer was genuinely told that no manual review was possible, it would be useful to establish whether that limitation applies specifically to the verification flow they entered or whether another escalation channel exists.
Withdrawal Controls Are Creating Similar Friction Across Platforms
Coinbase is not alone in balancing transaction-risk controls against customer access.
A Binance Kazakhstan customer recently reported an extended withdrawal restriction despite supplying source-of-funds documentation, while customers at Polymarket have reported week-long withdrawals and account holds.
Those cases involve different platforms and potentially different causes, so they should not be treated as evidence of a common technical problem.
They do illustrate the same operational tension.
Crypto platforms need controls capable of stopping fraudulent or unauthorized withdrawals because blockchain transfers can be irreversible. At the same time, the recovery process has to work reliably for legitimate customers whose transactions are incorrectly flagged.
The problem becomes more severe when verification itself is the only route out of the restriction.
The Second Failure Is More Important Than the First
The initial Coinbase lock is not necessarily the interesting part of these cases.
Financial platforms flag transactions all the time.
Sometimes they should.
If an account suddenly sends funds in a way that differs from its historical behavior, temporarily stopping the transaction can prevent an irreversible loss. A customer would probably prefer an inconvenient security check to discovering that stolen crypto has already left the platform.
The more consequential failure occurs if the recovery system cannot distinguish the legitimate customer from the threat it was built to stop.
That creates a strange loop.
The risk engine says: prove you are the account owner.
The customer provides the requested identification.
The verification engine says the identification cannot be accepted.
Support then cannot remove the restriction because verification remains incomplete.
If there is no effective human escalation route, each individual control can technically be working while the overall system becomes impossible for the customer to exit.
That is a second-order account-recovery problem.
Automation Makes False Positives Cheap Until Someone Has to Resolve Them
Automating fraud detection makes sense for a business operating at Coinbase’s scale.
Coinbase reported 7.6 million monthly transacting users and $245.9 billion in assets on its platform at the end of the second quarter of 2026.
No human compliance team could manually review every withdrawal before it happens.
Automation is therefore unavoidable.
But fraud systems have asymmetric economics.
Blocking one suspicious transaction automatically is cheap. Investigating whether that block was wrong can be expensive.
That creates a temptation across financial platforms to automate the first decision more aggressively than the appeals process that follows it.
Recent complaints elsewhere show why that becomes dangerous. At Skrill, a customer said an account was permanently locked immediately after card funding, leaving the customer trying to determine how the remaining balance would be returned. In another case, a Binance user reported money trapped between multiple payment and account restrictions.
The amounts and circumstances differ, but the customer-experience problem is similar: once several automated controls interact, there may be no simple path back to normal account access.
For Coinbase, This Is Ultimately a Trust Problem
Two Reddit cases are financially immaterial to Coinbase.
They should not be presented as evidence of a systemic operational failure.
But the mechanism they describe matters more than the number of complaints currently visible.
Coinbase itself tells investors that users and assets on the platform are important operational indicators because they reflect the trust customers place in the company.
That makes account recovery more than a customer-support function.
If customers believe legitimate withdrawals can trigger a lock, that is manageable if the recovery process is predictable. If they believe the recovery process can itself become another automated dead end, the risk calculation changes.
This is especially important for a centralized exchange because access is part of custody.
A customer can see every dollar or token in their account and still effectively lose liquidity if the platform will not authorize movement.
That distinction also explains why restrictions such as loss of withdrawal access receive disproportionate attention even when the underlying assets remain intact.
The Next Cases Will Show Whether This Is Noise or a Pattern
The evidence is not strong enough yet to say Coinbase has a widespread ID-verification problem.
What exists is an emerging two-user pattern with unusually similar sequences.
In both cases, the customers say they were established Coinbase users. In both, a transaction preceded an account lock. In both, account recovery required renewed identity verification. In both, multiple government-issued documents allegedly failed. And in both, Coinbase’s public support team ultimately asked the customer to move the issue into Modmail.
The most useful next evidence would be whether Coinbase resolves those cases manually and, if so, how long resolution takes.
If both users regain access quickly after escalation, this may turn out to be ordinary edge-case friction in an automated verification system.
If additional customers begin reporting the same sequence — transaction flagged, account locked, repeated ID rejection, no accessible manual override — the story becomes much more significant.
At that point, the question would no longer be whether Coinbase’s security controls are too aggressive.
It would be whether the exchange has built enough human recovery capacity behind them.
Michael Lebowitz is a financial markets analyst and digital finance writer specializing in cryptocurrencies, blockchain ecosystems, prediction markets, and emerging fintech platforms. He began his career as a forex and equities trader, developing a deep understanding of market dynamics, risk cycles, and capital flows across traditional financial markets.
In 2013, Michael transitioned his focus to cryptocurrencies, recognizing early the structural similarities—and critical differences—between legacy markets and blockchain-based financial systems. Since then, his work has concentrated on crypto-native market behavior, including memecoin cycles, on-chain activity, liquidity mechanics, and the role of prediction markets in pricing political, economic, and technological outcomes.
Alongside digital assets, Michael continues to follow developments in online trading and financial technology, particularly where traditional market infrastructure intersects with decentralized systems. His analysis emphasizes incentive design, trader psychology, and market structure rather than short-term price action, helping readers better understand how speculative narratives form, evolve, and unwind in fast-moving crypto markets.