What to export before losing provider dashboard access
Preserve the records needed to explain balance movements, connect payouts to their transactions, continue open cases and support existing accounting records. Capture each file’s account label, report period, currency, filters and export date. Open the files before access ends and list anything missing. Store authorized originals securely for your actual retention needs; make separate minimized copies for a specific recipient. Do not strip required fields from the only original. A financial-report export is not a transfer of saved cards or payment credentials.
For: An authorized owner of a research-only business who can still access the payment-provider dashboard and needs usable records after that access ends.
Begin with the real access deadline, if one has been stated, and the person who can currently open the account. Export existing records while that access works. If the latest reporting period is incomplete, preserve what is available and identify the missing interval rather than waiting for a perfect archive that may arrive after access ends.
Stripe’s owner-close guidance says to export records first and that a closed account cannot be reopened. Its scheduled-payout article says closure does not stop payouts already scheduled, but later payout information may be unavailable and a failed payout can be hard to retry after Dashboard access is revoked. These articles describe Stripe’s owner-close situation. A forced restriction or another provider’s account needs its own access instructions.
Create a small index of files with a non-sensitive account label, report type, selected dates, currency, filters, time basis where shown and the actual export date. Keep separate currencies and accounts distinguishable. A filename saying final is not evidence that the file includes activity posted after it was downloaded.
Keep balance activity and payout matching as separate records
For Stripe, export the balance summary for the required period and the itemized transactions you are authorized to retain. The balance report describes the balance over a selected period in settlement currency and separates gross, fee and net activity. It does not associate each payout with the payments that funded it. Saving only this report leaves a payout-matching question open.
The Stripe payout reconciliation report matches automatic payouts to transaction batches. A batch can contain earlier transactions, so a payout inside your selected period need not consist only of sales made in that period. Preserve the report’s references and stated dates instead of forcing the batch into the store’s sales-day total. Stripe’s expected bank-arrival date is an expectation; use an actual bank record separately if you need to establish receipt.
For instant payouts, Stripe says the business performs the reconciliation because Stripe cannot identify their component transactions. Mark that reconciliation as separate work. The report is not evidence that every payout type is automatically matched. Its daily data is normally available by noon the following day, with exceptions, so an export taken before the needed data appears can have a genuine coverage gap.
Preserve cases and documents that totals cannot explain
For open disputes, preserve the case reference, current status, provider-stated response deadline, correspondence and record of what was already submitted, using the authorized access available. Keep relevant historical outcomes as well. A balance entry records a financial movement; it does not replace the correspondence or evidence needed to understand the case. Do not assume your provider offers a single bulk export containing all of it.
Save available statements and invoices in their issued form, with their period, issuer and document reference. Index them separately from a transaction CSV so a later reader can identify which document states a charge and which file shows its balance movement. If a document is absent or cannot be downloaded, record that precise gap and the official route for requesting it. Do not generate a replacement and call it the provider’s statement.
A catalog snapshot can explain which products the business listed, but it is a separate store-side record. WooCommerce’s built-in CSV exporter exports product data with choices for columns, types, categories and optional custom metadata. That file does not preserve orders or payment credentials. Include it only when the catalog is relevant to the archive’s purpose; it cannot fill a missing provider payment record.
Preserve the original and minimize the copy you share
An authorized original and a consultation copy serve different purposes. Preserve necessary originals in controlled storage with access limited to the people responsible for the records. For each intended recipient, identify the question they need to answer, then create a separate copy containing only the relevant period, fields and cases. Keep an internal note of the source and what was removed so the reduced copy is not mistaken for a complete export.
Check both visible fields and free-text or metadata columns. Remove unnecessary customer names, email addresses, street addresses and unrelated order notes from the sharing copy. Preserve the references needed for the authorized recipient to follow the specific issue. Never put card numbers, authentication codes, passwords, API secrets, private payment-link tokens, full bank details or identity documents into this worksheet or the public consultation form.
PCI SSC FAQ 1085 states that unprotected primary account numbers must not be sent through email, instant messaging, SMS or chat. That rule concerns card numbers; it is not a blanket prohibition on ordinary email. Avoid treating an ordinary report export as a way to migrate payment credentials. If sensitive payment data appears unexpectedly, keep it out of ordinary sharing and use the responsible provider’s secure process to resolve the handling question.
Verify retrieval before calling the export complete
Open each saved file from its storage location, check that it is readable, and compare its account, date range and currency with the index. Confirm whether open cases and scheduled payouts are represented and whether a later export is needed for new activity. Give the record owner a list of missing files or periods. A downloaded file that nobody can open does not preserve usable access.
This checklist does not set a retention period or authorize deletion. Preserve records according to the business’s actual retention needs and obligations, with appropriate advice where those are unresolved. For a scoped Prism processing consultation, describe the access issue and the missing record in ordinary language. Confirm any requested archive assistance and authorized access separately. Send no exports or customer lists through the public form; a consultation request is not a processing application.
Access-window export checklist
For each record you actually need, note the file reference, covered period, export date, responsible owner and any gap. Also record what a separate sharing copy removes. Do not paste financial records or personal data here, and do not alter the only original to make a minimized copy.
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.
Access-window export checklist. The last column is for temporary notes.
Record to preserve
What it can establish and what it cannot
Minimization and coverage check
Your file, owner and gap
Transaction and balance history
What it can establish and what it cannotStripe’s balance summary and itemized activity describe a selected period in settlement currency; they do not match payouts to payments.
Minimization and coverage checkKeep necessary amounts, currencies, dates and references. Omit unrelated customer fields from a sharing copy; record all selected filters.
Payout history and reconciliation
What it can establish and what it cannotFor Stripe automatic payouts, preserve batch-to-transaction matching, including earlier activity. Instant payouts require the business’s own reconciliation.
Minimization and coverage checkRemove full destination bank details from a sharing copy. Preserve the payout reference, currency and dates needed to follow the question.
Open dispute cases
What it can establish and what it cannotCase status, actual response deadline, correspondence and submission record establish the work visible when copied.
Minimization and coverage checkLimit shared case material to the authorized question. Keep unrelated customer details and identity material out of the worksheet.
Historical dispute outcomes
What it can establish and what it cannotSaved outcome records preserve the provider’s reported disposition; a balance movement alone does not preserve the whole case.
Minimization and coverage checkSelect only relevant cases for a recipient. Retain authorized originals separately from any reduced history.
Statements and invoices
What it can establish and what it cannotIssued documents identify their periods and charges; a transaction export is a separate record.
Minimization and coverage checkKeep original issued files securely. Redact unnecessary account or address details only on the recipient copy. Record unavailable documents.
Separate store-side catalog snapshot
What it can establish and what it cannotA WooCommerce product CSV describes products and selected metadata, not orders, payouts or saved-card data.
Minimization and coverage checkInclude only if relevant. Inspect optional metadata before sharing; do not mistake this file for provider history.
Export index and incomplete interval
What it can establish and what it cannotThe file index records what was saved and when; later activity can remain outside its coverage.
Minimization and coverage checkUse non-sensitive account labels. List unreadable files, missing periods and the owner of any follow-up export.
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.
Limits
Preserve authorized originals under actual retention needs. This guide supplies no retention period and does not authorize destruction of required records.
Stripe’s reporting and owner-closure guidance apply to Stripe; availability and export options at other providers must be established from their own records.
Ordinary reports and product CSVs do not migrate payment credentials. Keep payment data, secrets, identity documents and customer lists out of the public consultation form.
Stripe: Closing with scheduled payouts pending — checked 2026-09-21. Stripe says scheduled payouts continue after closure, later payout information may be unavailable, a failed payout can be hard to retry after Dashboard access is revoked, and reports should be exported first.
Stripe: Close a Stripe account — checked 2026-09-21. Stripe’s owner-close guidance says to export records before closure; a closed account cannot be reopened and post-closure access and actions are limited.
Stripe balance summary report — checked 2026-09-21. The balance report covers a selected period in settlement currency, separates gross, fee and net activity and exports itemized transactions; it does not associate payouts with payments.
Stripe payout reconciliation report — checked 2026-09-21. Payout reconciliation matches automatic payouts to batches that can include earlier transactions; instant payouts are reconciled by the business. Arrival dates are expected dates, and daily data is normally available by noon the next day with exceptions.
WooCommerce product CSV exporter — checked 2026-09-21. WooCommerce’s CSV exporter exports product data, selected columns and optional custom metadata; it is not an order or payment-credential export.
PCI SSC FAQ 1085 — checked 2026-09-21. PCI SSC FAQ 1085 prohibits sending unprotected primary account numbers by email, instant messaging, SMS or chat; this is a card-number rule, not a general email ban.
Prism solutions — checked 2026-09-21. Prism’s processing preparation and website support are subject to agreed scope, fees and terms; provider account decisions remain with the provider.
Prism contact — checked 2026-09-21. The public form excludes payment card details, passwords and customer records; a request does not submit a processing application.
Discuss my processing options
Want to talk through your own processing situation?