# Support
source: https://developer.mastercard.com/payment-currency-conversion/documentation/support/index.md

## FAQs {#faqs}

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/MPQR program and guide you through Mastercard Send/MPQR 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:customer_support@mastercard.com) to request a regional representative, identifying your company name, region, and the Mastercard program (Mastercard Send or MPQR) and services that interest you.

For technical support, use the **Get Help** button at the bottom of this page.
This service assists Originating Institutions with cross-border payment transactions by enabling them to get the current currency conversion rates and calculated settlement amounts before they initiate those transactions. Mastercard publishes currency conversion rates once per day and the rates are effective for a 24-hour period. Yes, all of our APIs are PCI compliant. See [Guides](https://developer.mastercard.com/payment-currency-conversion/documentation/tutorials-and-guides/index.md). The APIs are RESTful APIs with OAuth security. Your API requests must have an OAuth 1.0a Authorization Header for authentication, see [API Basics](https://developer.mastercard.com/payment-currency-conversion/documentation/api-basics/index.md).

The APIs do not use additional encryption. Your API GET requests do not have body payloads.
Yes, the Sandbox APIs are provided so that you can try the APIs quickly. They are API stubs that return simulated responses. The expandable sections in [API Reference](https://developer.mastercard.com/payment-currency-conversion/documentation/api-reference/index.md) provide **Execute** buttons that allow you to try the Sandbox APIs quickly, directly from your browser.

When you are ready to make API calls to the Sandbox server from an API tool or your application, you must create a Mastercard Developers project choosing the **Currency Conversion for Originating Institution** API service, generate the Sandbox Keys, and use the keys to generate OAuth 1.0a Authorization Headers for your API requests. See [API Basics](https://developer.mastercard.com/payment-currency-conversion/documentation/api-basics/index.md).
See [Error Codes (Reason Codes)](https://developer.mastercard.com/payment-currency-conversion/documentation/codes-and-formats/index.md#error-codes-reason-codes). To start using the Sandbox APIs, create a Mastercard Developers project choosing the **Currency Conversion for Originating Institution** API service, and download the Sandbox 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. For more information, see [API Basics](https://developer.mastercard.com/payment-currency-conversion/documentation/api-basics/index.md). See the [Currency Conversion Rates guide](https://developer.mastercard.com/payment-currency-conversion/documentation/tutorials-and-guides/index.md#currency-conversion-rates-guide). Your API request was made before the new conversion rates are published, so the previous day's conversion rate is still effective, as reflected by the date in the `conversionRateDate` field. You might not be using the current date in your API request path (`transaction_date` query parameter). Please use the current date. When you request Production access for your project (by clicking **Request Production Access** in your project page), it requires approval and configuration by Mastercard, which can take 5-7 business days. See [Good to Know](https://developer.mastercard.com/payment-currency-conversion/documentation/index.md#good-to-know).

The Production Key and Consumer Key (used for authentication) are different from the Sandbox keys. The Production API endpoints are also different.
Throttling is not implemented for this API. It is currently approximately 642 milliseconds. We are making changes during 2024 that will noticeably improve the response time. This varies over time. We have seen an average of approximately 35 TPS. All 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. The currency conversion rate and the converted amount are indicative only and based on the API request values you submit. Receiving issuers (Receiving Institutions) may or may not use Mastercard currency conversion rates to credit cardholders and may impose additional fees in connection with foreign currency transactions.

Currency conversion rates are specific to the date and time the receiving issuer authorizes the transaction (which generally occurs at the point of sale/interaction). If Mastercard is unable to apply the currency conversion rate at authorization, Mastercard will apply the currency conversion rate at the date and time the transaction is processed. If a transaction is converted by the receiving issuer, Mastercard currency conversion rates will not apply. This will usually occur when you initiate a payment transaction in the sending card's currency as opposed to the receiving card's currency.

Mastercard, in its sole discretion, may restrict usage of this API as Mastercard may deem necessary or appropriate.

## Get Help {#get-help}

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