# Release History source: https://developer.mastercard.com/mastercard-send-disbursements/documentation/release-history/index.md ## Release Notes {#release-notes} The Mastercard Send releases are quarterly. Mastercard will share advance Release Notes to help notify participants of intended changes. For the release dates and Release Notes, see [Mastercard Send Release Notes](https://developer.mastercard.com/mastercard-send/documentation/send-release-notes/). To stay current on all Mastercard Send API updates, be sure to visit that page regularly. ## Release History {#release-history} Notable changes specific to these APIs are listed below (in reverse chronological order). The Release Date is when the change takes effect in Production. Changes prior to release 20.R1 (25 May 2020) are not included. Ensure you check the main Release Notes page (see section above) for any other changes that may affect use of these APIs. | Release Date | Notes | |------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 23 January 2026 25.4 | Updated the API specification server domains to the new RNTZ domains. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-25.4.pdf#page=3). | | 9 September 2025 25.2 | Added `Repeat-Flag` header parameter. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-25.2.pdf#page=7). For POST response, removed code 02 from `network_decision_code` field description because it is not relevant to that response. | | August 2025 25.2 | Changed `acceptor_tax_id` field description to add guidance for Chile, Paraguay, and Peru. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-25.2.pdf#page=6). | | 21 May 2025 | Adjusted the API specification to include 'All fields' example payloads that show all possible fields. | | 8 May 2025 25.1 | `transaction_purpose` code mapped to the Visa Purpose of Transaction code for Visa OCT transactions, see [Transaction Purpose](https://developer.mastercard.com/mastercard-send-disbursements/documentation/field-uris-codes/transaction-purpose/index.md). | | 11 April 2025 25.1 | Added `transaction_purpose` codes 17 and 18. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-25.1.pdf#page=12). Added to request and responses: * `acceptor_tax_id` and `acceptor_tax_id_name` for Brazil use - see [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-25.1.pdf#page=8) * `payment_facilitator_id` and `sub_merchant_id` for Mastercard transactions - see [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-25.1.pdf#page=9) * `additional_networks` object that contains a `visa_network` object with fields required for Visa OCT transactions - see [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-25.1.pdf#page=10)
Implemented validations to prevent processing newlines (\\n) and carriage returns (\\r) for some request fields. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-25.1.pdf#page=13). | | 31 March 2025 25.1 | Made `sender.address.postal_code` and `recipient.address.postal_code` optional. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-25.1.pdf#page=7). | | 15 November 2024 | Added `merchant_advice_code` response field that is present when the transaction was declined by the issuer. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-24.3.pdf#page=9). | | 22 October 2024 24.3 | Added `payment_type` code 'FRD' (Fast Refund) and optional `purchase_trace_id` field to request and responses. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-24.3.pdf#page=7). Added optional `mastercard_assigned_merchant_id` field to request and responses. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-24.3.pdf#page=8). | | 24 September 2024 | Improved the API specification, including adding sample request payloads. | | 19 September 2024 | Removed information relating to U.K. Faster Payments Service (FPS) functionality and APIs because we are no longer promoting those APIs. | | 11 September 2024 24.2 | Added `network_decision_code` response field that is present when the transaction was declined by the Mastercard Network instead of the issuer. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-24.2.pdf#page=6). Added optional `mpg_id` field to request and responses. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-24.3.pdf#page=5). | | 29 May 2024 24.1 | Added a POST API request `decline_details` query parameter which, if set to 'true', will cause declined transactions to be returned as 201 responses instead of 402 error responses (the default). The 201 decline response will have `status` as 'DECLINED' and additional `network_status_code` and `network_status_description` fields. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-24.1.pdf#page=10). | | 17 April 2024 | Corrected `transfer_acceptor_address.line1` field description to maximum length 48. | | 20 March 2024 | Adjusted `sender.first_name` and `sender.last_name` field descriptions to reflect the network control changes communicated in announcement *GLB 9211.1 Revised Standards and Mastercard Network Controls for Send Transactions*. The '#NOTINCLUDED' value is no longer permitted for these fields. | | 26 January 2024 | Improved the documentation as follows to indicate the `sender_account_uri` field requirements for disbursements to Mastercard accounts: * Improved the Disbursement API specification's `sender_account_uri` field description. * Updated the [Account URIs](https://developer.mastercard.com/mastercard-send-disbursements/documentation/field-uris-codes/account-uris/index.md), [Government ID URIs](https://developer.mastercard.com/mastercard-send-disbursements/documentation/field-uris-codes/gov-id-uris/index.md), and [Funding Source](https://developer.mastercard.com/mastercard-send-disbursements/documentation/field-uris-codes/funding-source/index.md) documentation pages. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-23.R4.pdf#page=2). | | 12 September 2022 | Updated the API specification (presented in the documentation pages) to OpenAPI 3.0.3 and improved some of the definition names. | | 7 June 2022 22.R2 | For the request fields `recipient.first_name`, `recipient.last_name`, `sender.first_name`, `sender.last_name`, `sender.address.line1`, `sender.address.city`, added support for use of alternative value '#NOTINCLUDED' when the actual value cannot be provided. This is to assist participants who need additional time to comply with the DE 108 (Additional Transaction Reference Data) data requirements relating to the Mastercard Gaming and Gambling Payments Program. Mastercard will allow support of the alternative value until 6 June 2023. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-22.R2.pdf#page=2). | | 19 May 2022 22.R1 | Enhanced description for the `customer_service_contact_info` field in the API specification to provide better guidance on what can be provided. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-22.R1.pdf#page=5). | | 19 April 2022 22.R1 | Enhanced Recipient field descriptions in the API specification to provide better guidance for VISA OCT transactions. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-22.R1.pdf#page=3). | | 3 March 2022 21.R4 | Added new value of 'OTHER' to the `funding_source` field, which is in the request and responses. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-21.R4.pdf#page=7). | | 11 November 2021 21.R3 | Added optional `transaction_purpose` field to request and responses. This enables participants to provide accurate information about the purpose of the transaction, which can be passed to downstream networks. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-21.R3.pdf#page=6). Added optional `sender.account_type` and `recipient.account_type` fields to request and responses. This enables participants to identify the type of account number passed in the Account URI fields (`sender_account_uri` and `recipient_account_uri`). In addition, the 'raw' schema for the Account URI fields has been enhanced to support the different account types. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-21.R3.pdf#page=7). Improved the Sandbox validations for POST requests: * Added some missing validations, see [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-21.R3.pdf#page=11). * Fixed the JSON validation for `recipient.government_ids.government_id_uri`, which is an optional field. | | October 2021 | Removed the API specifications and details for the Account Information and Account Verification services, which now have their own documentation sets. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-21.R2.pdf#page=2). | | 24 August 2021 21.R2 | Added optional `canada_domestic_indicator` field to request and responses. This enables participants in Canada (who have elected to include Debit Mastercard in scope) to provide a value of 'true' for Canada DMC, MCC and cross-border transactions. Mastercard will decline a transaction if the value is not passed as 'true' and it is a Canada DMC. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-21.R2.pdf#page=10). Added optional `merchant_verification_value` field to request and responses. This enables participants to provide the Merchant Verification Value (MVV) for Visa OCT GMR (Gaming Repay) transactions when the MCC is 7800, 7801 or 7802 (U.S. only). Merchants must register with Visa to obtain an MVV. (Participants must also pass the applicable MCC in the GMR request.) See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-21.R2.pdf#page=5). | | 25 May 2021 21.R1 | Added optional `transfer_acceptor_address` object. This enables participants to provide the Transfer Acceptor Address when it is different from the Sender Address, to ensure accurate information is passed to downstream networks. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-21.R1.pdf#page=8). Added `payment_type` code 'GMR' (Gaming Repay) to support new Gaming and Gambling Payments Program. Participants must pass the applicable MCC in the GMR request. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-20.R3.pdf#page=6). | | 18 March 2021 | Updated the API specification from Swagger 2.0 to OpenAPI 3.0, adjusting the server base URLs and paths. | | 25 August 2020 20.R2 | Added `payment_type` code 'B2B' (Business-to-Business) to support a new use case. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-20.R2.pdf#page=5). Made expiration date optional for pan schema in the `sender_account_uri` and `recipient_account_uri` fields. Participants requesting payments to PANs issued in the U.S. must provide an expiration date. Including the expiration date in the request will increase the approval rate. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-20.R2.pdf#page=2). | | 30 April 2020 20.R1 | Added optional fields for disburser information. This enables Resellers to pass disburser information in their API requests, instead of the Reseller information. When populated, the fields are mapped and passed to downstream networks. When the Sender Address is included, it will be mapped as Card Acceptor address to downstream networks. See [Release Notes](https://static.developer.mastercard.com/content/mastercard-send/release-notes/mastercard-send-release-notes-20.R1.pdf#page=3). | ## Announcements {#announcements} Mastercard regularly publishes announcements relating to Operations, Rules/Standards, and other categories that might impact Mastercard Send API customers. To help you identify which announcements might be relevant to your business, we provide an Announcements spreadsheet. See [Announcements](https://developer.mastercard.com/mastercard-send/documentation/announcements/).