Agentic payments, built for Africa

What are agentic payments?

Agentic payments are transactions initiated by AI agents on a customer's behalf - an assistant that researches a purchase, selects a supplier and completes payment within limits its owner set in advance. The human authorises once, up front, by granting a mandate; the agent executes, possibly many times, proving on each transaction that it is acting inside that mandate. It is a small change to describe and a large one to build for, because almost everything in today's payment flow assumes a human is present. Checkout pages assume eyes and a cursor. Fraud engines assume human browsing behaviour. 3-D Secure assumes there is a person to challenge. Agentic commerce replaces those assumptions with delegation designed in from the start: machine-readable storefronts, verifiable mandates, and settlement that software can complete without a form in sight.

How does the agentic protocol stack work?

By 2026 the landscape has settled into a layered stack rather than a single standard, and each layer does a different job.

Checkout - ACP and UCP. Checkout protocols define how an agent discovers products, prices, stock and delivery options, and how it assembles an order without scraping a web page built for human eyes. ACP and UCP are the two names to know; both exist to make a storefront legible to software, so an agent can compare and compose a basket the way a person compares tabs.

Authorisation - AP2. The mandate layer. AP2 defines how a customer's authorisation is captured as a signed, verifiable mandate - what the agent may buy, from whom, up to what value, until when - and how a merchant or payment provider checks that a specific transaction sits inside it. This is the layer that answers the question every risk team asks first: how do we know this agent is allowed to do this?

Settlement - x402. The payment itself. x402 revives HTTP status code 402, "Payment Required", left dormant in the web's specifications for three decades, so that payment becomes a native part of a web request. Software can pay for goods, data or API calls machine-to-machine, without redirecting anyone anywhere.

A payment provider that wants to serve agentic commerce properly has to speak all three layers - checkout, authorisation and settlement - because an agent arrives expecting the whole conversation, not a third of it.

Is agentic commerce real, or another hype cycle?

The honest answer: the signals have moved well past the whitepaper stage. x402 is now stewarded under the Linux Foundation - and neutral governance is what separates shared infrastructure from a single vendor's side project. Adyen shipped an agentic commerce suite in June 2026, and Stripe has been building agentic commerce tooling into its platform; when payment providers of that scale ship product rather than blog posts, the protocols have crossed from research into roadmap. Industry analysts project agent-influenced commerce reaching trillion-rand scale globally by 2030. Those are projections, not bookings, and early-stage forecasts are always generous - but the direction of every serious forecast is the same. Hype is when the story runs ahead of the infrastructure. Here the infrastructure - open protocols, neutral stewardship, live product from major providers - is being laid in public, and the story is barely keeping up.

What is LekkaPay building?

Our agentic capability is in development, and it is badged that way deliberately: precision about what is not yet live is what makes every other claim on this site worth trusting. Three things are on the bench.

Agent-readable checkout. A hosted checkout an agent can traverse - structured order, price and availability data, and a payment flow that completes without a human filling in a form - with the same tokenised, PCI DSS Level 1 card handling underneath that protects every LekkaPay transaction today.

Mandate verification. The machinery to accept, validate and store AP2-style mandates, so a merchant can prove that an agent-initiated payment was authorised by a real customer, within limits, before the money moved - and so disputes about delegation are settled by cryptography rather than correspondence.

Protocol interoperability. One integration that surfaces ACP, UCP, AP2 and x402 as each matures, so merchants are not forced to bet on a single protocol winning. The stack will shift over the next few years; your integration should not have to.

We also participate in the DAIAA Agentic Commerce working group, because standards are shaped by the people in the room - and African rails deserve a voice in that room.

What should merchants do now?

No bets are required yet, but three preparations cost little and pay off whichever protocols win.

Keep your product data machine-readable. Structured data, accurate feeds, consistent SKUs, prices and stock levels. Agents buy from storefronts they can parse; a catalogue that only makes sense to a human eye is invisible to them.

Adopt strong customer authentication that supports delegation. Tokenisation and 3-D Secure 2 are the foundations on which mandates will sit. If your payment setup already authenticates customers properly and stores credentials as tokens, you are most of the way to accepting a delegated payment safely.

Choose a payment provider that is building for this. Agentic readiness is not a plugin bolted on later - it reaches into checkout, risk and settlement. Ask your provider what they are doing about ACP, AP2 and x402, and listen for a specific answer.

Join the waitlist

Agentic payments at LekkaPay are in development, and the waitlist is where the first pilots will come from. Leave your details in the form below and we will keep you posted as capabilities move from bench to beta - no noise, just milestones. When merchants take their first agent-initiated payments, we intend the rails to be ready and the earliest merchants to be the ones reading this page now.