Describe the original payment method behind each sales stream
Separate where a sale occurred from how the buyer funded it. A marketplace or platform is an arrangement, not a payment rail: its sales may be card-funded even when your business receives a combined bank payout. Index each stream by the original payment method where documented, the entity and account involved, the available records and their coverage. Describe bank-transfer receipts as bank-transfer history. Preserve genuine platform card history without calling its payout report a direct merchant-account statement. Ask the requesting provider which available records it will consider.
For: An owner of a research-only merchant with marketplace, platform, bank-transfer or mixed sales records who is preparing a processing-history answer.
Start with the real order or transaction record and look for the original payment method. Then identify the platform, seller account or payment account associated with it. Keep those as separate fields. The name of the marketplace tells you where the sale occurred; it may say nothing about whether the buyer paid by card or another method.
A bank credit to your business establishes receipt of money, not the funding method for every underlying sale. If the platform export identifies card payments, describe that documented card-funded activity even if you did not hold a standalone card merchant account. If the export only shows a combined payout and gives no original method, record original rail unavailable. Do not label the whole amount card or non-card to satisfy a form.
Stripe’s Connect overview documents multi-party arrangements in which businesses can collect from their own customers or a marketplace can collect and distribute payments. That supports separating collection from distribution. It does not establish that your platform uses Connect, which payment method a particular buyer used, or which records you are entitled to access.
State what each record covers and what it cannot show
For each stream, identify the legal entity, selling-account label, requested period, actual record dates, currency and record owner. List the file type using its original name: a marketplace settlement report, platform transaction export, issued invoice, bank receipt or processor statement. A record can be authentic and still answer a different question from the one in the application.
Record whether the file shows original payments, refunds, disputed transactions, adjustments or only the final payout. Do not infer a missing field from a net total. An invoice documents the billing record, but an issued invoice alone does not prove that it was paid. Connect it with actual payment evidence before describing it as a receipt. Conversely, a transfer into the bank does not automatically establish customer revenue if its business purpose is unresolved.
Keep originals unchanged and use an index to explain the boundaries. If one report covers several entities or currencies and cannot be separated, disclose that limit. If the original rail or transaction detail is held by the platform, identify the platform as the record owner and request the particular missing field through its support route. For Stripe used through a third-party platform, Stripe’s guidance routes platform users first to the platform and relevant authenticated Dashboard support.
Prevent the same sale from becoming two histories
A customer payment, a platform settlement report and the resulting bank credit may describe different stages of the same activity. Link them by the references and dates available in your private records. Do not add the platform’s sales total to the associated bank deposits and present the sum as additional sales. Likewise, a store order export and a processor statement may cover the same payments.
Choose the record appropriate to each question. A question about original card payments needs evidence of that funding, while a question about amounts received in the bank uses deposit records. A provider’s request for gross volume is not answered merely by renaming a net payout total. Document the unavailable component rather than inventing an adjustment to make the totals agree.
If records cannot be matched fully, describe the scope you can establish and the unmatched portion separately. Missing access to a statement is not proof that no processing occurred. Record whether the activity did not happen, happened but the document is unavailable, or is visible only through a platform’s limited report. These lead to different history answers.
Answer both the history question and the evidence question
Write the history description by stream and period: identify the sales arrangement, the original payment method where known, the relevant entity and the records available. State whether the business held a direct merchant account, used a platform relationship or had only the documented non-card receipts. Use a claim of no card history only when that is supported, not simply because there is no standalone monthly processor statement.
Then address the evidence gap directly. Ask whether the specific marketplace export, platform report or bank-transfer record will be considered for the stated request, and what missing fields or coverage the provider needs. Stripe’s published business-verification description is not a list of substitute records a provider must accept. The provider that requested the history decides whether the offered documents are sufficient.
Prism can help organize this account of the business and the questions for a processing-preparation consultation. Scope, responsibilities, fees and terms are discussed before work; eligibility and account terms remain with the provider. Send a concise description of the website, products, streams and document gap through the public inquiry. Keep transaction files, full bank details and customer records in the authorized document-exchange process rather than the public message.
Sales arrangement and payment-rail history index
Use one copy per stream or repeat the applicable row in your own records. Record arrangement and original rail separately, then name the record owner, covered period, available fields and gaps. Link overlapping records privately so a payout and its underlying sales are not counted twice.
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.
Sales arrangement and payment-rail history index. The last column is for temporary notes.
History stream or check
Records and scope to identify
How to describe the result
Your index entry
Marketplace sales
Records and scope to identifySeller/entity, period, transaction or settlement report, original-method field and report owner.
How to describe the resultMarketplace is the arrangement; report documented card or other funding separately, or mark the original method unavailable.
Platform or aggregated-account activity
Records and scope to identifyPlatform and account relationship, available payment export and who holds missing detail.
How to describe the resultCard-funded platform activity may be relevant card history; an aggregate payout alone does not establish its full composition.
Invoiced bank-transfer receipts
Records and scope to identifyIssued invoices matched to actual transfer evidence, dates and currency.
How to describe the resultName bank-transfer history and distinguish paid receipts from invoices still unpaid.
Other documented non-card receipts
Records and scope to identifyThe actual named payment method, record owner and supporting receipt or ledger reference.
How to describe the resultUse the method’s real name; keep unrelated or unexplained bank credits outside claimed customer sales until established.
Direct card-account history
Records and scope to identifyThe actual account relationship and processor-issued records for the requested entity and dates.
How to describe the resultState the history that exists; lack of a direct account does not erase documented card-funded platform sales.
Coverage and unavailable fields
Records and scope to identifyRequested versus available periods, entity/currency coverage and missing payment, refund or dispute fields.
How to describe the resultName missing access or detail; do not convert unavailable information into zero activity.
Overlap between reports and deposits
Records and scope to identifyPrivate references connecting original payments, platform distribution and bank receipts.
How to describe the resultIdentify records of the same activity and avoid adding them together as separate sales.
Provider’s evidence decision
Records and scope to identifyThe precise history request and written answer about these named records.
How to describe the resultA substitute is acceptable only if the requesting provider says so; retain unanswered requirements as gaps.
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
Platform and marketplace arrangements must not be treated as payment methods. A combined payout may contain payments whose original rails are not shown.
Alternative records are not guaranteed substitutes for card-processing statements, and provider documentation does not establish this merchant’s eligibility.
Do not put card data, customer lists, full bank details, private payment-link tokens, identity documents or credentials in the worksheet or public inquiry.
Stripe Connect — checked 2026-09-29. Stripe Connect describes platforms and marketplaces managing payments among multiple parties, supporting the distinction between customer collection and seller distribution. It does not identify the payment rail of an unseen sale.
Stripe help: getting started through a platform — checked 2026-09-21. For Stripe used through a third-party platform, support is routed through the platform and relevant authenticated Dashboard process, without full card numbers or CVC.
Stripe business information requirements — checked 2026-09-21. Stripe’s verification description is not a list of acceptable substitute processing records; the requesting provider must determine document sufficiency.
Prism solutions — checked 2026-09-21. Prism can help organize an accurate processing description and questions within agreed scope; the provider decides eligibility and terms.
Discuss my processing options
Want to talk through your own processing situation?