Platforms and operators Tailored programme

Your users pay without leaving your journey. The account, the envelope and the rule, carried by an authorised institution.

Your software already runs the business journey. MAP adds, for each user, an account, an envelope and the rule that frames it. Your service receives each payment, its status and the rule applied, the moment it happens.

Request a demo How it works

Example · booking services 1,200 users

Monthly budget: €300,000.00
Per user: €250.00
Spent: €86,500.00

Funds: Your customer
Spends: The end user
Receives: The journey’s providers

A service booked in your app accepted

A payment outside the journey declined

Amounts given as examples.

The starting point

Three frictions everyone knows.

They have nothing to do with the goodwill of your teams. It is the circuit that is badly laid out.

Holding the funds yourself is another business

Holding your customers’ money means a licence, ring-fencing and controls. That is not your product.

A means of payment sitting next to the journey

The user leaves your interface to pay, and all you receive is a statement with no link to your business logic.

Who is responsible for what stays vague

Your customer funds, the user spends, the provider gets paid. Without written roles, every incident turns into a negotiation.

Two professionals test a journey together on a mobile device with no readable content.

What you decide

Four settings, and the budget holds on its own.

You do not have to watch expenses one by one: whatever falls outside the frame is refused at the moment of payment.

See accounts and payments

The envelope per user

€250.00 per user per month, set by your customer or by your business logic.

The authorised services

The providers of your journey, listed by you, or a category of expenditure.

The timing of the payment

At booking, at the end of the service, over a period. The rule applies before every payment.

What your service receives

The status of each payment, the rule applied, reconciliation data, through the agreed interfaces.

Setting up

Four steps, and a single point of contact.

The timeline is set in the first conversation, depending on the number of beneficiaries and the exchanges with your information system.

See the integration

You describe the journey

Who funds, who spends, who gets paid, and what your service must receive. The roles are written down.

We settle the interfaces

The integration points, the responsibilities and the tests to run, with your engineering teams.

Accounts open from your product

Each user receives their account, their envelope and their card, without leaving your interface.

You receive every payment

Status, rule applied and reconciliation data reach your service, in real time.

On the accounting side, each payment arrives with its amount, its supplier, its date and the rule applied. Your exports can be used as they are for closing and for an audit.

Every integration is run with your teams, with no self-service route. The interfaces opened to your service, the contracts and the operating model are settled in the first conversation.

Get in touch

Thirty minutes to frame your programme.

Tell us who funds it, who uses the funds, and what the programme must make it possible to pay for.

Request a demo How it works An expert MAP gets back to you. No commitment.