Steps

Integrate the Nekuda SDK into your agent application and present the user with Nekuda's secure credential collection UI so they can authorize a card for agent use
Define the mandate parameters: allowed merchant categories, maximum per-transaction amount, maximum cumulative spend, expiry date, and any merchant-specific locks
The SDK securely vaults the card credentials and issues a mandate token to your agent; the raw card data never enters your application or the agent runtime
At checkout, the agent calls the Nekuda SDK's pay method with the mandate token and transaction details; the SDK injects the tokenized card credential and appends the required MIT/MOTO network flags to signal agent-initiated status to the acquiring bank
After the transaction, read the mandate's remaining balance and transaction history from the Nekuda API to enforce agent-side spending guardrails and provide receipts to the user

Known gotchas

Card network rules for merchant-initiated transactions (MIT) require a stored credential agreement to have been obtained during a consumer-initiated transaction first; the Nekuda mandate flow handles this but you must ensure the initial user-authorization step completes successfully before any agent-initiated charge
Nekuda mandates are scoped at creation time; if a user wants to change spend limits mid-session, a new mandate must be issued — there is no partial amendment of an existing mandate token
Authorization rates for agent MIT transactions may differ from in-person card-present rates; test with your target issuer mix in sandbox before assuming the same decline rates as your existing checkout flow

developer.mastercard.com/mastercard-checkout-solutions/documentation/use-cases/agent-pay · 5 steps · unrated

Design and enforce scoped payment credentials with spend controls for agent mandates using Stripe Shared Payment Tokens and OAuth-gated Link wallet authorization

docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens · 6 steps · unrated

Signal correct MIT/MOTO card network flags in Nekuda agent payment mandates to maximize authorization rates and ensure correct liability assignment

docs.nekuda.ai · 5 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans

Use the Nekuda SDK to create an agentic mandate that delegates scoped card payment credentials to an AI agent for autonomous checkout

Steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,600+ more routes

Need this verified for your stack — or a route we don't have yet?