# Manage DPAs
source: https://developer.mastercard.com/mastercard-checkout-solutions/tutorial/onboarding-sandbox/step9/index.md

## 9. Managing your DPAs {#9-managing-your-dpas}

Digital Payment Applications (DPAs) could be a merchant e-commerce website or mobile application with unique registrations for each digital channel. To initiate payments for Click to Pay, Guest Checkout Tokenization, or Secure Card on file programs, you must register your DPAs.

|            Program             | DPA Registration |
|--------------------------------|------------------|
| Click to Pay                   | Mandatory        |
| Guest Checkout Tokenization    | Mandatory        |
| Commerce Platform Direct       | Optional         |
| On Behalf of Commerce Platform | Optional         |
| Merchants Direct               | Mandatory        |
| On Behalf of Merchants         | Mandatory        |
| On Behalf of Shared Merchants  | Mandatory        |

## Program Information {#program-information}

On the **DPA management** page, you will see all the available program types for that project. The program information for each of the active program types is listed in tabular form.

When the program information shows "pending" approval, there is a pending tag beside the program information section.

## Generate Test DPA Data {#generate-test-dpa-data}

To generate sample SRC DPA ID (also referred to as `srcDpaId`) values for initial testing on Sandbox:

1. Click on the projects tab and open a project.
2. Go to the **DPA Management** tab and click **Generate Data**.
3. In the Generate test data dialog box, select the applicable program.
4. This table lists the actions you should do in the Generate test data dialog box to create test data for each Program Type.

|             Program Type             |                                                                                           Action                                                                                           |
|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Click to Pay                         | * Select **Yes** if you want Click to Pay to return token-based credentials in the payload * Select **No** for PAN-based credentials.                                                      |
| Commerce Platform Direct model       | Select the name of an available Commerce Platform you want to create the test data for and click **Generate** to create test ID values.                                                    |
| Guest Checkout Tokenization          | Click the **Generate** button to create test ID values.                                                                                                                                    |
| Merchant Direct model                | Select the name of an available Merchant you want to create the test data for and click **Generate** to create test ID values.                                                             |
| On Behalf of Merchant Model          | Click the **Generate** button to create test ID values.                                                                                                                                    |
| On Behalf of Shared Merchant Model   | Click the **Generate** button to create test ID values.                                                                                                                                    |
| On Behalf of Commerce Platform Model | Click on the 'On Behalf of Commerce Platform Model' from the Program Type, choose the commerce platform name and the client name combination, and click on **Generate** to test ID values. |

You can follow the same steps to generate a maximum of six SRC DPA ID Values. You will need to wait for a while (up to 5 minutes) before the test data shows up.

At any point if you choose to delete any test DPA data, use the **Delete** button in the Test DPAs section.

### Use the Sample serviceId {#use-the-sample-serviceid}

To call the DPA Registration API in the Sandbox, you will require a sample `serviceId` value. Along with the test DPA data, a sample `serviceId` is available for your initial testing in the Sandbox environment. For more information on the usage of `serviceId` refer to [Enroll Card API](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/api-reference/apis/index.md#card).

![ServiceId in Test DPA](https://static.developer.mastercard.com/content/mastercard-checkout-solutions/documentation/images/mcc_test_dpas.png "ServiceId and Program Name")

## DPA Registration API {#dpa-registration-api}

When you have finished testing, the sample data should be replaced. You can create new DPA data by calling the [DPA Registration API](https://developer.mastercard.com/mastercard-checkout-solutions/documentation/api-reference/apis/index.md#registration).

The following table outlines the required fields for UPDATE function for each program type:

|             Program Type             |         Mandatory fields for UPDATE function          |
|--------------------------------------|-------------------------------------------------------|
| Click to Pay                         | * `dpaName` * `srcDpaId` * `dpaAddress.countrycode`   |
| Merchant Direct Model                | * `serviceId` * `srcDpaId` * `dpaName`                |
| Commerce Platform Direct Model       | * `serviceId` * `srcDpaId` * `dpaName`                |
| On Behalf of Merchant Model          | * `serviceId` * `programName`                         |
| On Behalf of Shared Merchant Model   | * `serviceId` * `programName`                         |
| On Behalf of Commerce Platform Model | * `serviceId` * `srcDpaId` * `dpaName` * `customerId` |
| Guest Checkout                       | * `dpaName` * `srcDpaId`                              |

Note: Under 'On Behalf of Commerce Platform Model', 'On Behalf of Merchant Model', and 'On Behalf of Shared Merchant Model', a Technical Integrator can execute DPA Registration APIs only for their approved clients.