Kivel

Test checkout

Exercise checkout outcomes and signed webhooks. Test mode, no real payment.

Loading test payments…

About Test checkout

Test checkout outcomes, extra verification and signed webhook events without collecting real card details. Test mode, no real payment.

When to use it

Test an agent payment and human approval with fake money.

Test checkout example
create_test_wallet({name: "Research agent", balance: 100}) → create_test_paywall({name: "Article", amount: 1}) → wallet_pay({id: wallet.id, payee: paywall.endpointUrl, idempotencyKey: "article-1"}) → inspect the ledger

How to use it

  1. Create an item, amount and optional public webhook URL. Save the webhook secret returned once.
  2. Use the hosted outcome buttons, complete_test_checkout with a fake fixture, or wallet_pay with a USD checkout.
  3. Verify the timestamped HMAC signature and inspect test attempts and delivery retries.

Test an agent that pays

Create a wallet with fake USD balance, then a paywall that returns HTTP 402. The agent calls wallet_pay with the paywall URL. A payment within its controls unlocks the content; an amount above the approval threshold asks a human before it can debit. Repeating the same idempotency key resumes that payment safely.

Only a signed-in workspace owner or admin can change wallet limits and approval thresholds or answer approvals. API keys can read controls, add free test balance and request payments. Every test wallet, paywall and checkout counts toward the normal resource pool and expires under mock retention rules.

No real payment details

These resources use fake test money only. No blockchain settlement, real funds or private keys exist. The public checkout offers test outcome buttons and a second confirmation step. It never collects card details. API and MCP clients may submit fake fixtures from the card generators; the service retains only the result and last four digits.

Checkout events are generic, signed and timestamped. Save the webhook secret returned once, verify the signature on raw bytes, reject stale timestamps and deduplicate event IDs. Inspect attempts and delivery results inside the dashboard or through the API.

Limits & privacy

Hosted pages are noindex and have no card fields. Item and description are plain text, up to 80 characters. API/MCP cards are never stored or logged; only outcome and last four digits remain. Generated Luhn-valid fixtures succeed by default; documented sandbox fixtures trigger failures. Requires-verification returns a confirmation token valid up to five minutes. Delivery retries server errors and 429 up to three times. Resource expiry or deletion removes state and logs.

Use this tool from the API reference or connect through the SDK, CLI, SSH, or MCP. Hosted calls share your plan allowances.