San Martin de Tucuman vs. San Martin de San Juan

Platform comparison

Market context

San Martín de Tucumán and San Martín de San Juan are due to meet in Primera Nacional on Saturday, with the market currently pricing **YES** at 0%, which implies an almost complete rejection of the event resolving as listed. The cleanest read for a power-user is that this is a calendar-driven market: if the fixture is officially played on schedule, the correct side should be validated by the match being completed before the settlement window closes on 9 August 2026 at 21:00 UTC, so automation should watch both fixture confirmation and any rescheduling notice rather than just the scoreline feed.[1][2]

Historically, this pairing has been low-scoring and tight. Across head-to-head samples, the sides are broadly even or slightly tilted towards Tucumán depending on the source set, with draws common and several recent meetings finishing 1-1 or otherwise level; the latest listed encounter ended 1-1 in March 2026.[1][2][3][7] That matters for probability framing because a 0% crowd price can persist when traders treat the listing as a binary scheduling check, not a football handicap: in programmatic terms, the market is less about expected winner strength than about whether the match entry is realised and parsed correctly by the settlement logic.[1][6]

The main catalysts to monitor are official fixture changes, late venue or kick-off adjustments, and team-list publications close to matchday, since Argentine lower-division schedules can move with limited notice. Live score and lineup pages are useful for confirmation, but a bot or conditional-order workflow should prioritise the league fixture source and compare it against the market’s settlement timestamp, because the edge here is usually in detecting cancellations, postponements, or time shifts before they propagate through secondary data feeds.[9][12]

Sources: 1 · 2 · 3 · 4 · 5

Methodology

We track San Martin de Tucuman vs. San Martin de San Juan across the five venues with material prediction-market liquidity. The probability shown is the live Polymarket mid; the comparison rows summarise how each venue treats the underlying contract — fees, KYC thresholds, settlement currency, deposit options. The highlighted row marks the cheapest route into Polymarket's order book.

Resolution & payout

Settlement runs on-chain. Polymarket's contract logic separates YES and NO shares as conditional tokens; at resolution the winning share lifts to $1.00 and the losing one to $0. The outcome input comes from the UMA Optimistic Oracle, which secures against bad resolution with a bond + dispute window.

Once finalised, the smart contract pays USDC to the holders' wallets within minutes — no withdrawal fees beyond Polygon network gas. Kalshi settles in USD via CFTC clearance, Betfair in account currency net of commission, Manifold in play-money mana with no cash-out.

FAQ

How does resolution work?

Through the UMA Optimistic Oracle on Polygon: a proposer submits the outcome, a two-hour challenge window opens, and USDC payouts settle automatically once the result is final.

What's the difference between YES and NO shares?

A YES share pays $1.00 if the event happens, $0 otherwise. A NO share pays $1.00 if the event doesn't happen. The market price between 0¢ and 100¢ is the implied probability.

How fast are USDC deposits?

Polygon credits deposits after 12 confirmations — usually under 30 seconds. Withdrawals follow the same path and land back in your wallet within minutes.

Do I need to KYC for this market?

On Polymarket directly, no — it's wallet-based. Intermediary brokers like Kalshi Fees trigger KYC only above $1,500 of lifetime trading volume; under that you trade pseudonymously with a single wallet address.

How reliable are the quoted odds?

The YES/NO percentages are the live mid-prices of the Polymarket order book. On deep markets they move every few seconds; on thinner ones you'll see short plateaus.