Common comparison error
Expiry time shown locally can be wrong by an hour when daylight-saving, venue timezone, or Expiry only observation is unidentified.
GlossaryPricing & settlement
Expiry time
The moment when a binary-option condition is evaluated for final settlement.
Detailed explanation
How Expiry time works in practice
01
Mechanics
Expiry can mean a fixed clock time or the end of a duration measured from acceptance or another entry event. The full timeline includes submission, server acceptance, entry tick, cutoff, observation end, and settlement credit.
02
Worked example
Record each event in UTC and calculate acceptance latency, accepted duration, and settlement lag. Compare a 60-second acceptance-start contract with a fixed 10:01:00 clock expiry; the same button label can produce different timelines.
03
Decision rule
Check timezone, daylight-saving, holiday, weekend, maintenance, rejection, missing tick, and path-dependent early-determination rules. A countdown alone is not a complete expiry specification.
Practical use
How to verify Expiry time
Read Expiry time together with Expiry cutoff, Expiry-only observation, Clock expiry. The comparison must preserve the exact rule, value, state, and evidence described below.
A neutral example
The interface calls Expiry time five minutes, yet order history measures from server acceptance and shows 4:57 exposure. The Expiry cutoff timeline controls comparison. The result is classified under Expiry time because the exact final evaluation moment, quote source, and timezone govern the settled condition.
Evidence path
Where to verify Expiry time
Use the source that governs the exact contract, account, entity, or platform state. A general definition cannot replace current broker terms.