Portland Fire vs. Phoenix Mercury

Platform comparison

Market context

The Portland Fire and Phoenix Mercury meet on 16 August in a regular-season WNBA matchup with settlement closing at 23:00 UTC. Current implied odds favour Phoenix at 65%, reflecting the Mercury's stronger roster depth and recent form. The game tips at 7:00 PM ET, with final score determination including any overtime periods.

Historical matchup data and season records provide the foundation for reading this 35% YES probability on Portland. The Mercury have won three of their last four encounters against Portland this season, and Phoenix's defensive rating ranks significantly higher across the league standings. However, Portland's home-court advantage—should this game be played in Portland—historically narrows the gap by 3–5 percentage points in similar fixtures. The current probability sits below what pure strength-of-schedule models would suggest, indicating the market may be pricing in roster availability concerns or recent injury reports affecting Portland's backcourt depth.

Traders monitoring this market should track official injury announcements from both franchises through 16 August, as late-game roster changes materially shift book depth and funding flows. Weather conditions and venue confirmations matter less for indoor basketball than for other sports, but any postponement triggers the market's extension clause. Liquidity tends to tighten significantly in the final two hours before tip-off; deposit friction via Klarna or SEPA transfers can delay position entry for European traders, making early commitment to conviction bets strategically relevant. Recent WNBA scheduling changes have occasionally affected game times by 30–60 minutes, so confirmation of the 7:00 PM ET slot should be verified through official league sources within 24 hours of settlement.

Methodology

This page compares Portland Fire vs. Phoenix Mercury 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. Polymarket Klarna UK additionally offers Klarna and SOFORT as fiat on-ramps to USDC. Live odds reflect the Polymarket order book.

Resolution & payout

Settlement path determines payout latency. Polymarket settles on-chain (USDC, minutes). Broker frontends like Polymarket Klarna UK 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).

UK Frequently Asked Questions

What does SOFORT cost as a deposit method?

Polymarket Klarna UK charges no fees for SOFORT. The only cost is the internal FX spread (typically <1%) on EUR→USDC conversion. SOFORT itself has no end-user fees — the platform absorbs acquirer costs.

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.

Can UK traders use Klarna to deposit on Polymarket?

Polymarket does not natively accept Klarna. To fund a Polymarket account from the UK, you must first purchase USDC via a crypto exchange (Coinbase UK, Kraken) or Revolut, then transfer to a Polygon-compatible wallet. Some third-party on-ramps (MoonPay, Transak) accept UK debit cards and may support Klarna buy-now-pay-later for crypto purchases.

What payment methods can UK users use for Polymarket?

UK traders typically use: (1) Coinbase UK or Kraken — buy USDC with GBP debit card or bank transfer; (2) Revolut — buy crypto and send to wallet; (3) MoonPay or Transak — Visa/Mastercard UK debit card directly to USDC on Polygon. Standard GBP-to-USDC conversion fees range from 0.5–2.5%.

How long do Polymarket withdrawals take for UK users?

Polymarket withdrawals to your Polygon wallet are instant (on-chain). Converting USDC back to GBP via Coinbase UK or Kraken typically takes 1–3 business days for bank transfer, or near-instant for Revolut. Polygon gas fees are minimal (<$0.01 per transaction).