Strong customer authentication when an agent initiates the payment
PSD2 and the UK regulations require strong authentication with dynamic linking for remote payments, including through initiation services. Where an agent fits in that.
AgenticOpenFinance blog
A weekly topic every Monday, the parallel series on their own weekdays and a monthly report with business days for the UK, US, euro area, India, China, Singapore and Australia, each with its official or specification sources.
PSD2 and the UK regulations require strong authentication with dynamic linking for remote payments, including through initiation services. Where an agent fits in that.
Elicitation lets an MCP server ask the user for input. The specification forbids form mode for payment credentials and requires URL mode instead.
Payment liability rules were written for people, not agents. Here is how unauthorised transactions, errors and scams are allocated today, and where agents create open questions.
MIT permits almost everything and has one condition: keep the copyright and licence notice in all copies. This episode looks closely at that one condition.
Agents can pay with scheme tokens, with account-to-account payments, or under a variable recurring payment consent. How each carries limits, and where each is still emerging.
How an MCP server reached over HTTP asks for tokens, why tokens must be issued for that server, and what this means for an account-data server.
Approval steps protect customers only if they are rare, specific and strong. Decoupled authentication lets an agent pause and ask a person for a recorded decision.
Permissive licences such as MIT allow almost any use; copyleft licences such as the GPL require modified versions to stay under the same terms when distributed.
Payment law already lets consent travel through a payee or an initiation service. Protocol tokens and mandates add limits that the payment provider can enforce.
The MCP tools specification expects a human in the loop who can deny a call. What that means for a tool that moves money.
Payment rails already support bounded, standing authority. Variable recurring payments and capped tokens show how limits can be enforced by the provider, not the agent.
A public repository without a licence file grants no right to use or modify the code. Why that is, and what to do when you meet one.
We email you when we announce an event or publish an important guide or report. A few times a month at most.