Leaving a platform that arranged your processing

Map what the platform supplied and what you hold directly

Collect the platform agreement, any direct provider agreement, account notices and the access you legitimately hold. Record the contracting party named in each document and the company responsible for each payment function. Identify who can request account changes, retrieve payment records and obtain help. If a document is unavailable, name it as missing rather than inferring the arrangement from a logo in checkout.

The practical distinction is between a relationship the platform supplied and one the merchant already holds independently. Do not assume that either arrangement applies. A platform may be involved even when a merchant can see provider records, and access to those records alone does not establish the right to use the same account outside the platform.

Stripe has specific support guidance for businesses using Stripe through a third-party platform. Its recorded guidance directs account questions through logged-in Dashboard support with appropriate references, without full card numbers or CVC. Use the support channel available for the actual account to clarify unanswered responsibilities. That guidance does not itself promise an account conversion or migration.

Obtain an answer for the independent arrangement

Describe the destination business accurately: the legal seller, research-only catalog, country, website, sales channels and proposed payment integration. Ask the relevant provider whether the existing account can serve that arrangement after the platform relationship ends, or whether another account and agreement are required. Preserve the dated answer and any conditions. A working independent website does not answer the processing question.

If a new Stripe account is needed, Stripe’s multiple-accounts documentation says it does not inherit special status from an existing account. Record eligibility and account terms for the destination separately from the platform-era terms. Do not present the earlier approval or operating history as proof that the independent arrangement has been approved.

Independent approval status should describe what a provider has actually confirmed: the named seller, account and disclosed activity, together with unresolved conditions. A submitted request remains a request. Silence remains unanswered. This guide neither classifies all research-only merchants under one Stripe policy outcome nor assumes that leaving a platform makes processing unavailable.

Define each transfer by the records it includes

Create separate transfer lines for payment credentials, payment history and the store’s operational records. For each, name the source, the authorized destination, the party able to transfer it and the written scope. Being able to download an order list does not establish a route for moving stored card credentials, and a credential-migration offer does not establish that the other records will arrive.

Stripe’s card-data export process transfers card data only to another PCI DSS Level 1 processor through its process. Link credentials are excluded, and the export does not include payment history or other objects. Apply those limits when that Stripe process is the proposed route. They do not define an export from every platform, and they do not promise the destination will accept every requested credential.

Ask separately how the merchant will retain access to transaction history and the records needed for unresolved orders, refunds and disputes. Record export coverage, available dates, ownership and access restrictions from the actual agreements or replies. If subscriptions or other ongoing billing are involved, obtain a separate scope for them; a card-data transfer alone is not evidence that their operating setup moves.

Keep credential transfer between the authorized providers. The worksheet needs a scope and status, not card data, private tokens or a file of payment credentials. A migration should never be represented as complete merely because the payment-credential portion was confirmed.

Make the exit decision from the remaining dependencies

Before stopping the platform relationship, line up four confirmations: the destination payment arrangement, authorized account access, the agreed transfer or retention scope and the owner of existing activity. Take notice dates and access deadlines from the documents or the platform’s written answer. Do not infer that cancellation preserves access, closes a separate processing agreement or transfers outstanding responsibilities.

The integration owner also needs a defined destination account and an agreed checkout handoff. Record that technical work separately from the provider’s approval. If the processing relationship is unresolved, the independent store is not yet established as ready to take payments through it. If old records will become inaccessible before their required handoff, name the missing record or permission as an exit dependency.

For a Prism processing consultation, summarize which relationship the platform supplied, what the destination provider has confirmed and which access or transfer question remains open. Use the processing service page to define the consultation scope, responsibilities, fees and terms before work. Keep contracts and private account records in your authorized systems until an appropriate sharing route is agreed. A consultation does not create the new agreement, approve the business or complete a data migration.

Platform exit dependency map

Complete this from the agreements, current access and written replies for your real platform exit. In the last column record the evidence reference, responsible party and confirmed status or open question. A payment relationship and a data transfer need separate answers; keep private identifiers and credentials out of the sheet.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.