Skip to content

GUIDE / BUSINESS CONTINUITY

When a payment provider reviews or rejects your store

A provider-neutral process for diagnosis, evidence and safe migration. The goal is not a quick provider comparison but reliable payment continuity without carrying the same root cause forward.

Last expert review
30 July 2026
Reviewed by
FoxPay Product & Compliance
Continuity checklistSTATUS
01
CauseProduct, market, policy, evidence or operations
DIAGNOSE
02
EvidenceCheck completeness and contradictions
VERIFY
03
ContinuityProtect checkout, refunds and pending payments
PROTECT
04
MigrationTest, parallelise and switch under control
PLAN
REVIEW-IDSEO-2026-07 / EN

01Diagnosis

Understand the actual reason first

01

Policy vs law

A provider decision is not automatically a legal prohibition—and vice versa.

02

Product boundary

One product, claim or delivery market can affect the entire account.

03

Evidence gap

Missing licences, UBO data or supply-chain records can be addressed directly.

04

Operating signal

Complaints, refund patterns or unclear fulfilment need operational correction.

02Continuity

Stabilise payment operations under control

01

Pending payments

Inventory status, refunds and support cases with the current provider.

02

Communication

Change checkout and customer support only with confirmed information.

03

Fallback

Prepare an alternative method without creating duplicate payments.

04

Data export

Secure references, payouts, fees and evidence in time.

03Migration

Approve the new payment path with evidence

01

Scope

Get products, markets and requested methods confirmed explicitly.

02

Sandbox

Test success, abandonment, delay, retry and refund.

03

Parallel phase

Where possible, switch under control and monitor both status sources.

04

Closure

Revoke old credentials, resolve open cases and update documentation.

04Workflow

A safe switch in five steps

Each step reduces the risk of carrying the same cause or new operating failures forward.

  1. 01

    Record decision

    Capture reason, deadline and affected scope in writing.

  2. 02

    Evidence pack

    Update company, products, markets and controls.

  3. 03

    Review fit

    Approach the new provider with the complete merchant case.

  4. 04

    Test technology

    Approve checkout, status, webhooks and refunds.

  5. 05

    Migrate under control

    Name monitoring and ownership for the switch.

06FAQ

Frequently asked questions

Answers for the current, expert-reviewed scope.

Should I change provider immediately?

Not without diagnosis. Clarify the reason, deadline, pending payments and possible corrections first, then review the switch with the full scope.

Does one rejection mean every provider will reject me?

No. Policies, risk models and product scope differ. Legality and complete evidence remain necessary regardless.

Which data should I secure?

Payment references, payouts, fee records, refunds, open disputes and technical logs where legally permitted.