A network or partner fee has no obvious matching line in the quote
Keep the statement label intact, identify the party it names and ask how that item maps to the applicable written fee terms. “Network” or “partner” identifies an attributed source of a charge; the label alone does not establish that the amount is mandatory, passed through unchanged or agreed at that rate. Match the period, currency, event or amount base and calculation. If that chain is incomplete, send the contracted provider a precise question about the missing link rather than assuming either a valid charge or an improper one.
For: A research-only merchant reviewing a statement charge attributed to a network or partner that has no obvious match in the written processing quote.
A charge can appear on a provider statement while its description attributes it to a network or external partner. Stripe’s Fees report can include fees from Stripe, networks and partners. That explains why more than one party’s fee can appear in the same reporting surface; it does not determine which agreement authorizes a particular merchant charge.
Copy the exact line label and the reporting company, then separately record any named charging party. If the label is only a category and does not identify an entity, record that limitation. Do not turn a category into a guessed company, and do not infer that the named party has a direct contract with the merchant.
Treat “pass-through” as wording that needs a definition in the offer or agreement. Ask whether the documented amount is the external fee alone, includes another component, or is presented as a combined amount. Neither a familiar network name nor a salesperson’s description establishes the calculation or confirms that there is no markup.
Find the written pricing authority for that period
Compare the quote with the fee schedule and other applicable written pricing documents for the actual account. Stripe’s general terms recognize written fee agreements that can differ from public pricing; the applicable agreement also includes service and incorporated terms, with regional terms depending on account country. A public price page is therefore not sufficient to establish a merchant’s agreed rate.
Locate the clause that the provider says covers this fee and the version or effective date relevant to the billed activity. A fee need not use the exact wording of the statement label to have a documented basis, but the correspondence needs an explanation. Retain both labels and the written mapping rather than renaming the statement line to make it fit.
If the provider cites a separate schedule or external rule, request the precise reference and an explanation of how it applies through the merchant’s agreement. That is an evidence request, not a conclusion about enforceability. A missing line in a short quote is a reason to locate the applicable documents; it does not prove that the fee is either prohibited or unavoidable.
Trace the amount without counting the same event twice
Record the charge amount, currency, activity period and the stated calculation base. For an event-based term, match the quantity to the defined event. For a percentage term, identify the amount base the provider used. Keep tax and any separate adjustment visible rather than treating them as part of an unexplained rate. If the statement does not expose the necessary inputs, the calculation remains unverified.
Stripe’s Fees report separates amount, tax and currency and provides product and feature fields. The incurred_by field can connect fees with the underlying transaction, but multiple fee rows can relate to that same transaction. Several rows therefore do not automatically mean several customer payments or duplicate billing. Preserve the distinct components and ask which clause covers each one.
Use the documented product, feature and fee_description fields where available, rather than relying on deprecated fee_category or balance_transaction_description fields. Match the incurred-at or balance-transaction date basis to the question being asked. The report covers most balance-paid fees, has exclusions including after-use invoiced fees, and data may take up to 96 hours after balance effect to appear. A row missing from that report does not prove a separately invoiced fee is invalid.
Ask for the missing link, then record the answer
A useful provider question names the statement and line, the attributed party, the pricing document already checked and the exact gap. Request the clause or schedule reference, its applicable date, the calculation inputs and any distinction between the external fee and another component. If the provider says a rule makes the fee mandatory, ask which rule and which provision makes it applicable to this account and activity. The provider’s explanation should address the claim it actually made.
Classify the result after the response. If the written mapping and calculation reconcile, record the match and preserve the explanation. If a document is supplied but the amount still cannot be reproduced, keep the calculation question open. If the provider confirms a correction, track the actual adjustment separately; a promised credit is not evidence that it has posted. Resolving the arithmetic does not itself settle a legal disagreement about a term.
For a Prism processing consultation, summarize the unexplained fee category and which part of the document-to-charge comparison is missing. Confirm any requested fee-review assistance, scope, responsibilities, fees and terms before work. The contracted provider explains its billing and account terms; a consultation does not guarantee a credit, decide enforceability or establish provider eligibility for the research-only business.
Pass-through charge trace
Use one actual charge. Enter document references and non-sensitive findings in the final column. A label match alone is incomplete: trace the attributed party, applicable authority and reproducible calculation separately, and keep an unanswered link open.
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.
Pass-through charge trace. The last column is for temporary notes.
Trace element
Evidence needed
Interpretation boundary
Your finding
Statement fee label
Evidence neededExact wording, statement reference and billed period.
Interpretation boundaryPreserve the original label; do not rename it to force a match with the quote.
Named charging party
Evidence neededEntity actually identified on the fee record or in the provider’s explanation.
Interpretation boundaryA network or partner category may not name an entity or establish a direct merchant contract.
Agreement authority
Evidence neededFee schedule, applicable clause, version and account-country context.
Interpretation boundaryWritten pricing may differ from public rates; ask how the statement label maps to the term.
Pass-through definition
Evidence neededWritten explanation of what the quoted pass-through amount includes.
Interpretation boundaryDo not assume unchanged external cost, no markup or universal applicability from the label.
Calculation basis
Evidence neededDefined event or amount base, quantity, rate, currency and period.
Interpretation boundaryKeep any missing input unknown; store orders and fee rows are not automatic event counts.
Fee-component trace
Evidence neededRelevant product, feature, fee description and underlying event reference where available.
Interpretation boundaryMultiple Stripe rows may relate to one incurred_by object; this alone does not establish duplication.
Tax and adjustment separation
Evidence neededSeparately identified tax or adjustment amounts and their references.
Interpretation boundaryDo not fold them into an inferred rate or draw a tax-liability conclusion from the fee export.
Provider clarification
Evidence neededWritten mapping, rule reference if asserted, calculation explanation and response date.
Interpretation boundaryMark each link explained or still open; an assertion of mandatory status needs its stated basis.
Correction outcome
Evidence neededProvider confirmation and the actual later credit or adjustment record, if any.
Interpretation boundaryA promised adjustment and a posted adjustment are different facts; no refund outcome is assumed.
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
A fee label does not establish legal enforceability, mandatory status, negotiated pricing or the absence of markup. An unmatched charge is an unresolved question, not proof of wrongdoing.
Stripe reporting and agreement details apply to Stripe and the applicable account terms. Use another provider’s own records and definitions for its charges.
Leave full statements, account numbers, customer data, bank details and payment credentials out of public consultation messages. Keep original evidence in authorized systems.
Stripe Fees report — checked 2026-09-29. Stripe fee reporting can include Stripe, network and partner fees. Current product, feature, fee description, amount, tax, currency and incurred_by fields support component tracing, with multiple rows possible for one transaction. Report exclusions and timing limit what absence establishes.
Stripe Services Agreement general terms — checked 2026-09-29. Written fee agreements can differ from Stripe’s public pricing. General, service, incorporated and account-country terms must be considered for the actual merchant; the terms do not establish the authority or calculation of an unseen charge.
Discuss my processing options
Want to talk through your own processing situation?