# Mastercard Cross-Border Services source: https://developer.mastercard.com/cross-border-services/documentation/index.md ## Overview {#overview} Note: This documentation is for the developers and technical managers who want to integrate with Cross-Border Services to deliver a fund transfer solution. For program details, rules and further implementation guidance, contact your Mastercard representative. Mastercard Cross-Border Services is a global cross-border payment service that enables banks and non-bank financial institutions like fintechs, remittance providers and platform partners to send Payments on behalf of their customers, reaching bank accounts, mobile wallets, cards and cash pickup locations across 190+ countries and territories. Cross-Border Services APIs support four customer Payment Types: * **Person to Person (P2P)** -- for example consumer remittances, family transfers * **Business to Person (B2P)** -- for example payroll payouts, insurance claim payouts, creator/gig-economy payouts, marketplace seller payouts, business disbursements * **Business to Business (B2B)** -- for example supplier payments, invoice settlements * **Person to Business (P2B)** -- for example bill payments, tuition payments ## Who can use it {#who-can-use-it} A bank or non-bank financial institution that will connect to Cross-Border Services **directly** to initiate fund transfers for its customers. ## How it works {#how-it-works} ![how-it-works](https://static.developer.mastercard.com/content/cross-border-services/uploads/HowItWorks1.png) Note: The diagram above illustrates a Customer that is an Originating Institution sending funds on behalf of its Senders. * **Sender**: The Customer's end user who wants to send money across borders. May be a consumer, business or non-profit organization. The Sender does not interact with the Cross-Border Services API directly - they interact with the Customer's app, website or branch, and the Customer submits the Payment to Cross-Border Services on their behalf. * **Transaction Originator**: An optional third party that the Customer partners with. Senders initiate Transactions through the Transaction Originator, which then routes them to the Customer. * **Customer (Originating Institution)**: The bank or non-bank financial institution that integrates with Cross-Border Services and initiates Payments on behalf of its Senders. * **Mastercard Cross-Border Services**: Routes the Transaction, provides the FX Rate, performs KYC and AML screening and settles between the Customer and Mastercard. * **Receiving System**: The payout partner, beneficiary bank, mobile wallet operator or cash-out location that holds the Recipient's account or provides the payout mechanism. * **Recipient**: The beneficiary receiving the Payment. May be a consumer, business, mobile money agent or cash-out location. * Send cross-border Payments to bank accounts, cards, mobile wallets and cash pickup locations across 190+ countries and territories. * Show Senders the exchange rate, fees, and Recipient amount before they confirm the Payment. * Use Mastercard's wholesale and retail FX Rates. * Get settlement and reconciliation reporting for every Transaction. * Support use cases like outbound remittances, marketplace seller payouts, payroll, gig-economy and creator payouts, insurance claims, humanitarian aid, supplier payments and personal transfers. For more detail on how each API supports these flows, see the [Use cases](https://developer.mastercard.com/cross-border-services/documentation/use-cases/index.md) section. ## Good to know {#good-to-know} * Onboarding: Create a Mastercard Developers account, generate Sandbox project credentials, then request production access for the same project later. You'll need to meet eligibility and compliance requirements before going live. See [API Basics](https://developer.mastercard.com/cross-border-services/documentation/api-basics/index.md) to get started. * Integration options: Use this API for real-time use cases. Contact your Mastercard representative for batch integration options. * Testing: The sandbox returns simulated, static responses. The Mastercard Test Facility (MTF) gives you the full APIs in a production-like environment once your eligibility is confirmed. See [Testing](https://developer.mastercard.com/cross-border-services/documentation/testing/index.md) for details. * Authentication: Use [OAuth 1.0a](https://developer.mastercard.com/cross-border-services/documentation/api-basics/index.md#getting-started-with-the-apis-using-oauth-10a) by default. If you're contracted with MTS EU or MTS UK, use [OAuth 2.0](https://developer.mastercard.com/cross-border-services/documentation/api-basics/index.md#getting-started-with-the-apis-using-oauth-20) to comply with PSD2. ## Next steps {#next-steps} 1. Look at the [API Basics](https://developer.mastercard.com/cross-border-services/documentation/api-basics/index.md) to learn about the Mastercard environments and the required project keys. 2. Take a look at the [Use Cases](https://developer.mastercard.com/cross-border-services/documentation/use-cases/index.md) to understand how the Cross-Border Service APIs facilitate the supported transaction types. 3. When you are ready to use the APIs, see [Getting Started with the APIs](https://developer.mastercard.com/cross-border-services/documentation/api-basics/index.md#getting-started-with-the-apis-using-oauth-10a) for information on connecting to the Cross-Border Service APIs. 4. Use the [API Reference](https://developer.mastercard.com/cross-border-services/documentation/api-ref/index.md) information for the APIs you want to use, to see details of the fields and values relevant to the transaction types you are supporting. 5. Try out the [Tutorials](https://developer.mastercard.com/cross-border-services/documentation/tutorials/index.md) if you need help on how to make API calls to the Cross-Border Service APIs in the Sandbox environment.