B2B & procurement

Company mandate and signing authority verification

The proposed European Business Wallet turns that chain into credentials. A mandate states which person may act for which entity, within what scope, until when, signed by the registry or the company. You verify entity, representative and scope in one step, then accept a qualified signature that carries the mandate with it. The proposal landed in November 2025, so this is a build-ahead rather than something live.

The problem

What teams do today

Accepting a bid means answering a genuinely hard question: can this person bind that company. Today the answer is a chain of PDFs. A registry extract, a board resolution, a power of attorney, assembled by hand, often in a language the buyer does not read, and almost never rechecked before countersigning.

01
Signing authority confirmed by data, not by a stack of translated PDFs
02
Out-of-scope signatures fail before a bid enters evaluation
03
Cross-border suppliers verify through the same path as domestic ones
How it works

Three steps with Authbound

  1. Step 01

    Verify the entity

    Request the legal entity identifier and registry attributes to confirm the company exists and is in good standing.

  2. Step 02

    Verify the mandate

    The representative presents a mandate credential with scope and validity, signed by the entity or the registry.

  3. Step 03

    Accept a bound signature

    The bid or contract is signed with a qualified signature linked to that verified mandate.

Rules in play

European Business Wallet proposal COM(2025) 838, EU public procurement directives

Live demo

We built Mandator, a company that does not exist, to show this running inside a finished product. The wallet flow in it is the real SDK.

Open the Mandator demo
Questions

What people ask

What is the European Business Wallet?
A wallet for legal entities, carrying registry attributes, mandates and company seals so authority to act can be checked digitally instead of on paper. It is a separate draft regulation, COM(2025) 838, published in November 2025, not part of eIDAS 2.0 and not yet law. Timelines can still move.
How is a mandate credential better than a PDF?
It is machine readable, signed by the issuer, scoped, and revocable. A PDF power of attorney has to be read, translated and trusted, and nothing in it tells you when it was withdrawn.
Can we restrict which mandate scopes we accept?
Yes. Scope is a structured field, so your procurement rules can require a specific mandate type and reject anything narrower automatically.

Built on Authbound Digital Signatures. One API key covers every flow you add later.