> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# Getnet

> Connect Getnet to Payrails, covering API credentials, account details, and the two approvals raw card processing requires.

<Note>
  **Who should use this guide**

  This guide is intended for merchants who:

  * Use **Payrails** as a payment orchestrator
  * Use **Getnet Payments**
  * Are approved to process **raw card data**

  *Because we use a server-to-server integration with Getnet, both of the following must be in place before raw card processing works in production:*

  * \*Your Getnet account is \****approved to process raw card data***
  * *A valid ****PCI-DSS Attestation of Compliance (AoC)**** is in place*

  *If either is missing, payments won't work in production. Contact your Getnet account manager or support team to activate both.*
</Note>

<Note>
  Getnet is region-specific. Separate provider accounts exist per market—Argentina (ARG), Chile (CHL), Mexico (MEX), and Mexico–US (MEX-US). Configure one Getnet integration per region you operate in.
</Note>

## Create and Configure a Getnet Integration in Payrails

1. Log in to the Payrails portal
2. Go to **Settings → Integrations**
3. Select **Add instance** to create a new Getnet integration configuration
4. Select the **Workspaces** where this integration should be available

<Note>
  **About Workspaces**

  Workspaces determine where this integration is available. They let you isolate provider setups by region or business line, or share the same configuration across multiple Workspaces.
</Note>

## Step 1: Choose the Integration Type

* Select **Payment** and continue to the next step.
  <img src="https://mintcdn.com/payrails-42074109/6ZmkK5ZUHpx1-EP_/images/docs/getnet-image-01.png?fit=max&auto=format&n=6ZmkK5ZUHpx1-EP_&q=85&s=8ecdf41029bb3020785e41ebba99f34b" alt="Payrails integration type selection with Payment selected" className="mx-auto block rounded-lg object-cover" width="80%" data-path="images/docs/getnet-image-01.png" />

## Step 2: Choose the Provider

* Select **Getnet **and** **continue to the next step
  <img src="https://mintcdn.com/payrails-42074109/6ZmkK5ZUHpx1-EP_/images/docs/getnet-image-02.png?fit=max&auto=format&n=6ZmkK5ZUHpx1-EP_&q=85&s=8a4119720ebaece75c177104b30375b0" alt="Payrails provider selection with Getnet selected" className="mx-auto block rounded-lg object-cover" width="100%" data-path="images/docs/getnet-image-02.png" />

## Step 3: Configure Your Getnet Integration

<Tip>
  **What you'll need from Getnet**

  Getnet authenticates via OAuth2 client credentials, which Getnet issues to you when API access is provisioned for your merchant account. Before beginning, ensure you have:

  * Client ID (OAuth2)
  * Client Secret (OAuth2)
  * Merchant / Seller ID
  * Merchant name
</Tip>

### Integration Instance Name

An integration instance is a specific payment provider setup in Payrails. Multiple instances can be created per provider based on region, currency, or business needs. Because Getnet is region-specific, include the region in the name (for example, `Getnet ARG` or `Getnet MEX`). Choose a clear, consistent name for routing purposes.

**In Payrails:**

* Enter an **Instance name** for your integration
  <img src="https://mintcdn.com/payrails-42074109/6ZmkK5ZUHpx1-EP_/images/docs/getnet-image-03.png?fit=max&auto=format&n=6ZmkK5ZUHpx1-EP_&q=85&s=a14d1e4d44283dbb40f0664323c4cb5c" alt="Payrails Getnet integration instance name field" className="mx-auto block rounded-lg object-cover" width="80%" data-path="images/docs/getnet-image-03.png" />

### API Credentials

**In Getnet:**

1. Sign in to your Getnet merchant account
2. Locate the OAuth2 **Client ID** and **Client Secret** issued for your account

**In Payrails:**

* Enter the credentials into the corresponding fields:

| Field | Required | Description |
| - | - | - |
| Client ID | Required | Getnet Client ID, issued by Getnet. Stored masked. |
| Client Secret | Required | Getnet Client Secret, issued by Getnet. Stored masked. |

### Account Details

**In Payrails:**

* Enter your Getnet account details:

| Field | Required | Description |
| - | - | - |
| Merchant ID | Required | Merchant / Seller ID of the Getnet account (the Getnet "Seller ID") |
| Merchant Name | Required | Merchant name of the Getnet account |

<img src="https://mintcdn.com/payrails-42074109/6ZmkK5ZUHpx1-EP_/images/docs/getnet-image-04.png?fit=max&auto=format&n=6ZmkK5ZUHpx1-EP_&q=85&s=6f5e32ccebfd9cf96786bcb57a3d971f" alt="Payrails Getnet account details fields for merchant ID and merchant name" className="mx-auto block rounded-lg object-cover" width="80%" data-path="images/docs/getnet-image-04.png" />

### Payment Methods

**In Payrails:**

* Select **Card** to enable Getnet card payments for this integration

## Enable the Integration

**In Payrails:**

* Select **Save account** to enable the integration

The **Enabled** status indicates that the Getnet integration is active. Your Getnet integration is now ready to process payments.

## Next Steps

1. Run a test payment using a supported Getnet [test card](https://docs.globalgetnet.com/pt/articles/test-cards)
2. Verify that:
   * The payment appears in Getnet
   * The payment status updates correctly in Payrails
3. Once verified in test mode, repeat the setup in live mode


## Related topics

- [Integrations](/docs/orchestration/integrations/index.md)