EXTANCY LEAGUEFootball opportunity ecosystem

Match Center

Every match is a verified event, not a reported claim

The Match Engine is how football actually happens on Extancy League. A fixture is proposed, accepted, officiated, reported and confirmed — and only then does it count. That sequence is deliberate: it is what makes a league table, a qualification position and a scouting record mean something.

This page explains the whole flow — match requests, quick matches, referee assignment, match reporting and result verification — and how a verified match connects to teams, standings, tournaments, scouting and integrity.

How a fixture works

The five stages every match passes through

Step 1

A match request is raised

One team proposes a fixture against another team. A request records the requesting team, the receiving team, the proposed date and the competition context, and it stays pending until the receiving team accepts or declines it.

Step 2

The receiving team accepts

Acceptance turns a request into a scheduled fixture with a kickoff time. Declining or cancelling closes the request without creating a match, so a fixture only exists once both sides have agreed.

Step 3

Match officials are assigned

Referees and assistant referees are assigned to the fixture. Their role is to observe and confirm what happened on the pitch, which is what makes the outcome worth more than an unverified claim.

Step 4

The match is reported

A match report captures the result and the substance of the fixture — participants, scoreline and the detail needed to check it. Reporting is what transforms a scheduled fixture into a recorded event.

Step 5

The result is confirmed and verified

The official confirms the outcome and the match is marked verified, with the verification time recorded. Verified matches are the only activity that feeds league standings, qualification, tournament progress and scouting records.

Match types

Three ways matches are played here

League fixtures

Scheduled league matches

Arranged between two teams as a match request, played inside the league structure, and counted toward Community League standings once verified. Regions define who a team actually competes against.

Casual

Quick Match sessions

Short-format sessions created around a playground rather than a formal fixture list. A session has a rotation rule, a team cap and a target; recorded results are kept as history when the session finishes.

Cups

Tournament matches

Played inside a published tournament. Registration, structure and results are handled through the same match infrastructure, so a cup tie carries the same verification weight as a league fixture.

Why verification matters

What a verified match actually feeds

Standings

League position

Community League tables and qualification progress are calculated from confirmed results, not from fixtures that were merely arranged.

Promotion

League level qualification

Progress toward Live League, Top League and the Extancy League tier follows published qualification rules and regional slot limits, driven by verified results.

Visibility

Scouting and records

Verified participation is what a player or team record is built from. Scouts work from activity that has been confirmed, which is why the verification step matters more than raw appearance counts.

Integrity

Integrity scoring

A match carries an integrity assessment. That standing is consulted before rewards and transfers are authorised, so the record of what actually happened has practical consequences.

Rewards

Wallet rewards

Eligible participation is what generates EXT rewards. The reward path runs through the same verified activity, and payouts respect the published integrity floor.

Public match data

What is shown publicly, and why

Match activity is intentionally selective. The platform publishes the structure of the Match Engine — how fixtures are arranged, officiated and verified — rather than a live list of every fixture or its internal state.

Fixtures are participant data. A scheduled match is an arrangement between two specific teams, and it is not a public announcement until it is confirmed. Match detail therefore stays inside the authenticated application.
Results are owned by the teams involved. Who played, when, and what the score was is information about real participants. It is available to the teams, officials and competitions that were part of it.
The method is public. How verification works, what a verified match feeds, and what the integrity requirements are — all of that is documented here so the competition is auditable from the outside.

No public match list is published on this page. Where a team, tournament or league page shows activity, it is only what has been cleared for disclosure. This page does not display match counts, results or participation figures, because they are not public data.

Empty state

If you were looking for live fixtures

Signed-in teams, officials and fans find their fixtures inside the Match Engine workspace: quick match sessions, match requests, their own team's fixtures and verified history are all there. That workspace requires an account because every view in it is scoped to the teams and sessions the signed-in person belongs to.

If you arrived here to understand how Extancy League competition works rather than to follow a specific fixture, the sections above cover the complete flow.

Open the Match Engine

Quick match sessions, match requests, officiating assignments and verified match history live in the signed-in application. Creating an account is the first step for teams and officials who want to take part.

See the journey League levels

Extancy League application

The Match Engine workspace — quick matches, match requests, officiating, match reporting and verified history — requires an account, because every view is scoped to the teams and sessions you belong to. This page is the public explanation of how the match ecosystem works.

Create Account Sign In Open Dashboard

Every match is a verified event, not a reported claim

The five stages every match passes through

Step 1

A match request is raised

Step 2

The receiving team accepts

Acceptance turns a request into a scheduled fixture with a kickoff time. Declining or cancelling closes the request without creating a match, so a fixture only exists once both sides have agreed.

Step 3

Match officials are assigned

Referees and assistant referees are assigned to the fixture. Their role is to observe and confirm what happened on the pitch, which is what makes the outcome worth more than an unverified claim.

Step 4

The match is reported

Step 5

The result is confirmed and verified

Three ways matches are played here

League fixtures

Scheduled league matches

Arranged between two teams as a match request, played inside the league structure, and counted toward Community League standings once verified. Regions define who a team actually competes against.

Casual

Quick Match sessions

Cups

Tournament matches

Played inside a published tournament. Registration, structure and results are handled through the same match infrastructure, so a cup tie carries the same verification weight as a league fixture.

What a verified match actually feeds

Standings

League position

Community League tables and qualification progress are calculated from confirmed results, not from fixtures that were merely arranged.

Promotion

League level qualification

Progress toward Live League, Top League and the Extancy League tier follows published qualification rules and regional slot limits, driven by verified results.

Visibility

Scouting and records

Verified participation is what a player or team record is built from. Scouts work from activity that has been confirmed, which is why the verification step matters more than raw appearance counts.

Integrity

Integrity scoring

A match carries an integrity assessment. That standing is consulted before rewards and transfers are authorised, so the record of what actually happened has practical consequences.

Rewards

Wallet rewards

Eligible participation is what generates EXT rewards. The reward path runs through the same verified activity, and payouts respect the published integrity floor.

What is shown publicly, and why

Fixtures are participant data. A scheduled match is an arrangement between two specific teams, and it is not a public announcement until it is confirmed. Match detail therefore stays inside the authenticated application.
Results are owned by the teams involved. Who played, when, and what the score was is information about real participants. It is available to the teams, officials and competitions that were part of it.
The method is public. How verification works, what a verified match feeds, and what the integrity requirements are — all of that is documented here so the competition is auditable from the outside.

If you were looking for live fixtures

If you arrived here to understand how Extancy League competition works rather than to follow a specific fixture, the sections above cover the complete flow.

Extancy League application