Payment Gateway
Roles in Agentic Card Payments Explained (Part 4 of 5)
.png)
TL;DR
EMVCo's draft framework defines roles, not companies, and one firm can hold several. It covers the consumer, agent, wallet, payment credential provider, payment system, Intent Service Provider, merchant and acquirer. Each may use the approved intent differently, from checking a cart to resolving a dispute, while keeping its own risk decisions.
Agentic Payments Series, Part 4: Who Does What in an Agentic Card Payment
How each participant might use the intent
The framework walks through how different parties may rely on the same approved intent at different moments:
- The agent tracks the instruction and lets the consumer view, change or cancel it.
- The wallet prompts the consumer to approve, which creates the intent.
- The merchant can check that the checkout matches what was approved.
- The payment system, token service provider or issuer can check that a request for payment credentials fits within the approved limits, and set controls for authorisation.
- The 3-D Secure directory service can confirm the consumer already approved the payment, which may avoid asking the consumer to act again.
- In a dispute, the consumer, issuer, merchant, acquirer and payment system can refer to the intent.
What changes for merchants
The framework states that the merchant's role does not fundamentally change. Merchants still handle product selection, shipping, tax and payment. What is new is extra context: merchants may choose to tell apart human and agent shoppers, and in autonomous purchases they can see what the consumer approved.
Where each party draws the line
The framework leaves decisions with each participant. It defines what the shared concepts mean, but issuers, networks and merchants each apply their own risk models and rules when acting on them. Liability, dispute procedures and scheme rules are outside its scope.
.png)
.png)
.png)
.png)