Before moving live checkoutA payment test is only one part of a switching plan.
Use this acceptance plan with the proposed provider and whoever maintains your store. A cheaper quote does not resolve an untested refund, a duplicate subscription or an unknown first deposit. Record the result, date and responsible person for every workflow you actually use. These are questions to resolve, not features promised by Qualified Commercial.
Write down the setup before testing
List your platform and plan, gateway, checkout version, invoice software, accounting edition, terminal models and recurring-billing tools. Ask the proposal to name supported connections, installation and support owners, connector costs and security responsibilities. Include your normal ticket, largest routine order, sales channels and currencies so the tests reflect your business. Do not infer compatibility from a familiar brand name.
Evidence to request before accepting the cutover| Workflow | Result to document | Pause the switch if |
|---|
| Checkout and invoices | In the provider's approved test environment, check success, decline, authentication when required, receipt and order status. Confirm a retry does not create two paid orders. | A failed payment looks paid, or a retry duplicates an order. |
|---|
| Refunds and cancellations | Confirm full and partial refunds, voids if supported, original transaction lookup, customer notice, fee treatment and the account that funds the refund. | The operator cannot locate or refund an old sale through the agreed process. |
|---|
| Recurring billing | Map each active schedule to one billing owner, next charge date, amount and cancellation status. Confirm transfer exclusions and rebuild only the schedules that need it. | Both systems can bill the same customer, or no owner can verify the next charge. |
|---|
| Accounting and reporting | Trace one order identifier through payment, applicable tax, refund, fees and accounting entry. Confirm the connector does not post the same sale twice. | The sale is duplicated or the bookkeeper cannot explain an unmatched entry. |
|---|
| Payouts and ongoing support | Get account-specific first and ongoing payout terms, bank availability, reserve conditions, support contact and escalation owner in writing. | Payroll depends on an unconfirmed deposit or no one owns launch support. |
|---|
Use the provider's documented test tools and test credentials. Stripe, for example, documents simulated successes, declines and authentication, and prohibits testing in live mode with real payment details. Follow your actual provider's rules. A simulated success does not establish bank availability; confirm the real account's payout conditions separately. Do not send customer card numbers, security codes, API keys or passwords to our form or secure room.
A recurring-payment mismatch is a reason to pause.
Illustrative planning example: your old billing list has 120 active schedules. The migration report maps 118, leaving two unresolved. Do not treat the count as complete or simply recreate all 120. Resolve the two exceptions, check next charge dates and cancellation status, and assign exactly one system to each future charge. A card-data transfer is not proof that recurring schedules transferred. This is a control example, not a statement about any supported integration.
Agree on the old-account plan and a fallback
Before cancelling, ask the current provider about notice, renewal, termination, equipment leases, outstanding refunds, disputes, reserves, final fees and report access. Ask how long access remains available and what can still be done after closure. Export permitted business reports before losing access. The new provider does not automatically release an old reserve or take over an old dispute.
Name who can pause a launch and how orders will be handled while an issue is resolved. A fallback must use an approved payment workflow; do not collect card details by email or charge a customer twice. Record when recurring billing moves, who disables the old schedules and who checks the first accounting entries and deposits. If costs, compatibility or account terms remain unresolved, the review can end with a decision to defer or decline the switch.
Bring the unresolved questions to the statement review
Start with contact details below. In your separate secure room, provide the requested statement, separately billed gateway or platform costs, contract and a list of unresolved workflows. The desk can compare the written proposal with your payment mix and flag missing information. Implementation and acceptance tests must be agreed with the actual provider; requesting our review neither changes your processor nor commits you to switch.
Request an online-processing statement reviewProvider examples, not integration promises. Reviewed November 3, 2026: