Insurance businesses can have more complex payment requirements than a standard ecommerce merchant.
An insurer, broker or MGA may need to collect:
- annual premiums;
- monthly or recurring payments;
- high-value commercial premiums;
- telephone payments;
- payments through online quote-and-buy journeys;
- renewals;
- policy amendments; and
- other customer payments across multiple systems or legal entities.
But choosing an insurance payment provider is not simply about finding a processor willing to accept an “insurance” Merchant Category Code.
The provider also needs to understand:
- what type of insurance business you operate;
- who the customer is paying;
- where the premium money is ultimately going;
- whether the business receives or holds client money;
- how recurring premiums and renewals work;
- whether premium finance is involved;
- how the payment journey integrates with insurance software; and
- which entity should hold the merchant account.
For insurance businesses, payment-provider selection needs to follow the money flow as well as the customer journey.
This guide is designed for established UK insurers, insurance brokers, MGAs and insurance intermediaries reviewing their card-processing arrangements or building a more integrated payment setup.
Key Takeaways
- Insurance is not one universal merchant-account risk category.
- Insurers, brokers, MGAs and intermediaries can have very different payment flows.
- The provider needs to understand what customers are paying for and which legal entity receives the money.
- Receiving insurance premiums can create client-money considerations for insurance intermediaries.
- A merchant settlement account is not automatically the same thing as an FCA-compliant client bank account.
- Annual card payments, recurring card instalments and premium finance are different payment models.
- Retail premium finance has separate regulatory considerations and should not simply be treated as another recurring-payment option.
- Insurance firms may need ecommerce, MOTO, payment links, recurring card payments and API integration within the same payment estate.
- Provider selection should consider regulation, money flow, integrations, refunds, renewals, recurring payments and processing history.
- Established insurance businesses changing processor should also consider token portability and how existing recurring payments will migrate.
Find Your New Processor
Who Is This Guide For?
This guide may be relevant to established:
- insurance companies;
- insurance brokers;
- Managing General Agents (MGAs);
- commercial insurance brokers;
- specialist insurance intermediaries;
- online insurance platforms;
- insurance software businesses integrating payments;
- firms collecting recurring insurance premiums; and
- insurance businesses reviewing an existing payment provider.
The exact payment structure will depend on the firm's regulatory permissions, contractual relationships and how premium money moves between the customer, intermediary and insurer.
Insurance businesses can have payment requirements that differ according to transaction type, recurring billing, customer journey, regulation and provider appetite. For a broader overview of merchant accounts, acquiring and provider selection, read our main Merchant Accounts guide.
Are Insurance Businesses High Risk for Card Processing?
Not automatically.
It is too simplistic to describe every insurance company or insurance broker as a high-risk merchant.
Providers will usually assess the individual business and payment model.
Relevant factors can include:
- type of insurance;
- whether the business is an insurer, broker or intermediary;
- FCA status and permissions;
- who receives customer funds;
- average transaction value;
- annual card-processing volume;
- recurring-payment model;
- refunds and cancellations;
- chargeback history;
- customer geography;
- business financials;
- sales channels;
- premium-finance arrangements; and
- the acquiring provider's own appetite.
This means two insurance businesses may receive very different underwriting outcomes despite appearing to operate in the same broad sector.
For a wider explanation of how merchant risk is assessed, see our High-Risk vs Low-Risk Merchant Accounts guide.
MAS View
The useful underwriting question is not “Does this provider support insurance?” It is “Does this provider support this insurance business, this money flow and this payment model?”
Insurance Payments Can Involve Several Different Money Flows
Before comparing providers, map what happens to every customer payment.
For example:
| Payment | Possible payment flow |
| Annual premium |
Customer pays insurer directly |
| Broker-collected premium |
Customer pays intermediary before funds are transferred under the relevant contractual/client-money arrangement |
| Monthly card payment |
Customer pays recurring premium or instalment through the payment processor |
| Premium finance |
Finance provider may fund the insurance premium while the customer repays under a separate finance arrangement |
| Policy adjustment |
Additional premium collected during the policy term |
| Cancellation/refund |
Money may need to be returned to the policyholder |
A payment provider needs to understand which legal entity is contracting for card processing and what that entity is entitled to collect.
Insurance Merchant Accounts and Client Money Are Not the Same Thing
This is one of the most important distinctions for insurance intermediaries.
A merchant account is the acquiring arrangement used to accept card payments.
A client bank account exists for a different purpose.
Under the FCA's CASS 5 rules, client-money requirements can apply to firms that receive or hold money in connection with insurance distribution activity, subject to the detailed application and exemptions within the rules.
See FCA CASS 5: Client Money — Insurance Distribution Activity.
The FCA explains that the purpose of these rules includes protecting customers where an insurance intermediary is responsible for transferring premiums to an insurer or transferring claims money or premium refunds to customers.
The payment processor does not determine whether a particular receipt is client money.
That depends on the firm's legal and regulatory arrangements.
Why This Matters When Choosing a PSP
A broker might ask a provider:
“Can you settle card transactions into our account?”
But the more important question may be:
“Does this settlement structure fit the way we are permitted and contractually required to handle premium money?”
Do not assume that because a PSP can technically settle funds to a bank account, the resulting structure automatically meets the firm's client-money obligations.
What Is Risk Transfer in Insurance Payments?
Insurance intermediaries can sometimes operate under contractual arrangements where they receive money as agent of the insurance undertaking.
FCA CASS 5.2 contains specific rules and guidance relating to firms holding money as agent of an insurance undertaking, including requirements around written agreements.
See FCA CASS 5.2.
This is sometimes referred to in the insurance industry as a risk-transfer arrangement.
Whether such an arrangement applies is a legal and regulatory question for the insurance business and relevant counterparties.
It should be established before designing the payment settlement flow.
Who Should Hold the Merchant Account?
This can become particularly important where there are several organisations involved in the insurance journey.
For example:
- insurer;
- broker;
- MGA;
- software platform;
- premium-finance provider; and
- other distribution partners.
The merchant account should reflect the genuine commercial and contractual payment flow.
Underwriters may want to understand:
- which entity contracts with the customer;
- which entity appears on the customer's statement;
- which entity is authorised to collect premiums;
- where funds settle;
- who is responsible for refunds;
- who carries chargeback exposure;
- which insurer underwrites the policy; and
- how funds subsequently move between the parties.
Trying to force a complex insurance model through the wrong merchant entity can create underwriting, reconciliation and operational problems later.
Paying Insurance Premiums Annually by Card
Some customers prefer to pay the full annual premium by debit or credit card.
For established insurance businesses, considerations can include:
- average premium value;
- consumer versus commercial policies;
- credit-card acceptance;
- corporate/commercial cards;
- card-processing costs;
- refund handling;
- payment authentication;
- international cards;
- MOTO payments; and
- integration with the policy administration system.
For larger commercial premiums, the cost of card acceptance can become commercially significant.
Businesses processing substantial card volumes should therefore understand their actual acquiring costs rather than looking only at a headline percentage.
See our guide to auditing payment fees for high-turnover businesses.
Monthly Card Payments Are Not Necessarily Premium Finance
This distinction is important.
A customer paying an insurance premium in several payments does not automatically mean every instalment structure is the same as a regulated premium-finance agreement.
The legal and regulatory treatment depends on the specific arrangement.
Insurance firms should distinguish between:
- an annual premium paid upfront by card;
- a genuine recurring or subscription-style insurance payment model;
- instalments collected by the insurer or intermediary; and
- premium finance supplied under a separate credit arrangement.
The payment technology may look similar to the customer — for example a monthly amount leaving their account — while the contractual and regulatory structure is very different.
Premium Finance Needs Separate Consideration
Retail premium finance should not simply be treated as a payment-processing feature.
The FCA has specific requirements concerning retail premium finance, including disclosure of:
- the cost of the policy without premium finance;
- the cost with premium finance;
- the difference between those costs; and
- other relevant information about the finance arrangement.
See FCA ICOBS 6A.5: Retail Premium Finance.
The FCA also states that its insurance conduct rules apply alongside other regulatory requirements relevant to regulated credit agreements.
This is why a business reviewing its card processor should not confuse:
payment-provider selection
with:
premium-finance product selection.
They can interact within the same customer journey, but they solve different problems.
Recurring Card Payments for Insurance
Some insurance payment models require recurring card payments rather than a one-off annual transaction.
A provider should be assessed for:
- tokenisation;
- card-on-file support;
- recurring transaction processing;
- expired-card handling;
- account updater capabilities where available;
- failed-payment management;
- retry logic;
- customer notifications;
- cancellations;
- refunds;
- reporting; and
- integration with policy-management software.
The recurring-payment engine should also distinguish between:
- a customer purchasing a new policy;
- scheduled payments during the policy term;
- policy renewal; and
- an entirely new insurance contract.
For more on the payment technology involved, see our Subscription and Recurring Payment Processing guide.
Insurance Renewals Need Payment and Regulatory Thinking
Insurance renewal should not be treated only as a recurring-card technical event.
The customer journey also needs to reflect the firm's wider insurance conduct obligations.
The FCA's ICOBS rules cover information supplied by insurers and insurance intermediaries, while the Consumer Duty requires firms within scope to focus on delivering good outcomes for retail customers.
See FCA ICOBS 4.1 and FCA Consumer Duty guidance.
Payment automation therefore needs to sit behind the correct renewal and customer-communication process rather than determine it.
Payment Links for Insurance Brokers
Payment links can be particularly useful where customers:
- buy over the telephone;
- need to make an additional premium payment;
- need to pay following a policy amendment;
- cannot complete an online quote-and-buy journey;
- receive a payment request by email or SMS; or
- need to pay a broker outside the normal website journey.
A hosted payment link allows the customer to enter card information directly into a provider-controlled payment environment.
This can be preferable to staff manually collecting card numbers, depending on the business process.
MOTO Payments for Insurance Businesses
Many brokers still take some payments by telephone.
Mail Order/Telephone Order — MOTO — transactions create different fraud, security and operational considerations from ecommerce transactions.
When comparing providers, establish:
- whether MOTO is supported;
- how virtual-terminal access is controlled;
- whether different user permissions are available;
- how card information is protected;
- whether calls are recorded;
- how sensitive payment information is excluded from call recordings;
- what fraud controls apply; and
- how the transactions appear in reporting.
Where possible, payment links may provide an alternative to staff manually entering customer card details.
PCI DSS Still Applies to Insurance Payment Journeys
Insurance firms taking card payments also need to understand PCI DSS responsibilities.
Scope can vary significantly depending on whether the business uses:
- hosted checkout;
- payment links;
- embedded payment fields;
- a virtual terminal;
- telephone payments;
- Direct Post;
- custom APIs; or
- merchant-controlled card-data infrastructure.
Using a PCI DSS compliant processor does not automatically remove all merchant responsibilities.
See our PCI DSS Compliance Guide.
Insurance Payment Integrations
For larger insurance businesses, the merchant account is often only one part of the requirement.
Payments may need to connect with:
- quote-and-buy systems;
- policy administration platforms;
- broker management systems;
- CRM systems;
- customer portals;
- renewal engines;
- finance systems;
- accounting platforms;
- call-centre technology; and
- internal reporting.
The payment provider may therefore need:
- robust APIs;
- webhooks;
- tokenisation;
- recurring-payment functionality;
- payment links;
- multiple merchant IDs;
- granular reporting;
- refund APIs;
- user permissions; and
- reconciliation exports.
For businesses with bespoke systems, see our Payment API Integration guide.
Reconciliation Is Particularly Important for Insurance
Payment reconciliation can become complex where one business handles:
- multiple insurers;
- many policies;
- annual and monthly payments;
- adjustments;
- refunds;
- commissions;
- client money;
- premium finance;
- several branches; or
- multiple legal entities.
The lowest-cost processor may not be the cheapest solution overall if finance teams spend substantial time manually matching settlements against policies.
Before selecting a provider, understand what identifying information can be carried through the transaction and settlement data.
Refunds and Policy Cancellations
Insurance payment systems also need to support efficient refund handling.
The firm may need to manage:
- policy cancellations;
- cooling-off periods where applicable;
- mid-term adjustments;
- overpayments;
- duplicate payments;
- premium recalculations;
- partial refunds; and
- historic transactions.
Before changing processor, establish how refunds against transactions processed through the old provider will continue to work.
This can be particularly important if the previous merchant facility is closed too quickly.
Chargebacks for Insurance Payments
Insurance merchants can also receive card disputes.
Potential causes may include:
- unrecognised billing descriptors;
- fraud;
- disagreement around cancellation;
- renewal misunderstandings;
- duplicate payments;
- refund timing;
- customer-service issues; and
- other disputes around the transaction.
Insurance businesses should understand their chargeback performance rather than assuming that being FCA regulated prevents payment disputes.
See our 2026 Chargeback Guide.
High-Value Commercial Insurance Payments
Commercial insurance brokers can also face a different problem: relatively low transaction counts but very high payment values.
This can affect:
- provider underwriting;
- transaction limits;
- fraud controls;
- payment authentication;
- processing costs;
- settlement expectations; and
- the economics of accepting cards.
A provider designed mainly for small consumer payments may technically accept the merchant but still be commercially unsuitable for large premium transactions.
Can Insurance Firms Accept International Card Payments?
Potentially, yes, subject to the firm's business model, permissions, provider appetite and target markets.
International insurance businesses should consider:
- where the customer is located;
- where the insured risk is located;
- where the insurance business is authorised to operate;
- transaction currencies;
- cross-border acquiring;
- FX charges;
- settlement currency;
- local acquiring; and
- international fraud controls.
Payment-processing capability should not be confused with permission to distribute insurance in a particular jurisdiction.
For the payments side of international expansion, see our UK & EU Local Acquiring guide.
Changing Payment Provider as an Insurance Business
Established insurance firms should approach a PSP migration carefully.
Before moving, establish:
- which policies have stored cards;
- how existing tokens work;
- whether tokens can migrate;
- how recurring payments continue;
- how historic refunds will work;
- how existing chargebacks will be managed;
- whether merchant IDs need to be replicated;
- how payment references map into insurance systems;
- whether client-money settlement flows change; and
- when the previous processor can safely be closed.
See our guide to moving stored cards, tokens and recurring payments.
What Documents May an Insurance Payment Provider Request?
The exact underwriting requirements vary, but an established insurance business may be asked for information including:
- company details;
- ownership information;
- FCA registration or authorisation details where applicable;
- insurance permissions;
- details of insurers or principals;
- business model;
- customer terms;
- refund and cancellation policies;
- processing statements;
- chargeback history;
- financial accounts;
- bank statements;
- expected monthly card turnover;
- average and maximum transaction values;
- customer geography;
- website and payment journey;
- premium-finance arrangements; and
- an explanation of how premium money flows through the business.
A clear application is particularly important where several regulated or contractual parties sit between the policyholder and insurer.
What Should Insurance Businesses Compare Between Payment Providers?
| Area | What to check |
| Underwriting |
Does the provider understand the specific insurance model? |
| Money flow |
Can settlement be structured appropriately for the entities involved? |
| Recurring payments |
Tokenisation, retries, card updater and recurring transaction support |
| MOTO |
Virtual terminal, user controls and telephone-payment security |
| Payment links |
Ability to collect remote payments without staff handling card data |
| Integration |
APIs, webhooks and compatibility with insurance software |
| Refunds |
Partial refunds, historic refunds and API support |
| Reporting |
Policy references, reconciliation and settlement data |
| International |
Currencies, cross-border processing and local acquiring |
| Commercials |
Processing fees, fixed fees, settlement and other charges |
| Migration |
Stored-card/token portability and recurring-payment continuity |
| Future fit |
Can the provider support growth, new products and new payment channels? |
Find Your New Processor
The MAS Insurance Payment Fit Test
When reviewing payment providers for an insurance business, we would separate the requirement into seven areas.
1. Regulatory Structure
Which entity is regulated, what activity does it perform and what is it permitted to collect?
2. Money Flow
Where does the customer payment enter the business, who holds it and where must it ultimately settle?
3. Payment Model
Are customers paying annually, by recurring card payment, through premium finance or using several methods?
4. Customer Journey
Are payments collected online, over the telephone, through payment links, through a broker or through an integrated insurance platform?
5. Technical Requirements
What APIs, recurring payments, tokens, merchant IDs, reporting and software integrations are required?
6. Commercial Requirements
What are the card volumes, transaction values, card mix, settlement requirements and current processing costs?
7. Provider Fit
Which providers can support the complete insurance model rather than simply accepting the merchant's industry?
MAS View
The right insurance payment provider should fit the regulated money flow, payment architecture and customer journey — not force the insurance business to redesign them around the processor.
How Merchant Advice Service Helps Insurance Businesses Compare Payment Providers
Merchant Advice Service is an independent payments information, comparison and provider-matching service.
For established insurance firms reviewing payments, we may consider:
- current provider;
- reason for switching;
- annual card volume;
- average transaction value;
- insurance business model;
- FCA status;
- money flow;
- client-money arrangements;
- recurring premiums;
- premium finance;
- MOTO;
- payment links;
- software integrations;
- stored cards and tokens;
- refunds;
- international requirements; and
- future payment strategy.
Merchant Advice Service does not determine how an insurance business should comply with FCA client-money or insurance-distribution rules.
Our role is to help identify payment-provider options that fit the commercial and technical requirements once the firm's regulatory and legal payment structure is understood.
For wider regulated-sector payment guidance, see our Financial Services Merchant Accounts guide.
Read more about How Merchant Advice Service Works.
Sources & Further Reading
FCA — CASS 5: Client Money for Insurance Distribution Activity
FCA Handbook rules and guidance covering client money received or held in connection with insurance distribution activity.
FCA CASS 5
FCA — Holding Money as Agent of an Insurance Undertaking
FCA rules and guidance covering relevant agency arrangements between insurance intermediaries and insurance undertakings.
FCA CASS 5.2
FCA — Retail Premium Finance
FCA rules covering disclosure and remuneration considerations for retail premium finance.
FCA ICOBS 6A.5
FCA — Insurance Conduct of Business
FCA information requirements and wider conduct rules applying to insurers and insurance intermediaries.
FCA ICOBS 4.1
FCA — Consumer Duty
FCA guidance on the Consumer Duty and expected outcomes for retail customers.
FCA Consumer Duty
Related Merchant Advice Service Guidance
Editorial and Commercial Disclosure
Merchant Advice Service is an independent payments information, comparison and provider-matching service.
MAS may receive commission or a referral fee from some payment providers where a business chooses to proceed following an introduction. This does not determine the factual information or provider-selection principles included in this guide.
Merchant Advice Service is not an insurer, insurance intermediary, premium-finance provider, legal adviser or regulatory adviser.
The FCA rules applying to an individual insurance business depend on its activities, permissions, contractual arrangements and circumstances.
References to client money, risk transfer and premium finance in this guide are provided to explain why these matters can affect payment-provider architecture. They should not be treated as a determination of how a particular firm's funds must be handled.
Insurance businesses should obtain appropriate compliance, legal or regulatory advice where necessary before changing their settlement or client-money arrangements.
Payment-provider underwriting, technology, fees and risk appetite can change.
Merchant Advice Service does not make underwriting decisions or guarantee provider acceptance.
FCA and payments information last checked: 26 August 2026
Article last reviewed: August 2026
This guide provides general payment information and should not be treated as legal, regulatory, compliance or insurance advice.