Counter-Strike: Natus Vincere vs Legacy (BO3) - IEM Atlanta Group B

Platform comparison

Market context

Natus Vincere and Legacy face off in the Counter-Strike upper bracket final at IEM Atlanta, a best-of-three match originally scheduled for 13 May at 7:00 PM ET. The 49% crowd probability reflects genuine uncertainty: Na'Vi remains one of the world's most consistent tier-one rosters, whilst Legacy has demonstrated capacity to upset established squads in recent months. Book depth on this market correlates directly with deposit flows from regional traders; SEPA rails and Klarna on-ramps have historically driven liquidity spikes around major esports tournaments, particularly when European-based teams compete. Withdrawal friction on secondary markets has compressed, allowing tighter spreads as traders can now settle positions via USDC or direct bank transfers within 24 hours.

Historical precedent suggests Na'Vi's consistency commands a slight edge in best-of-three formats, where preparation depth and map pool flexibility compound over multiple games. Legacy's recent performances at regional qualifiers show improved anti-eco discipline and mid-round adaptation, though sample sizes remain limited against top-tier opposition. The current 49-51 split likely reflects traders pricing in Na'Vi's institutional advantage whilst acknowledging Legacy's upward trajectory and the inherent volatility of single-elimination matches.

Traders should monitor roster confirmations and any schedule shifts; IEM Atlanta's group stage compression occasionally forces rescheduling that can affect preparation time. Recent ESL announcements have confirmed the tournament's on-time progression, reducing tail risk of the 7-day delay clause. Deposit availability and withdrawal confirmation times on major platforms will influence position sizing, particularly for traders managing exposure across multiple esports markets during the tournament window.

Methodology

This page compares Counter-Strike: Natus Vincere vs Legacy (BO3) - IEM Atlanta Group B with a focus on payment rails and deposit friction. Polymarket accepts USDC on Polygon only; Kalshi only ACH/Plaid (US only); Betfair card/SEPA in EU/UK; Manifold no deposit. PolyGram additionally offers Klarna and SOFORT as fiat on-ramps to USDC. Live odds reflect the Polymarket order book.

Resolution & payout

Resolution source: This market settles from the official publication at https://www.twitch.tv/ESLCSb. A proposer submits the result to the UMA Optimistic Oracle on Polygon, the two-hour challenge window opens, and the smart contract pays out in USDC.

Settlement path determines payout latency. Polymarket settles on-chain (USDC, minutes). Broker frontends like PolyGram add Klarna/SOFORT as fiat withdrawal options with T+1 processing. Kalshi: USD via ACH (T+1 to T+3). Betfair: local currency via card/SEPA (T+1 to T+5).

FAQ

How does Klarna deposit work on PolyGram?

You enter the deposit amount in EUR/GBP, choose Klarna as the method, run through Klarna's standard authentication (Pay Later or Direct Bank Transfer), and PolyGram converts internally to USDC for the Polymarket order book. Processing: typically under 30 minutes.

Which payment methods are supported?

Klarna (Pay Now / Pay Later), SOFORT, SEPA bank transfer, credit card (Visa/Mastercard), Apple Pay, Google Pay, and direct USDC deposit on Polygon. Availability depends on your jurisdiction.

What's the minimum deposit?

10 EUR / 10 USD equivalent. No upper limit, but deposits over $1,500 lifetime volume trigger a quick KYC flow (typically 5-10 minutes).

How do withdrawals work?

Identical methods in reverse. SEPA withdrawal: T+1 (standard) or under 10 seconds (SEPA Instant). Klarna withdrawals process via bank-account refund. USDC withdrawal to external wallet: Polygon gas cost (typically $0.01).

Are payment details protected?

Yes. Card and bank details are never stored by PolyGram — they pass directly through PCI-DSS compliant payment service providers (Adyen, Stripe). PolyGram retains only transaction IDs and Klarna reference numbers for reconciliation.