Configure Web Checkout by API
This document applies to the following countries:
| Argentina | Brazil | Colombia | Chile | Mexico | Europe | Uruguay |
|---|
For other countries, see the Configuration via Portal document.
To configure Web Checkout by API, follow these three steps.
Step 1: Get seller registration data
Important: This step is only required if this is the seller’s first time setting up Web Checkout.
| Field | Type | Description | Example | Required |
|---|---|---|---|---|
sellerID | String | Seller ID to use in the query. | 672c0dd1-28b1-4136-b230-de68c1b92ae0 | ✅ |
Request
Example of request:
200 response
Example of response:
Use the information from the response to configure Web Checkout by API.
Step 2: Set the technical configuration
In this step, you can customize the appearance of the Web Checkout interface that customers see. This aligns the checkout experience with the branding of your e-commerce site.
Available customization options include brand color, accent color, and font. You also configure the redirect URLs. These URLs send customers to predefined endpoints when a transaction is approved or declined during checkout.
You must provide two URLs:
- Success: for approved transactions.
- Error: for declined transactions.
You need both URLs to complete the integration.
The table below lists the fields you must send.
| Field | Type | Description | Example | Required |
|---|---|---|---|---|
success_url | String | Redirect URL in case of successful checkout. | https://www.google.com/success | ✅ |
error_url | String | Redirect URL in case of an error during checkout. | https://www.google.com/error | ✅ |
url | String | Webhook URL to receive payment notifications. | https://webhook/bce0b3b3-49b6-4680-88d7-4e23131d91b2 | ✅ |
user | String | Username for webhook authentication. | 1cb9c739-8452-4436-816b-a833960b7680 | ✅ |
password | String | Password for webhook authentication. | 78ce12f6-665b-4354-8eaf-f0384413aaa8 | ✅ |
hide_getnet_logo | Boolean | Hides the Getnet logo at checkout when set to true. | true or false | -- |
Request
Example of request:
200 response
Example of response:
Step 3: Set the business configuration
You can optionally configure your checkout experience by enabling or disabling specific payment operations. These settings determine which payment methods appear during checkout. Examples include credit cards, debit cards, Boleto (bank slip), Pix (instant payment), and QR Code.
The table below lists the fields you must send.
Important: For each object-type attribute in the table, set theenableparameter totrueorfalse.
| Field | Type | Description | Example | Required |
|---|---|---|---|---|
instant_payment | Object | Payment method. | -- | ✅ |
bankslip | Object | Payment method. | -- | ✅ |
credit | Object | Payment method. | -- | ✅ |
debit | Object | Payment method. | -- | ✅ |
enable | Boolean | Whether the payment method is accepted. | true | ✅ |
qr_code_checkout | Object | (Argentina only) Displays the QR Code as a payment option on the Web Checkout screen. | -- | ✅ |
Important: The QR Code is available only for Argentina. It uses theenableparameter, set totrueorfalse. When you enableqr_code_checkout, the QR Code appears as a payment option on the Web Checkout screen. You don't need to change your integration.
Request
Example of request:
200 response
Example of response:
Your configuration is complete.
Next steps
- To create a payment intent, see Quickstart Create a Payment
- Learn about QR Code payment - Argentina
On this page