The refunds and disputes you still own after leaving the platform
Document support responsibilities, payment timelines and customer records before cancelling the old account.

You cancel your old storefront on Monday. On Tuesday, a customer asks for a refund for a file they bought last month. On Wednesday, a cardholder disputes a payment, and the payment processor asks for evidence you can no longer find. Leaving a platform removes a tool from your workflow. It does not automatically remove the promises you made to customers, or the payment issues attached to earlier transactions.
Make a case list before you switch anything off
Start with a simple export or spreadsheet. Give each unresolved matter one row and one owner, even if that owner is you. Search your support inbox, payment dashboard and order history for refund requests, delivery failures, duplicate purchases, subscription cancellations, complaints and disputes. Do not rely on memory or on a platform's dashboard remaining available after cancellation.
| Record | What to capture | Next action |
|---|---|---|
| Refund request | Order reference, product, amount, request date and reason | Approve, decline or ask a clarifying question |
| Dispute | Payment reference, dispute status, response date and evidence required | Submit evidence through the processor before its deadline |
| Failed delivery | Customer address, product version and delivery method | Send a working replacement or explain the remedy |
| Support promise | The exact promise, message or policy involved | Record what you will do and by when |
Save the source material as well as the summary: order confirmations, invoices, product descriptions, refund terms, delivery logs and relevant messages. If a customer bought a course, membership or coaching session, note their access status and any unused part of the service. A row saying “refund pending” is not enough evidence to reconstruct the case later.
Separate the platform from the payment
There are usually at least three moving parts: the storefront that displayed the offer, the payment processor that handled the card transaction and your own records of the customer relationship. A platform cancellation may stop new checkouts or remove your admin view. It may not cancel a processor account, reverse a settled payment or answer a card dispute on your behalf.
Check the payment status for every open case. A payment can be pending, completed, refunded, failed or disputed, and the correct action differs in each state. Do not promise that money will arrive or return on a particular date unless the processor confirms that date. For disputes, identify the response deadline shown in the processor's notice; missing it can leave you unable to present your evidence.
Write the evidence a stranger could follow
A dispute reviewer is not inside your business. Build a short evidence pack that explains the transaction in order: the offer the customer saw, the checkout record, the payment reference, what access or file was delivered, and the support exchanged afterwards. For a digital download, this might include the delivery event and the file name. For a course or membership, include the access terms and relevant activity records. For coaching, include the booking and cancellation terms.
- 1Match the payment to the customer, order and product without exposing unrelated customers' information.
- 2Show the terms that applied at the time of purchase, rather than a policy edited after the complaint.
- 3Explain the remedy you offered, such as a replacement, cancellation or refund, and record whether it was completed.
- 4Submit only the evidence requested through the payment processor's dispute process.
Keep the language factual. “Customer is dishonest” is not evidence. “The download link was issued at 14:10, and the customer reported an access problem at 14:35” gives a reviewer something they can assess. Redact information that is not needed, and store the pack somewhere you can access without the old platform.
Give customers a clear route after the move
Before closing the old account, update the places customers actually use: your receipt footer, help page, email signature, product documentation and profile links. State where existing customers should ask for help, what information to include and how you handle refund requests. Keep the wording consistent so a customer does not have to guess whether the old or new address is active.
Your new storefront should make the same promise easy to keep. With store.fan's customer CRM, you can keep customer information connected to the storefront rather than treating support as a collection of scattered messages. If you sell downloads, courses or memberships, check that the new product grants the right access and that your support instructions point to the correct place.
Choose a storefront that keeps the handover manageable
The move is not complete when the new checkout works. Test a purchase, refund route, confirmation email, access link and support reply before directing customers there. You are checking the whole path from payment to remedy, not just the sales page.
store.fan can be the new home for that path: a storefront lives at store.fan/username, money goes straight to your own Stripe and store.fan takes 0% of sales, while Stripe's own processing fee still applies. Paid plans start with a 14-day trial. The free plan is link-in-bio only, so it will not provide the same selling setup as a paid storefront. Pro adds tools such as email marketing, discount codes, hosted course video and creator-run affiliate programmes.
If sale alerts matter while you are dealing with a migration, store.fan also has an iOS app with instant sale alerts. That does not replace a case log or a written refund process, but it can help you notice new orders that create new support responsibilities. Review the available payments features and test your own workflow before cancelling the old account.
Close the old account in stages
Use a short cooling-off sequence rather than one irreversible click. First export permitted order, customer and product records. Next resolve or document every open case. Then publish the new support route and test it from a customer's point of view. Only after that should you stop new sales on the old platform and confirm what access, reporting and payment support remain available.
- Keep a copy of your final product files, terms, policies and order references.
- Record the old platform's cancellation date and any stated access or data-export deadline.
- Reconcile open refunds and disputes with your Stripe records, not just the old storefront total.
- Remove obsolete links only after the replacement route has been tested.
- Set a calendar review for unresolved cases and any payment activity still marked pending or disputed.
Possibly, but do not assume the platform will finish it for you. Record the case, confirm whether the refund must be issued in the payment processor, save the customer conversation and check what access you retain after cancellation.
There is no single safe period for every creator. Tax, consumer, contract and privacy rules can differ by location and product. Define a retention rule that fits your obligations, restrict access and delete records when you no longer have a valid reason to keep them.
Do not treat a new storefront as an automatic migration. Export only records you are allowed to use, obtain any consent required for marketing and tell customers where their existing support route has moved. Your evidence for old transactions may still need to remain with your payment records.
Set up the next storefront with your customer support and payment handover in view.
Try store.fanTurn your knowledge into income
Launch your Store.Fan in minutes — sell digital products, courses, and calls straight from your bio. Free to start.



