Payments and rules
Test an authorised purchase, then a decline for a category, supplier, ceiling, period or geographic area outside the rules.
Integration and deployment
From scoping to launch, a journey prepared together
Your organisation and MAP define the services, rules, interfaces and responsibilities. Testing verifies the complete journey before it is opened to users.
Integration and deployment
Project stages
Each stage clarifies what will be put in place and what the next stage needs.
Five milestones, from the first conversation to going live, each with what it puts in writing. The first conversation: a shared note. Services and interfaces: what is covered, settled and written down. Who does what: a written allocation, carried into the contract. The tests before launch: shared, signed tests. Operation: the MAP account in service.
Who does whatThe allocation is defined with your teams and reflected in the contractual framework.
- Your organisation
It defines the need, budgets, eligible users and rules. It prepares the data and support for its network.
- MAP
MAP handles the selected financial services, account management and application of the agreed rules.
- Technical teams
They document exchanges, implement connections within their scope and jointly validate operating scenarios.
What acceptance testing checks
Testing before launch
Acceptance testing covers authorised operations, expected declines and visibility for each role.
Accounts and balances
Check opening, allocation, debiting after payment, refunds and available balances.
Rights and reporting
Verify what users, organisations and funders can see, together with the agreed tables and exports.
Each stage in detail
Launch covers the scope validated during testing.
Scoping
Users, funders, suppliers, rules of use and information to be reported.
Integration
Selected services, journeys under your brand or with MAP, data exchanged and interfaces required.
Launch preparation
Accounts, permissions, means of payment, test scenarios and support for your teams.
Going live
Approve the launch. Confirm scope, settings, access, contacts and support arrangements.
Open to users. Activate the planned accounts and means of payment, then support the first operations.
Monitor operation. Track operations, handle requests and organise adjustments with your teams.
Your project
Define how your solution will work with us
Tell us about your users, money flows and requirements. We define the appropriate services and journey.