Discover the operating model
We document the company, participating entities, intended users, use case, markets and proposed movement of funds.
OutputA shared discovery brief
The programme path
A clear process to determine what is needed, what may be feasible and what must be approved.

Programme path
Each stage turns business context into a clearer scope, responsibility model and implementation plan.
Eligibility, due diligence, risk, technical and commercial dependencies are considered.
Onboarding, configuration and acceptance activity are planned only after approval.
Programme, provider and business owners confirm launch criteria and support responsibilities.
Decisions, documentation and open dependencies remain visible before availability.
Five clear stages
Every programme depends on the business, intended use, jurisdictions and approved service providers. The work starts by making those dependencies explicit.
We document the company, participating entities, intended users, use case, markets and proposed movement of funds.
OutputA shared discovery brief
Requirements are translated into funding roles, responsibilities, desired controls, reporting needs and exception paths.
OutputA proposed programme blueprint
The proposed programme is assessed for eligibility, due diligence, risk, technical and commercial feasibility.
OutputA documented scope decision
Once the approach is approved and agreed, onboarding, configuration, responsibilities and acceptance activities are planned.
OutputAn implementation plan
Launch criteria, support responsibilities, programme documentation and operational readiness are confirmed before availability.
OutputA controlled launch path
The blueprint
A well-defined programme should make the operating logic understandable to finance, operations and the relevant providers.
Who owns, administers, funds and uses the programme.
What business activity the cards support and where exceptions sit.
How funds enter, move through and leave the proposed structure.
How responsibility, oversight and incident handling are divided.
Prepare for discovery
High-level business information is enough to begin. Do not send personal cardholder data, card numbers, account credentials or sensitive financial information.
The legal entities, ownership context and business activity relevant to the proposed programme.
The employee, contractor, participant, site or other cardholder groups involved.
The business purchases or operating activity the programme is expected to support.
The countries connected to the business, participants and intended card use.
Where programme funds originate, who allocates them and how responsibilities are divided.
An estimated number or range of users, expected timeline and important operational constraints.
Questions
The entities responsible for card issuance and any regulated payment services, where applicable, will be identified in the programme documentation provided before onboarding.
Availability is assessed case by case and depends on the business, intended use, participants, jurisdiction and required approvals.
We assess business requirements and define a proposed programme structure. The final configuration depends on the solution approved for that programme.
Timing depends on programme scope, due diligence, technical requirements and approvals. A realistic plan can be set after discovery.
Commercial terms depend on the approved programme scope and are provided during the proposal process.
Begin with discovery
Tell us how your company operates, who needs to pay or get paid and what the solution should achieve.
Start programme discovery