# Onboarding Checklist source: https://developer.mastercard.com/cross-border-services/documentation/tutorials/onboarding-checklist/index.md This guide outlines the end-to-end requirements and readiness activities for moving a Mastercard Cross-Border Services integration from the Sandbox environment through Mastercard Test Facility (MTF) and Production Validation Testing (PVT) to Production. Use this checklist to understand what needs to be completed at each stage, prepare for the next testing environment, and ensure your technical and operational capabilities are ready before commercial launch. Cross-Border Services uses three testing environments: Sandbox, Mastercard Test Facility (MTF), and Production Validation Testing (PVT). ### Prerequisites {#prerequisites} Before progressing through the testing journey, work with your Mastercard representative and implementation team to define your programme scope and configuration. ### Programme set-up {#programme-set-up} Complete the following onboarding activities: * Complete the Non-Disclosure Agreement (NDA) * Complete the programme scope assessment * Determine your ICA assignment * Complete Mastercard due diligence, including AML/KYC Compliance review and Credit Risk assessment where applicable * Complete and sign the Program Form * Confirm the applicable participation model * Define the Service Configurations included in your programme, including Sending Territory, Receiving Territory, Receiving Channel, Recipient Currency, Payment Type, Settlement Currency and Sender Currency, as applicable ### Confirm your solution configuration {#confirm-your-solution-configuration} Before development and testing, confirm: * Integration method, such as API or Payment File Processing * Pricing model, either Customer Managed Sender Pricing (CMSP) or Mastercard Managed Sender Pricing (MMSP) * Mastercard FX Rate delivery and rate management method * Settlement model * Required APIs and services for your selected configuration * Optional APIs, services and features included in your programme scope Your Mastercard project leader will conduct a kickoff meeting to review the defined scope, required forms, timelines, testing expectations, target live dates and contacts. Development may begin following the kickoff. ### 1. Sandbox {#1-sandbox} #### What is the Sandbox? {#what-is-the-sandbox} The Sandbox is an unattended, simulated testing environment available to customers integrating through APIs. It allows you to establish API connectivity, validate payload formatting and test application responses using predefined scenarios. The Sandbox does not contain your programme-specific configuration and does not generate the settlement files and transaction reports used in normal transaction processing. #### Set up your Sandbox project {#set-up-your-sandbox-project} Complete the following activities: * Create a project on Mastercard Developers * Select **Cross-Border** from the available APIs * Initiate a Sandbox certificate request * Download the certificate and import it into your development environment * Install and configure the required API libraries and files * Establish connectivity to the Sandbox environment #### Develop and test your integration {#develop-and-test-your-integration} * Make requests to the Sandbox environment * Format requests according to the Mastercard Specifications for APIs * Complete the applicable Sandbox test scenarios * Validate that API payloads are correctly formatted * Validate how your application processes responses * Test applicable reject and error scenarios * Review responses and update your application where required Cross-Border Services enforces field-format and data-quality requirements. Your integration should be able to process API errors identifying the relevant field and error reason when submitted data does not meet the required specification. #### Security and encryption {#security-and-encryption} Cross-Border Services APIs require secure authentication and payload encryption. * Implement the authentication requirements applicable to your programme * Implement JSON Web Encryption (JWE) for payload encryption * Validate encryption and decryption of API messages * Establish an approach for API key renewal **Best practice:** Set up your API project using an email address associated with a distribution list or shared mailbox so key-renewal reminders reach the appropriate contacts. Set a reminder to add and transition to a new key before the existing key expires. #### Ready for MTF? {#ready-for-mtf} Before entering MTF, ensure: * Your Program Form is signed * Your programme scope assessment is complete * All applicable Sandbox test scenarios have been successfully completed * Your application appropriately handles the Sandbox responses * Development against the Mastercard Specifications and Endpoint Guide has been completed for the selected destination endpoints * Mastercard has completed configuration based on the Participation Agreement * Your Partner ID has been provided * You have received and reviewed the MTF test plan and test cases * Requests are correctly formatted according to the applicable Mastercard API or Payment File Processing specifications * Your application has been updated to address issues identified during Sandbox testing ### 2. Mastercard Test Facility (MTF) {#2-mastercard-test-facility-mtf} #### What is MTF? {#what-is-mtf} MTF allows you to test the code developed and validated in Sandbox against configured Cross-Border Services endpoints. Unlike Sandbox, MTF tests your programme-specific configuration. Settlement files are generated for successful transactions, allowing you to test settlement and reconciliation processes. Daily Transaction Reports and Status Change Reports are also provided. #### Validate your programme configuration {#validate-your-programme-configuration} * Validate connectivity using your configured Partner ID and endpoints * Validate the Service Configurations included in your programme * Validate your applicable APIs or Payment File Processing integration * Validate your selected Mastercard FX Rate configuration * Validate applicable pricing functionality * Validate optional APIs and services included in your scope #### Test using the Endpoint Guide {#test-using-the-endpoint-guide} The Endpoint Guide provides configuration and operational information specific to your Participation Agreement, including mandatory and optional fields for selected destination endpoints. Configuration information may also be retrieved using the Endpoint Guide API. * Review the Endpoint Guide for your selected destinations * Validate required fields for each applicable Service Configuration * Validate conditional and optional fields * Confirm your application conforms to Mastercard Specifications for your selected endpoints * Validate the handling of errors and rejected Transactions **Important:** Fields identified as required must be provided for the individual Transaction. Missing required information may result in the Transaction being rejected or delayed through a Request for Information (RFI). #### Complete functional testing {#complete-functional-testing} * Complete all applicable MTF test cases * Validate successful transaction scenarios * Validate applicable status and error scenarios * Complete error-code mapping * Complete front-end interface validations * Verify and reconcile Sender pricing outputs * Resolve identified defects before progressing to the next testing stage #### Validate settlement and reporting {#validate-settlement-and-reporting} * Validate the settlement process associated with your settlement model * Receive settlement files generated for successful test Transactions * Validate settlement reconciliation * Validate receipt and processing of the Daily Transaction Report (DTR) * Validate receipt and processing of the Status Change Report (SCR) * Validate other applicable settlement reporting for your selected model #### Ready for Production Validation Testing? {#ready-for-production-validation-testing} Before progressing, complete your applicable MTF testing and ensure that issues identified through testing have been addressed. Final pre-production criteria require completion of all MTF test cases, error-code mapping, front-end interface validation, testing and reconciliation of Sender pricing outputs. ### 3. Production Validation Testing (PVT) {#3-production-validation-testing-pvt} #### What is PVT? {#what-is-pvt} Production Validation Testing, also referred to as soft launch, takes place in the **Production environment** and uses live Transactions to confirm that connectivity, configuration, settlement and other elements of your Service Configuration function as expected. PVT should use a representative subset of your Service Configurations across the relevant regions. #### Prepare for PVT {#prepare-for-pvt} * Agree the PVT/soft-launch plan with Mastercard * Identify the Service Configurations that will be included * Identify the production accounts that will be used * Generate your production key and provide it to your assigned Mastercard implementation manager for configuration * Confirm production configuration is complete * Confirm your aggregate Transaction amount limit has been established and verified Production Validation Transactions use production accounts. Where you cannot provide your own Receiving Accounts, Mastercard will make every effort to provide selected Receiving Accounts. Transactions performed during production validation and soft launch are not reimbursable. #### Recommended PVT parameters {#recommended-pvt-parameters} The Product Guide recommends: * **Transactions:** 1 to 2 Transactions per Service Configuration * **Maximum individual Transaction:** USD 5.25 * **Maximum cumulative PVT amount:** USD 500, Mastercard default * **PVT duration:** one week * **Completion:** at least five days before the commercial launch date * **Production accounts:** provided by the Cross-Border Services Customer #### Complete end-to-end production validation {#complete-end-to-end-production-validation} * Perform attended connectivity testing with impacted stakeholders * Validate Quotes API calls for each applicable currency pair * Validate Payments for each currency where accounts are available * Complete 1 to 2 Transactions for applicable Service Configurations * Validate production settlement * Validate receipt and processing of the Settlement Reconciliation File, where applicable * Validate the Daily Transaction Report * Validate the Status Change Report or Status Change Push, as applicable * Resolve all issues and defects identified during PVT **Best practice:** Conduct PVT on Monday or Tuesday where possible so that time remains available to address identified issues #### Prepare for commercial launch {#prepare-for-commercial-launch} * Provide Mastercard with at least five business days' notice before your requested production launch date * Establish a contingency date in case the planned production move cannot proceed * Complete PVT and resolve identified issues * Agree the commercial launch date jointly with Mastercard ### 4. Production readiness {#4-production-readiness} Before moving to commercial Production, complete the following final readiness checks. #### Testing complete {#testing-complete} * All applicable MTF test cases are complete * Error-code mapping is complete * Front-end interface validations are complete * Sender pricing outputs have been tested and reconciled * PVT is complete * All PVT issues and defects have been resolved * You have received a **Testing Acknowledgement Notification (TAN)** The TAN must be issued before commercial production launch. #### Service and support readiness {#service-and-support-readiness} * Your teams understand how to access Cross-Border Services support resources * You have developed an end-user support plan and Mastercard has confirmed the plan * Mastercard Connect access has been established * Administrators and users have been assigned * RFI Exchange Tool training and set-up have been completed #### Go-live readiness {#go-live-readiness} * Your production key has been generated and provided to the assigned Mastercard implementation manager * Mastercard has confirmed that due-diligence requirements have been met and passed * Mastercard production configuration is complete * Your aggregate Transaction amount limit has been established and verified * The production validation/soft-launch plan has been completed and agreed * The implementation and go-live date have been jointly agreed with Mastercard ### 5. Go live {#5-go-live} Once Production readiness requirements are complete: * Confirm the Testing Acknowledgement Notification has been received * Confirm the agreed commercial go-live date * Complete the transition to commercial Production processing * Ensure operational and support contacts are current * Ensure your teams can receive relevant Cross-Border Services operational and product communications Any Transaction thresholds established specifically for PVT are lifted once the PVT phase is complete and the commercial launch date is jointly set. ### 6. After go-live {#6-after-go-live} #### First 30 days {#first-30-days} Project post-implementation support is provided for 30 days following implementation as soon as your production configuration is enabled at Mastercard. During this period, use your dedicated customer delivery implementation resource for support. Continue to monitor: * Transaction processing and statuses * Settlement and reconciliation * Applicable Transaction and settlement reports * Operational support processes #### Ongoing support {#ongoing-support} From day 31 following implementation, ongoing support is managed by the Cross-Border Services Customer Support team. Maintain up-to-date operational contacts and monitor applicable service communications, including product bulletins, planned maintenance, Receiving System changes, incidents, settlement events, Service Configuration changes, key-expiration notifications and Mastercard FX Rate updates.