# Support
source: https://developer.mastercard.com/cross-border-services/documentation/support/index.md

## FAQs {#faqs}

### General {#general}

Cross-Border Services is a global cross-border payment service that lets banks and non-bank financial institutions send payments to bank accounts, mobile wallets, cards and cash pickup locations across 190+ countries and territories. See the [Overview](https://developer.mastercard.com/cross-border-services/documentation/index.md) for full details. The APIs support four Payment Types: P2P (person to person), B2P (business to person), B2B (business to business) and P2B (person to business). These cover use cases such as consumer remittances, payroll, gig-economy and marketplace seller payouts, insurance claim payments, supplier payments and bill payments. See [Use Cases](https://developer.mastercard.com/cross-border-services/documentation/use-cases/index.md) for implementation details. You can send payments to bank accounts, cards, mobile wallets and cash pickup locations across 190+ countries and territories. Availability varies by corridor. Check with your Mastercard representative for the payout methods supported under your program. Yes. Marketplace seller payouts are a B2P (business to person) use case, alongside gig-economy earnings and other business disbursements. See [Use Cases](https://developer.mastercard.com/cross-border-services/documentation/use-cases/index.md) for details. Banks connect directly and use the APIs to initiate P2P Payments on behalf of their customers. Mastercard handles FX conversion, routing, compliance screening and settlement. Follow the [Quick Start Guide](https://developer.mastercard.com/cross-border-services/documentation/quick-start-guide/index.md) to get started. Cross-Border Services uses OAuth for authentication and JWE (JSON Web Encryption) for payload encryption. See [API Basics](https://developer.mastercard.com/cross-border-services/documentation/api-basics/index.md) for full details. Yes, all our APIs are PCI compliant.

### Onboarding {#onboarding}

The APIs are available to financial institutions and organizations registered as a Customer for Cross-Border Services. A Customer can send funds transfer requests to Mastercard, initiated either for its own consumers or by a Mastercard-approved Transaction Originator it partners with. Contact your Mastercard representative to discuss registration and eligibility. Create a Mastercard Developers account, then create a project and select the Mastercard Cross-Border Services API. Follow the [Quick Start Guide](https://developer.mastercard.com/cross-border-services/documentation/quick-start-guide/index.md) to create your account, project and keys. Yes, the Sandbox APIs are stubs that return simulated, static responses, so you can try them without a registered partner ID. Follow the [Quick Start Guide](https://developer.mastercard.com/cross-border-services/documentation/quick-start-guide/index.md) to create an account, generate your Sandbox keys and make your first call. Note: OAuth 2.0 testing in Sandbox isn't available without registering. See the [API Tutorial using OAuth 1.0a](https://developer.mastercard.com/cross-border-services/documentation/tutorials/api-sdk-tutorial/index.md) for a complete walkthrough of generating an SDK and making your first API call.

### Integration {#integration}

Use OAuth 1.0a by default. See [Getting Started with the APIs using OAuth 1.0a](https://developer.mastercard.com/cross-border-services/documentation/api-basics/index.md#getting-started-with-the-apis-using-oauth-10a).

If you're contracted with MTS EU or MTS UK, you must use OAuth 2.0 to comply with PSD2:

* Authorization code flow for the Balance API
* Request token flow for all other APIs

See [Getting Started with the APIs using OAuth 2.0](https://developer.mastercard.com/cross-border-services/documentation/api-basics/index.md#getting-started-with-the-apis-using-oauth-20).
Yes. Request payloads and success responses are encrypted for an extra layer of security during transmission. Error responses are not encrypted. For OAuth 2.0 (MTS EU or MTS UK) Customers, request payload encryption is required. See [Payload Encryption](https://developer.mastercard.com/cross-border-services/documentation/api-basics/index.md#transport-encryption) for implementation details. Yes. The Quote API returns an upfront Mastercard FX Rate before you submit a Payment, giving your Senders visibility of the cost and the amount the Recipient will receive. See [Use Cases](https://developer.mastercard.com/cross-border-services/documentation/use-cases/index.md) for quote-based flow details. Use the [Retrieve Payment API](https://developer.mastercard.com/cross-border-services/documentation/api-ref/transaction-apis/retrieve-payment-api/index.md) to check a Payment's status and details, using either the Transaction ID or the Transaction reference. This is especially useful for Payments submitted without a quote, where the final amounts and Mastercard FX Rate are only known after processing. A single quote is valid for one Payment. If you use the quote confirmation service, you must confirm the quote within the `confirmationExpiryTime` returned in the Quote API response. See [Use Cases](https://developer.mastercard.com/cross-border-services/documentation/use-cases/index.md) for quote-based flow details. Use the [Account Validation APIs](https://developer.mastercard.com/cross-border-services/documentation/api-ref/index.md) to check a Recipient's account details, such as IBAN or bank name, before submitting a Payment. Set your timeout to at least 40 seconds. If a request times out, follow the retry guidance for each API. The recommended approach depends on whether you're calling the Quote, Payment or Quote Confirmation API. See [Timeouts](https://developer.mastercard.com/cross-border-services/documentation/code-and-formats/index.md#timeouts) for details. We've deprecated the generated SDKs in favor of lightweight OAuth libraries. You can use these to implement your own OAuth header, or generate your own SDK by using the OpenAPI Generator with Mastercard's authentication libraries. See the [API Tutorial using OAuth 1.0a](https://developer.mastercard.com/cross-border-services/documentation/tutorials/api-sdk-tutorial/index.md) for instructions.

### Environments and Keys {#environments-and-keys}

There are three environments: Sandbox (API stubs returning simulated, static responses), MTF (Mastercard Test Facility, the full APIs in a production-like environment) and Production. For base URLs and details, see [Environments](https://developer.mastercard.com/cross-border-services/documentation/api-basics/index.md#environment-descriptions). MTF (Mastercard Test Facility) is a production-like environment for full integration testing before you go live, using the complete APIs rather than the simulated responses returned by Sandbox. Access is granted after Sandbox testing. Contact your Mastercard implementation manager. See [MTF Access Guide](https://developer.mastercard.com/cross-border-services/documentation/tutorials/guide-mtf-access/index.md). Sandbox keys are used in the open test environment for development and validation. Production keys are used only after Production access is granted for your project. Build and test in Sandbox first, then switch to Production once your integration is ready. Integration and functional errors are cheaper to fix in Sandbox. Project keys are subject to annual renewal. For instructions on generating a new set of keys, see [API Basics](https://developer.mastercard.com/cross-border-services/documentation/api-basics/index.md).

### Troubleshooting {#troubleshooting}

Common cause: Your OAuth credentials are invalid or expired.

Steps to resolve:

1. Regenerate your OAuth Authorization Header.
2. Verify your signing key and consumer key are correct.
3. Check whether your keys have expired (keys renew annually).

For all HTTP-level error resolutions, see [HTTP Response Codes](https://developer.mastercard.com/cross-border-services/documentation/code-and-formats/index.md).
See [Error and Return Message Codes](https://developer.mastercard.com/cross-border-services/documentation/code-and-formats/index.md#error-and-return-message-codes) for the complete list of error and return message codes, including descriptions and handling guidance.

### Production {#production}

Once you've validated your integration in MTF, you can promote the same project to Production. See [Step 6: Promote the same project to Production](https://developer.mastercard.com/cross-border-services/documentation/quick-start-guide/index.md#step-6-promote-the-same-project-to-production) in the Quick Start Guide for the step-by-step process.

### Support {#support}

Contact your Mastercard representative, or reach out through the [developer forum](https://forum.developer.mastercard.com/s/) for community support. The [API Status page](https://developer.mastercard.com/api-status) shows the current health of Cross-Border Services in Sandbox and Production.

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