Skip to content

docs: add stablecoin payments topic #196

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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
EddieNBT wants to merge 2 commits into
base: main
Choose a base branch
from
+51 −0
Open

docs: add stablecoin payments topic #196

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
79cff80
Create ap2-and-stablecoin-payments.md
EddieNBT Mar 25, 2026
3603115
Update mkdocs.yml
EddieNBT Mar 25, 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
50 changes: 50 additions & 0 deletions docs/topics/ap2-and-stablecoin-payments.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
# Exploring Stablecoin Payments in AP2
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Mar 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For this new topic to appear in the site navigation, it needs to be added to mkdocs.yml. Please add an entry for this file under the Topics section in the nav configuration.

For example:

nav:
  - Topics:
      # ... other topics
      - AP2 and x402: topics/ap2-and-x402.md
      - AP2 and Stablecoin Payments: topics/ap2-and-stablecoin-payments.md
      - Privacy and Security: topics/privacy-and-security.md
      # ... other topics

This document is an exploratory contribution examining how the Agent Payments
Protocol (AP2) could apply to stablecoin-based payments. It does not represent
an official AP2 specification.
## Push vs Pull Payment Semantics
AP2 v0.1 focuses on "pull" payment methods (e.g., credit/debit cards), where
the merchant initiates a charge against the user's credentials. Stablecoin
payments operate on "push" semantics — the payer initiates a transfer directly
to the payee's address.
Despite this difference, AP2's core mandate architecture could be applicable
to push payments as well. The following table outlines a conceptual mapping
of how each AP2 component might function in a stablecoin context:
| AP2 Component | Pull Payments (Cards) | Push Payments (Stablecoins) |
|---------------|----------------------|---------------------------|
| Cart Mandate | Merchant signs cart, user confirms | Same — cart signing is payment-agnostic |
| Payment Mandate | Shared with card network/issuer | Could be shared with settlement network for trust |
| Credentials Provider | Returns card token | Could execute transfer and return proof of payment |
| MPP | Initiates charge | A verification layer could confirm on-chain receipt |
## Potential Use Cases
### Social Entertainment Payments
Social platforms process high volumes of micro-transactions across borders.
Possible AP2 applications include:
- **Creator Tipping (Human Present):** A user tips a live streamer in USDT.
The Shopping Agent facilitates the flow, the Merchant Agent builds a cart
for the tip amount, and the user confirms via a Cart Mandate. Settlement
could occur on-chain.
- **Digital Gifting (Human Present):** A user purchases virtual gifts to send
to a friend. The cart contains multiple virtual items with a total settled
in stablecoins.
- **Subscriptions (Human Not Present — Future):** A user subscribes to premium
content with monthly stablecoin payments. This would align with future AP2
capabilities such as Intent Mandates planned for v1.x.
### Cross-Border B2B Settlement
Stablecoins are increasingly used for cross-border merchant settlement,
particularly in emerging markets where traditional banking rails are slow or
expensive. AP2 mandates could provide the accountability and audit trail
needed for these transactions.
## Possible PaymentMethodData Extension
One possible approach to supporting stablecoins is to define a payment method
identifier following the W3C Payment Method convention. For example:
```json
{
"supported_methods": "https://example.com/stablecoin/v1",
"data": {
"supported_tokens": ["USDT", "USDC"],
"supported_chains": ["ethereum", "tron", "polygon"],
"preferred_chain": "tron",
"settlement_currency": "USD"
}
}
1 change: 1 addition & 0 deletions mkdocs.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@ nav:
- Core Concepts: topics/core-concepts.md
- AP2, A2A and MCP: topics/ap2-a2a-and-mcp.md
- AP2 and x402: topics/ap2-and-x402.md
- Exploring Stablecoin Payments: topics/ap2-and-stablecoin-payments.md
- Privacy and Security: topics/privacy-and-security.md
- Life of a Transaction: topics/life-of-a-transaction.md
- AP2 specification: specification.md
Expand Down