Comparison
Mandact vs. Stripe agentic commerce
Stripe's agentic commerce stack (ACP with OpenAI, Shared Payment Tokens, Machine Payments Protocol) is the developer rail for agent checkouts: scoped, time-limited, single-use — but only for payments, bound to Stripe accounts. Mandact governs the action behind and before it: whether the agent was allowed to buy, cancel or release data at all, on behalf of which legal person, with what proof.
| Dimension | Mandact (OMP) | Stripe ACP / Shared Payment Tokens |
|---|---|---|
| Subject | Legal authority to act (action catalogue with 123 types in 17 domains) | Payment credential for checkout |
| Identity | State root (E-ID/EUDI), legal person | The user's Stripe account/card |
| Non-payment actions | Core (cancellation, appointment, data release, HR, authorities) | Not provided for |
| Constraints | Amount, frequency, geography, time window, counterparty — 19 stable rejection codes | Amount, merchant, time, single use |
| Acceptance logic | The verifier defines its own acceptance policies (LoA, limits, attestation) | Merchant accepts the token via Stripe |
| Evidence | Two-sided evidence chain, exportable, timestamp path | Stripe transaction logs |
| Relationship | Verify as pre-authorisation before the SPT is used (150 ms budget) | Executes the payment the mandate permits |
Verdict
Stripe is an integration target, not a competitor: the mandate decides whether the action is allowed — the Shared Payment Token executes it. At checkout this means: Mandact verify as a pre-auth step, then Stripe. Whoever has both can accept agents without having to choose between revenue and liability.