Getnet, as part of the Santander Group , has the mission to help merchants and partners by offering different acquiring solutions that include in-store and online payment capabilties.
Geographical Footprint
Getnet currently is operative in Brasil, Mexico, Chile, Argentina, Uruguay, Spain and Portugal.
Local Acquiring
Save costs with Getnet's local acquiring services that are done by country in a scalable and flexible way.
Security
Security measures and compliance standards across all payment transactions.
Find a guide to integrate all Getnet APIs
Regional API
Single-entry-point (SEP) direct API connection for merchants that desire to operate throughout the region
Web Checkout
Low code payments integration that implies using Getnet's prebuilt checkouts with three types of flavours.
Payment Link API (BR Only)
Solution targeted for merchants and partners that want to automate their payment link operations and processes
Web Chekout Iframe (BR Only)
Low code payments integration that implies using Getnet's prebuilt checkouts with three types of flavours.
Merchant Reporting
Unified and standardized Getnet reports to simplify Merchant´s financial reconciliation processes
Onboarding API
Solution for partners to accelerate onboarding processes with Getnet Brasil.
Agentic Commerce
An overview of Agentic Commerce, a new channel for interaction and purchasing based on autonomous intelligent agents that can take decisions throughout the customer’s purchase journey.
MCP AI Toolkit
MCP AI Toolkit is a solution that enables AI assistants (powered by ChatGPT, Claude, Gemine, N8N and custom agents) to perform payment operations on the GetNet platform.
Payment-Terminals
This API lists the active payment terminals owned by the merchant, including the characteristics of each payment terminal.
Getnet OAuth2 Token API
Authentication via OAuth2 Client Credentials Flow for the Getnet staging environment.
Pendencies API (Partner)
API intended for partners to query onboarding/accreditation pendencies of a Merchant (EC). The goal is to expose a minimum, stable, and secure contract, allowing the partner to identify: (1) which pendencies exist for the EC and (2) the status of each pendency. For pendencies of type DATA_GRID, the response includes the list of registration attributes (gridInfo) that must be reviewed/resolved by the partner, indicating which ones are required.
