Which old charges remain relevant after closing?
List actual merchant accounts, original charges, pending refunds, disputes, and other cases requiring review. Identify the seller or other party tied to each account. The buyer's new payment setup may not provide the same access or rights.
Use the buying hub to connect those facts to the deal. A plan to bill new jobs is different from the plan for old transactions. The buyer needs both paths assessed before the seller account is treated as no longer needed.
A legacy payment case register links each relevant old charge to its account, job evidence, case status, permitted action, funding responsibility, and next requirement. It helps the parties review the actual handoff without assuming one merchant migration completes every task.
What do the refund instructions establish?
Stripe's refund guidance describes refunds associated with charges, supported processing methods, and status differences. It states that refunds return to the original payment method, with relevant failure and issuer handling conditions. The actual case and method matter.
Confirm the supported action with the relevant provider and account parties. A buyer should not infer that its new account can act on every seller charge. Another provider can have different processes and terms.
Keep customer communications aligned with the actual status. A requested refund, pending refund, and completed result can differ. Do not promise completion simply because someone entered a request or the sale agreement assigns the commercial responsibility.
Why should dispute cases be mapped separately?
Stripe's dispute guidance describes cardholder challenges, charge reversals, balance effects, and evidence responses. The provider's process depends on the actual case. A dispute is not just another note in the customer service queue.
Identify the person with accepted access and authority to respond. Record the real requirements and relevant dates from the case and provider. This guide does not impose a universal deadline or promise a successful response.
The diligence guide helps place these duties in the closing plan. Pending cases should have owners and supported next actions. A generic allocation of old liabilities may not explain who can perform the required provider task.
How are technical access and legal responsibility different?
The merchant terms, sale documents, charge facts, and actual provider process need review. One party may bear a commercial cost while another account holds the supported action path. Those roles should be clear rather than assumed from one login.
Ask counsel and the provider to assess the actual arrangement. The parties need accepted access, authority, cooperation, and funding terms. A technical role does not settle every legal duty, and a contractual duty does not create a provider feature.
Record any transition access and its limits. Do not assume the seller account should close immediately or remain accessible forever. The actual accepted plan should explain the needed tasks, permitted users, and completion evidence.
Does payment-data migration move old histories?
Stripe's migration overview describes supported transfer of payment data and mapping between records. That process does not establish universal movement of old-charge histories or action rights. Confirm the actual provider scope.
Separate customer IDs and credentials from job files, original charge evidence, case records, and communications. The buyer may need several retrieval paths. A successful import screen does not prove that all those records are available.
Test the relevant access through the approved plan. Use safe references and controlled evidence without exposing raw card data in the deal room. The team needs to know what is available and which histories or permissions remain unresolved.
Which job evidence should be preserved?
Identify the actual records relevant to a case. Authorization, accepted scope, approved changes, completion evidence, invoices, and communications may support different questions. Do not collect unrelated customer information merely because it is available.
Record where the evidence is held and who can retrieve it under the accepted terms. A seller agency, dispatch system, or personal mailbox can create a dependency. The buyer needs a supported path before those sources become unavailable.
Keep the provider's actual evidence requirements visible. Having a document does not prove it addresses the dispute reason. The responsible reviewer should decide how the accepted evidence supports the permitted response, without promising a favorable outcome.
How should pending amounts connect to the financial file?
Reconcile case amounts to actual charge records and their current status. Separate principal, fees, refunds already completed, disputes already resolved, and other relevant effects. A headline total can include different stages or overlapping cases.
Use the P&L reading guide when comparing those records to statements. A cash movement, revenue entry, reserve assumption, and legal obligation are different measures. Explain the actual basis before adjusting the underwriting model.
Keep expected outcomes distinct from known amounts. The buyer should see which figures are verified and which remain assumptions. No standard percentage or automatic price adjustment follows from finding a pending case.
Which sequence supports the handoff?
Define the review while the account holders and providers are available. The buyer and seller should see how pending tasks will be completed under the accepted terms. A responsibility clause should connect to a practical action path.
- Identify old accounts, original charges, case statuses, and amounts.
- Confirm actual provider access, action scope, and case requirements.
- Review sale and merchant terms for authority, cooperation, and funding.
- Preserve relevant job evidence and reconcile overlapping amounts.
- Assign accepted actions, owners, and completion records for each case.
Use permitted test methods without issuing real refunds or changing customer cases. This guide does not authorize a financial action. Actual refunds and responses require their own accepted operating process.
How can overlap change a planning total?
The following illustration assumes $500 of pending refund principal and $800 of disputed principal. It assumes $200 refers to the same underlying charge in both sets. These invented figures show an overlap check; they are not target losses, reserve advice, or final liability.
| Illustrative set | Assumed amount | Meaning |
|---|---|---|
| Pending refund principal | $500 | Relevant case status still needs review |
| Disputed principal | $800 | Relevant response and balance effects still need review |
| Shared charge principal | $200 | Included in both sets under the assumptions |
| Distinct principal count | $1,100 | Arithmetic count only, before actual outcomes and other effects |
The calculation is $500 plus $800 minus $200, or $1,100. It prevents counting that assumed shared principal twice. It does not determine expected loss or required funding. Actual provider handling, fees, decisions, terms, and case status still matter.
Who handles a customer question during the transition?
Give staff the approved contact, process, and relevant status source. A customer may ask the buyer about an old seller charge. Staff should know how to route the question without inventing a refund power or promising a date.
Record the actual request and its link to the case. Check whether a refund and dispute overlap before proceeding through the authorized path. Stripe's method-specific guidance includes circumstances where duplicate credits can be a concern; apply the real process to the facts.
Keep the customer record private and the responsible parties informed through accepted channels. A transition should not let a case disappear between seller and buyer teams simply because the new system has no matching status field.
What belongs in the final acceptance record?
Keep the old-account map, case register, provider responses, relevant sale and merchant terms, access tests, evidence paths, reconciled amounts, and responsible contacts together. Identify unresolved items and the accepted follow-up plan.
The purchase guide connects that file to closing readiness. A useful record shows what the parties can do under the actual facts and who must act. It cannot promise universal refund rights, complete migrated history, recovered funds, or favorable dispute decisions.