pay.2nth.ai Tree ai strategy-advisor
ai · Strategy advisor · Leaf

The advisor that frames the decision.

For the person who owns the payments P&L. A proposed agent that turns the rails, scheme economics and market-entry questions into structured options — grounded in a moderated knowledge base, not a model’s imagination. It frames the trade-off; the executive still makes the call.

Strategy advisor Proposed Executive Grounded Human-in-the-loop

A decision-framing agent for Heads of Payments.

Proposed — not yet live

This agent is part of a proposed roster of four role agents for payments executives and consulting teams. It is scoped here so partners can pressure-test the brief before any of it is built. The one agent that is live today is the research & regulatory-watch agent — the editorial engine that keeps the knowledge base these role agents would read from current and human-moderated.

A Head or Chief of Payments spends their week on a small set of high-stakes questions: which rail to back, which market to enter, whether the scheme economics work, and whether to build or buy. The answers are scattered across regulation, scheme rules, interchange tables and hard-won market knowledge.

The strategy advisor is a proposed agent that compresses the research half of that work. It reasons over the pay.2nth.ai tree — modes, rails, regions — to lay out the options, the trade-offs and the sources behind each one. It does not pick the strategy. It frames the decision so the executive can make it faster and with the receipts in hand.

Retrieve the tree, frame the options, cite the source.

The agent is a thin reasoning layer over a thick, moderated knowledge base. It does not free-associate; it retrieves expert-approved leaves, reasons over them, cites the source, and hands a draft to a human.

// Strategy advisor — a framing loop, not an oracle

1. ASK      “Should we back PayShap or stay card-first for SME payouts?”
2. RETRIEVE pull the relevant leaves: rails/, modes/payouts,
            regions/south-africa, scheme economics
3. FRAME    lay out options × trade-offs (cost, speed, reach,
            regulatory load, build effort) with sources cited
4. STRESS   surface the counter-case and the unknowns —
            not just the recommendation
5. HAND OFF the executive decides; the agent never commits
            the business to a rail or a spend

null

The owner of the payments P&L.

Heads / Chiefs of Payments

The person accountable for rail selection, scheme relationships and the cost of payments across the business.

Strategy & corp-dev teams

Building the market-entry or build-vs-buy case who need the payments landscape framed quickly and defensibly.

Consulting leads

Running an advisory engagement who want a first-pass structure before the senior partner’s time is spent. Pairs with the consulting analyst.

The four questions it is scoped for.

Rails selection

Card vs instant vs account-to-account vs wallet for a given flow — framed on cost, settlement speed, reach and reversibility.

Market entry

What it takes to launch in a market: licensing, dominant rails, local schemes, regulator posture. Grounded in the regions tree.

Scheme economics

Interchange, scheme fees and interchange++ pass-through modelled at a structural level — the shape of the economics, not a priced quote.

Build vs buy

Processor / orchestration / PayFac options framed against in-house build, with the regulatory and certification load made explicit.

Moderated content, not the open web.

The pay.2nth.ai tree

Every leaf in this surface — modes, rails, regions, compliance, training — is the agent’s primary context. It reasons over expert-approved content, not the open web.

Human-moderated provenance

Each leaf carries a named reviewer and a review date. The agent inherits that provenance: it can only stand on content a domain-expert partner has signed off.

Primary sources, not vibes

Regulator directives, scheme bulletins and standards bodies are cited inline. The agent surfaces the source so the human can check it — never “trust me”.

Modes, rails & regions

The advisor’s working memory is the pay.2nth.ai modes, rails and regions leaves — the same content a domain-expert partner reviews.

Strategy framing is not a fiduciary decision.

An advisor that frames options well can still be confidently wrong about a number or a rule. In a regulated, capital-committing context, these are the lines the agent does not cross alone:

Never a board recommendation on its own

A rail bet or a market entry commits capital and reputation. The agent frames it; a human executive owns the decision and the consequence.

Pricing is structural, not a quote

Interchange and scheme-fee economics shift and are commercially negotiated. Treat the agent’s numbers as shape, never as a contracted rate.

Regulatory interpretation is not legal advice

Whether a licence is required for a flow is a legal call. The agent points at the directive; a qualified human interprets it.

It does not move money or commit spend

No agent in this roster initiates a transaction, signs a scheme contract or authorises spend. Money movement stays with accountable humans.

And when to phone a human first.

Reach for it when you need the payments landscape framed fast — the options, the trade-offs and the sources — before a strategy session, a board paper or a vendor conversation. It turns a week of desk research into a structured starting point you can interrogate.

Do not lead with it when the decision is already down to a contract, a licence application or a number that will be quoted to a board. There, the agent’s output is an input to a human expert, not the answer. The cost of being wrong — a mis-chosen rail, a missed licensing requirement — is measured in years and rands, so the human gate is the point, not the friction.

The honest external framing is unchanged: this is “scaffolding and testing with customers who are looking to get into production” — a proposed agent on a moderated tree, not a finished advisory product.

Where this sits in the tree.

Primary sources behind the model strategy.