Getnet

Getnet Web Checkout

Getnet is Santander's payments business. The plugin uses Getnet's Web Checkout, the one Getnet product that serves Latin America and Europe with the same integration. Travellers pay on Getnet's checkout with a card, Pix in Brazil or the other methods Getnet has enabled for you, and the money is paid into your own Getnet account. The booking shows whether the traveller paid by card, Pix or boleto.

Currencies

Getnet appears at checkout for tours priced in ARS, BRL, CLP, MXN or EUR, and the booking is charged in the tour's own currency. Uruguayan pesos aren't offered, because Getnet needs VAT details on every UYU payment. If your website's main currency isn't on the list, the plugin's status panel says so.

The ID document and billing address Getnet asks for

Getnet requires the payer's ID document and billing address on every payment, which a booking doesn't ask for. So when a traveller chooses Getnet, a short page opens first, headed with your business name and the amount. It asks for the country, the type and number of an ID document, the street and number, the city (optional) and the postal code.

The country starts on the usual one for the currency, such as Brazil for reais, and the full list of countries is shown in the traveller's language. The document types follow the country: DNI in Argentina and Spain, CPF or CNPJ in Brazil, RUT in Chile, RFC or INE in Mexico, and a passport anywhere.

Tourtify doesn't store these details; they are sent only to Getnet. The traveller then goes straight on to Getnet's checkout. The link to the page is signed and expires, and a payment that has already been paid or closed sends the traveller back to your website.

Confirmed by webhook

Getnet's Web Checkout reports results only by webhook. In your Getnet technical configuration, set the callback URL shown in the plugin and choose a user and password for its notifications; enter the same user and password in the plugin. Every notification must carry them.

Tourtify then checks that the notification is about one of your payments, in the booking's currency, before keeping the result. An approved payment confirms the booking. A decline isn't treated as final, so the traveller can try again, and an approval is never replaced by a later decline. Without the webhook, Getnet payments can't confirm, which is why the status panel marks it as required.

Refunds in the Getnet portal

Getnet refunds are made in your Getnet portal rather than from Tourtify. Refund the traveller there, then choose "I refunded it in the provider's dashboard" on the booking so the booking, the traveller's balance and your reports stay correct.

Homologation and live

Getnet issues a separate client ID and client secret for its homologation (test) environment. In Test mode Tourtify uses that environment and no real money moves; Live uses Getnet's production environment. When you connect, Tourtify checks the keys by asking Getnet for an access token.

Setting up Getnet

1. 1Get your homologation keys. Getnet gives you a client ID and client secret for the homologation environment when your Web Checkout is set up.
2. 2Connect in Test mode. On the Payments page, add Getnet, paste both and choose Test.
3. 3Set up the webhook. In your Getnet technical configuration, set the callback URL shown in the plugin and choose a user and password. Enter the same user and password in the plugin's Webhooks section.
4. 4Make a test booking. Choose Getnet at checkout, fill in the details page, pay on Getnet's test checkout and check the booking confirms.
5. 5Switch to Live. Update the client ID and secret with your production ones, set the same webhook in your production configuration and choose Live.