YourMoneyRules
Join early access

In development

Product design | In development

A clear chain of authority, from instruction to payment.

YMR is being built to connect what you asked an agent to do with what it is allowed to spend and what actually happens. Every stage has a role in keeping that authority bounded and visible.

The chain of authority

From instruction to payment

Six stages, one bounded authority.

  1. Know the owner and the agent.

    Each agent is linked to a verified individual or business. That link establishes whose authority the agent is using and who can change or revoke it.

  2. Sign the spending rules.

    The owner sets a mandate covering permitted actions, recipients, budgets, expiry and approval requirements. The agent works within that signed authority. Requests outside it require new owner authority.

  3. Check the proposal independently.

    YMR checks the proposed action against the mandate and relevant controls, including available budget, approval requirements and stop status. The agent requesting a payment does not get to decide whether its own request is permitted. Where policy allows an action without a fresh human signature, a separate verify-only agent works alongside deterministic rules and cannot expand the mandate.

  4. Get the required signatures.

    The proposed Signer app lets authorised people review and sign where the policy requires it. A business can define the approvers and thresholds that suit its responsibilities.

  5. Limit how the payment can happen.

    Depending on the supported route, payment execution can use a restricted single-use card credential or a specifically authorised transfer. Restrictions such as amount, recipient and expiry depend on what the provider can enforce. In the initial bank workflow, a named person releases the prepared payment inside their bank.

  6. Monitor, stop and keep the record.

    Monitoring can pause further authority when a problem is detected. Owners can stop an agent and revoke unused credentials where supported. Signed records connect the instruction, mandate, approvals and payment outcome, making it possible to inspect who authorised what.

Your money stays under your control.

The intended design keeps fiat funds with your bank or payment provider. For cryptocurrency payments, the owner's signing key remains under their control in the Signer app, separate from the agent's identity key. YMR coordinates authority and execution across these routes.

What stopping an agent means.

A stop action is intended to block further payment authority and revoke unused credentials where a provider supports it. It cannot undo a completed payment, and an action already in flight may not be recoverable. The interface will distinguish a requested stop from a confirmed provider response.

Development status

Built in stages, with a clear starting point.

Existing foundation

ARNEL's agent governance and execution functionality.

In development

YMR's payment mandates, Signer experience, payment-specific evidence and provider integrations.

Initial workflow and expansion

Assisted bank payments first, with delegated card and cryptocurrency routes introduced as the relevant arrangements and controls are established.

Common questions

Questions about YMR

The full set of questions about YMR's development, controls and scope.

Can I use YMR today?

YMR is in development. You can register your interest in early access or a partnership conversation. ARNEL provides the existing core functionality; payment-specific features and integrations are being developed around it.

Is YMR only for cryptocurrency?

No. YMR is being designed for payment work across supported banks, card providers and crypto wallets. The initial bank workflow keeps payment release with a named person inside their bank. Other routes will depend on the relevant integrations and arrangements.

Will YMR hold my money?

The intended model keeps fiat funds with your bank or payment provider and cryptocurrency signing keys under your control. YMR manages the rules, authority and execution process around supported payment routes.

Do I have to approve every payment?

Approval requirements follow the signed mandate and the supported workflow. You can require human signatures for specified actions. Where a policy permits action without a fresh signature, independent verification and deterministic controls still apply. An agent cannot grant itself more authority.

Can I stop an agent?

YMR is being designed to stop further payment authority and revoke unused credentials where supported. A stop action cannot undo completed payments, and recovery of an action already in flight is not guaranteed.

Does it work with every agent, bank and wallet?

YMR is intended to work across providers through supported connections. Availability will be introduced through pilot and integration arrangements. Register your interest and tell us which agent or payment provider matters to you.

What is ARNEL's role?

ARNEL is the existing agent governance and execution foundation on which YMR is built. YMR extends that core functionality into payment-specific authority, approval, execution and evidence.

Who is YMR for?

Individuals who want agents to handle defined payment tasks, businesses that want to reduce payment administration, and prospective operators who want to offer controlled agent payments to their own customers.

What will it cost?

Subscription plans are envisaged for individuals and businesses, with separate arrangements for operator deployments. Pricing and any applicable provider fees will be explained before customers commit to using a service.

Be part of YMR's first workflows.

Register your interest as an individual, business or potential partner.

Join early access