New User Is Asked for Card Statement After Funding Skrill Through Revolut
A fresh Skrill account restriction has exposed a potential verification edge case involving Revolut, as multiple other users in Portugal report their wallets being restricted and funds becoming temporarily inaccessible.
In a Sept. 16 Reddit post, a newly restricted Skrill customer said the payments platform asked for a copy of the credit or debit card statement associated with the card previously used to deposit money into the wallet.
According to the user, the complication is that the funding instrument was a Revolut card, leaving them uncertain whether Skrill expects an ordinary Revolut account statement, documentation identifying the specific card or statements from another bank.
The complaint is unverified and there is no evidence that Skrill rejected a Revolut document. But the case highlights a potentially awkward intersection between two fintech platforms whose documentation formats do not necessarily match.
Skrill’s own verification documentation confirms that customers may be asked for a credit or debit card statement after their initial verification has already been completed.
For card statements submitted as source-of-funds evidence, Skrill says the customer’s name and account information should be visible while the document should show only the first six and last four digits of the card number.
That is broadly consistent with the wording posted by the customer, who said Skrill instructed them to conceal the middle eight digits of the card used to make the deposit.
Revolut, however, produces several different types of documents.
A normal Revolut currency-account statement primarily identifies the customer’s account, IBAN, balance and transactions. Revolut separately provides a card-confirmation document covering physical, virtual and single-use cards, while its subject-access documentation can include a masked primary account number showing the first six and last four card digits.
That suggests the verification request may be resolvable with a more specialized Revolut document rather than representing an impossible requirement. Whether Skrill will accept those specific documents in this customer’s case remains unknown.
The report adds another dimension to a recent cluster of Skrill restriction complaints involving customers who say access to transactions or funds was suddenly limited.
A separate Portuguese customer said their Skrill account was restricted on Saturday after making a deposit to betting platform Betano. The user said they opened a support case, only for it to later appear as “resolved” without Skrill requesting documents or telling them what action was required.
Other users joined the same discussion with similar reports.
One Portuguese customer said their account was restricted despite making no recent deposit and claimed approximately €1,000 remained inaccessible. Another participant said €300 was trapped. Additional users said restrictions began around Saturday or Sunday and that they were still waiting for support responses.
A separate Portuguese personal-finance discussion contains further Sept. 15-16 reports. One customer said their account was restricted after three deposits totaling €900, while another said a €27 deposit was followed by a restriction.
Those reports do not establish that Skrill has imposed a coordinated or erroneous restriction on Portuguese customers. Different users could be undergoing unrelated security, compliance or transaction reviews.
Skrill has not publicly announced a broad account-restriction incident.
Its official guidance says temporarily restricted users should normally see information in their account dashboard explaining what is required. Customers may be asked to provide documents, explain recent transactions or login activity, or update personal information. Skrill says it can also send instructions directly to a customer’s registered email address.
That makes the customer whose case was allegedly marked resolved without instructions particularly interesting. If accurate, it would represent a breakdown between the restriction status and the support workflow rather than simply a slow review.
Similar problems have emerged elsewhere when prolonged verification reviews leave customers uncertain whether they are still expected to provide information or simply wait for a compliance team.
The latest reports also arrive alongside a useful resolution update from an older Skrill complaint.
A customer who posted in June after their account was restricted immediately following a deposit returned to the thread on Sept. 16 and said Skrill ultimately sent the money back and deleted the account.
The user did not provide enough detail to establish why Skrill chose closure rather than restoring normal access. However, the outcome is consistent with Skrill’s published procedures.
Skrill says accounts may be permanently closed if identity details cannot be verified, if a customer refuses required verification or if the company believes its terms have been breached. Where money remains in a closed account, Skrill says it may arrange a refund after performing any required anti-money-laundering, fraud or other financial-crime checks.
For customers in the European Economic Area, including Portugal, Skrill services are provided through Paysafe Payment Solutions Limited, an Irish electronic money institution authorized by the Central Bank of Ireland.
That regulatory framework does not prevent Skrill from imposing additional identity checks. Electronic money firms are expected to monitor customer activity and perform further verification where necessary.
The unresolved question is whether the current reports represent normal individual reviews occurring at roughly the same time or a wider operational change affecting how Skrill is screening particular customers or funding methods.
Refund and Closure May Be as Important as Restoring Access
The Sept. 16 update from the older restriction case changes the most useful question to ask about this cluster.
It is no longer simply: how long does Skrill take to remove a restriction?
It is also: what proportion of these reviews end with the customer being allowed to use Skrill again?
Those are very different outcomes.
A temporary compliance hold that ends after a bank statement is reviewed is ordinary financial-services friction. A process that ends with the customer’s money being returned and the commercial relationship terminated is effectively forced offboarding.
Skrill’s own documentation makes clear that both outcomes are possible.
That matters for the Portuguese customers currently waiting with €300, €900 or roughly €1,000 inside restricted accounts. The fact that the money is temporarily unavailable does not establish that it will be confiscated or permanently inaccessible. Skrill expressly provides mechanisms for returning balances when accounts are closed.
But users may have entered the review expecting account restoration when the actual outcome could be refund followed by termination.
That pattern is already familiar across digital finance. Customers dealing with funds remaining inaccessible during compliance reviews often focus on when the restriction will end, when the more consequential decision is whether the provider still wants the customer relationship at all.
The Revolut-funded account adds another layer.
Legacy compliance language often assumes a conventional bank-issued credit or debit card accompanied by a monthly card statement displaying a masked card number.
Modern fintech cards do not always produce documentation in that format.
Revolut customers can have physical cards, disposable virtual cards, additional virtual cards and account-level statements tied primarily to an IBAN. A compliance system requesting “the card statement” therefore needs to make clear precisely which document it will accept.
Revolut appears capable of producing documentation that bridges the gap. Its card-confirmation and subject-access documents can identify the cards connected to an account, including masked card information.
But customers should not have to guess which financial institution’s document maps to an automated verification requirement.
That is where compliance design becomes a product issue.
Fintech companies increasingly layer sophisticated automated risk controls over simple customer interfaces. Those digital-wallet controls may be necessary to detect fraud and financial crime, but the user-facing workflow also has to explain how a legitimate customer can satisfy the resulting request.
The same principle applies to consumer-disclosure requirements. The strength of a financial institution’s internal controls matters little to a customer if the instructions produced by those controls are ambiguous, unavailable or apparently inconsistent with the documents their other financial providers issue.
There is still not enough evidence to call the current Skrill complaints a platform-wide restriction event.
There is, however, now enough clustering to investigate systematically.
The useful data points are whether the affected Portuguese users share a common funding method, merchant category, transaction date or verification request; whether Revolut-funded accounts appear disproportionately among them; and, most importantly, how each restriction eventually ends.
If most accounts are restored after routine document checks, this may prove to be a temporary compliance-review backlog.
If a meaningful number instead receive refunds followed by permanent closure, the story becomes different: Skrill may effectively be reducing exposure to a category of customers or transactions through offboarding rather than additional verification.
And if users funded through fintech-issued cards repeatedly receive document demands that do not map cleanly to the documentation those issuers provide, the Revolut case may reveal a separate verification-design problem inside the process.
The next meaningful update is therefore not another complaint that an account is restricted.
It is what Skrill ultimately does with the account and the money.
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.