High-Risk Merchant Account Requirements in the UK

Applying for a high-risk merchant account is less about finding the perfect form and more about making the business easy to understand.

An assessor needs to know who operates the company, what customers buy, when they receive it, where payments come from and what happens when something goes wrong. When those answers are clear and supported by evidence, the application is easier to evaluate. When the website, documents and processing history tell different stories, delays and further questions are likely.

This guide explains what to prepare before a UK merchant-account assessment. Requirements vary by provider, sector and business model, so treat it as a readiness checklist—not a promise of approval.

Why some merchant applications receive extra scrutiny

“High risk” does not describe one type of company. It is a broad label applied when a payment arrangement may create greater financial, regulatory, fraud, chargeback or fulfilment exposure.

The cause might be:

• a closely regulated or restricted sector;
• long delivery or fulfilment periods;
• subscriptions and recurring transactions;
• high average order values;
• international or card-not-present sales;
• elevated refunds, fraud or chargebacks;
• limited trading history;
• a previous account restriction or termination;
• product or advertising claims that require additional evidence.

Different models create different questions. A tour operator taking deposits for future travel does not look like a CBD retailer, licensed gaming operator or software subscription business. Good underwriting examines the actual model rather than relying only on the sector label.

1. Company and ownership information

Start with the legal basics. The company name, number, address, directors and ownership information used in the application should match official records and the public website.

You may be asked for:

• certificate of incorporation;
• registered and trading addresses;
• director and beneficial-owner details;
• group or parent-company structure;
• proof of identity and address for relevant people;
• business bank-account evidence;
• trading names and associated domains.

UK companies must identify and report people with significant control. Companies House guidance describes these people as those who own or control the company and explains the related reporting and identity-verification duties. Review your record before applying and correct outdated details through the proper process. Read the Companies House PSC guidance.

Do not send identity or banking documents through an ordinary website contact form. Use the secure route specified during the application.

2. A complete, consistent website

The website often provides an assessor's clearest view of the customer journey. It should answer the same questions a real customer would ask before paying.

Check that it clearly shows:

• the legal or trading identity of the seller;
• accurate descriptions of products and services;
• prices, currencies and material recurring charges;
• delivery or fulfilment timeframes;
• cancellation, return and refund terms;
• contact and customer-support details;
• privacy and cookie information;
• age restrictions or eligibility rules where relevant;
• prohibited locations or customer types;
• any licences, registrations or disclosures required for the activity.

Remove placeholder copy, broken links, contradictory prices and unsupported claims. If the application says the business sells one thing while the website promotes something broader, expect questions.

3. Processing history and forecasts

Established merchants are commonly asked for recent processing statements. These help show how the business performs in practice.

Prepare clear records of:

• monthly transaction volume;
• average and highest transaction values;
• refund value and count;
• chargeback value and count;
• fraud alerts or losses where available;
• card-present versus card-not-present mix;
• domestic, European and wider international sales;
• seasonality and anticipated growth;
• reserves or restrictions under the current arrangement.

If performance changed sharply, explain why. A product launch, seasonal peak, supplier failure or temporary fraud attack may provide important context, particularly when accompanied by evidence of the response.

New businesses should prepare realistic forecasts rather than copying a best-case sales target. Forecasts should align with the marketing plan, fulfilment capacity and working capital available.

4. Refund, cancellation and fulfilment exposure

Payment risk continues after a transaction is authorised. If customers pay long before receiving the product or service, the provider may still face exposure if the business cannot fulfil orders or issue refunds.

Document:

• the time between payment and fulfilment;
• stock ownership and supplier arrangements;
• cancellation and refund timeframes;
• customer-service escalation paths;
• protection, insurance or bonding relevant to the sector;
• how unfulfilled orders would be handled during disruption;
• the value of outstanding customer commitments at peak periods.

Make sure the written policy matches actual practice. A customer promise hidden in a FAQ but omitted from the terms can still create a dispute.

5. Chargeback and fraud controls

An application is stronger when it shows how the business prevents avoidable disputes rather than simply reporting a historic ratio.

Useful evidence may include:

• transaction-screening and authentication controls;
• address, device or behavioural checks where appropriate;
• recognisable billing descriptors;
• order and delivery evidence;
• clear renewal reminders for subscriptions;
• accessible cancellation routes;
• customer-service response standards;
• a defined process for handling fraud alerts and disputes;
• monitoring by product, channel and market.

Do not describe controls that are not actually operating. A short, accurate process is more credible than a generic policy copied from another business.

6. PCI DSS scope and payment-data handling

Map how payment data moves through the website, apps, terminals and service providers. Identify whether your systems store, process or transmit cardholder data and which third parties are involved.

Outsourcing payment processing can reduce the requirements that apply directly to a merchant environment, but it does not remove all responsibility. The PCI Security Standards Council says merchants remain responsible for confirming that relevant providers are compliant, defining shared responsibilities and validating the appropriate scope. Read the PCI SSC guidance.

Confirm the correct validation route with the organisation managing your compliance programme, such as the relevant acquirer or payment brand.

7. Sector-specific evidence

Some applications need evidence beyond ordinary company documents.

Depending on the model, this might include:

• licences or regulatory registrations;
• product testing and supplier records;
• age-assurance and access controls;
• responsible-use or customer-protection procedures;
• product authorisations or catalogue evidence;
• advertising and claims review;
• bonding, insurance or consumer-protection arrangements;
• terms for subscriptions, trials and renewals.

The evidence must fit the countries served. A permission or product status that is relevant in one jurisdiction does not automatically answer questions in another.

8. Understanding Smarta's role and the regulated provider

Ask who is providing each part of the service and how that firm is regulated. The FCA notes that non-bank payment service providers must be authorised or registered, and recommends checking the underlying legal entity on the Financial Services Register. Brand names do not always match the regulated entity name, so the contractual documents and website footer should make the relationship clear. See the FCA consumer guidance.

Smarta should explain its own role, the parties involved in a proposed arrangement and where to verify the relevant status before a merchant proceeds.

9. Questions to ask before accepting an offer

Approval is not the only consideration. Before signing, ask:

• Which legal entity provides the acquiring or payment service?
• What are the full rates and fixed fees?
• Does a reserve apply, and how is it calculated and released?
• What settlement schedule applies?
• Which activities, products and countries are approved?
• What changes must be reported in advance?
• How are chargebacks, fraud alerts and complaints handled?
• What could trigger a review, restriction or termination?
• Is there a minimum term or early-termination fee?
• What happens to customer tokens or recurring payments if you leave?
• Who provides day-to-day support?

Keep the final agreement, approved business description and related policies. Operational teams need to know what was approved so the live business does not gradually move outside that scope.

Common causes of avoidable delay

• company records and application details do not match;
• the website is unfinished or hides key customer terms;
• requested statements are cropped, incomplete or inconsistent;
• historic restrictions are omitted and discovered later;
• sales forecasts do not match the operating plan;
• licences or product evidence are out of date;
• marketing claims go further than the supplied evidence;
• the applicant cannot explain the flow of funds;
• sensitive documents are sent through an insecure route;
• different advisers give conflicting descriptions of the business.

Resolve these issues before submission where possible. More documents are not always better; the goal is a complete and coherent account of the business.

High-risk merchant account readiness checklist

Before requesting an assessment, confirm that:

• [ ] Companies House and ownership records are current.
• [ ] The website accurately describes the approved business model.
• [ ] Prices, delivery, refunds and contact details are easy to find.
• [ ] Processing statements and dispute figures are complete.
• [ ] Forecasts are realistic and explainable.
• [ ] Sector licences and product evidence are current.
• [ ] Fraud, complaints and chargeback procedures reflect real practice.
• [ ] Payment-data flows and PCI DSS responsibilities are understood.
• [ ] Previous restrictions or terminations can be explained honestly.
• [ ] Sensitive documents are ready for a secure upload process.
• [ ] Decision-makers understand the proposed fees, reserve and settlement terms.

Ready for an initial assessment?

Smarta Payments helps legal, complex businesses understand their options and prepare for a meaningful payment conversation. Tell us how the business operates, what has happened with your current provider and the approximate volume you expect to process.

Request a merchant assessment →

All payment services are subject to assessment and approval. This guide is general information, not legal, regulatory or financial advice.