Yes, if the records connect the fee to a defined billable event and the actual attempt. Start with the applicable pricing term, then trace the itemized charge to its payment or activity reference and recorded outcome. A failed payment label alone establishes neither that a fee is due nor that the attempt must be free. Preserve an unmatched line as a specific question about the event, reference or calculation that is missing.
For: A research-only merchant comparing billed payment activity with attempts that did not complete successfully.
Read the fee description and the applicable pricing document before counting failed orders. Identify the event the term charges for, the unit it counts, the effective period and any stated conditions. Do not substitute 'successful sale' for the event actually written, or assume every attempted request is billable. If the document never defines the event behind the charge, that missing definition is the first question.
Stripe's general terms allow written fee agreements to differ from public pricing, and its regional terms depend on the account country. For a Stripe account, use the agreement and pricing that apply to that account and activity. For another provider, use that provider's documents. A public price from a different country, payment method or service does not settle your fee line. This comparison identifies a documentary match; it does not decide contractual enforceability.
Trace the fee without collapsing several attempts into one order
Stripe's Fees report uses incurred_by to identify the transaction associated with fee activity, and one transaction can have multiple fee rows. Retain all related rows with their fee_description, product or feature, amount, tax and currency. Several rows are not automatically several attempts, and a shared order reference is not enough to identify which attempt incurred the activity.
Follow the reference as far as the provider records permit. If it resolves to a payment with several recorded attempts, compare the individual attempt times and outcomes with the event named by the fee. If the export does not identify the attempt precisely, record that limitation and ask for the mapping. Do not distribute a total across failures simply because dividing it produces a convenient per-attempt amount.
Keep the account, currency and date basis consistent. Stripe distinguishes when a fee was incurred from when it affected the balance. Its report covers most balance-paid fees, excludes some categories including after-use invoiced fees, and data may take up to 96 hours after the balance effect to appear. An absent row may require the relevant invoice or a later report; it does not establish zero cost.
Use the recorded failure to test the event match
Stripe distinguishes issuer declines, blocked payments and invalid API calls. A blocked payment does not obtain issuer authorization, and invalid API calls typically do not appear as payments in the Dashboard. Those differences help identify what happened to a request; they are not a fee schedule. The declines documentation does not establish the charge for each outcome.
Use the payment details available in the Dashboard or API, and existing non-sensitive request records when no payment entry exists. Record the actual outcome beside the agreement's event. If the fee term requires an event the available record does not show, mark the link unproven. If the evidence shows the specified event despite an unsuccessful final payment, compare the fee calculation using the term's real inputs. Do not retry a payment or change a blocking rule to investigate a historical fee.
Close only the lines the evidence explains
A supported match needs the applicable term, the activity reference, the event and the calculation. A status mismatch, missing reference or unreproducible amount stays open. Ask the provider to identify the billable event, show how it connects to the named attempt and explain the rate or count used. Keep its reply with the original line so an explanation and any later fee credit remain separate records.
For a Prism processing consultation, summarize which part of that chain is unresolved and the scope of help requested. Confirm any statement-analysis or provider-follow-up work, responsibilities, fees and terms before work begins. The provider determines its account terms and any correction; a consultation does not promise a credit or establish research-only merchant eligibility.
Attempt-related fee trace
Use one copy for each questioned fee line and retain any companion rows. Enter references and non-sensitive findings from real records. Classify the result as matched, missing event evidence, missing reference or unexplained calculation; a blank is not a zero-fee finding.
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.
Attempt-related fee trace. The last column is for temporary notes.
Trace element
Record to compare
What must be established
Your finding
Fee agreement event
Record to compareApplicable written fee term, account country, service, payment method and effective date.
What must be establishedThe exact event and unit the agreement prices, including any stated conditions.
Fee row
Record to compareItemized row with description, product or feature, amount, tax, currency and associated rows.
What must be establishedWhich fee component is in question; do not treat multiple rows as a count of attempts.
Payment reference
Record to compareProvider activity reference; for Stripe, incurred_by and the linked payment details.
What must be establishedA trace to the actual activity, or the precise point where the attempt mapping is absent.
Actual payment status
Record to compareOutcome and time of the relevant attempt, with later attempts kept separate.
What must be establishedWhether the documented billable event is supported, regardless of the final order label.
Count and calculation
Record to compareTerm's rate or formula and the provider's documented quantity for the same period.
What must be establishedWhether the line can be reproduced without inventing a rate or deriving an assumed count.
Report coverage
Record to compareAccount, currency, export date basis and any separate invoice.
What must be establishedWhether missing data could reflect timing or report scope rather than an absent charge.
Provider explanation
Record to compareReply identifying the event, linked activity and applicable term for the named line.
What must be establishedWhich uncertainty the reply resolves and whether a separate correction remains outstanding.
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
Stripe's failure categories and report fields do not establish a universal failed-attempt fee or a fee rule for another provider.
This worksheet does not determine legal enforceability, authorize payment retries or guarantee fee recovery.
Keep card numbers, authentication codes, API secrets, full bank details and private payment links out of worksheets and the public consultation form.
Stripe Fees report — checked 2026-09-29. incurred_by supports transaction reconciliation and a transaction can have multiple fee rows. Amount, tax, currency and product or feature are distinct fields. Date bases differ; data may take up to 96 hours and after-use invoiced fees are excluded. These fields do not establish the fee price.
Stripe declines — checked 2026-09-21. Issuer declines, blocked payments and invalid API calls are distinct failures. A block does not obtain issuer authorization; invalid calls typically do not appear in the Dashboard. Payment details are available through the Dashboard or API.
Stripe Services Agreement general terms — checked 2026-09-29. Written fee agreements can differ from public pricing. Regional terms depend on account country; the actual merchant agreement must be read. This does not establish a particular attempt fee or legal conclusion.
Prism solutions — checked 2026-09-21. Processing preparation and storefront review are published support types. Scope, fees and terms are confirmed before work; the provider decides account terms.
Discuss my processing options
Want to talk through your own processing situation?