# Quick Start Guide source: https://developer.mastercard.com/account-to-account-commerce-for-dsp/documentation/getting-started/index.md ## Overview {#overview} The debtor service provider interested in consuming Account to Account Commerce service must contact the Local Mastercard representative to commence the onboarding process. You can also reach out to us by filling the form [here](https://www.vocalink.com/contact-us/). ## What does this API do? {#what-does-this-api-do} Mastercard Account to Account Commerce enables debtor service providers (DSPs) to offer fast, secure, and convenient pay-by-bank experiences through their customers' mobile banking apps. Using these APIs, DSPs can allow customers to view account balances before checkout, authorize payments directly from their bank accounts, initiate refunds, save accounts for future purchases, and manage recurring payment agreements. Account to Account Commerce supports payment requests across a wide range of industries, including food delivery, online retail, bill payments, and ride-hailing services. The APIs can be integrated into websites and mobile applications to deliver a seamless, conversion-optimized checkout experience for both businesses and consumers. ## Who should use this API? {#who-should-use-this-api} This API is intended for: * Debtor Service Providers (DSPs) offering mobile banking applications and digital banking services * Banks and financial institutions enabling account-to-account payment experiences for their customers * Digital banking platforms integrating pay-by-bank checkout capabilities * Mobile banking app providers supporting payment requests, refunds, and recurring payments * Open banking and payment service providers facilitating secure bank-to-bank transactions * Developers building account-to-account payment experiences within websites, mobile apps, and digital commerce platforms ## Main Supported Flows {#main-supported-flows} Mastercard Account to Account Commerce enables Debtor Service Providers (DSPs) to offer secure, seamless, and conversion-optimized pay-by-bank experiences through their customers' mobile banking applications. It supports key payment journeys such as account balance verification before payment, direct bank account payments, recurring payments, refunds, and payment authorization for frequent purchases. By integrating with Account to Account Commerce, DSPs can enable their customers to securely approve payment requests, use their bank accounts for one-time or recurring transactions, and receive refunds directly to their accounts. The solution supports a wide range of merchant use cases across industries such as food delivery, online retail, bill payment, and ride-hailing. For more information on supported payment journeys and implementation scenarios, refer to the Use Cases topic. ## Process Flow {#process-flow} ![Account to Account Commerce Debtor Serviece Provider Process Flow](https://static.developer.mastercard.com/content/account-to-account-commerce-for-dsp/documentation/images/A2AC_dsp_process_flow.png) ## Account-to-Account Commerce Onboarding Process, Activities, and Customer Responsibilities {#account-to-account-commerce-onboarding-process-activities-and-customer-responsibilities} Any customer seeking to implement the Account-to-Account (A2A) Commerce service must be onboarded onto the Mastercard platform. The onboarding process includes several key activities along with specific customer responsibilities to ensure successful implementation. ### Key Onboarding Activities and Customer Responsibilities {#key-onboarding-activities-and-customer-responsibilities} * Sign the Agreement * Sign the Mastercard Account-to-Account Commerce Agreement. * Obtain Credentials and Access * Obtain Mastercard credentials, including Interbank Card Association (ICA) and Mastercard Connect access. * Create a [Mastercard Developers Account](https://developer.mastercard.com/account/sign-up), and register on [Mastercard Connect](https://www.mastercardconnect.com). * Provide Resources and Information * Provide the necessary resources to support onboarding and testing activities. * Share required participant information for onboarding. * Code Development and Implementation * Develop and implement A2A Commerce according to the technical specifications in the API Reference. * Security Setup (Key Exchange) * Exchange and manage certificates and cryptographic keys through the Key Management Portal (as outlined in [API Basics](https://developer.mastercard.com/account-to-account-commerce-for-dsp/documentation/api-basics/index.md)). * Connectivity Setup * Provide a network to establish connectivity between the participant and Mastercard. * Set up a logical address for file exchange. * Data Onboarding and Testing * Complete data onboarding to internal systems, including approximately 7 days in the Mastercard Test Facility (MTF) followed by production onboarding. * Perform certification in MTF and conduct connectivity testing. * Deployment and Launch Preparation * Deploy the solution to production. * Plan and prepare for launch. ## Get access to the API {#get-access-to-the-api} 1. Go to [Mastercard Developers Account](https://developer.mastercard.com/account/sign-up), and register on [Mastercard Connect](https://www.mastercardconnect.com). 2. Activate your account by opening the link sent to your email address, and log in. 3. Open your [My Projects](https://developer.mastercard.com/dashboard) page and start a new project. Sandbox access is open, so you can begin testing as soon as your project credentials are generated. ## Create a project and generate Sandbox credentials {#create-a-project-and-generate-sandbox-credentials} Create a Mastercard Developers project to generate your Sandbox credentials. Sandbox give you access to rich, mocked data that helps you understand the API and validate your integration before requesting Production access. To create a Sandbox project, refer to [Creating Sandbox](https://developer.mastercard.com/account-to-account-commerce-for-dsp/tutorial/creating-a-sandbox-project/index.md) guide. ## First Sandbox call {#first-sandbox-call} Once you have your credentials, you can make your first call to the Sandbox environment. To run test cases, refer to [Invoking API using Insomnia](https://developer.mastercard.com/account-to-account-commerce-for-dsp/tutorial/insomnia/index.md). ## Integrate and Test {#integrate-and-test} ### Testing the Service {#testing-the-service} Now that you have your credentials, choose your preferred method to start testing immediately: * GUI-based tools (Insomnia): See Testing with [Insomnia](https://developer.mastercard.com/account-to-account-commerce-for-dsp/documentation/testing/index.md). * Reference Application: See the [Reference Application](https://developer.mastercard.com/account-to-account-commerce-for-dsp/documentation/reference-app/index.md) page. ## Promote the same project to Production {#promote-the-same-project-to-production} Once your project is working in Sandbox, request Production access for that same project. To request a production access, refer to [Move to Production](https://developer.mastercard.com/account-to-account-commerce-for-dsp/tutorial/move-to-production/index.md) guide. ## Key conventions {#key-conventions} | Terms (Acronyms in brackets) | Description | |------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | API Gateway (APIGW) | The API Gateway provides routing, configuration, authentication, and authorization for API traffic between Mastercard and its customers. The primary function of the API Gateway is to act as a security policy enforcement point for Mastercard APIs exposed to customers. | | Creditor | An individual or business who makes a request to the debtor (payer) for payment, either for a bill, invoice, or funds transfer.​ | | Creditor Service Provider (CSP) | An entity that consumes Account to Account Commerce services to (1) associate a creditor to a debtor for the purpose of facilitating bill and invoice presentments and peer-to-peer fund transfers, and (2) exchange payment request data with the debtor service providers for such presentments and fund transfers. | | Debtor | An individual or business who authorizes a debit of their financial account to make payment for a bill, invoice, or funds transfer request. | | Debtor Service Provider (DSP) | An entity, often but not exclusively a financial institution, that consumes Account to Account Commerce services to (1) associate a debtor to a creditor for the purpose of facilitating bill and invoice presentments and fund transfers, and (2) exchange payment request data with creditor service providers for such presentments and fund transfers. | | Designated Settlement System (DSS) | Refers to the method of processing settlement instructions and includes a payment system. A payment system is used for transferring funds. | | Initiating Party | Unique identification of the party that has initiated the message exchange. | | Operator | An entity that operates Mastercard's requests for pay products, services, and solutions. The operator holds and manages the business relationships with creditor service providers, creditor institutions, debtor service providers, and debtor institutions, determines which entities are allowed to be onboarded to Mastercard's Request for Pay (RFP) programmes, and sets 'resale' pricing of Mastercard RFP services for creditor service providers, creditor institutions, debtor service providers, and debtor institutions. | | Key Management Portal (KMP) | Self-service portal, available in Mastercard Connect, for participants to request and exchange keys and certificates with Mastercard. | | Key Management Services (KMS) | The business function within Mastercard is responsible for key and certificate exchange. | | Mastercard Connect (MCConnect) | [Mastercard Connect](https://www.mastercardconnect.com/) is a secure global platform for business customers to explore, onboard, enrol, service, and grow their businesses with Mastercard. | | Mastercard Test Facility (MTF) | Test environment for customers to perform testing with Mastercard. | | AtoAC | Account to Account Commerce | | Participant (Customer) | A creditor service provider or a debtor service provider. | | Zapp Platform | Zapp is the core platform powering the Account to Account Commerce solution. | ## Next Steps {#next-steps} 1. Use the [API Reference](https://developer.mastercard.com/account-to-account-commerce-for-dsp/documentation/api-reference/index.md) section for details on environmental domains and specifications for each API. 2. Refer to the [API Basics](https://developer.mastercard.com/account-to-account-commerce-for-dsp/documentation/api-basics/index.md) page to understand the Mastercard environments and the required project keys. 3. For information on testing and test cases for each API, visit the [Testing](https://developer.mastercard.com/account-to-account-commerce-for-dsp/documentation/testing/index.md) page.