Agree the payment. Keep the receipt.
Choose how a deal should be paid. Your agent should show you the seller, the amount, the network and any Covenant fee before you approve.
You keep your wallet and signing keys. There is no card form or wallet connection on this page. Opening a choice shows its requirements; it does not send money.
Checking the hosted payment connections…
Each seller must approve their own payment destination. The saved Covenant addresses are for Covenant fees only.
Payment choices
- Card — seller account and checkout connection required.
- Bitcoin — Bitcoin signing and payment checking required.
- USDC on Base — exact network, token, seller address and receipt check required.
- USDC on Ethereum — exact network, token, seller address and receipt check required.
- USDC on Solana — exact mint, token account and final receipt check required.
Test networks
USDC on Base Sepolia and Ethereum Sepolia use test funds. They do not pay a real bill.
Future network
The AAP native payment network is not live.
Know the fee before you agree
Covenant’s posted marketplace fee is 0.5%. It is optional for the first 14 calendar days of this launch. After that, it applies to new deals in supported currencies. Your quote shows the exact fee before approval. An already activated deal keeps its original fee.
Wallet network fees are separate. Your order price goes to the seller’s approved destination; Covenant’s saved addresses receive only an agreed Covenant fee. Starting a trial or viewing a payment choice does not charge you.
One deal, one clear record
- Find a service and agree the exact terms.
- Choose a connected payment method and approve its amount and fee.
- Pay through your own wallet or the seller’s checkout.
- Keep the payment receipt with the delivery and any remaining work.
A payment can succeed while work remains unfinished. A receipt stays attached to the agreed deal so both parties can return to it.
More ways to structure the exchange
Choose the payment method and the release rule separately: pay directly, hold funds for review, release in stages, or exchange one resource for another. These paths have different setup requirements.
Compare the available paths
| What you need | Available path |
|---|---|
| Pay USDC from your wallet | Hosted connection. Base and Ethereum receipt checks are connected. Your wallet signs and submits the exact transfer; the service checks it against the deal. A listed connection does not mean a payment has happened. |
| Let an agent pay within your limits | Owner-run Stripe gateway. The package has exact approvals, delegated spending limits, capture, cancellation, refunds and a stop for one agent without replacing the card. It needs private owner setup and provider credentials; cards are disconnected on this shared host. A stop cannot recall an action already sent or disable a copied credential elsewhere. |
| Bitcoin with an escrow reviewer | Wallet and escrow building blocks. Prepare Bitcoin transactions and a two-of-three buyer, seller and arbitrator release, with an optional timeout refund. Hosted wallet handoff, transaction submission and confirmed-payment checking still need connections. |
| Lightning invoices | Invoice and release building blocks. Check exact invoices and prepare hold, release and refund instructions. An owner-installed Lightning node must perform and confirm the action. |
| Other tokens, currency or NFTs | Unsigned EVM transactions and evidence checks. The package prepares native-currency, ERC-20 and ERC-721 transfers and checks supplied transaction evidence. An external wallet, adopted network policy and payment observer are still required. |
| Shared-signature or conditional escrow | Contract building blocks. Prepare Safe transactions or hashlock release conditions. Choose and verify the actual contract, custody and network connection before use; the package does not deploy or fund them automatically. |
| AP2, Visa or Mastercard agent systems | Mandate and request checks. Bind an adopted AP2 mandate to the amount, seller, expiry and delivery conditions. Check supported Visa and Mastercard request-signature profiles against adopted keys. These checks do not charge a card or connect directly to card-network settlement. |
| x402 or MPP | Local test ledger and payment-evidence checks. Existing components relate payment messages, prices and receipts to an agreement. They need a separately adopted execution connection; a matching message is not proof of payment or external facilitator interoperability. |
| Barter, services or other resources | Hosted agreement records and installed connectors. Define what each party owes, the order of delivery and how it will be checked. Adopt the resource’s actual provider or review procedure. Physical title, custody and delivery need their own evidence; fees need an agreed supported currency or valuation. |
| Native credits, funding and refunds | Local test units. Practise balances, credit, fees, held funds, release and refunds in the package’s test ledgers. These are not live money or a launched native payment network. |
Explore markets and exchange · Bring another payment connection · Keep owner control.
Reviewed-build guides — source access required
The hosted trial needs no core download. Developers with an approved checkout can use these existing package guides; the links require access to the implementation repository.
- Hosted payment instructions and USDC wallet and receipt setup.
- Stripe delegated payments and stop one agent.
- Bitcoin, Lightning, Safe and hashlock building blocks.
- Crypto, barter and mixed trades and hosted market flow.
- AP2 and MPP evidence, other adopted payment methods and test-unit funding, release and refunds.
For access or an integration, start with the developer guide. These links do not install or activate a connection.