> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentcard.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Get checkout coverage

> What the direct SDK can pause and complete, processor by processor, with its modes and limitations.

A richer view than [recognizers](/api-reference/vault/recognizers): for each processor it says how the card reaches it, where a bank challenge surfaces, and what the Vault does not cover (subscription renewals, unbound Stripe tokens). It describes the direct SDK only. KERNEL's native integration has its own coverage.

<RequestExample>
  ```bash cURL theme={null}
  curl https://api.agentcard.sh/api/v2/checkout/coverage \
    -H "Authorization: Bearer $ORG_TOKEN"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {
    "object": "checkout_coverage",
    "integration": "direct_sdk",
    "merchant_confirmation_required": true,
    "validation": "merchant_and_browser_test_required",
    "processors": [
      {
        "psp": "stripe",
        "mode": "token",
        "methods": ["POST"],
        "hosts": ["api.stripe.com"],
        "client_side_encryption": "not_supported",
        "challenge_surface": "merchant_browser",
        "outcome": "merchant_confirmation_required",
        "request_flows": [
          { "flow": "tokenization", "coverage": "tokenization_response_only", "amount_authority": "display_only" },
          { "flow": "direct_payment_intent_confirm", "coverage": "card_bearing_template_required", "amount_authority": "requires_amount_cents_and_currency_verification" },
          { "flow": "token_to_payment_intent_confirm", "coverage": "unsupported_unbound_intent" }
        ],
        "limitations": []
      }
    ]
  }
  ```
</ResponseExample>

Recognition is not a purchase test. Validate each merchant and browser combination end to end before marking it covered.
