Skip to content

mpp: correct the production claim in the Production patterns section #150

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

Merged
stellar-triage-bot merged 1 commit into from
Oct 15, 2026
Merged

mpp: correct the production claim in the Production patterns section #150

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
11 changes: 7 additions & 4 deletions skills/agentic-payments/mpp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -252,8 +252,10 @@ console.log("Channel closed:", txHash);
## Production patterns

Three patterns for running Charge and Session behind the same server,
verified against a service that's been billing real USDC over MPP Charge
in production since before this skill existed.
taken from a deployed service. Its Charge mode was verified end to end
on testnet (settled payments, `pull` and `push`); its mainnet endpoint
has not been verified with a settled payment, so treat these as tested
patterns, not as proof of a production billing history.

### Recipient resolution (recover at boot, fail closed per request)

Expand Down Expand Up @@ -474,8 +476,9 @@ export function mppSessionMiddleware(amount, description) {
}
```

This is the pattern actually running in production: Charge mode is
initialized and billing; Session mode's instance is `null` there today,
This is the pattern running on that deployment: Charge mode is
initialized and verified on testnet (not yet on mainnet); Session mode's
instance is `null` there today,
by choice — it requires deploying and funding a channel contract per
deployment, a step that carries custody implications worth a compliance
pass before turning on for a given business. Session works the same way
Expand Down
Loading