Release notes v26.10.0
Release Date: October 15, 2026
🚀 What's New?
- API References (New): The MatchMove Banking API Specifications are now available on the developer portal. Each API reference covers its endpoints, the base URLs for the sandbox and production environments, and its webhooks.
- Onboarding API
- Accounts API
- Cards API
- Collections API
- Payouts API
- Platform API
- Reference: API References (New): https://developer.matchmove.com/matchmove-banking-api-specifications/onboarding-api
#GLOBAL
✨ Enhancements
- Cross-Border Recipient Status Webhook (Updated): The payload of the
PAYOUT.RECIPIENT.CROSSBORDER.STATUSwebhook now carries the recipient state within anentitiesobject, including a newsub_statusfield for granular lifecycle tracking. Partners should review the updated payload so their integrations continue to handle recipient status updates correctly.- Field:
sub_status(string) - Description: Granular sub-status within
PENDING. It is empty for non-PENDINGstates. - Possible values:
RISK_EVALUATION_IN_PROGRESSRISK_EVALUATION_PENDING_REVIEWRISK_EVALUATION_CLEARCOOLING_PERIOD_IN_PROGRESSCOOLING_PERIOD_COMPLETED
- Reference: Create a Recipient for Cross-Border Payment (Updated): https://developer.matchmove.com/matchmove-banking-operating-system/cross-border-payouts/create-a-recipient-for-cross-border-payment
#PAYOUTS #CROSS-BORERD #GLOBAL
- Source of Funds Document Type (New):
SOURCE_OF_FUNDSis now supported as an additional document type for high-value cross-border transaction document requirements.- Reference:
- Perform a Cross-Border Payment Using an Existing Recipient (Updated): https://developer.matchmove.com/matchmove-banking-operating-system/cross-border-payouts/perform-a-cross-border-payment-using-an-existing-recipient
- Perform a Cross-Border Payment Without an Existing Recipient (Updated): https://developer.matchmove.com/matchmove-banking-operating-system/cross-border-payouts/perform-a-cross-border-payment-without-an-existing-recipient
- PH Individual Onboarding – Improved Guidance (Updated):
- The Philippines individual onboarding guides for document-based and authentication-based verification now put more emphasis on one requirement: the user must be updated with all the information required by regulation before the KYC process can be initiated. This is a documentation update only, and platform behavior is unchanged.
- Missing required information: If the user profile has any gaps or missing information that is required before KYC, the missing fields are listed in the
user.requirementsobject underimmediately_due.required_attributes. - Initiate verification step: The request to initiate verification is already marked optional for partners who are enabled for only a single primary KYC method. It is required only for partners with multiple KYC methods enabled.
- Guidance: Partners will need to follow the guides in the correct order throughout the individual onboarding workflow.
- References:
- 2. Update individual profile (when needed or when required information gaps exist)
- [Action Required]:
- Review your onboarding workflow according to the guide order.
#IDENTITY #PHILIPPINES
- Enhanced Cross-Border Transaction Statuses (New): Every cross-border payout now follows one consistent lifecycle, whichever payment provider or rail carries it. Each payment provider's own statuses are translated into a single, unified set, so you integrate once and your logic keeps working as more payment providers are added.
- One set of statuses: No overlapping or ambiguous codes.
- Clear ownership: You can tell whether a transaction is waiting on MatchMove or on the payment provider.
- Predictable refunds: Every failure path ends with the user's funds returned or held for compliance.
- Deprecated to updated state mapping (first three shown; see the reference for the full list):
Origin State
Trigger
Next State
| Payment intent created |
|
|---|---|---|
| Payload validation and user risk check |
|
| A manual internal compliance check required |
|
.. | .. | .. |
- Reference: Cross-Border Payout Transaction Lifecycle (New): https://developer.matchmove.com/matchmove-banking-operating-system/cross-border-payouts
#PAYOUTS #CROSS-BORERD #GLOBAL
- PH Address –
state_provinceEnumeration for Maguindanao (Updated): The Philippinesstate_provinceenumeration has changed for Maguindanao values. - Values:
MAGUINDANAOis deprecated- to be replaced by
MAGUINDANAO_DEL_NORTEandMAGUINDANAO_DEL_SUR
cityimpact: Thecodevalues are unchanged. Cities that previously showed Maguindanao now show Maguindanao Del Norte or Maguindanao Del Sur in thedescription.- Existing users:
- Active users and users who have already submitted KYC (PUT documents API call made) are unaffected and will continue using
MAGUINDANAO. - Rejected users using
MAGUINDANAOneed to correct theirstate_provinceaddress information toMAGUINDANAO_DEL_NORTEorMAGUINDANAO_DEL_SURbefore resubmission. - Users who have not yet submitted KYC, including newly registered users, users with a verified email or mobile number, and users who have only uploaded documents, will all be migrated to the new values.
- [Staging environment] – starting today, October 15, 2026:
- The new values are live in UAT.
- [Live environment] – roll-out date will be communicated to partners individually:
- Migrating Pre-KYC users needs careful planning before the new values go live in production.
- [Action Required]:
- Rejected users using
MAGUINDANAOmust correct theirstate_provincetoMAGUINDANAO_DEL_NORTEorMAGUINDANAO_DEL_SURbefore resubmission. - No action is required for all other users.
#IDENTITY #PHILIPPINES
- Initiate KYC Capture API (New): Initiate KYC Capture API (
POST /{{entity_type}}/authentications/documents/verifications) is an improved version of the Process KYC API.- Applies to the following entities:
- Individuals:
/users - Businesses:
/businesses - Business associated parties:
/associated_parties/
- It still returns the href or redirect link to the eKYC web app, and it adds the optional callback parameters that let you send users from the eKYC capture screen back to your application once they complete or exit the eKYC flow. Include these (optional) parameters in your request:
redirect_url: The fully qualified callback URL to which the user is redirected upon exiting or completing the eKYC flow.redirect_mode: The method of redirection. Accepted values areauto(immediate redirection upon completion) orbutton(requires explicit user interaction to trigger the redirect).redirect_text: The custom label displayed on the redirection button, for example "Exit" or "Return". It applies only whenredirect_modeis set tobutton.
- The Initiate KYC Capture API is now live in UAT. However, the optional callback feature (redirect_url) will only be enabled on Nov 1.
- References:
- [SG] Document-based verification (Individuals - Updated): https://developer.matchmove.com/matchmove-banking-operating-system/individual-users/onboard-individual-user-v2/individual-ekyc/sg-document-based-verification
- [SG] Authentication-based verification (Individuals - Updated): https://developer.matchmove.com/matchmove-banking-operating-system/individual-users/onboard-individual-user-v2/individual-ekyc/sg-authentication-based-verification
- [SG] Partner-assisted verification (Individuals - Updated): https://developer.matchmove.com/matchmove-banking-operating-system/individual-users/onboard-individual-user-v2/individual-ekyc/sg-partner-assisted-verification
- [SG] Document-based verification (Businesses - Updated): https://developer.matchmove.com/matchmove-banking-operating-system/business-users/onboard-business-users-v2/business-ekyc/sg-document-based-verification
#IDENTITY #GLOBAL
⚠️ Deprecations & Breaking Changes
- Legacy Cross-Border Transaction Statuses Deprecated: The legacy cross-border transaction statuses are deprecated in favor of the enhanced statuses. The previous statuses were too coarse to show where a user's money was, who was holding a payment up, or whether a refund had completed. The full deprecated-to-updated state mapping is available in the reference below.
- [Staging environment] – starting today to December 15, 2026 (Deprecation Period):
- The enhanced transaction statuses take effect immediately in the staging environment, and the legacy statuses will officially be retired on December 15.
- Partners who are currently in the implementation stage are required to update to the enhanced statuses immediately.
- [Live environment] – starting February 15, 2027 (Grace Period):
- The legacy statuses will be fully retired in the live environment. Partners must be migrated to the enhanced statuses to continue tracking cross-border transactions.
- [Action Required]:
- Please plan to update your applications to adopt the enhanced statuses and test your integration in the staging environment before the February 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: Cross-Border Payouts (Updated): https://developer.matchmove.com/matchmove-banking-operating-system/cross-border-payouts
#PAYOUTS #CROSS-BORDER #GLOBAL
- Legacy Remittance Transactions APIs Deprecated: The cross-border payout transactions
(/payouts/remittances/transactions)APIs are deprecated and replaced by the enhanced cross-border payout payments(/payouts/remittances/payments)API.- [Staging environment] – starting today to December 15, 2026 (Deprecation Period):
- The enhanced
/payouts/remittances/paymentsAPI takes effect immediately in the staging environment, and the/payouts/remittances/transactionsAPIs will officially be retired on December 15. - Partners who are currently in the implementation stage are required to use the new API immediately.
- [Live environment] – starting February 15, 2027 (Grace Period):
- The
/payouts/remittances/transactionsAPIs will be fully retired in the live environment. Partners must be migrated to the/payouts/remittances/paymentsAPI to continue tracking cross-border payments.
- [Action Required]:
- Please plan to update your applications to adopt the new API and test your integration in the staging environment before the February 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: Track the Status of a Cross-Border Payment (Updated): https://developer.matchmove.com/matchmove-banking-operating-system/cross-border-payouts/track-the-status-of-a-cross-border-payment
#PAYOUTS #CROSS-BORDER #GLOBAL
- Process KYC API Deprecated: The Process KYC API (
POST /{{entity_type}}/authentications/documents/process) is deprecated and replaced by the new Initiate KYC Capture API (POST /{{entity_type}}/authentications/documents/verifications).- Applies to the following entities:
- Individuals:
/users - Businesses:
/businesses - Business associated parties:
/associated_parties/
- [Staging environment] – starting today to November 15, 2026 (Deprecation Period):
- The new Initiate KYC Capture API takes effect immediately in the staging environment, and the Process KYC API will officially be retired on November 15.
- Partners who are currently in the implementation stage are required to use the new API immediately.
- [Live environment] – starting January 15, 2027 (Grace Period):
- The Process KYC API will be fully retired in the live environment. Partners must be migrated to the Initiate KYC Capture API to continue capturing KYC.
- [Action Required]:
- Please plan to update your applications to adopt the new API and test your integration in the staging environment before the January 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.
- References:
- [SG] Document-based verification (Individuals - Updated): https://developer.matchmove.com/matchmove-banking-operating-system/individual-users/onboard-individual-user-v2/individual-ekyc/sg-document-based-verification
- [SG] Authentication-based verification (Individuals - Updated): https://developer.matchmove.com/matchmove-banking-operating-system/individual-users/onboard-individual-user-v2/individual-ekyc/sg-authentication-based-verification
- [SG] Partner-assisted verification (Individuals - Updated): https://developer.matchmove.com/matchmove-banking-operating-system/individual-users/onboard-individual-user-v2/individual-ekyc/sg-partner-assisted-verification
- [SG] Document-based verification (Businesses - Updated): https://developer.matchmove.com/matchmove-banking-operating-system/business-users/onboard-business-users-v2/business-ekyc/sg-document-based-verification
#IDENTITY #GLOBAL
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].
Was this section helpful?
On this page
- Release notes v26.10.0