Your Funds

Polypar's on-chain asset flow uses native USDC on Polygon:

wallet → approved parlay vault → Won or Lost resolution → redemption or treasury

The Deposit screen can open Reown's Meld onramp or receive native Polygon USDC from an external exchange. That same token is accepted directly by current parlay vaults; Polypar does not perform an intermediate stablecoin conversion.

Meld and its available payment providers perform their own eligibility, identity, and payment checks. Availability, assets, networks, methods, fees, and limits depend on the user's location and chosen provider. Polypar never sees card or bank credentials. The dormant direct Coinbase integration remains disabled unless it is separately approved and enabled.

Before deposit: wallet-controlled

USDC remains in the user's wallet until a wallet-signed transaction succeeds. A backend quote is only an EIP-712 price-signature payload for one vault; the backend cannot pull wallet funds merely by creating or signing it.

If allowance is too low, the user separately approves that specific parlay vault for the stake amount requested by the app. An approval permits the vault to transfer tokens under ERC-20 allowance rules, but does not itself place the parlay.

After deposit: contract-controlled

A successful depositWithQuote transfers the stake into the selected vault and mints shares to the receiver. From that point:

• the user controls transferable vault shares, not the deposited USDC;
• there is no Open-state withdrawal, cancellation, refund, or cash-out;
• contract resolution determines whether collateral goes to the treasury or remains available for winning redemptions;
• a winning redemption is pro-rata over the balance actually held by that vault.

Self-custody of the wallet does not mean self-custody of assets already deposited into a smart contract.

Network and asset boundaries

Polypar has no internal bridge. Users already on Polygon must still confirm they hold the exact configured USDC token, not a similarly named asset. Users arriving from another chain may need an external bridge or exchange withdrawal, which has separate smart-contract, counterparty, routing, fee, delay, and wrong-network risks outside Polypar.

Google/Apple smart accounts use a restricted Polygon ERC-20 paymaster for wagers, reward claims, and redemptions. Pimlico fronts the native network token and charges the user's own USDC balance; Polypar does not sponsor the fee. External wallets continue to pay Polygon gas normally. If USDC fee payment is unavailable, Polypar stops the embedded-wallet action instead of silently asking the user for POL.

Verify token and contract addresses in Network & Contracts before any interaction.

Next: use the transaction sequence in Place a Parlay and review custody, bridge, token, and contract risks in Risks & Limitations.