Verified User Says External Crypto Transfer Prompted Immediate Restriction
A growing cluster of Skrill account restrictions has gained a potentially important new lead after a verified customer said their account was restricted immediately after they attempted to move funds to an external cryptocurrency wallet.
The Sept. 15 report adds a crypto-related trigger to complaints that began clustering around Friday and Saturday, when multiple customers independently said previously functioning Skrill accounts were suddenly placed under review.
The latest user said their identity and address had already been verified before they attempted to convert or send funds to a cryptocurrency address. The account was then restricted and Skrill requested a credit or debit card statement, according to the customer’s account.
The report remains unverified and there is no evidence establishing that Skrill is systematically restricting customers who use its crypto-withdrawal service.
Still, it adds a new common factor worth monitoring because Skrill explicitly offers withdrawals to external crypto wallets and says Australia is among the countries where the feature is supported.
Under Skrill’s current process, customers can send cryptocurrency to either custodial addresses operated by exchanges such as Binance and Coinbase or non-custodial wallets such as MetaMask and Ledger. Customers are asked to identify the type of destination and, where applicable, the exchange receiving the funds.
Skrill’s cryptocurrency terms also state that additional information or identity checks can be required either before or after crypto services have been made available to a customer.
That means the fact that an already verified customer was subjected to another review does not itself indicate anything abnormal. Financial platforms routinely apply account restrictions when transaction activity triggers additional fraud, identity or compliance controls.
The more unusual part of the latest report involves the documents Skrill requested.
The customer said they had funded Skrill through Revolut and submitted a Revolut statement containing their name, address, card details and Australian BSB and account information. They said Skrill’s chatbot nevertheless indicated that a Revolut statement might not qualify because Revolut was considered a digital bank.
Skrill’s published address-verification requirements support part of that response. The company explicitly says it does not accept statements from purely online financial institutions, naming Revolut and PayPal as examples.
However, the customer’s situation exposes an increasingly awkward edge case in that policy.
Revolut Payments Australia received an Authorized Deposit-Taking Institution license from the Australian Prudential Regulation Authority on July 21. Revolut now operates there as Revolut Bank Australia and is legally authorized to conduct banking business.
The development reflects Revolut’s broader expansion from a fintech and payments application into regulated banking and digital-asset infrastructure across multiple markets.
Skrill’s generic support documentation still names Revolut among online institutions whose statements are unacceptable for address verification, without distinguishing between jurisdictions where Revolut operates under different licenses.
There is another complication. The customer said Skrill requested a credit or debit card statement rather than simply proof of address.
Skrill’s separate card-verification documentation says it can request a credit-card statement when manually verifying ownership of a payment card. Its document-rejection guidance says those statements should display the customer’s name and appropriate account or card details, with sensitive card digits masked.
That creates uncertainty over which document rule applies in this case: the policy excluding Revolut statements for address verification, or the separate process for proving ownership of a card used to fund the account.
Other reports posted Sept. 15 suggest the wider restriction cluster remains unresolved.
One customer said an account restricted on Friday was still under review after a bank statement was submitted that day. Another said their restriction began Saturday and they had received no meaningful response. A third commenter said their account had already remained restricted for approximately one month despite repeated emails and calls.
Those reports follow similar complaints from Sept. 7 and Sept. 8 involving customers who said requested documents had been submitted but their accounts remained restricted beyond the expected review period.
The pattern resembles other cases involving extended withdrawal reviews, where the underlying compliance check may be legitimate but uncertainty over timing becomes the central customer issue.
One additional Sept. 14 report raises a separate technical question.
A customer claimed their iPhone continued showing the account as under review even after they had supplied information. According to the user, signing into Skrill from an Android device unexpectedly presented an additional verification step; completing it immediately restored account access.
That report is unverified and could represent an account-specific or device-specific issue. There is no evidence establishing a general difference between Skrill’s Android and iPhone verification flows.
It is nevertheless worth watching because other customers have complained that they were shown a restriction notice without clear instructions explaining what verification remained outstanding.
Paysafe’s public system-status page provides no indication of a wider Skrill outage. The Skrill Consumer Wallet, API, website and mobile application are currently listed as operational, and no Skrill incident was reported Sept. 15.
That makes the growing reports look more like account-level risk or verification actions than a conventional technical outage.
The Crypto Trigger Changes What Investigators Should Watch
The first wave of complaints left several plausible explanations.
Skrill could simply have been processing an unusually visible group of routine KYC cases. Some users had questionable funding arrangements, including one customer who admitted using a business card that was not registered in their name. Skrill explicitly prohibits that practice.
The new crypto case makes the picture more interesting because it identifies a specific transaction immediately preceding a restriction.
External crypto-wallet withdrawals create a different risk profile from spending money inside a conventional wallet ecosystem. Once assets leave for a blockchain address, reversing the movement becomes considerably harder. It therefore makes sense for a payments provider to apply stronger identity, fraud and transaction controls around those transfers.
That does not mean crypto caused the broader restriction cluster.
There is currently only one fresh report explicitly identifying an external crypto transfer as the trigger. Other users have described card deposits, ordinary account activity or no identifiable trigger at all.
The useful question now is whether more customers independently report the same sequence: verified account, attempted external crypto withdrawal, immediate restriction and a request for payment-instrument documentation.
If that pattern repeats, it would begin to look less like random KYC friction and more like a specific risk-control pathway.
The Revolut issue may prove equally significant.
Digital finance has moved faster than many compliance-document policies. A company that was once straightforwardly classified as an online fintech can later become a licensed bank while retaining exactly the same app-based customer interface.
Revolut Australia is a good example. It is now an Australian bank, but Skrill’s support page still categorizes Revolut alongside PayPal as an online financial institution whose statements are not accepted for one type of verification.
That does not necessarily make Skrill’s policy wrong. A regulated business can decide which document formats and institutions satisfy its own verification procedures. But customers need to know which rule applies before their money becomes inaccessible.
The distinction becomes particularly important when a customer is being asked to verify the very payment instrument used to fund Skrill. Rejecting that provider’s statement while simultaneously asking for evidence tied to that provider can create a circular compliance problem.
The reported Android workaround raises another question: whether some customers are actually waiting for manual reviews or are stuck because a required verification workflow is not being presented consistently across devices.
If true, that would be materially different from a genuine compliance investigation.
Similar uncertainty has made prolonged account freezes at other financial platforms difficult to interpret. A customer sees the same outcome—money cannot be moved—whether the cause is AML screening, a fraud rule, missing documentation or a software problem.
From the customer’s perspective, those distinctions disappear once funds become inaccessible.
For Paysafe, the issue is small in financial terms so far but worth watching operationally. Its Digital Wallets division, which includes Skrill and Neteller, generated $206.6 million of revenue in the second quarter, up 3% year over year. First-half Digital Wallets revenue reached $422.7 million.
Wallet businesses depend heavily on customers treating stored balances as liquid money rather than trapped balances awaiting permission to move.
That becomes even more important as payments platforms connect conventional bank funding to on-chain wallet infrastructure and other crypto rails.
There is still no evidence that Skrill has launched a formal weekend batch review, no evidence of a solvency problem and no indication that customer balances are missing.
But the story has moved beyond one unhappy user.
The next useful evidence will be whether additional restricted customers identify external crypto withdrawals as the trigger, whether Revolut-funded accounts are disproportionately represented, and whether customers who appear stuck on one device can unlock additional verification steps through another interface.
If those patterns repeat independently, the current cluster may reveal something much more specific than ordinary KYC delays: a risk-control or verification process that is being triggered predictably but communicated inconsistently to the customers caught inside it.
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.