# Prices and payment policy (/guides/concepts/prices-payment-policy)

A **price** tells Recuut what a payer must pay to access a resource. Payment policy is the set of choices that Recuut owns around that price: accepted payment methods, settlement coordination, and payout policy.

Your application identifies the resource and reports its execution. It does not calculate a replacement amount from caller input or choose a different payment method for one request.

Prices and revisions change independently:

| Change | Consequence |
| --- | --- |
| Change a price | Future payers receive new payment requirements. The execution reporting contract stays the same. |
| Publish a new revision | Future executions use new reporting rules. Historical transactions keep the revision that described them. |

The payment requirements returned to a payer include the active price. An x402-capable wallet uses those requirements when it prepares payment proof. The wallet does not receive the merchant API key or choose the merchant policy.

The test guide uses a fixed **0.01 USD** Price. Recuut converts that policy into **10,000 Base Sepolia USDC atomic units** for the payer: USDC uses six decimal places, so 1 USDC is 1,000,000 atomic units. The wallet must have at least the required amount, and its approval limit must be at least that amount. The guide uses a 100,000-unit limit (0.10 USDC), which covers the example without approving an open-ended amount.

Test payment requirements use Base Sepolia (`eip155:84532`) and test USDC. The server reports the revision values; it never converts prices or accepts a caller-supplied amount.

[See the x402 payment retry →](/guides/concepts/x402-payment-retry/)