Release notes v26.08.0
Release Date: August 14, 2026
🚀 What's New?
- Launching a Card Program: New end-to-end documentation covering the full card operational process—from program setup through to card issuance and management. This gives partners a comprehensive guide to launching and running a card program on the MatchMove platform.
- Reference: Launching a Card Program (New)
#CARDS #GLOBAL
- MatchMove FAQs: A centralized knowledge base of the platform's most frequently asked questions and answers, covering integration, operational, and product topics—designed for existing and prospective partners and anyone exploring the MatchMove Banking Operating System.
- Reference: MatchMove FAQs (New)
#PLATFORM #GLOBAL
- KYC Verification: Three new verification models are introduced, offering partners flexibility in how KYC is performed across different markets and use cases.
1. Partner-Assisted eKYC: A hybrid eKYC model where partners handle document uploads, and MatchMove performs liveness detection and Enhanced Due Diligence (EDD). This model gives partners control over the collection experience while relying on the platform for verification.
Reference: Partner-Assisted eKYC (New)
#IDENTITY #GLOBAL
2. Authentication-Based Verification: A hybrid verification model that uses PH National ID eVerify through the Banking Partner integration, combined with supporting document upload via the MatchMove Banking API.
Reference: Authentication-Based Verification (New)
#IDENTITY #PHILIPPINES
3. Document-Based Verification: An enhanced version of the existing KYC verification process where all document requirements are uploaded via the MatchMove Banking API, and the financial institution does the final verification.
Reference: Document-Based Verification (New)
#IDENTITY #PHILIPPINES
✨ Enhancements
- Card Transaction Fees (Updated): Updated documentation on card transaction fee structures, providing partners with clearer guidance on how fees are applied across different transaction types.
- Reference: Card Transaction Fees (Updated)
#CARDS #GLOBAL
- Capture End User Context (New): To keep abreast of the growing threat landscape in the region and the increasing regulatory posture on transaction security, MatchMove is introducing new content headers for API usage. These headers enhance request traceability and security across the platform, supporting stronger audit trails and compliance readiness. The headers are currently optional. Partners are encouraged to begin including them now to ensure a smooth transition.
- [Staging environment] – starting September 15, 2026 (Warning Period):
- The API specification will begin reflecting in the documentation that context headers are required parameters.
- These context header requirements will also start to be enforced in the staging environment. API calls not passing these context headers will start receiving validation errors.
- [Live environment] – starting November 15, 2026 (Enforcement Period):
- The context header requirements will start to be enforced in the live environment. API calls not passing the required parameters will start receiving validation errors.
- [Action Required]:
- Please plan to update your applications and test them in the staging environment before the November 15 production enforcement date. Our Customer Growth and Implementation teams will be in contact with you to help plan your migration strategy and provide any needed support.
Reference: Capture request context headers (New)
#PLATFORM #GLOBAL
⚠️ Deprecations & Breaking Changes
- User and KYC Status Webhooks Deprecated (V2 Identity and Onboarding): The following webhooks are deprecated in favor of unified status events that carry revised payload structures and additional data. Partners should migrate to the replacement webhooks at the earliest opportunity.
1. PH-Configured Programs:
|
|
|---|---|
|
|
|
|
- [Staging environment] – starting today to September 15, 2026 (Deprecation Period):
- The new replacement webhooks will take effect immediately in the staging environment, and legacy webhooks will officially be retired on September 15.
- Partners who are currently in the implementation stage are required to update to the new webhooks immediately.
- [Live environment] – starting November 15, 2026 (Grace Period):
- The legacy webhooks will be fully retired in the live environment and will no longer send payloads. Partners must be migrated to the new webhooks to continue receiving event notifications.
- [Action Required]:
- Please plan to update your applications to adopt the new webhooks and test your integration in the staging environment before the November 15 production retirement date. Our Customer Growth and Implementation teams will be in contact with you to help plan your migration strategy and provide any needed support.
Reference: [PH] Authentication-Based Verification (New)
Reference: [PH] Document-Based Verification (New)
#IDENTITY #PHILIPPINES
2. SG-Configured and All Other Programs:
(Individual and business users) |
|
|---|---|
(Associated parties of a business user) |
|
- [Staging environment] – starting today to September 15, 2026 (Deprecation Period):
- The new replacement webhooks will take effect immediately in the staging environment, and legacy webhooks will officially be retired on September 15.
- Partners who are currently in the implementation stage are required to update to the new webhooks immediately.
- [Live environment] – starting November 15, 2026 (Grace Period):
- The legacy webhooks will be fully retired in the live environment and will no longer send payloads. Partners must be migrated to the new webhooks to continue receiving event notifications.
- Action Required:
- Please plan to update your applications to adopt the new webhooks and test your integration in the staging environment before the November 15 production retirement date. Our Customer Growth and Implementation teams will be in contact with you to help plan your migration strategy and provide any needed support.
Reference: [SG] Document-based Verification (Updated), formerly Perform Individual KYC (Renamed)
Reference: Perform Business KYC (Updated)
#IDENTITY #SINGAPORE #GLOBAL
3. Submit Individual KYC (v2) Deprecated: The current v2 - Submit Individual KYC guide and workflow are deprecated and will be removed from the developer portal after 60 days. It is retained only as a reference for past implementations. This legacy workflow will be replaced by the new Document-based verification and Authentication-based verification methods.
- [Staging environment] – starting today to September 15, 2026 (Deprecation Period):
- Documentation-based verification: The new process will take effect in the staging environment, introducing minor changes to the KYC submission workflow. This is the direct replacement of the deprecated Submit Individual KYC process.
- Partners who are currently in the implementation stage are required to adopt the new document-based verification immediately.
- Authentication-based verification (Optional): The new alternative process will take effect in the staging environment, introducing a new way of verifying users via PH National ID through eVerify. As this new capability involves specific commercial terms, please connect with our Customer Growth team to explore pricing and integration steps.
- [Live environment] – starting November 15, 2026 (Grace Period):
- The legacy KYC process will be fully retired in the live environment. Partners must be migrated to the new document-based verification to continue processing user verifications.
- [Action Required]
- Please plan to update your applications to adopt the new Document-based verification process and test your integration in the staging environment before the November 15 production retirement date. Our Customer Growth and Implementation teams will be in contact with you to help plan your migration strategy and provide any needed support.
Reference: (Legacy) Submit Individual KYC (Deprecated)
Reference: Document-Based Verification (New)
Reference: Authentication-Based Verification (New)
#IDENTITY #PHILIPPINES
📝 Document Corrections
- Domestic Payment Cooling Period – Status Change Reverted: The recipient status field change announced in v26.07.0 (
PENDING_ACTIVATION→PENDINGwithSUB_STATUShandling) has been reverted for domestic payouts. Domestic payout recipients will continue to usePENDING_ACTIVATIONas the status during the cooling-off period.- Reference: Create a Recipient for Domestic Payout (Corrected)
#PAYOUTS #GLOBAL
- Added Deprecation Period and Grace Period timing and advisory with respect to the deprecated platform features.
Need help? Reach out to your MatchMove integration partner or contact the support team.
Interested to learn more?
- Reach out to our Business Development and Customer Growth teams at [sales@matchmove.com].
On this page
- Release notes v26.08.0