Skip to main content
For banks and PSPs

Two ways to work with us. Our agent layer in your product, or your rails under ours.

Your customers' agents are starting to buy on their own. Pick the side that fits you.

Talk to usRead the docs
White label

In your product

Agent spending under your brand. We run policy, control and audit behind it.

Your rails

On your rails

Our customers' agents spend through your accounts and cards.

Four ways in

Cards or accounts, your brand or ours.

Yours
Nevermined

In your product

For PSPs, wallets, banks, issuers

  1. Your app
    (yours)
  2. Nevermined
    (Nevermined)
  3. Your cards
    (yours)

Cards

Cardholders set a spend mandate on their card, in your app.

  1. Your app
    (yours)
  2. Nevermined
    (Nevermined)
  3. Your accounts
    (yours)

Bank accounts

Customers set a spend mandate on their account, in your app.

On your rails

For Banks and issuers

  1. Our customers' agents
    (Nevermined)
  2. Nevermined
    (Nevermined)
  3. Your cards
    (yours)

Cards

Our customers' agents spend on your cards.

Visa today · Mastercard coming
  1. Our customers' agents
    (Nevermined)
  2. Nevermined
    (Nevermined)
  3. Your accounts
    (yours)

Bank accounts

Your accounts power our wallets, in the customer's name.

In every cell the money stays with you. Nevermined is the policy and control layer.

Talk to us

How it plugs in

Five steps. Your customer never leaves your product.

Your backend talks to ours, server to server. You keep the customer and the money; we hold the mandate, check every purchase against it and record it.

Your customer revokes the mandate in one action and every credential under it stops at once.

Example flow · illustrative amounts

Your product and rails
Nevermined

  1. Step 1: Your customer sets a spend mandate

    In your product, under your brand, with your own identifier for the customer. No sign-up with us.

  2. Step 2: The agent asks to buy

    It presents the credential your backend holds for it: one thing, one price.

  3. Step 3: We check it against the mandate and record it

    Recorded before anything moves. Outside the mandate, it stops here and nothing is charged.

  4. Step 4: Your rails move the money

    On a card you issued or an account you hold. We never hold it.

  5. Step 5: The receipt comes back to your product

    Who bought what, for how much, under which mandate.

What your team checks first

The networks we build on, and the reports your security team will ask for.

Cards run on the networks your customers already carry. The controls around them are audited, and the reports are ready to share.

Security and reports

Card networks

  • Live in productionBuilt on Visa Intelligent CommerceWave 1 design partner, first in production globally.
  • ComingMastercard Agent PayInitial participant at the June 2026 launch.

Assurance

  • CertifiedISO/IEC 27001An audited information security management system.
  • Report under NDASOC 2 Type IISecurity, availability and confidentiality, independently audited.
  • SAQ-DPCICard data is captured and tokenized by a PCI Level 1 vault. We never store card numbers.
The pilot

A pilot needs four answers, not a committee.

We stand up a working integration against a sandbox in days. Four answers shape it.

  1. 01RailCards, bank accounts, or both.
  2. 02WayOur layer inside your product, or your rails under ours.
  3. 03IdentityYour own customer identifier, or an address you already hold.
  4. 04BrandInvisible behind your front end, or a feature you name and market yourself.
Week oneexample
  1. Day 1Sandbox keys issuedyour stack, our APIs
  2. Day 2First mandate createdamount · expiry · purchases
  3. Day 3First purchase settledon your rails, recorded
  4. Day 5Audit export reviewedby your team

Example. The shape of a first integration, not a schedule.

The first integration is a sandbox and a week, not a programme.

Talk to usOpens a calendar in a new tab.