Five ways to give a payment a reason to move.
Choose a date and a time. Your payment can be released when Solana’s on-chain clock reaches that moment.
For example: Send 0.1 SOL on the first of the month.
A transaction is still required to settle. Every payment has a separate expiry and refund path.
Explore this condition ↗Give a payment a price threshold and a deadline. A verified oracle must provide the value the program can trust.
For example: Send 20 USDC if SOL reaches $200.
Pyth price conditions are implemented. Real signing requires the deployed price-capable program and a fresh, fully verified Devnet Pyth account; market quotes alone cannot release assets.
Explore this condition ↗The sender and recipient each approve in their own Solana wallet. Only both approvals make the payment ready to release.
For example: Send 20 USDC when we both say OK.
The recipient can return the payment. An undecided payment can be refunded after expiry.
Explore this condition ↗Choose a Solana address you both trust. That referee can release or return the payment, but cannot receive its funds.
For example: Send 0.5 SOL if our referee approves.
The referee is a trust assumption. Make sure both people agree on the address before signing.
Explore this condition ↗A supported market question can give a payment a final result. Settlement needs an independently verifiable resolution.
For example: Send 20 USDC if the question resolves yes.
Preview only. A result resolver is not configured. This site does not execute Polymarket trades.
Explore this condition ↗