Connect your app, your point-of-sale software or your own hardware to Getnet terminals. Choose by where your code runs and how close to the card you need to be.
Your Android app runs on the Getnet smart POS and calls the Getnet payment app to charge the card.
Best for: apps that run on the Getnet terminal itself.
Your point-of-sale software drives a Getnet terminal, over USB, the local network or the cloud.
Best for: retail and hospitality systems with their own cash register.
Your terminal talks to the Getnet host directly, with your own card reading and PIN handling.
Best for: terminal makers and acquirer-level integrations.
Build your own payment app with the Getnet SDK, then customize screens, theme and receipts.
Best for: partners shipping a payment app under their own brand.
Bring Getnet payments to your own terminal hardware through the hardware abstraction layer.
Best for: manufacturers certifying a new terminal.
Pick the sentence that sounds most like you.
| App2App | Integrated POS | Host-to-Host | Getnet Toolbox | POS Manufacturers | |
|---|---|---|---|---|---|
| Where your code runs | Android app on the Getnet POS | Your POS software | Your terminal | Your payment app | Your terminal firmware |
| Talks to | Getnet payment app | Getnet terminal | Getnet host | Getnet SDK | Getnet kernel via HAL |
| Card and PIN handled by | Getnet | Getnet | You | Getnet SDK | You (certified) |
| Integration effort | Low | Low | High | Medium | High |
Tell us what you want to build and we’ll point you to the right solution, or compare every Getnet product in one place.