---
title: "Approve a checkout"
description: "Create a bounded purchase intent and approve only the checkout digest the user reviewed."
image: "https://help.agent.mq/og.svg"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.agent.mq/llms.txt
> Use this file to discover all available pages before exploring further.

# Approve a checkout

## Prerequisites

Use a management credential with application write access. Do not send personal credentials or payment data.

1. **Create the intent**

```bash
curl -X POST https://api.agent.mq/v1/applications/app_<32-lowercase-hex>/purchases \
  -H "Authorization: Bearer $AGENTMQ_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"merchantOrigin":"https://merchant.example","itemDescription":"One blue notebook","maxTotalUsdMicros":50000000,"currency":"USD"}'
```
2. **Read current state**

   `GET /v1/applications/{appId}/purchases/{purchaseId}` returns `purchase`, `revision`, and the next required action.
3. **Approve the exact snapshot**

```bash
curl -X POST https://api.agent.mq/v1/applications/app_<32-lowercase-hex>/purchases/pur_<32-lowercase-hex>/approve \
  -H "Authorization: Bearer $AGENTMQ_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"checkoutDigest":"<64-lowercase-hex>","expectedRevision":<revision>}'
```

## Verify

The approved digest must equal the currently stored checkout digest. If the checkout or revision changed, the API returns a conflict and requires a fresh review.

## Next steps

- [Browser handoff leases](/agentic-purchases/handoffs)
- [Availability and boundaries](/agentic-purchases/availability)

Source: https://help.agent.mq/agentic-purchases/checkout-approval/index.mdx