Changing Acquirers Mid-Contract: A Continuity Plan for UK Card Acceptance
Photo: Francisclarke, CC BY-SA 4.0, via Wikimedia Commons
A change of card payment provider is usually driven by cost, service quality or a need for better integration. The commercial case may be clear, but the operational risk sits in the handover. For a UK merchant, the objective is simple: customers should never encounter a counter without a working card machine, and cash flow should not stall while one provider hands over to another. Achieving that requires a plan built around contracts, approvals, terminals, compliance and settlement timing rather than a last-minute switch.
Begin with the contract, not the terminal
The first task is to establish exactly what the existing agreement permits. Notice periods are often longer than merchants expect, and auto-renewal clauses can extend a term if notice is missed by even a few days. Check the minimum term, termination process, early termination charges and any minimum service or volume commitments. If the terminal estate is leased, treat that arrangement separately from the merchant account: returning hardware and ending acquiring services are distinct obligations with separate deadlines.
Obtain written confirmation from the incumbent provider of the notice required, the proposed end date and the arrangements for final settlement. Do not serve notice until the new facility has been approved and the practical details of the switch are understood. A signed contract with a new provider is not the same as a live merchant account, and a gap between the two is precisely the outcome the plan should prevent.
Sequence approval before notice
New acquirer applications involve underwriting, identity and business verification, and sometimes a site or process review. The time taken varies with the complexity of the business, the sector and the quality of the information supplied. Prepare trading history, company details, ownership information, website or premises evidence and any required licences before applying. If the business takes card-not-present payments, be ready to explain despatch, refund and fraud controls.
Approval should be confirmed in writing, including the merchant category code, pricing schedule, settlement account and go-live requirements. Only then should notice be served on the outgoing provider. Where possible, agree a short period of dual capability. Running two facilities indefinitely creates reconciliation complexity, but a controlled overlap can protect trading if terminal delivery or configuration slips.
Map the settlement gap
Settlement timing is one of the most common sources of avoidable strain. The outgoing acquirer will process final batches and may apply reserve or holdback arrangements before releasing the last funds. The incoming provider may have its own first settlement cycle, and the cutover date may not align neatly with either. Do not assume that card takings will move from one account to the other on the same day.
Build a cash buffer to cover at least the expected settlement interval plus a contingency period. Confirm in writing when the old provider will pay final balances and when the new provider will make its first payment. Reconcile the final statements carefully, including fees, chargebacks and any reserve release. If the business relies on daily card receipts for wages, supplier payments or direct debits, the buffer is not optional.
Reconfigure the terminal estate
Terminal reconfiguration is more than swapping a box on the counter. List every payment point, including backups, pop-up locations, kiosks and integrated tills. Confirm which devices will be retained, which must be returned and which will be replaced. For integrated systems, check that the new provider supports the EPOS software, the necessary middleware and the required payment methods. Test contactless, chip and PIN, refunds, voids and receipts before the first live transaction.
If devices are being replaced, arrange delivery and installation dates against the cutover timetable. Keep at least one tested spare terminal where trading volumes justify it. Staff should know how to reach technical support and how to process a refund or void on the new device. A short test transaction on the morning of go-live is worthwhile; discovering a configuration error at the busiest point of the day is not.
Revalidate PCI DSS without a lapse
The new provider will usually require evidence of PCI DSS compliance, and the scope of the assessment may differ from the previous arrangement. Confirm which self-assessment questionnaire applies, whether an approved scanning vendor is needed and what evidence must be uploaded to the provider portal. Update internal policies, data-flow records and retention practices if systems or suppliers have changed.
PCI DSS revalidation should be treated as a scheduled task with an owner and a deadline. A lapse in evidence can delay activation or create a compliance query at the worst possible moment. Keep copies of certificates and submission confirmations, and ensure that any third-party terminal or payment pages are included in the merchant's understanding of responsibility.
Brief the counter team properly
The switch should be invisible to customers, but it cannot be invisible to staff. Brief supervisors and counter teams on the go-live date, the new terminal layout, refund and void procedures, receipt options and the escalation route for failed transactions. Provide a short written prompt at each till if the device differs from the old one. Identify a single switch lead who can liaise with the provider and make decisions on the day.
Where a brief interruption is possible, agree a fallback process in advance. That may be a backup terminal, an alternative payment method or a clear instruction to direct customers to another branch. Staff should not improvise under pressure. A simple communication plan also helps if customers ask why the terminal looks different; a brief, neutral explanation is usually sufficient.
Use a cutover timetable
Work backwards from the intended go-live date. Six weeks out, confirm contract terms, application evidence and terminal requirements. Four weeks out, complete underwriting and order hardware. Two weeks out, configure and test devices, submit PCI DSS evidence and brief staff. One week out, confirm settlement arrangements and prepare the cash buffer. On the day, run test transactions, monitor the first batches and keep the old provider's support details available until final settlement is confirmed.
After the switch, reconcile daily for the first fortnight and compare effective rates against the quotation. Confirm access to chargeback notifications, statements and support channels. A provider change is complete only when the new facility is trading normally, the final old settlement has been reconciled and the terminal estate is fully accounted for. Handled in that order, a mid-contract switch can be a controlled transition rather than a disruption to trade.