# Applications
source: https://developer.mastercard.com/open-finance-au/documentation/access-and-config/applications/index.md

Applications are web or mobile apps developed by you to provide services to your customers. You must register each of your applications with Mastercard so that FIs recognise your product as being legitimate when accessing the consented accounts of your customers.

When a customer is created they must be assigned to the application. Each application has a unique set of customers.

## Registering Applications {#registering-applications}

Note: If your application will not be hosted in Australia, contact your Mastercard representative for advice.

To register an application for production, you must complete your contract with Sales. Once the contract is finalised, you need to request application registration in the Mastercard Open Finance system and with the Australian Competition and Consumer Commission (ACCC). Depending on whether you are [an ADR, CDR Representative or BCDC partner](https://developer.mastercard.com/open-finance-au/documentation/access-and-config/access-models/index.md), you must provide the following mandatory information in the API call:

|                                                                                                   As an **ADR** under OSP model                                                                                                   |           As a **Representative** under CDR Representative model           |                                                                            As a **BCDC** model partner                                                                             |
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 1. Application name 2. Legal entity name 3. Policy URL 4. Data complaints email address 5. Software ID 6. Organisation ID 7. Copyright logo 8. Business name 9. From email address 10. Application image 11. ADI exemption status | 1. Application name 2. Description 3. Application URL 4. Application image | 1. Application name 2. Description 3. Application URL 4. Application image 5. Disclosure type 6. Data handling policy URL (provided as policyUrl) 7. Data complaints email address |

For all applications, Consumer Data Right (CDR) rules require disclosure of information about Outsourced Service Providers (OSPs).
To enable Open Finance to provide this information to consumers as part of the consent flow, you must provide the following information
for each OSP your application uses:

1. Name of the OSP
2. Accreditation number (optional)
3. Country where the OSP is based
4. OSP CDR policy URL (optional, but mandatory if accreditation number provided)
5. Purpose statement - a statement detailing why the OSP needs access to consumer CDR data

<br />


API Reference: `POST /applications`

While working in **Sandbox** , application registration happens instantly in the Mastercard system and does not require interaction with the ACCC because no real Data Holders (DHs) are accessed.
You can use an `applicationId` from the application registration API call straight away to proceed with further implementation and testing.

When moving to **Production** , Mastercard will use this information to complete the application registration with CDR register and all supported Data Holders (DHs).
A Solution Engineer may contact you during this time to request your support with the registration process. This will take some time (about 1 month).
Once the registration process is complete, you will be notified. Only then can you use the `applicationId` from the response to proceed with further implementation and testing.
Note: Once an application request is submitted in **Production** environment, notify your Mastercard Solution Engineer. Warning: The **applicationId** of the approved application is required when creating new customers. See [Customers](https://developer.mastercard.com/open-finance-au/documentation/access-and-config/customers/index.md). Attempting to create a customer using the `applicationId` of an application that has not yet been approved will result in an error.

## Checking Application Registration Status {#checking-application-registration-status}

Because application approval can take a long time in the Production environment, the following API endpoint lets you check the status of the application and retrieve its additional details.

API Reference: `GET /applications`

After the application is approved, Mastercard proceeds with registering it with each supported FI.
To check which FIs your application can access, use the following endpoint:

API Reference: `GET /applications/{application_id}/institutions`

## Dealing With Rejected Application Requests {#dealing-with-rejected-application-requests}

If the data provided during application registration does not meet the requirements for the Production environment, the request will be rejected. When you check the status of your application request, the reason for rejection will be included in the `note` field.

API Reference: `GET /applications`

After reviewing the submitted data and confirming that it meets the requirements, you can update your application details by calling the following API:

API Reference: `PUT /applications/{application_id}`

Note: Once application update request is submitted or if you have any issues with the process, please notify your Mastercard Solution Engineer.

## Next Steps {#next-steps}

* Once the application is approved and you receive an applicationId, you can create active [customers](https://developer.mastercard.com/open-finance-au/documentation/access-and-config/customers/index.md).
* To learn more about Consent, which allows you to access your customer's accounts, refer to [Consent](https://developer.mastercard.com/open-finance-au/documentation/consent/index.md).
* To learn more about Connect, which allows your customers to consent access to their accounts, refer to the [Connect Application](https://developer.mastercard.com/open-finance-au/documentation/connect/index.md).
* For the full list of testing profiles available, refer to [Test Profiles](https://developer.mastercard.com/open-finance-au/documentation/integration-and-testing/test-the-apis/index.md).