What is Safeguarding?
UK/EU rule requiring EMIs and PIs to segregate customer funds in dedicated safeguarding accounts or insured against insolvency; strengthened under 2026 UK rules.
Safeguarding is a regulatory obligation under the UK Electronic Money Regulations 2011 (EMRs) and Payment Services Regulations 2017 (PSRs), requiring electronic money institutions (EMIs) and payment institutions (PIs) to protect customer funds.
This protection is achieved by depositing funds into a segregated safeguarding account at an authorised credit institution, or by insuring them against the PI's insolvency.
The regulations mandate that these funds remain distinct from the PI's operational capital and are inaccessible to the PI's creditors in the event of liquidation, ensuring that the full value of the customer's e-money or payment transaction is returned.
For a merchant, safeguarding primarily provides assurance that funds held by their payment service provider (PSP) are secure and ring-fenced from the PSP's own financial health.
While merchants do not directly interact with safeguarding accounts, they benefit from the regulatory oversight that ensures their settlement funds are protected from provider insolvency.
A common misconception for merchants is that safeguarding functions identically to deposit insurance schemes like the Financial Services Compensation Scheme (FSCS); however, safeguarding only protects the principal amount, not any interest,
and the recovery process in an insolvency can be lengthier than for FSCS-protected bank accounts.
Worked example
A merchant reviews a €500 transaction where Safeguarding is the deciding factor. The merchant checks geography, payment type, customer status, and exemption criteria before deciding which compliance treatment applies.
The operational cost is modelled at non-compliance exposure that can exceed the processing margin on the sale, and the relevant action must complete at Checkout or onboarding.
Step 1 is to capture the original request data, including amount, currency, issuer country, MID, and response or status code. Step 2 is to apply the merchant's rule set, for example whether to retry, challenge, refund, release goods, or hold for review.
Step 3 is to reconcile the result against acquirer reporting so finance can see the cash impact. If the rule improves the outcome by even 50 basis points on 2,000 similar monthly transactions, the merchant protects roughly 10 extra orders from avoidable failure or loss.
Scheme notes
This is not wholly scheme-specific, because regulatory obligations come from legislation, regulators, and local payment-system rules rather than Visa or Mastercard alone. Scheme rules still matter operationally because they define message fields, liability allocation, evidence standards, and monitoring consequences.
UK and EEA treatment can diverge after Brexit, and domestic schemes or bank-transfer rails may apply separate rulebooks. Merchants should treat scheme compliance and legal compliance as overlapping controls, not substitutes.
Why it matters for merchants
Commercially, this affects compliance cost, payment acceptance, refund and dispute obligations, and the risk of regulatory or scheme enforcement.
For a merchant processing £500,000 per month, a 25 basis point movement is worth £1,250 before secondary effects such as disputes, reserves, support tickets, or failed delivery costs.
The impact is larger in high-risk, subscription, travel, digital-goods, and cross-border models because issuer decisions and scheme monitoring can compound quickly.
Cardflo can help by combining acquiring access, MID routing, orchestration rules, KYB review, and chargeback tooling where relevant, so the merchant is not dependent on one processor interpretation or one fixed transaction path.
Frequently asked
Which data should a merchant store for Safeguarding?
Store the transaction ID, MID, acquirer, amount, currency, issuer country, card scheme, response or status code, timestamp, and any 3DS, exemption, refund, or dispute reference. For card transactions, keep authorisation and Clearing identifiers because settlement or chargeback questions may arrive 30 to 120 days later.
For regulated flows, keep customer consent and evidence records for at least the period required by local law or scheme rules. Good records reduce investigation time from hours to minutes when acquirer reporting does not match the order system.
How often should Safeguarding be reviewed?
High-volume merchants should review exception rates weekly and trend the main metric monthly by scheme, acquirer, issuer country, MCC, and payment method. A movement of 20 to 50 basis points can be material if the merchant processes thousands of orders.
Finance should reconcile the cash impact at settlement level, while risk or payment operations should analyse the root cause. Reviewing only blended totals hides problems that appear on a single BIN range, region, or MID.
What threshold usually triggers action on Safeguarding?
The threshold depends on the category, but merchants should investigate any sudden change above 10% relative movement or 25 basis points absolute movement. For disputes and fraud, scheme thresholds such as 0.9% under Visa monitoring or 1.5% under Mastercard ECM can create immediate escalation risk.
For settlement or pricing items, even 5 to 15 basis points can justify routing or contract review. The key is to set thresholds before month-end, not after a processor invoice or scheme notice arrives.
Can Safeguarding differ between acquirers?
Yes. Acquirers can map response codes differently, apply different risk rules, support different data fields, and settle on different cycles.
One acquirer may return a generic decline while another exposes issuer advice that allows a safe retry. Fee treatment can also vary by contract, especially for cross-border, FX, premium cards, and alternative payment methods.
This is why merchants using orchestration should compare performance by acquirer and scheme rather than relying on a single blended approval or cost figure.
What is the first remediation step when Safeguarding creates losses?
Start with a 30-day sample and split it by scheme, issuer country, card product, payment method, MID, and response or dispute code. Quantify the value at risk in cash terms, not just percentage points.
Then decide whether the fix is operational, such as better evidence or customer communication, technical, such as richer data or 3DS indicators, or commercial, such as a different acquirer route.
Recheck the same metric after one full settlement or dispute cycle to confirm the change worked.
See how Safeguarding plays out in practice
Industries and regions where this term drives real acquiring, routing, or dispute decisions.
Related terms
The EU's Payment Services Directive 2, which mandates SCA, opens banking APIs, and reshapes payment liability.
Successor to PSD2 (Payment Services Regulation and PSD3) tightening SCA, fraud liability, IBAN name-checking, and open finance access; in EU legislative process.
The currency in which an acquirer pays a merchant, potentially different from the transaction currency and requiring FX conversion.
Related guides.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.