A fee disclosure can answer a narrow question without answering your broader one. A statement about one party’s charge is not, by itself, a statement about every charge associated with an action.

Before treating a terminal’s fee wording as an all-in cost promise, identify four things: who charges, what activity is covered, the stated calculation basis, and when the policy applies. If the document leaves one out, record the gap rather than filling it with an assumption.

A short prerequisite: venue and interface are different scopes

For disclosure reading, distinguish the venue where trading occurs from a third-party interface used to access it. Wording about a venue trading fee does not automatically describe an interface’s separate charges, or vice versa.

This is a scope distinction—not a claim that every interface charges an additional fee. Read each applicable disclosure on its own terms.

Start with a deliberately incomplete example

Fictional disclosure for this guide—not a real vendor policy: “Example Terminal charges an interface fee on completed purchases made through its web interface. This policy is effective September 1, 2026.”

The excerpt names a charging party, describes covered activity and supplies an effective date. It does not state a rate, a calculation basis, or when the charge is collected.

That makes it useful for identifying boundaries, but insufficient for determining an amount.

1. Who is charging?

Look for the party whose fee the statement describes. A page’s branding alone should not substitute for explicit wording about who imposes the charge.

In the fictional excerpt, “Example Terminal charges” attributes the interface fee to Example Terminal. It does not describe the venue’s fee policy or establish that no other party charges anything.

A useful reading note would be:

“This statement describes Example Terminal’s interface fee. Other parties’ charges are outside the excerpt’s stated scope.”

If the text merely says “no fees,” ask whose fees it means. Do not silently expand an unnamed or narrowly named fee category into a universal claim.

2. What activity is covered?

Identify the actions and access method the wording actually includes. Pay attention to qualifiers rather than treating them as fine print.

The fictional excerpt covers “completed purchases” made through the “web interface.” It does not establish the treatment of sales, incomplete activity or another access method. Those are unanswered questions, not confirmed exemptions.

When reading a real disclosure, ask:

  • Which action does this sentence describe?
  • Is a particular interface or access method named?
  • Are any conditions or exclusions stated elsewhere in the policy?

Keep the conclusion as narrow as the evidence. “This sentence covers purchases through this interface” is defensible. “Everything I do through this provider has the same fee treatment” requires more support.

3. What calculation basis is explicitly stated?

A calculation basis specifies what a charge is calculated on. A percentage, if one is disclosed, is not enough without knowing what that percentage applies to.

Our fictional excerpt supplies neither a rate nor a basis. It would be inappropriate to infer either from the words “interface fee.” The correct annotation is:

“Calculation basis not stated in this excerpt; the amount cannot be determined from it.”

If another section provides a formula or definition, read it together with the scope statement. Check that it applies to the same activity and policy version. If no applicable definition is available, ask the provider to identify it.

Do not substitute a familiar calculation from another service. Similar fee labels do not establish identical definitions.

4. When does the policy apply?

Separate an effective date from the date a page was viewed, captured or shared. A screenshot’s capture time does not necessarily tell you when the policy took effect.

The fictional date tells us when the statement says the policy becomes effective. It does not tell us when a charge is assessed or collected, whether a later policy supersedes it, or how any transition is handled.

For a real disclosure, retain the source and applicable version where available. If you are examining a past action, ask which policy applied to that action—not merely what today’s page says.

An undated excerpt should remain undated in your notes. Do not assign it a policy date based on when someone reposted it.

A disclosure is not an implementation test

A vendor’s disclosure is evidence of what the vendor states its policy is. It is not, on its own, independent confirmation of how a particular action was handled.

Keep these conclusions separate:

  • Policy statement: the document says a charge applies under specified conditions.
  • Observed record: a record shows a particular amount or field for a particular action.
  • Unresolved interpretation: more evidence is needed to connect that record to the policy’s definitions.

A difference between an expectation and a record does not alone prove an undisclosed fee or an implementation error. Ask what the record measures and which policy provision explains its treatment before assigning a cause.

A compact disclosure-reading check

Before relying on a fee claim, make sure you can finish these sentences using the document’s own wording:

  • Charging party: “The statement concerns charges imposed by …”
  • Covered activity: “It applies to … through …”
  • Calculation basis: “The charge is calculated on …” or “The basis is not stated.”
  • Applicable timing: “The policy applies from …” or “The applicable date is unresolved.”

Then add one final boundary: “This statement does not establish …” That may include other parties’ charges, activities outside its scope, or implementation for a specific action.

The goal is not to make a disclosure say more. It is to know exactly what it supports—and what you still need to ask.

Source context

The supplied research draws on Polymarket’s trading-fee documentation and a third-party terminal’s fee disclosure. They provide context for distinguishing fee layers; this guide does not reproduce current rates, compare vendors or independently validate implementation. The excerpt above is entirely fictional.

TickBetter is PRE-ALPHA and currently in development, with a focus on execution clarity. No live TickBetter execution functionality is offered by this guide.