Demo and go-live checklist
Learn how to verify the mandatory UAT exit criteria and operational benchmarks required for formal stakeholder sign-off. This checklist ensures that all functional, security, and regulatory requirements are fully validated to guarantee the integrity of the program before it moves to production.
Partner product demo
Before a staging program is promoted and granted access to the production environment. A partner product demo showcasing the various workflows on how a user or customer can gain access to the financial capabilities of the platform will be required. This demo can be a live demonstration through a conference call or a recorded video.
The partner product demo will be reviewed by all the stakeholders of the program, which include, but are not limited to, the MatchMove Technical, Implementations, Compliance, Finance, and Card Operations teams. This final review is to ensure that all best practices and required guidelines for a financial product or application have been met.
After the demo and review have been concluded, a UAT exit form will be signed by the partner and MatchMove, indicating that the program is now cleared to move to production. This will commence all the activities required to promote the staging environment to production.
To aid the demo submission process, listed below are the items included in, but not limited to, the review:
Onboarding | ☐ As per payment regulatory guidelines, partners and extension partners integrated in the MatchMove (financial licensee) platform must ensure that the:
are displayed, accessible, and agreed to by the onboarding user on the sign-up page. |
Accounts | ☐ Inform the user that access to the Accounts feature is disabled until his profile is KYC verified. |
Cards | ☐ Inform the user that access to the Cards feature is disabled until his profile is KYC verified. ☐ As per network payment guidelines, all your app screens displaying a digital representation of your card must ensure that:
|
Collections | ☐ Inform the user that access to the Collections feature is disabled until his profile is KYC verified. ☐ When a virtual account is provisioned to the user, ensure that the virtual account details are hidden or masked from the user until the virtual account status is already active and usable. This is to prevent users from moving funds to an inactive virtual account, which will only result in transaction rejections. |
Payouts | ☐ Inform the user that access to the Payouts feature is disabled until his profile is KYC verified. |
Workflows | ☐ Showcase the user journey of a new onboarding user into the partner application. This shall include the following:
☐ Showcase the user journey on how a user gains access to financial assets in the platform. This shall include the following:
☐ Showcase the user journey on how a user manages the financial assets provisioned to him. This shall include the following:
☐ Showcase the user journey of how a user utilizes the financial capabilities of the platform. This shall include the following:
|
On this page
- Demo and go-live checklist