Switch payment processors with a plan for your customers.

Decide what the move needs to solve.

Write down the reason you are changing: provider suitability, a new customer market, settlement terms, a checkout requirement or dependence on one account. Separate the essential requirement from features that would simply be nice to have.

Then map your current setup. Include the merchant account or PSP, gateway, storefront, subscription system, fraud tools and reporting. One brand may supply several of these layers. This map shows what will change when you accept a new proposal.

• What you sell, where your company is registered and where customers pay.
• Monthly volume, average and highest order value, currencies and payment methods.
• Storefront, gateway, billing system and the tools you want to keep.
• The business problem, upcoming deadlines and current processing history.

Compare the complete offer before committing.

Give shortlisted providers the same business profile. Ask each to identify the account, gateway, integration and support included in its proposal. Keep advertised capabilities separate from what is confirmed for your application.

A rate comparison should include the commercial terms that affect cash available to your business. Read settlement timing, reserves, refund and dispute fees, minimums, currency conversion, contract length and exit conditions alongside the transaction price.

Approve the account, then prove the flow.

Prepare the provider’s requested documents and resolve information gaps before setting a launch date. Work in its approved test environment first. Agree who will build the integration and who can authorize a production change.

Your test plan should reflect the payments you actually take. Include a successful payment, a failure, an authentication request where applicable, a refund and a notification that arrives late. Check that your order system and finance reports show the same outcome.

• Confirm production credentials and supported payment methods.
• Verify customer-facing receipts and statement descriptors.
• Check refunds, webhooks, duplicate prevention and reconciliation.
• Record a rollback decision and the person who can make it.

Saved cards and subscriptions need separate planning.

Ask both processors to assess eligible payment credentials and the secure transfer process. Keep raw card details out of spreadsheets and ordinary email. Confirm receiving-provider requirements and payment-method exclusions before scheduling the move.

Build a separate list of customers, products, renewal dates, subscription states and billing references. Those business records must be mapped to the new setup. For Stripe, its published card export excludes Link credentials, subscriptions and payment history; confirm the current process with the migration teams.

Keep ownership clear after launch.

Agree which system handles new transactions, existing refunds and outstanding disputes. Keep the access and records needed for reconciliation under the relevant provider’s terms. Moving new sales does not relocate old transactions.

Review the first live payments, settlement and renewals with the people who own them. Compare actual outcomes with your acceptance criteria before widening the move. ShieldBill Pay can discuss the provider search and onboarding; ShieldBill can be considered separately for supported billing, routing and continuity requirements.