# Support
source: https://developer.mastercard.com/mastercard-send-person-to-person/documentation/support/index.md

## FAQs {#faqs}

### General {#general}

This service enables registered Program Participants (such as banks, issuers, and digital players) to provide P2P payment solutions that enable consumers/individuals (Senders) to transfer funds quickly, such as sending money to family and friends. You should decide when to use the services based on your Know Your Customer (KYC) policies. You may opt to screen cardholders when they register for your funds transfer service and again prior to payment initiation (to ensure the account is still valid).

We recommend that you run checks using both the Account Information Service (first) and the Account Verification Service (second) prior to submitting every payment transaction. Submit as much account and address information as possible to the Account Verification Service, because additional detail improves the accuracy of the service.

**NOTE:** Successful responses from these services do not guarantee that the Receiving Institution (issuer) with approve the payment transaction. Other factors, such as receiving limits and the issuer's compliance and fraud checks, may cause it to decline a transaction.
Yes. In addition to card PANs, you can use different types of Account URIs in your API messages to identify accounts, see [Account URIs](https://developer.mastercard.com/mastercard-send-person-to-person/documentation/field-uris-codes/account-uris/index.md).

### Onboarding {#onboarding}

Contact your regional Mastercard representative. If you have not been connected with a Mastercard representative, please [contact us](mailto:digital.support@mastercard.com) to request a regional representative, identifying your company name, region, and the Mastercard program (Mastercard Send) and services that interest you. You can use the Sandbox API before registering as a Program Participant.

To use the full service in the MTF and Production environments, you must become a Mastercard Send Program Participant, which involves registering for the required programs and services and meeting program eligibility requirements; see [Mastercard Send Registration and Eligibility](https://developer.mastercard.com/mastercard-send/documentation/send-eligibility/).
Please [contact us](mailto:digital.support@mastercard.com) for pricing and region information.

### Integration {#integration}

Yes, there is a Sandbox API you can try before registering as a Program Participant. See [API Basics](https://developer.mastercard.com/mastercard-send-person-to-person/documentation/api-basics/index.md). To start using the Sandbox API stubs, create a Mastercard Developers project choosing the **Mastercard Send** APIs, and download the Sandbox Signing Key. The APIs use OAuth 1.0 authentication, so your API requests must have an OAuth 1.0a Authorization Header generated using the Sandbox keys. See [API Basics](https://developer.mastercard.com/mastercard-send-person-to-person/documentation/api-basics/index.md).

Ensure you use the Sandbox API endpoints with a `partnerId` value of the correct length, e.g. `ptnr_BEeCrYJHh2BXTXPy_PEtp-8DBOo`.
Sandbox has limited-capacity mock APIs, enabling you to try the APIs quickly. While it can help with initial integration and development, it returns mock responses and is not intended for full testing.

Use the MTF APIs for full integration testing. See [API Basics](https://developer.mastercard.com/mastercard-send-person-to-person/documentation/api-basics/index.md).
Access to the MTF APIs uses the same Sandbox keys as the Sandbox environment (unless you renew them), but Mastercard must configure the environment. Contact your Mastercard representative or Delivery Manager and provide your Sandbox Consumer Key. Allow 5-7 business days for configuration.

When you [onboard to Mastercard Send](https://developer.mastercard.com/mastercard-send/documentation/send-eligibility/), you will be provided with a `partnerId` value, which you must use in your API calls to the MTF and Production environments. Ensure you use the MTF API endpoints.
See [MTF Test Cards](https://developer.mastercard.com/mastercard-send/documentation/implementation/test-cards/). You must:

* Become a Mastercard Send Program Participant, see [Mastercard Send Registration and Eligibility](https://developer.mastercard.com/mastercard-send/documentation/send-eligibility/).

* Complete testing in the MTF environment.

* Request Production access for your project (by clicking **Request Production Access** in your project page) and receive approval from Mastercard.

* Provide your Production Consumer Key to your Mastercard representative or Delivery Manager so they can configure the environment for your keys.

When you request Production access for your project (by clicking **Request Production Access** in your project page), it requires approval from Mastercard.

The Production Signing Key and Consumer Key (used for authentication) are different from the Sandbox keys.

Contact your Mastercard representative or Delivery Manager and provide your Production Consumer Key. Allow 5-7 business days for configuration.

Ensure you use the Production API endpoints.
All Mastercard Send API responses include a Correlation ID (correlation-id) header value, which is a unique ID for each API call in Mastercard systems. We recommend you log this ID for tracking purposes. When seeking support, providing the relevant Correlation ID may help resolve your inquiry more quickly.

### Policy {#policy}

All Mastercard Send APIs support Transport Layer Security (TLS) 1.2 and 1.3, and use OAuth 1.0a for authentication; see [API Security](https://developer.mastercard.com/mastercard-send-person-to-person/documentation/api-basics/index.md#api-security). Yes, all our APIs are PCI compliant.

### Performance {#performance}

Instead of throttling, Mastercard applies rate limits to control the number of requests per second (RPS) per customer and ensure system reliability. For the Production API, the default rate limit for POST calls is 100 Requests per Second (RPS) per customer. If you exceed this limit, you may receive a standard HTTP error such as a 429 Too Many Requests response. You should implement appropriate retry logic with exponential back‑off to recover safely. See [Quotas and rate limits](https://developer.mastercard.com/platform/documentation/errors-and-troubleshooting/oauth1-and-mtls-error-codes/#quotas-and-rate-limits). If you expect your application to exceed the standard rate limit, you can request a temporary increase. Submit your rate‑limit increase request through your Mastercard product contact or support channel. Higher limits are not granted automatically and are reviewed on a case‑by‑case basis to ensure they align with platform capacity, downstream system constraints, and overall operational stability. Please allow 5-10 business days for the review. Actual throughput can vary depending on request patterns, payload complexity, concurrency levels, system load and downstream processing. The platform is designed to support high‑volume usage, but no fixed TPS guarantees are provided. Performance may fluctuate, so you should architect for variable throughput. For MTF and production, testing indicates an average of less than 100 milliseconds per response.

### Support {#support}

When you contact Mastercard and request access to this service, you are typically connected with a regional Mastercard representative who can provide further information about the Mastercard Send program and guide you through Mastercard Send registration and eligibility requirements. When you are ready for program implementation, you will be assigned a Mastercard Delivery Manager who will guide you through implementation.

If you have not been connected with a Mastercard representative, please [contact us](mailto:digital.support@mastercard.com) to request a regional representative, identifying your company name, region, and the Mastercard program (Mastercard Send) and services that interest you.

For technical support, use the **Get Help** button at the bottom of this page.
Use the near real-time, self-service [Send Customer Portal](https://developer.mastercard.com/mastercard-send/documentation/customer-site/) to research your transactions in MTF and Production. See [Peak season freeze dates](https://developer.mastercard.com/mastercard-send/documentation/send-release-notes/#peak-season-freeze-dates). The [API Status](https://developer.mastercard.com/api-status) page informs Mastercard Developers users of the status of each API. Direct links to the status for the Mastercard Send services: [MTF APIs](https://developer.mastercard.com/api-status?environment=sandbox&group=send) and [Production APIs](https://developer.mastercard.com/api-status?environment=production&group=send).

## Get Help {#get-help}

### Contact us for technical support. {#contact-us-for-technical-support}