Commerce

Subscriptions and utilities

Recurring payments already have mandates; agents make them change more often.

Utilities and subscription businesses rely on recurring payments, and agents now switch tariffs, cancel services and move payments between providers for their users. Variable recurring payments in UK open banking let a customer set parameters within which payments run without authenticating each one. AgenticOpenFinance keeps each agent's changes inside the customer's parameters and records them.

What agents do

What you build on AgenticOpenFinance

1

Parameters per payee

Maximum per payment, per period and an end date are set once and checked on every collection.

2

Switching under mandate

An agent may switch a tariff or cancel a subscription only within the action classes the customer allowed.

3

Change notices

Every change the agent makes is sent to the customer with a one-step undo where the provider allows it.

4

Failed-payment handling

Retries respect business days and the mandate, and stop when the customer revokes.

5

Evidence for complaints

Each collection and each change keeps the mandate and verdict for complaint handling.

Value chain

The actors in this chain

AgenticOpenFinance connects them with one identity check, one mandate model, one policy and one evidence trail.

CustomerCustomer's agentUtility or subscription businessBankPayment provider

Regulators and standards in the directory

Typical flow

A governed agent flow, step by step

  1. Customer sets parameters
  2. Agent reviews bills and plans
  3. Change proposed
  4. Policy check
  5. Payment or switch within parameters
  6. Customer notified
  7. Evidence sealed

Live demo

See it in the terminal

A sweep agent keeps the operating account above its minimum, within its mandate (demo). Demo data

DemoAll companies, people, agents and amounts are fictional. Protocol names refer to public specifications; naming one is not a partnership or an endorsement.

Build Subscriptions and utilities on AgenticOpenFinance.