# Quick Start Guide source: https://developer.mastercard.com/fld-fraud-submission/documentation/quick-start-guide/index.md ## Overview {#overview} Use this guide to go from account setup to your first successful Sandbox request for the Confirmed Fraud API. You will create a project, generate credentials, make a test call, and prepare the same project for Production access. ### Before you begin {#before-you-begin} * Create a [Mastercard Developers](https://developer.mastercard.com/) account. * Have a secure place to store downloaded OAuth and encryption keys. * Decide how you want to test: Insomnia, the reference application, or your own client. ### Sandbox checklist {#sandbox-checklist} | # | Step | What to do | |---|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 1 | Access | Get access to the Confirmed Fraud API and create your Mastercard Developers project. | | 2 | Credentials | Generate your Sandbox OAuth credentials and record your consumer key. | | 3 | Environment | Confirm that you are using the Sandbox base URL and that your project is still in Sandbox mode. | | 4 | Authentication | Configure OAuth 1.0a signing for the first request and confirm which consumer key and private key pair you will use. | | 5 | Encryption | Complete Mastercard Encryption setup in [API Basics](https://developer.mastercard.com/fld-fraud-submission/documentation/api-basics/index.md) before testing protected-payload flows such as fraud submission (FDA) and change (FDC). | | 6 | First call | Send your first Sandbox request using the Sandbox base URL and OAuth 1.0a signing. | | 7 | Validation | Use the sample response and [Testing](https://developer.mastercard.com/fld-fraud-submission/documentation/testing/index.md) page to validate positive, negative, and follow-on flows. | ## Step 1: Get access to the API {#step-1-get-access-to-the-api} 1. Go to [Mastercard Developers](https://developer.mastercard.com/) and create an account. 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. APIs with a 'lock icon' require permission to view their documentation and create a project; to gain access, submit an access request form and you will receive an email confirmation approving or denying your access. ## Step 2: Create a project and generate Sandbox credentials {#step-2-create-a-project-and-generate-sandbox-credentials} Create a Mastercard Developers project to generate your Sandbox credentials. Sandbox gives you rich, mocked data so you can validate your integration before requesting Production access. ### Project Details {#project-details} 1. Click 'Create new project' on your [My Projects](https://developer.mastercard.com/dashboard) page. 2. Enter a project name. 3. Indicate whether you are creating the project on behalf of a client. Note: Check **Yes** if you are creating an API integration project for a customer. For example, you act as an integrator, a processor, or a service provider, and your customer is a merchant, an issuer, or an acquirer. 4. In the **Select at least one API field** , choose **Confirmed Fraud API** and click **Proceed**. Note: If you are creating a project for a client, the commercial countries are where the client does business. ![Project](https://static.developer.mastercard.com/content/fld-fraud-submission/uploads/t1.png) ### Project Credentials {#project-credentials} Use the Keystore password with the .p12 file and client ID for OAuth authentication. These credentials give you access to the sandbox service in this project. 5. In the **Key alias** box, enter a unique value to identify the key. 6. In the **Keystore password** box, enter a password for keystore. ![Oauth](https://static.developer.mastercard.com/content/fld-fraud-submission/uploads/t2.png) 7. Download, and keep safe, your PKCS#12 (.p12) keystore file. 8. Click **Proceed**. ### Additional Credentials {#additional-credentials} Payload encryption and decryption require both client and Mastercard encryption keys. 9. In the **Key alias** box, enter a unique value to identify the key. 10. In the **Keystore password** box, enter a password for keystore. ![Project](https://static.developer.mastercard.com/content/fld-fraud-submission/uploads/t3.png) 11. Click **Create Project**. ### Create your sandbox project {#create-your-sandbox-project} Your sandbox project has been successfully created. The Mastercard Developers portal has generated your project keys, which are ready for download. 12. To save the project key, click the **Download key file** . Save this key in a safe location. 13. To view the project summary, click **Open project**. Note: Downloading the project keys file enables the **Open project** button. After confirmation, you will receive an email that includes the provisioning request and keys. ![Project](https://static.developer.mastercard.com/content/fld-fraud-submission/uploads/t4.png) 14. On the project dashboard, record the following values: * Sandbox and Production status * Authentication consumer key * Client encryption key fingerprint ![uploads](https://static.developer.mastercard.com/content/fld-fraud-submission/uploads/t5.png) ### Save the values you will need {#save-the-values-you-will-need} 15. After you finish this flow, you will land on the Project page. There, record the following: * Sandbox and Production status ('Ready' or 'Not Requested'). * Authentication consumer key. * Client encryption key fingerprint. ## Step 3: Make your first Sandbox request {#step-3-make-your-first-sandbox-request} Once you have Sandbox credentials, make a **GET** request to `/fraud-statuses/icas/{ica}` to confirm your project setup. Use the Sandbox base URL `https://sandbox.api.mastercard.com/fld/confirmed-frauds` and configure OAuth 1.0a signing for every request. Before you run the request, make sure that you have: * Your Sandbox consumer key. * The private key used to sign OAuth requests. * A Mastercard OAuth library or signer that generates `oauth_timestamp`, `oauth_nonce`, and `oauth_signature`. This first-call example uses `GET /fraud-statuses/icas/{ica}`, so you can verify access, OAuth signing, and the Sandbox base URL before moving on to encrypted submission flows. Note: This status query returns a plaintext response and does not require payload encryption. Submission flows such as fraud add (FDA) and change (FDC) do require **Mastercard Encryption** . For a full client setup, including encryption configuration, see the [API Basics](https://developer.mastercard.com/fld-fraud-submission/documentation/api-basics/index.md) section. **Example Request (cURL):** * Bash ```bash curl --request GET \ --url "https://sandbox.api.mastercard.com/fld/confirmed-frauds/fraud-statuses/icas/1076?ref_id=ecb2d942-eabd-42b6-87fd-69c19692bdc6" \ --header "Authorization: OAuth oauth_consumer_key=\"YOUR_CONSUMER_KEY\", oauth_signature_method=\"RSA-SHA256\", oauth_timestamp=\"1709596800\", oauth_nonce=\"a1b2c3d4e5f6\", oauth_version=\"1.0\", oauth_signature=\"YOUR_COMPUTED_SIGNATURE\"" ``` This example shows the required OAuth 1.0a header fields explicitly, but uses placeholders for sensitive values. Replace `YOUR_CONSUMER_KEY` with the consumer key from your project and generate `oauth_signature` with a Mastercard OAuth library. The library also handles `oauth_timestamp` and `oauth_nonce` for you. **Expected Response:** * Json ```json { "refId": "ecb2d942-eabd-42b6-87fd-69c19692bdc6", "timestamp": "2021-03-16T20:34:40-06:00", "icaNumber": "1076", "responseCode": "000", "responseMessage": "Success", "auditControlNumber": "123111111000025", "channel": "EXT_API", "currentStatus": "CONFIRMED-SUCCESS", "matchLevelIndicator": "M", "financialTransactionIndicator": "DECLINED", "authorizationResponse": "05 - Do not honor" } ``` ### What success looks like {#what-success-looks-like} * The request returns `200 OK`. * The response body includes a `responseCode` of `000` and `responseMessage` of `Success`. * The record includes an `auditControlNumber` and a `currentStatus` such as `CONFIRMED-SUCCESS`. * You can reuse the returned `auditControlNumber` in [Use Cases](https://developer.mastercard.com/fld-fraud-submission/documentation/use-cases/index.md) for change (FDC), delete (FDD), or confirm (FDE) scenarios. Note: **Test data:** The Sandbox includes dummy data with a limited set of sample records. For a negative-flow test, pass an invalid combination (for example, an `ica` with no matching record). The API returns a `400 Bad Request`. See [Testing](https://developer.mastercard.com/fld-fraud-submission/documentation/testing/index.md) for additional scenarios. ## Step 4: Choose how you want to test and integrate {#step-4-choose-how-you-want-to-test-and-integrate} After the first Sandbox request succeeds, pick the integration path that matches your workflow: * **Insomnia:** Use the [Insomnia Collection](https://developer.mastercard.com/fld-fraud-submission/documentation/developer-tools/insomnia/index.md) page for setup. * **Generate your own API client:** 1. Navigate to the [API Reference](https://developer.mastercard.com/fld-fraud-submission/documentation/api-reference/index.md) section. 2. Download the API specification, [confirmed-fraud.yaml](https://static.developer.mastercard.com/content/fld-fraud-submission/swagger/confirmed-fraud.yaml) (80KB). 3. Generate and configure an API client for this API. For more information, refer to [Testing](https://developer.mastercard.com/fld-fraud-submission/documentation/testing/index.md). 4. Configure your client using our [client libraries](https://developer.mastercard.com/platform/documentation/security-and-authentication/securing-sensitive-data-using-payload-encryption/#client-libraries). Note: For a detailed step-by-step guide, see [Generating and Configuring a Mastercard API Client](https://developer.mastercard.com/platform/documentation/security-and-authentication/generating-and-configuring-a-mastercard-api-client/). ## Step 5: Promote the same project to Production {#step-5-promote-the-same-project-to-production} Once your project is working in Sandbox, request Production access for that same project. ### Transition your project from Sandbox to Production {#transition-your-project-from-sandbox-to-production} 1. **Open your project in Mastercard Developers.** Go to your [My Projects](https://developer.mastercard.com/dashboard) page and open the Confirmed Fraud project you used for Sandbox testing. 2. **Request Production access for that project.** In the project dashboard, select **Request Production Access** . Your Sandbox and Production statuses are shown separately on the project page, so you can track when Production moves from `Not Requested` to an enabled `Ready` state. 3. **Generate or download your Production keys:** After Production access is approved, download the Production OAuth and encryption keys for the same project. Keep the Production key material separate from your Sandbox keys. 4. **Enter your Production key alias and keystore password**, and save them for future reference. 5. **Update your application configuration.** Switch the base URL from Sandbox to Production. Use the India base URLs instead if your data must remain in India: * Sandbox (Global): `https://sandbox.api.mastercard.com/fld/confirmed-frauds` * Sandbox (India): `https://sandbox.api.mastercard.co.in/fld/confirmed-frauds` * Production (Global): `https://api.mastercard.com/fld/confirmed-frauds` * Production (India): `https://api.mastercard.co.in/fld/confirmed-frauds` Update your application to use the Production consumer key, signing key, and encryption certificates. Note: OAuth 1.0a authentication and Mastercard payload encryption work the same way in Sandbox and Production. The main changes are the Production key set, the Production approval state, and the Production base URL. Production credentials generate instantly, but you need approval for Production environment access before going live. You get a notification when your access is approved or denied. If you need the full onboarding process, including contract, SLA, and escalation details, see the [Onboarding Checklist](https://developer.mastercard.com/fld-fraud-submission/documentation/onboarding-checklist/index.md) for detailed guidance. ## Next Steps {#next-steps} Continue with the documentation that matches your next task: * [API Reference](https://developer.mastercard.com/fld-fraud-submission/documentation/api-reference/index.md) for endpoint details * [API Basics](https://developer.mastercard.com/fld-fraud-submission/documentation/api-basics/index.md) for authentication, encryption, and client configuration * [Use Cases](https://developer.mastercard.com/fld-fraud-submission/documentation/use-cases/index.md) to learn about the different use cases of the service * [Testing](https://developer.mastercard.com/fld-fraud-submission/documentation/testing/index.md) for additional request scenarios * [Onboarding Checklist](https://developer.mastercard.com/fld-fraud-submission/documentation/onboarding-checklist/index.md) for detailed guidance on the full onboarding process, including contract, SLA, and escalation details.