Verified Revolut Business Accounts in 2026: Onboarding, Limits, and Operational Playbook

Revolut Business has become one of the most widely used neobank accounts for cross-border operators, freelancers, agencies, and small fintech teams. The combination of multi-currency IBANs, instant intra-Revolut transfers, an API, and a tolerable card program means that for many digital-first companies it has quietly replaced the traditional business current account. That popularity has a cost. In 2026 Revolut's compliance posture is materially tighter than it was even eighteen months ago, and the experience of opening, scaling, and surviving on a Revolut Business account has changed in ways that catch operators by surprise.

This guide is the long-form orientation for anyone who relies on Revolut Business as production infrastructure. It explains how the onboarding flow actually works in 2026, what a verified account unlocks at each plan tier, where the silent thresholds are, and how to operate within them without triggering the kind of review that ends with a closure letter and a six-week wait for a final balance transfer.

Revolut's Know-Your-Business process is no longer a thirty-minute form. The 2026 flow starts with company registry verification through a direct connection to the relevant national registry, then layers on identity verification for every individual holding 25 percent or more of the equity, plus any director or person of significant control. Each of those individuals goes through a separate full Know-Your-Customer journey including a liveness check, document capture, and a background screening pass against sanctions, politically exposed person, and adverse media lists.

Once individual verification is complete, the platform asks for a description of the business activity in free text, the expected monthly inbound volume, the expected average transaction size, the top three counterparties by country, and the source of initial funding. The free-text business description is read by a model and, on a non-trivial percentage of applications, by a human reviewer. Vague answers like 'consulting' or 'online business' now trigger a follow-up request for a more detailed description, sample contracts, or a website. Operators who treat this section as a formality routinely add days to their onboarding.

After the form is submitted, the account opens in a partially restricted state. Inbound payments are allowed, but outbound payments above a small threshold are blocked until the full review completes. The review is usually finished within two to seven business days. Applications that include unusual jurisdiction combinations, freshly registered entities, or beneficial owners who have triggered prior reviews on other Revolut products can sit in queue for two to four weeks.

Revolut Business currently offers Basic, Grow, Scale, and Enterprise plans. The marketing pages emphasize card limits, transfer allowances, and team seats, but the operational differences that matter to most teams are elsewhere. The Basic plan is suitable only for very small operators or as a test account. It includes a single local IBAN, a small free-transfer allowance, and a slower support channel. The Grow plan introduces additional currencies, a larger free-transfer allowance, and access to scheduled payments. It is the entry point at which Revolut Business starts to function as a real operational account.

The Scale plan is where most growing operators land. It includes a meaningful number of free international transfers, dedicated currency accounts for the major trading pairs, larger card spending limits, and access to the API at a level sufficient for automated payouts and reconciliation. The Enterprise plan is bespoke and includes negotiated FX margins, dedicated relationship management, and access to bulk payment tools. The relevant decision for most teams is whether to start at Grow and upgrade later or to start at Scale and avoid the disruption of a mid-quarter plan change.

The published limits on the Revolut Business plan pages are not the same as the operational thresholds the compliance engine cares about. There are at least three distinct silent thresholds that operators discover by hitting them. The first is the deviation threshold: a sudden change in monthly inbound volume of more than roughly three times the trailing average triggers a review even when the absolute number is well within plan limits. The second is the counterparty-concentration threshold: receiving more than approximately 70 percent of monthly inbound from a single counterparty, especially one in a jurisdiction different from the registered company address, raises a flag.

The third is the behavioral-anomaly threshold. Logging in from a new country, especially one with elevated risk scoring, can trigger a session-level challenge and, if repeated, a full account review. Operators who travel and access the account from multiple geographies should configure the trusted device list deliberately and avoid mobile data networks that route through unexpected exit nodes.

None of these thresholds are individually problematic. The pattern that produces freezes is the simultaneous trigger of two or more of them in the same week. A new top customer paying a large invoice from a new country while the founder happens to be travelling is exactly the combination that ends with a request for supporting documents and a temporary outbound restriction.

The single most cost-effective investment a Revolut Business operator can make is in proactive documentation. Every invoice above approximately 5,000 EUR-equivalent should be stored in a folder that can be uploaded inside two minutes if requested. Each invoice should clearly list the counterparty legal name, the counterparty registered address, a description of the goods or services, and a reference number that matches the payment narrative. The platform's review team is staffed by people working through a queue. Reviews that are easy to clear are cleared quickly.

Contracts with recurring customers should be stored alongside the invoices. A one-page master services agreement is sufficient for most reviews. Source-of-funds documentation for the initial capital injection should be kept indefinitely. Operators who started the company with personal savings should have at least one document showing the transfer from a personal account into the business; operators who took external investment should have the term sheet, the share-subscription agreement, and the bank statement showing the inbound investor transfer.

The multi-currency feature is the headline reason most operators choose Revolut Business, and it is also the feature most likely to produce surprising fees. The default behavior of the account is to convert inbound payments to the base currency at the interbank rate during weekday market hours, with a markup on weekends and outside of major-pair hours. Operators who receive USD payments on a Friday evening UTC and let them auto-convert to EUR are paying a meaningfully worse rate than operators who hold the USD over the weekend and convert during Monday morning London hours.

The cleanest pattern is to explicitly hold balances in the currencies you receive and to schedule conversions during the windows where the interbank rate is tightest. For most major pairs, the best window is approximately 09:00 to 16:00 London time on a weekday that is not a major holiday in either the source or destination market. Operators who automate conversions through the API can set rate alerts and execute conversions programmatically, which removes the temptation to convert at convenient but expensive times.

Revolut Business cards are useful for operational expenses, supplier payments, and travel, but the program has hard category restrictions that have tightened in 2026. Gambling, cryptocurrency purchases from non-whitelisted platforms, certain adult merchant categories, and a growing list of high-risk MCCs are blocked by default. Some categories can be unblocked through a request flow; others cannot. Operators who attempt to push blocked categories through the card see the transaction declined and, after a small number of attempts, a friction notice asking them to confirm the legitimacy of the attempted use.

Card spending limits are configurable per card and per team member, and the configuration model is one of the strongest aspects of the platform. Daily, weekly, and per-transaction limits can be set independently. For teams that issue cards to contractors or to specific projects, this is the difference between a usable expense tool and a constant source of reconciliation work. Operators should configure these limits before issuing the card rather than after the first overspend.

The Revolut Business API is sufficient for most automated payout and reconciliation use cases. It exposes endpoints for creating payments, listing transactions, managing counterparties, and reading account balances across currencies. The authentication model uses a JSON Web Token signed with a private key whose corresponding public key is uploaded to the dashboard, which is more rigorous than the simple bearer-token model used by some competitors and is appreciated by security teams.

The patterns that work in production share three properties. First, every outbound payment includes an idempotency key derived from the originating invoice or payout identifier, which prevents duplicate sends in retry scenarios. Second, the application reconciles against the API at least every fifteen minutes rather than relying solely on webhook delivery, which has improved but is not yet perfectly reliable. Third, the application alerts on counterparty-creation failures, which are the most common silent failure mode and which indicate that a recipient has not been added to the address book before the payment attempt.

Even well-operated accounts occasionally enter a review. The right response is to read the request carefully, respond inside the requested window, provide exactly the documents asked for, and avoid the temptation to over-explain. Reviews that close quickly are reviews that look organized. Reviews that drag are reviews where the operator submits a 40-page narrative and three folders of marketing material, leaving the reviewer to find the specific document that answers the specific question.

If an account is frozen rather than reviewed, the right response is to stop using it for non-essential activity, transfer time-sensitive operations to a backup banking provider, and engage with Revolut's recovery process through the formal channels. Public posts on social media and aggressive support-channel behavior rarely accelerate the outcome and occasionally harden the platform's position. Operators who maintain a relationship with a relationship manager on the Scale or Enterprise plan have a meaningfully higher rate of successful unfreezes than operators who only interact through the in-app chat.

No single neobank should be the only banking provider for a business that depends on continuity of operations. The cost of opening a second business account at a different provider is small relative to the cost of a multi-week outage during a review. Operators who treat Revolut Business as their primary operational account should maintain at least one backup account at a traditional bank and at least one secondary neobank, with the ability to switch primary inbound payments inside a single business day.

Backup is not just about having the account open. It is about having the counterparties pre-loaded, the API credentials provisioned, the team trained on the alternate interface, and the accounting integration configured. Operators who only test their backup the day they need it discover at the worst possible moment that the backup is not actually a backup. A quarterly drill in which a defined percentage of payments is routed through the secondary provider is the cheapest insurance available.

Revolut Business in 2026 is a powerful, mostly reliable, occasionally frustrating piece of infrastructure. Operators who treat it as such and invest in the documentation, multi-currency, API, and continuity patterns described above extract enormous operational leverage from it. Operators who treat it as a magic black box that takes care of compliance for them eventually experience the limits of that assumption, usually at the worst possible time.

The verified account is the foundation. Everything else is operational discipline. Both are required, and neither substitutes for the other.