Start your implementation

1

Project kickoff and program configuration confirmation

Prerequisite: A contract has already been signed between MatchMove and the partner to integrate the MatchMove platform.

A dedicated MatchMove Implementation team will be assigned to assist you with building your embedded finance applications. The project kickoff will introduce the project roster between MatchMove and the partner. In addition, the partner use cases and MatchMove capabilities that must be enabled will be discussed during this meeting. We will finalize the platform configuration settings that will be applied to your custom platform instance (staging environment).

The MatchMove Implementation team will request technical items from you (such as IP addresses) in order to prepare your custom platform instance.

2

Staging environment preparation and configuration

Every partner will receive a custom platform instance that is tailored to the capabilities enabled in the program configuration. This custom platform instance will first be available on the staging environment and will only be accessible to the whitelisted partner IP addresses.

The MatchMove Implementation team will coordinate all activities with the internal MatchMove teams to build your custom platform instance.

3

Resources handover and start of technical implementation

Once the custom platform instance is live on the staging environment, the MatchMove Implementation team will hand over to the partner the following, among other things:

• API credentials to access the endpoint
• Private encryption keys that are required for some capabilities
• Access to the project communication channels
• Access to the project tracking dashboards and tools
• Access to internal technical resources

At this point, the partner can commence implementation, following:

The MatchMove Implementation team will also hold weekly project meetings to discuss technical issues and other topics until the project is completed.

4

Customer onboarding and compliance discussions

To ensure the partner aligns with the program's regulatory policies, customer onboarding requirements, and practices, the MatchMove Implementation team will also schedule discussions between the MatchMove Legal and Compliance teams and the partner. Matters involving onboarding customers from sanctioned and high-risk countries, requirements for translation of non-English documents, and the SOP for all scenarios involving user onboarding will be discussed in these meetings.

For the customer due diligence requirements required by the API, you can review the Regional-specific Onboarding section.

The MatchMove Legal and Compliance team will dictate all aspects regarding user onboarding.

5

Card design and setup (optional)

Before a card can be issued, several activities must be completed. These activities may include card design, card approval with the payment network, card ordering, card and stationery (card kit) printing, and card delivery. To help you with building your card products, the MatchMove Card Operations team will conduct discussions and guide you through all the required processes.

The MatchMove Card Operations discussions and card issuance activities will run in parallel alongside the technical implementation.

6

Technical and operational training

The partner will receive several trainings to help them understand the platform's processes and operations. These trainings will be required for you to perform platform operations once the application goes live. These trainings include, but are not limited to:

• Compliance standard operating procedures (SOP)
• Tooling and platform administration (e.g., AdminNet dashboard)
• Card ordering and delivery management
• Finance and settlement cycles (e.g., Reconciliation)
• Ticketing and support escalations

The MatchMove Implementation team will schedule these trainings based on the partner's needs and implementation progress.

7

Implementation security and completion verification

Implementation security focuses on conducting rigorous tests to identify and remediate security flaws within the API architecture before it goes live. Completion verification then serves as the final audit to ensure the API integration is functionally sound and that all identified security risks have been successfully mitigated.

8

Application demo and UAT sign-off

Before a partner can go live with their embedded finance application, an end-to-end demo (from user onboarding to issuance to test transactions) or a “show-and-tell” of the product they built will be required. This demo will be attended by all the MatchMove internal stakeholder teams involved in the project. The sign-off will focus on ensuring the following but is not limited to:

• All technical implementation requirements are completed and verified
• All regulatory requirements are met
• Risk communications to customers are handled properly
• The terms and conditions and other required legal disclaimers are displayed
• The card data are securely displayed and accessible
• The users are onboarded based on the agreed-upon methods

The MatchMove Implementation team will collect all feedback from the stakeholders. Depending on the feedback, the UAT sign-off may be given or delayed until any highlighted items are corrected.

9

Live environment resources handover

A snapshot of the outstanding program configuration in the staging environment will be taken, which includes the initial program configuration and any other changes applied during project implementation. This snapshot will be used to promote the staging instance to the live environment.

Since this will be the live environment, the following configurations will need to be reconfirmed:

• The final markup details that will be applied to financial transactions
• The production IP addresses that will be used to access the live environment
• The finalized branding resources that will be used on the platform
• The finalized sender ID that will be used for SMS messages (when required)

Once the staging environment has been promoted to the live environment, a new set of environment resources, such as API credentials and encryption keys, will be provided. The partner will need to use these new API credentials and point the endpoints to the production hostnames to gain access to the live environment. The same implementation codebase used in the staging environment should work for the new live environment.

Except for webhook subscriptions, which must be updated to point to your live environment's callback URL.

10

Closed beta testing on the live environment and project handover

MatchMove recommends that before the partner releases their new application to the general end-users, they should conduct a closed beta test with a select group of users. The following tests can be done on the closed beta stage:

• Test the user onboarding scenarios and validate if you are handling the events properly (e.g., user is risk-flagged, user gets KYC approved)
• Test the card transactions on the top merchants in the top regions where it will be used
• Test cross-border payout in the top regions where you expect your user base to transact
• Test the domestic payout on select local bank accounts
• Test the bank collections on any active virtual accounts
• Validate if you are receiving any of the webhooks that you have subscribed to

As the project approaches its implementation stage completion, the MatchMove Implementation team will begin to gradually hand over the project to the MatchMove Customer Growth team. Until the Customer Growth team achieves self-sufficiency and the program becomes stable.

The MatchMove ticketing platform will be your primary point of contact for incidents and platform-related questions.

The MatchMove Customer Growth team will serve as your advisor and helper to maintain and grow your program.

At this point, the program implementation is complete. If a new platform capability or product is added to the program, the cycle will start over from the project kickoff.