The programme path

From business model to programme blueprint.

A clear process to determine what is needed, what may be feasible and what must be approved.

A business team reviewing plans around a shared table

Programme path

Move from discovery to a controlled launch decision.

Each stage turns business context into a clearer scope, responsibility model and implementation plan.

  1. 01 / Discover

    Operating model brief

    • Entities and participants
    • Use cases and markets
    • Proposed movement of funds
  2. 02 / Design

    Programme blueprint

    • Funding and decision roles
    • Control and reporting needs
    • Exceptions and governance
  3. 03A / Review

    Feasibility assessment

    Eligibility, due diligence, risk, technical and commercial dependencies are considered.

  4. 03B / Plan

    Implementation scope

    Onboarding, configuration and acceptance activity are planned only after approval.

  5. 04 / Readiness

    Responsible parties

    Programme, provider and business owners confirm launch criteria and support responsibilities.

  6. 05 / Output

    Controlled launch path

    Decisions, documentation and open dependencies remain visible before availability.

Illustrative programme-development flow. Review may result in changes or no current route, and launch depends on approval and agreed service documents.

Five clear stages

Define before you configure.

Every programme depends on the business, intended use, jurisdictions and approved service providers. The work starts by making those dependencies explicit.

01

Discover the operating model

We document the company, participating entities, intended users, use case, markets and proposed movement of funds.

OutputA shared discovery brief

02

Design the programme structure

Requirements are translated into funding roles, responsibilities, desired controls, reporting needs and exception paths.

OutputA proposed programme blueprint

03

Review feasibility

The proposed programme is assessed for eligibility, due diligence, risk, technical and commercial feasibility.

OutputA documented scope decision

04

Plan implementation

Once the approach is approved and agreed, onboarding, configuration, responsibilities and acceptance activities are planned.

OutputAn implementation plan

05

Prepare for launch

Launch criteria, support responsibilities, programme documentation and operational readiness are confirmed before availability.

OutputA controlled launch path

The blueprint

One document, four connected views.

A well-defined programme should make the operating logic understandable to finance, operations and the relevant providers.

01

Participants

Who owns, administers, funds and uses the programme.

02

Purpose

What business activity the cards support and where exceptions sit.

03

Fund flow

How funds enter, move through and leave the proposed structure.

04

Governance

How responsibility, oversight and incident handling are divided.

Prepare for discovery

What to bring to the first conversation.

High-level business information is enough to begin. Do not send personal cardholder data, card numbers, account credentials or sensitive financial information.

01

Business structure

The legal entities, ownership context and business activity relevant to the proposed programme.

02

Intended users

The employee, contractor, participant, site or other cardholder groups involved.

03

Purpose of cards

The business purchases or operating activity the programme is expected to support.

04

Target markets

The countries connected to the business, participants and intended card use.

05

Proposed fund flow

Where programme funds originate, who allocates them and how responsibilities are divided.

06

Programme shape

An estimated number or range of users, expected timeline and important operational constraints.

Questions

Programme basics.

Who provides card issuance and regulated payment services?

The entities responsible for card issuance and any regulated payment services, where applicable, will be identified in the programme documentation provided before onboarding.

Where are programmes available?

Availability is assessed case by case and depends on the business, intended use, participants, jurisdiction and required approvals.

Can a programme be customised?

We assess business requirements and define a proposed programme structure. The final configuration depends on the solution approved for that programme.

How long does launch take?

Timing depends on programme scope, due diligence, technical requirements and approvals. A realistic plan can be set after discovery.

What does it cost?

Commercial terms depend on the approved programme scope and are provided during the proposal process.

Begin with discovery

Bring us the operating model. We’ll help structure the questions.

Tell us how your company operates, who needs to pay or get paid and what the solution should achieve.

Start programme discovery