# Submit Your Integration for Validation

Once your Manufacturer Service App passes every mandatory scenario, submit a fixed set of artifacts to Getnet. Getnet uses them to validate your integration and continue the homologation process.

## How it works

Getnet reviews proof that your hardware is certified, the results of your EMV testing, and a build of your service for independent verification. Submit all three together, plus any supporting documentation your integration needs.

## Before you begin

Complete every mandatory scenario in the [Manufacturer Test App](/en/pos-manufacturers/first-steps-pos-mfg/quick-start-devkit) and generate `hal_test_scenarios.zip`.

## Step 1: Gather your LOAs

Collect every Letter of Approval (LOA) issued for your POS, both L1 and L2.

## Step 2: Collect the test report

Locate `hal_test_scenarios.zip`, generated by the Manufacturer Test App's **Send report** button, in your device's Downloads folder.

## Step 3: Package your service APK

Build an APK of your Manufacturer Service App for Getnet to validate independently.

## Step 4: Include any additional documentation

Include documentation for any library or process your integration depends on that this guide doesn't cover. Getnet needs it to evaluate your integration completely.

## What happens next

Getnet reviews your LOAs, test report, and APK before confirming your device's homologation status. If Getnet needs more information, expect a request about the specific library or process involved — see Step 4.

## Next steps

* [POS Manufacturers Overview](/en/pos-manufacturers/pos-manufacturers-overview) — where this submission fits in the overall process.
* [HAL architecture](/en/pos-manufacturers/core-concept-pos-mfg/hal-architecture) — revisit the contract your service implements if Getnet requests changes.