# RNTZ Migration
source: https://developer.mastercard.com/mastercard-send/documentation/rntz-migration/index.md

Mastercard has introduced the Regional Network Transit Zone (RNTZ) to provide a faster and more secure connection to Mastercard Send APIs. The following Mastercard Send APIs are now available through RNTZ:

* [Disbursement](https://developer.mastercard.com/mastercard-send-disbursements/documentation/api-reference/disbursement/)
* [P2P Payment Transfer](https://developer.mastercard.com/mastercard-send-person-to-person/documentation/api-reference/payment-transfer/)
* [Funding](https://developer.mastercard.com/mastercard-send-funding/documentation/api-reference/)
* [Account Information](https://developer.mastercard.com/mastercard-send-account-info/documentation/api-reference/)
* [Account Verification Service (AVS)](https://developer.mastercard.com/mastercard-send-avs/documentation/api-reference/)
* [Account Validation](https://developer.mastercard.com/account-validation/documentation/api-reference/)
* [Parameter Management Services](https://developer.mastercard.com/mastercard-send-parameter-management-services/documentation/api-reference/)

[Mastercard Send RNTZ Migration Playbook](https://static.developer.mastercard.com/content/mastercard-send/uploads/Send_RNTZ_Migration_Playbook.pdf)   
(added July 2026)

If you use any of these APIs, refer to the **Mastercard Send RNTZ Migration Playbook** for instructions on migrating to the new RNTZ endpoints.
Note: Customers using non-RNTZ endpoints must migrate to RNTZ by **31 March 2027**.