Wed. Sep 16th, 2026

Wise User Says €350 Is Stuck in KYC Loop as Required Upload Prompt Vanishes

ByShane Neagle

September 16, 2026 #Wise
WiseWise

Customer Says Wise Requested Documents but Provided No Way to Upload Them

A Wise customer says €350 has remained inaccessible for roughly two weeks after a verification request allegedly became trapped between the payments company’s backend review process and an app interface showing no outstanding action.

The Sept. 16 complaint, posted publicly on Reddit, describes a more technically specific problem than an ordinary delayed KYC review.

The customer said they transferred €350 on Sept. 2 from their usual Revolut IBAN to their Wise account using the same transfer route they had used previously.

According to the customer, Wise emailed them the same day saying the incoming payment was pending verification and warning that the money could be refunded if the requested steps were not completed within two business days.

But when the customer opened Wise, they say there was no verification task to complete.

Instead, the application displayed a message saying Wise already had everything it needed, accompanied by an acknowledgment button. The customer said there was no red verification banner, document-upload prompt or other mechanism for supplying the additional information referenced in the email.

The report remains unverified. Dave Finances has not independently reviewed the customer’s Wise account, internal case data or correspondence with support.

However, Wise’s own verification guidance shows that the state described by the customer is technically possible.

Wise says users experiencing verification problems may normally see a recovery link on a paused transfer or a banner on their account. If no recovery link or banner appears, Wise recommends attempting a new small transfer as a last resort because doing so can trigger the verification workflow again.

More importantly, Wise says a message stating that it has “all we need” means documents are already with its team for manual review and the customer cannot upload additional material until a decision is made.

That creates a potential conflict with the sequence described in the Sept. 16 complaint.

If Wise’s backend simultaneously required a new residence document while the customer-facing interface considered the account to already be under complete manual review, the customer could effectively receive an instruction that the app gave them no way to follow.

The alleged problem resembles other verification workflow issues recently reported by users of financial apps. In one separate Skrill case, a customer claimed an additional verification step appeared on Android but not on an iPhone, raising similar questions about whether compliance requirements are always presented consistently across customer-facing interfaces.

The Wise customer said support initially continued directing them to a red banner that did not exist.

After they challenged those instructions and provided screenshots, the customer says Wise eventually told them to reply by email with an image of their residence permit, identified as a Permesso di Soggiorno.

The customer said they supplied the document as instructed.

They nevertheless claim the €350 remains under specialist review after interactions with three separate support agents, with no case number and no estimated completion date provided.

The customer describes the process as having continued for 12 days. The original €350 transfer itself was initiated Sept. 2, roughly two weeks before the Sept. 16 post.

The duration alone does not establish that Wise’s review has exceeded its published procedures.

Wise says verification initiated after a transfer has already begun can take between five and 14 working days. If additional information is required, the company says it will contact the customer and will not complete the transfer until verification is finished.

Standard identity checks are often substantially faster, but more complex reviews can take longer.

This distinction is important when comparing the complaint with prolonged verification cases at other financial platforms. A long review can still be legitimate; conflicting instructions about what the customer needs to do raise a different operational question.

Wise also provides a general secure document-upload page for requested identity, address and other documents. Its help documentation nevertheless acknowledges that some verification processes depend on prompts, recovery links or specific account states rather than allowing the customer to freely upload any document at any time.

The customer says support ultimately bypassed the app flow by accepting the residence permit by email.

Wise has not publicly responded to the individual Reddit complaint.

The case arrives as the company continues operating a large international cross-border payments network where automated identity checks are central to balancing fast transfers against anti-money-laundering and fraud obligations.

For customers in the European Economic Area, Wise Account and money-transfer services are generally provided by Wise Europe SA, a Belgian payment institution authorized by the National Bank of Belgium and passported across the EEA.

Wise has also faced greater regulatory scrutiny as it expands. Germany’s BaFin recently fined Wise Europe €16,000 over consumer-disclosure requirements, while the company’s compliance framework has also been relevant to Wise’s broader regulatory strategy in the United States.

Neither development is evidence that the Sept. 16 customer’s KYC issue reflects a wider compliance failure.

The more immediate question is much narrower: did Wise require a residence document while its own app incorrectly showed that no further information was needed?

The Problem Is Not KYC — It Is Whether the Customer Can Complete KYC

Financial platforms sometimes need to freeze a transfer while they verify a customer.

That is normal.

What is not normal, if the customer’s account is accurate, is telling someone they must complete a verification step and then giving them no functioning route to complete it.

That distinction matters.

KYC delays are usually discussed as a trade-off between speed and compliance. Banks and fintech companies cannot simply release every payment immediately because customers find reviews inconvenient. Fraud screening, sanctions controls and customer due diligence inevitably create friction.

But this case may be about something more mundane: software state.

Modern fintech platforms run several systems at once. One service may determine that another document is required. Another may control the account’s verification status. A third may decide which banner or task appears in the mobile application. Customer support may then see only part of that information.

If those systems fall out of sync, everyone can technically be following the rules while the customer remains stuck.

The compliance engine says: upload a document.

The app says: nothing else is required.

The support agent says: click the banner.

The customer says: there is no banner.

That is much more interesting than a slow manual review because waiting longer does not necessarily fix it.

The recent Skrill complaint is useful for comparison. A customer there claimed a verification requirement that was invisible on one device became visible on another. The platforms and cases are unrelated, but both illustrate the same broader risk: compliance processes increasingly depend on customer interfaces working perfectly.

That dependency matters because financial apps have spent years making transfers look effortless. Instant-money platforms train customers to expect complex banking and payment infrastructure to disappear behind a few taps.

KYC is where that illusion breaks.

Once a transfer enters specialist review, the customer suddenly discovers how many separate layers sit behind the simple interface.

The €350 amount is small in corporate terms, but that actually makes the case more useful.

A customer should not need a bespoke escalation process, repeated support contacts and manual email submission to resolve a routine €350 transfer if the only missing item is a valid residence permit.

At the same time, Wise’s published five-to-14-working-day verification window means the elapsed time should not be overstated. The stronger story is not that 12 days automatically represents an excessive KYC delay.

It is that several of those days may have been spent trying to satisfy a requirement that the customer says the application did not display.

That is testable.

The most useful next step would be finding another Wise customer whose account received the same combination: an email demanding action within two business days, an app saying Wise already had everything required and no banner or recovery link through which the requested document could be uploaded.

If another independently documented case reproduces that sequence, the story moves from a difficult individual verification into a possible product bug affecting compliance workflows.

If it cannot be reproduced, this may remain an unusual account-specific interaction between Wise’s manual-review team and customer support.

Either way, the distinction is important.

Fintech companies need strong KYC controls. But a compliance requirement is only useful if the customer is actually given a functioning way to comply with it.

Financial Markets Analyst and Digital Assets Journalist at  |  More Posts

Shane Neagle is a financial markets analyst and digital assets journalist specializing in cryptocurrencies, memecoins, prediction markets, and blockchain-based financial systems. His work focuses on market structure, incentive design, liquidity dynamics, and how speculative behavior emerges across decentralized platforms.

He closely covers emerging crypto narratives, including memecoin ecosystems, on-chain activity, and the role of prediction markets in pricing political, economic, and technological outcomes. His analysis examines how capital flows, trader psychology, and platform design interact to create rapid market cycles across Web3 environments.

Alongside digital assets, Shane follows broader fintech and online trading developments, particularly where traditional financial infrastructure intersects with blockchain technology. His research-driven approach emphasizes understanding why markets behave the way they do, rather than short-term price movements, helping readers navigate fast-evolving crypto and speculative markets with clearer context.

Leave a Reply

Your email address will not be published. Required fields are marked *