Architecture & Connectivity
This document details the Cloud-to-Cloud (C2C) architectural framework used to integrate the Getnet Integrated POS with your external Cashier Software. By utilizing a cloud-based API, this model abstracts local hardware complexities and enables secure, remote transaction management.
The Cloud-to-Cloud (C2C) Integration Model
The C2C model represents a paradigm shift from traditional local integrations. Instead of communicating directly with the terminal via a physical connection or local network, your Cashier Software routes all commands through a secure Cloud API.
High-Level Architectural Flow
The communication process follows a strictly defined path from your infrastructure to the payment authorizer:
- Merchant Software: Initiates a request via a JWT-authenticated API over an encrypted HTTPS channel.
- Cloudflare WAF: Acts as a security gateway, validating requests through IP whitelisting or a dedicated API-KEY.
- Getnet Cloud (Adcom Platform): Receives the request and identifies the target terminal to route the command.
- Terminal POS: Receives the instruction from the cloud to begin the payment process.
Terminal Component Stack
The physical POS terminal is not merely a card reader; it runs a sophisticated internal software stack designed to maintain a persistent, secure connection with the Getnet Cloud.
- G-Services: The primary service on the device that validates communication with the Getnet Cloud.
- Connector App: Acts as the bridge between cloud-based commands and local hardware intents.
- App de Pagos Getnet: The core payment application that interacts with the user's card and communicates directly with the Payment Authorizer via PCI-compliant channels.
Connectivity Requirements
To ensure a seamless integration, you must meet the following infrastructure requirements:
Minimum Technical Prerequisites
[!NOTE] API Proficiency: Development teams must be experienced in consuming cloud-based APIs. All communications must be performed over HTTPS to ensure data integrity.
- Network Stability: While the API handles routing, the terminal requires a stable internet connection to receive instructions within the defined timeout windows.
Connectivity Parameters
When moving to production, the connection method is determined by your server's infrastructure:
| Infrastructure | Security Mechanism |
|---|---|
| Fixed IP Server | Your server's IP is added to the WAF whitelist. No code changes are required for this transition. |
| Variable/Dynamic IP | A unique API-KEY is configured in the WAF and must be included in the header of every endpoint request. |
[!IMPORTANT] The Getnet Cloud API will remain open for up to 5 minutes while waiting for a terminal response before canceling the operation due to a timeout. Ensure your backend can handle long-lived connections for synchronous transactions.