Quick Start: Run the Devkit
This guide takes you from a working Manufacturer Service App to a submitted test report. Along the way, you use Getnet’s two validation tools: the Devkit and the Manufacturer Test App.
Before you begin
Complete HAL integration setup. Your service must already bind successfully and respond through IMainService.
Step 1: Run the Devkit
The Devkit connects to your Manufacturer Service App through libposemv and libposdigital. These are the same libraries the Middleware App uses in production. If your service implements the interfaces correctly, the Devkit’s hardware calls work without further configuration — beeper, printer, LEDs, camera, card readers, and the rest.
Use the Devkit first to catch basic implementation issues before moving to EMV-specific testing.
The Devkit is not the same tool as the Manufacturer Test App below. The Devkit checks general hardware calls; the Manufacturer Test App checks EMV processing.
Step 2: Run the Manufacturer Test App
The Manufacturer Test App is a Getnet-built application focused on EMV operations rather than general hardware access. It walks through:
- Service initialization
- Loading AIDs and CAPKs
- A set of mandatory scenarios covering the card brands Getnet requires
Run every mandatory scenario. A scenario you skip blocks the next step.
Step 3: Generate the test report
After you complete the mandatory scenarios, the Manufacturer Test App shows a Send report button. Tap it to generate hal_test_scenarios.zip in your device’s Downloads folder. This file is one of the artifacts Getnet requires to continue the homologation process.
Verify the integration
Confirm all three tools agree your implementation is ready before you submit anything to Getnet.
| Check | What to expect |
|---|---|
| Devkit hardware calls | Beeper, printer, LEDs, camera, and card reads all respond without error. |
| Mandatory scenarios | Every required card-brand scenario in the Manufacturer Test App completes. |
| Test report | hal_test_scenarios.zip exists in the Downloads folder after tapping Send report. |
Next steps
- Submit your integration for validation — send
hal_test_scenarios.zipand the rest of the required artifacts to Getnet. - Implement the hardware services — the exact calls the Devkit makes against your service.
- EMV state machine — the transaction flow the Manufacturer Test App exercises.