Average ticket and largest ticket tell different stories

Translate the request into a measurable unit

Copy the provider's field labels and instructions before calculating anything. Typical is ambiguous unless the request defines it: an arithmetic mean, a median and a usual order range are different summaries. Maximum may mean the largest historical payment or the limit sought for future payments. If the wording does not distinguish these, record both questions for clarification and label any historical figures you can already substantiate.

Specify whether the unit is a completed payment, a capture, a store order or an invoice. One order can have several payment records; counting orders while summing payments may answer neither question accurately. Likewise, an authorization that never became a completed payment should not silently enter a completed-payment population. Keep the inclusion rule explicit and use the unit the provider actually requested.

Build one consistent historical population

Keep an unchanged source export and a separate working calculation. Record the entity, account, channel, payment method, date boundaries, time zone and date field used. Identify which rows are payments and which are fees, refunds, transfers, disputes or other movements. A balance activity export is not automatically a list of customer sale amounts simply because each row carries a monetary value.

For Stripe history, the balance summary report covers a selected period in settlement currency and can export itemized transactions. Its gross, fee and net components serve different purposes. Use the documented payment amount basis requested by the provider; a net amount after fees or a bank payout cannot be substituted for a payment ticket. Stripe states that this report does not associate payouts with payment transactions.

Keep currencies separate unless the provider has specified a conversion basis. A settlement-currency history and an original transaction-currency history can describe the same activity with different amounts. Label which you used. Do not combine currencies, accounts or methods merely to produce one convenient number. If the requested population spans several accounts, keep an account-level trail and remove duplicate copies of records without removing separate genuine payments.

Calculate both measures and retain the unusual payment

Once the included set is fixed, calculate the arithmetic mean as its total payment amount divided by its payment count. Read the maximum from the largest included payment amount. Both results must carry the same population label, period and currency. Where there are no included payments, the average and largest payment are unavailable; neither should be reported as a historical zero-sized payment.

Check the largest payment against its original provider record and associated order. A genuine unusual order belongs in the history when it meets the inclusion rule. Explain its actual channel, products, payment structure and dated fulfillment records only to the extent those facts are documented. Do not describe an order as recurring, exceptional or unlikely to recur merely because that makes the application easier to present.

If a median or a separate ordinary-order subset would help explain the pattern, label it as supplemental and state its rule. It must not replace the requested all-included-payments average or maximum. Refund treatment also needs a stated basis: retain a completed payment's original amount when reporting original completed payments, and show subsequent refunds separately unless the provider requested a different net measure. Do not quietly shrink the historical maximum by subtracting a later refund.

Submit a traceable answer, not a disguised limit request

Keep the worksheet, calculation and controlled references together so another authorized person can reproduce the figures from the same export. Resolve discrepancies in the count or largest record before copying values into the application. If the form permits only a number, use the provider's approved channel to supply the period, currency and definition rather than changing the number to fit an unstated assumption.

Stripe's restricted-businesses policy prohibits misleading information about the nature of the business and processing for undisclosed products; its approvals are service-specific and can change. Accurate historical figures support an honest description, but they do not establish approval or permission for a future large payment. Other providers' requests and account terms must be read on their own terms.

For a Prism processing consultation, summarize the requested fields, the history available and any definition still unresolved. Scope can address organizing an accurate business description and provider questions. Keep statements and individual payment or customer records out of the public form, and confirm any later document-sharing process within the agreed scope.

Ticket-size evidence comparison

Complete this from the provider's actual request and an unchanged historical export. Use the same defined set for the average and historical maximum. Record references to private evidence rather than customer details; mark unclear definitions before presenting a final figure.

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.