Skip to main content
A Stamped Mandate can express any authorisation that fits its language: what an agent may do, on what, within what limits, for whom and until when. The first four use cases on this page are the ones Sumvin supports or is rolling out. The ones under More use cases follow. They are examples, not a complete list.
Today an agent can ask you to sign a spending mandate. The payments it authorises are coming soon. The other use cases are rolling out, and each is labelled below.

Share your data

Private preview Let an agent tell a merchant or provider something true about you, and nothing more. The mandate names exactly what is shared and with whom.
  • That you are verified. The merchant learns your identity verification status. It doesn’t learn your name or documents.
  • That you are over 18. The merchant learns that one fact.
  • Your verified identity details. For a provider that has to hold them, such as one that would otherwise ask you to verify again. You sign for this separately, and the mandate says why the details are shared and who receives them.
Identity verification is carried out by Sumsub.
Scopes
See Examples.

Read open-banking data

Private preview Let an agent link your accounts through Meld and read your balances and transactions, limited to a date range if you want. Writing through Meld, such as initiating a transfer, is planned and not available yet.
Scopes
See Examples.

Prove a person sent the agent

Private preview Sites that take bookings, reservations and tickets block automated traffic to stop abuse. As more people send agents to do these jobs, a site can’t tell a person’s agent from a bot farm, and one blanket ID per AI assistant would not tell it which person is behind a given request. A mandate lets the request say it directly: a verified person asked this agent to come here. Your agent presents a mandate that carries proof of personhood and is addressed to that site by its hostname. It travels with the agent’s request, in the x-sumvin-pint-token header. The site checks, on its own server, that a real, verified person approved it and that it is addressed to that site. It doesn’t learn who you are. An online check that it still stands is coming soon. “Book a steakhouse for dinner on Friday” becomes a request the restaurant’s booking system can check, rather than one it has to guess about.
Scope, addressed to a site
See Examples.

Make purchases

Coming soon
Coming soon: payments arrive in a fast-follow release.
Let an agent buy something within a ceiling you set, in a currency you name, until an expiry. Purchases run as errands. Sumvin is a Visa Intelligent Commerce Launch Partner, and errands are built on Visa Intelligent Commerce. Payments aren’t part of this preview: they arrive in a fast-follow release, with its own waitlist. You can add conditions, such as a target price, that must hold before the purchase goes ahead.
Scopes
See Examples.

More use cases

The same language covers more than the four above. Each use case below is labelled with where it stands.

Prove your age or eligibility

Private preview Let an agent show a site that you meet a requirement, such as being over 18, without handing over your date of birth or your documents. The site learns the one fact it needs, and that a verified person stands behind it.

Reuse your verification to open an account

Private preview Opening an account with a provider usually means verifying your identity again. A mandate lets you share the verification you have already completed with that provider, for that purpose, so you don’t repeat it. You sign for each provider separately, and the mandate says who receives your details and why.

Manage subscriptions

Coming soon Let an agent look after your subscriptions: start one within limits you set, keep track of renewals, and cancel one when you ask. The mandate sets which services it may act on, how much it may commit you to, and until when.

Pass a narrower mandate to another agent

Coming soon An agent can hand a narrower mandate to another agent. The second agent can do less than the first, never more, and everything still traces back to what you signed.

Refunds and support requests

Coming soon Let an agent ask a merchant for a refund or raise a support request for you. The mandate shows the merchant that you sent the agent and what it may ask for, so the request can be handled without you repeating yourself.

Better treatment for verified agents

Coming soon A site can choose to treat an agent that carries a mandate differently from anonymous automated traffic, for example by letting it through where it would otherwise be blocked, or by offering it the same terms a signed-in customer gets. The site decides what it offers; the mandate gives it something it can check.

Share trip details for one journey

Coming soon Let an agent share the details a trip needs, such as traveller names or loyalty numbers, with the airline, hotel or booking site handling that journey, and nobody else. The mandate limits what is shared, with whom, and for how long.

Spending mandates for a business

Coming soon Let a business give its agents spending authority with the same controls a person has: a ceiling, a currency, the kinds of purchase allowed, and an expiry. Each agent’s authority stays within what the business signed.

A language others can extend

The scopes and resources on these pages form a small, open language. It will be open-sourced soon, so that others can propose and contribute new use cases.

Next

The mandate language

How a mandate is written.

Examples

A worked mandate for each use case.