MNNR is authorization and evidence infrastructure for agent-initiated payment workflows. It identifies actors, binds mandates, evaluates transaction intents against policy, and preserves decision evidence above existing payment infrastructure. MNNR does not move or custody money, issue cards, or replace a payment processor.

Does MNNR move money or settle payments?

No. MNNR evaluates whether an agent-initiated transaction intent is authorized under its mandate and policy, records the decision with reason codes, and exports evidence. Payment execution remains with your existing payment infrastructure.

Is MNNR compliant with PSD3, MiCA, or GDPR?

MNNR provides PSD3/PSR-aligned authorization controls and is designed to support MiCA and EUDI Wallet trajectories, with privacy-by-design data handling. MNNR does not certify compliance or guarantee regulatory outcomes; compliance determinations remain with the customer.

What does MNNR record for audit purposes?

Each evaluated transaction intent produces a decision record with reason codes, the policy and mandate versions applied, and an exportable evidence package (JSON or CSV) for internal oversight and review.

Use cases

Put authority between agent intent andfinancial execution.

MNNR is designed for workflows where software proposes a financial action on behalf of a person or organization and the decision must remain bounded, explainable, and attributable.

Common patterns

One decision boundary, multiple workflows.

These are authorization patterns, not claims that MNNR moves money or supplies the underlying commerce network.

Agent-initiated purchasing

May this agent buy this item now?

Resolve the agent and principal, validate its mandate, and evaluate amount, merchant, category, timing, and approval limits before a payment instruction is released.

A bounded decision and an attributable record

Enterprise procurement

Does this request fit delegated company authority?

Translate procurement policy into decision controls so an agent can operate within approved vendors, cost centers, budgets, and escalation requirements.

Policy enforcement without an open-ended credential

Delegated financial actions

Who granted permission, and for what purpose?

Bind a machine actor to a human or organizational principal through a scoped, time-bounded mandate that can be suspended, replaced, or revoked.

Authority that remains attributable and controllable

Evidence-sensitive workflows

Can the decision be reconstructed later?

Preserve the actor, mandate, policy version, normalized intent, outcome, and reason codes for audit, investigation, dispute, and oversight workflows.

Decision evidence without custodying funds

Reference flow

The same five questions should follow every proposed action.

01Actor
02Mandate
03Intent
04Policy decision
05Evidence

MNNR evaluates and records the authorization decision. Payment, settlement, custody, and legal compliance remain with the appropriate providers and responsible organizations.

Design partner program

Have a real authorization boundary to define?

Start with a scoped workflow, explicit principals and actors, a bounded mandate, and the evidence your organization needs to retain.

Request pilot access Read the quick start