Eligibility & due diligence
Business and participant information may be required to meet the onboarding and review obligations that apply to the proposed programme.
Responsible programme design
Responsibility starts before a card is issued.
The business, participants, intended use, fund flow and operating markets all influence whether—and how—a programme can proceed.
Responsible programme design
Make responsibility explicit before a card is issued.
Eligibility, governance, regulated roles and data duties belong inside the programme design from the start.
- 01 / Context
Proposed programme
- Business and participants
- Intended use and fund flow
- Entities and operating markets
- 02 / Governance
Owned decisions
- Eligibility and onboarding
- Oversight and exceptions
- Incidents and data responsibilities
- 03A / Review
Due-diligence readiness
Business and participant information is prepared for the checks that may apply.
- 03B / Operations
Programme responsibilities
Administration, use, support and review roles are agreed before launch.
- 04 / Regulated layer
Identified service entities
Where regulated services are required, responsible entities and terms are named in documentation.
- 05 / Readiness
Approval-aware decision
Availability follows only after required review, agreed responsibilities and applicable approval.
Designed into the programme
Four responsibilities to make explicit.
Responsible delivery is not a single approval at the end. It is the result of clear information, defined roles and an assessable operating structure from the beginning.
Programme governance
Roles, intended use, oversight, exceptions and incident responsibilities should be agreed before launch.
Regulated service roles
Where regulated services are required, the responsible regulated entity and applicable terms must be identified in programme documentation.
Data responsibilities
The information involved, the parties that handle it and the controls applying to an approved solution should be understood before implementation.
The review lens
The right questions reduce ambiguity.
Different businesses create different participation, funding and oversight requirements. The programme brief gives reviewers the information needed to understand that context.
BusinessWhat activity does the company perform?
ParticipantsWho owns, funds, administers and uses the programme?
PurposeWhat purchases or business activity should cards support?
MarketsWhich jurisdictions connect to the entities, users and intended use?
ResponsibilityWho oversees activity, exceptions and incidents?
Availability
No programme is available automatically.
Eligibility, jurisdiction, use case, programme structure and required approvals apply. Features described on this site are design considerations, not commitments for every programme.
Read the programme disclosuresCommon questions
Responsible by design.
Does a programme become available automatically after discovery?
No. Eligibility, jurisdiction, intended use, participating entities and required approvals all affect whether a programme can proceed.
Why does the proposed movement of funds matter?
Fund flow helps the relevant parties understand who provides money, who controls allocation, how cards are used and which responsibilities may apply.
When are regulated service providers identified?
The entities responsible for issuance and any regulated payment services, where applicable, are identified in the programme documentation before onboarding.
What information is needed at first contact?
Begin with high-level company, operating-model, use-case and market information. Do not send cardholder personal data or account credentials through the website.
Programme discovery
Bring responsible design into the first programme conversation.
Tell us how your company operates, who needs to pay or get paid and what the solution should achieve.
Discuss programme requirements