galleon-defi-paymentslisted

# DeFi payments Turn a payment request into a bounded obligation and a verifiable outcome. Use maintained wallet, x402 and streaming tools. This skill grants no spending authority and never treats a payment challenge as permission to pay. ## Choose the payment model Read [provider access](references/providers.md) for Coinbase/x402, Sablier and Superfluid. Use [payment workflows](references/workflows.md) for reconciliation and failure cases. A one-time token transfer, per-request API purchase, prefunded vesting schedule and open-ended stream have different obligations. Cross-chain funding needs a bridge lifecycle as well as a payment lifecycle. 1. Establish payer account, recipient or resource origin, chain, exact token/mint, base-unit amount, purpose, deadline and maximum total cost. Include gas, service fees, wrapping and recurring obligations. Resolve names before preparing anything; do not substitute a ticker match or follow a redirect with payment credentials. 2. Reuse the user's approved wallet/provider. Inspect current SDK or tool schemas and account permissions. An API key, managed wallet, alias or session may have a different owner and revocation path. Installing an upstream skill is a separate software action, not authorization to create a wallet or fund it. 3. Gather read-only evidence: spendable balance, allowance, nonce, current schedule/stream state and existing receipt for this obligation. A token balance includes neither guaranteed transferability nor issue