# Aftercard Docs

Canonical URL: https://aftercard.ai/docs
Markdown URL: https://aftercard.ai/docs/index.md
Summary: Aftercard gives personal AI agents one user-authorized payment stack: Aftercard Card, Memory requests, and routing across browser, API, and agentic payment rails.
Description: Product and developer documentation for Aftercard, the payment infrastructure for personal AI agents.

## Canonical Answer

Aftercard gives personal AI agents one user-authorized payment stack: Aftercard Card, Memory requests, and routing across browser, API, and agentic payment rails. Product and developer documentation for Aftercard, the payment infrastructure for personal AI agents. Aftercard Card, requests, secrets, and approvals stay under the human owner's control.

![Aftercard overview architecture](https://aftercard.ai/docs-assets/images/magicpay-overview-architecture.png)

## Key Points

- Payment infrastructure for personal AI agents.
- One user-authorized payment stack for online purchases, subscriptions, and agent-native rails.
- Aftercard Card, requests, secrets, and approvals stay under the human owner's control.
- Sensitive data is resolved inside Aftercard, never in LLM context.

## What Aftercard Is

Aftercard is designed to be the universal payment tool for a personal AI agent. The agent can use provider-backed cards and payment operations, APIs, crypto rails, browser checkout, and agent-native protocols to get the job done, while the user sees a simple Aftercard Card with one balance. Aftercard Card makes payments in the complex world of agentic protocols, new payment standards, and crypto feel as simple as topping up a card.

## Aftercard Overview

Aftercard is payment infrastructure for personal AI agents. The goal is to feel as simple as Apple Pay for users and their agents while hiding wallets, cards, protocols, approval routing, and protected execution behind one Aftercard Card interface.

- Protected requests: Approvals, secrets, identity details, and payment execution move through user-controlled requests instead of model context. (https://aftercard.ai/docs/components/memory-fill)
- Commerce Routing: MagicSearch finds provider-method guidance; the agent executes with built-in browser, an API, or an agentic protocol. (https://aftercard.ai/docs/reference/payment-methods)

## Purchase Loop

Every purchase is a session: the personal agent clarifies intent, Aftercard raises requests when user authority is needed, and execution continues through the best available payment rail.

- Intent To Session: The user asks their agent for a purchase, and Aftercard turns it into a tracked payment session with events. (https://aftercard.ai/docs/reference/entities#payment-session)
- User Authority: KYC, balance, approvals, secrets, and final confirmations stay owned by the human. (https://aftercard.ai/docs/reference/entities#request)
- Payment Execution: The session can finish through x402, MCP/API, SDK calls, or protected browser checkout. (https://aftercard.ai/docs/guides/e2e-purchase)

## Build With Aftercard

Use the built-in payment agent for end-to-end purchases, or connect your own personal agent runtime through the SDK and API while the user stays in control through the Aftercard apps.

- Built-In Payment Agent: Searches providers, coordinates built-in browser, ranks payment channels, and asks the user to approve each protected step. (https://aftercard.ai/docs/guides/e2e-purchase)
- Aftercard SDK: Bridges agents to the payment provider infrastructure and Aftercard backend services for sessions, auth, and preferences. (https://aftercard.ai/docs/integrations/sdk)
- Human UI: Web, mobile, ChatGPT, Claude, Telegram, and email apps handle approvals, sessions, card state, and confirmations. (https://aftercard.ai/docs/components/omnichannel-ui)

## Choose Your Path

Use the docs path that matches what you want to do next.

- Set up an account: Create the user account, pass KYC, top up the Aftercard Card balance, and connect your first agent. (https://aftercard.ai/docs/guides/account-setup)
- Understand the product: Start with Aftercard Card, Memory requests, built-in browser, MagicSearch, and the SDK. (https://aftercard.ai/docs/components)
- Run a purchase: Follow the built-in agent purchase flow from intent discovery to provider selection and user approval. (https://aftercard.ai/docs/guides/e2e-purchase)
- Integrate the SDK: Use Aftercard from your own agent, worker, MCP tool, or browser runtime. (https://aftercard.ai/docs/integrations/sdk)

## Recommended Path

Most users and builders should follow the same staged path before a real payment. This keeps setup, safety, and payment authority understandable for both humans and agents.

1. Create an Aftercard account and complete account, KYC, and balance prerequisites.
2. Connect one agent runtime and verify that Aftercard and built-in browser are available.
3. Run a browser-only task so the agent proves it can navigate without any protected data.
4. Run a low-risk protected form handoff, such as a shipping address.
5. Add reusable Aftercard Memory values only after the user understands what will be stored.
6. Move to SDK, API, or full purchase flows once request handling is observable end to end.

## Use Case Entry Points

Start from the workflow you are trying to ship. The components underneath are modular, but each path trusts the agent with a different amount.

- I want my agent to buy something: Use the end-to-end purchase guide to combine MagicSearch, built-in browser, approvals, and payment execution. (https://aftercard.ai/docs/guides/e2e-purchase)
- I want protected form fill: Use Aftercard Memory fill when the agent reaches card, login, identity, or confirmation fields. (https://aftercard.ai/docs/components/memory-fill)
- I want to integrate the SDK: Use Aftercard SDK when your app owns the surrounding agent or browser runtime. (https://aftercard.ai/docs/integrations/sdk)
- I want provider-backed payments: Use Payment Bridge docs for account linking, KYC, card state, top-up, and provider callbacks. (https://aftercard.ai/docs/components/payment-bridge)
- I want agent-readable rules: Use the agent operating guide for machine-readable rules, routing guidance, and discovery hints. (https://aftercard.ai/docs/agents)
- Something is stuck: Use troubleshooting for checkout, request, Memory, payment, and payment provider failure modes. (https://aftercard.ai/docs/guides/troubleshooting)

## Related

- Aftercard Card: https://aftercard.ai/docs/magiccard
- Getting Started: https://aftercard.ai/docs/getting-started
- Aftercard Components: https://aftercard.ai/docs/components
- Aftercard SDK: https://aftercard.ai/docs/integrations/sdk