Introduction to Getnet's SEP

The Regional API (Single Entry Point) is a unified solution that consolidates multiple local payment systems into a single integration. It is designed to address the specific needs of diverse markets by supporting local and global payment methods, enabling businesses to quickly adapt to regional requirements without managing multiple fragmented integrations.

Benefits

Wide variety of payment services Included solutions empower businesses to make their processing tools more flexible for their customers, adapt quickly in a fast-paced and competitive payment landscape, provide better customer experience and, overall, increase conversion rates.

Local Acquiring Country-based processing allows to improve authorizations rates, predictability of cash flow, and most important, ensure local compliance to legal and regulatory requirements.

Core Gateway and Value-added-services Ensures that the customer’s payment data is securely collected and transmitted without difficulties, giving customers peace of mind.

Automatic reporting capabilities A treasury-teams oriented tool that makes data accessible for efficiency and ultimately leads to better decision-making and cost saving.

Global and local schemes support Assistance on a small and large scale can facilitate cross-border payments avoiding unnecessary complications or charges.

Local Acquiring in Brazil, Mexico, Chile and Argentina (URU coming soon).
Core Gateway and Value-Added services.
Automatic reporting capabilities for treasury teams.
Global and local schemes support.

Features by Region

Below, a high-level summary of each one of the features that are going to be enabled in this phase:

Acquirer/PCI Tokenization: Used for tokenizing certain card-holder’s sensitive information on Getnet/PagoNXT’s environment so that Merchants are not required to
Authorization: Feature used to be able to make any normal payment, example: Visa, MasterCard, Amex and Local brands.
Cancels/Refunds: Feature used to cancel/refund already authorized transactions.
Card Verification: Feature used before authorizing a transaction to Verify a cardholder’s limit.
Query Payment: Endpoint is used to query a previously executed transaction and see it’s details.
Recurrence: Feature to be able to execute recurring payments in base of Clients, Plans and Subscriptions.

Available features	Argentina	Brazil	Chile	Mexico
Sales	✔	✔	✔	✔
Refund	✔	✔	✔	✔
Partial Refund	✔	✔	✔	✔
Cancellation	✔	✔	✔	✔
Partial Cancellation		✔	✔	✔
Antifraud	✔	✔	✔	✔
Gateway Tokenization	✔	✔	✔	✔
Vault	✔	✔	✔	✔
Recurrying Payments	✔	✔	✔	✔
3D Secure 2.0	✔	✔	✔	✔
Card Verification	✔	✔	✔	✔
Dynamic Billing Descriptor	✔	✔	✔	✔
Installments	✔	✔	✔	✔
Local Schemes	✔	✔		✔
BIN Lookup		✔	✔	✔
Pre-Authorizations		✔		✔
Network tokenization		✔

Payment Methods by Region

Below are the available payment methods that are supported in each country

Available Payment Methods	Argentina	Brazil	Chile	Mexico
Visa	✔	✔	✔	✔
Mastercard	✔	✔	✔	✔
Amex	✔	✔	✔	✔
Naranja - ARG Local Scheme	✔
Cabal - ARG Local Scheme	✔
Siscard - ARG Local Scheme	✔
Maestro	✔		✔
Elo - BR Local Scheme		✔
Hipercard - BR Local Scheme		✔
PIX - BR Local Scheme		✔
Carnet				✔
Discover				✔

API Authentication

The API's listed in this documentation use OAuth2 authentication, this means that in all requests it is necessary to inform an access token which will be obtained by authentication with your Client ID and Client Secret.

To consume APIs in the homologation environment, use DNS {{host_getnet_api}} https://api.pre.globalgetnet.com To use the APIs in the production environment, use DNS {{host_getnet_api}} https://api.globalgetnet.com

For detailed information on how to use the APIs, see API Explorer.

Generate Access Token

Make a request in your backend, to obtain an access token to the Digital Platform API.

Request

Bash

curl --location '{{host_getnet_api}}/authentication/oauth2/access_token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--header 'Accept: application/json' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id={{PUT_YOUR_CLIENT_ID_HERE}}' \
--data-urlencode 'client_secret={{PUT_YOUR_CLIENT_SECRET_HERE}}'