Skip to content

docs: sharpen agentcard copy on the payments overview #551

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AnnaXWang merged 2 commits into from
Sep 6, 2026
Merged

docs: sharpen agentcard copy on the payments overview #551

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e85de2a
docs: sharpen agentcard copy on the payments overview
keyserfaty Sep 6, 2026
788d717
Apply batched suggestions from code review
AnnaXWang Sep 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 9 additions & 7 deletions integrations/payments/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,8 +64,8 @@ the card number and cvc stay outside the agent-controlled environment. the brows
href="/integrations/payments/agentcard"
icon="credit-card"
>
enroll a card with Agentcard and approve each checkout while the request is
held.
add users' cards to agentcard's vault. the user approves each transaction
with Face ID and earns points on the purchase.
</Card>
</CardGroup>

Expand All @@ -77,13 +77,15 @@ the card number and cvc stay outside the agent-controlled environment. the brows

| behavior | stripe link | agentcard |
| ------------------------- | -------------------------------------------------------- | ------------------------------------------------------------------- |
| payment-method collection | hosted `link_oauth` action | hosted `card_enrollment` action |
| purchase authorization | explicit `authorize` operation before checkout | approval begins when the browser submits checkout |
| payment handoff | one-use credential substituted at egress | provider executes the held request and returns the response |
| reuse | card item and aliases are consumed on first substitution | card item and aliases remain reusable; each checkout needs approval |
| payment-method collection | hosted `link_oauth` action | fully white-labeled `card_enrollment` page |
| purchase authorization | explicit `authorize` operation before checkout | the user approves with Face ID |
| payment handoff | one-use credential substituted at egress | agentcard executes the request and returns the response |
| reuse | card item and aliases are consumed on first substitution | cards can be reused for recurring and one-time purchases |
| environment | live only | configured agentcard credential; not exposed through the vault api |

choose [stripe link](/integrations/payments/stripe-link) when each purchase needs a newly approved, one-use credential. choose [agentcard](/integrations/payments/agentcard) when the same enrolled card must support multiple separately approved purchases.
choose [stripe link](https://hypeship.dev/integrations/payments/stripe-link) when each purchase requires a newly approved, single-use credential. choose [agentcard](https://hypeship.dev/integrations/payments/agentcard) when one enrolled card must support multiple purchases, with separate approval for each.

both integrations may provide additional benefits, including card rewards and chargeback protection. review each provider鈥檚 own documentation for the most up-to-date details.

## Checkout and processor coverage

Expand Down
Loading