> ## 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.

# Authorize.net

> Connect Authorize.net to Payrails for cards, Apple Pay and Google Pay, covering your API credentials, signature key and webhooks.

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

  This guide is intended for merchants who:

  * Use **Payrails** as a payment orchestrator
  * Use **Authorize.net** for card and wallet processing
  * Have access to the Authorize.net merchant interface
</Note>

***

## Create a Authorize.net integration in Payrails

1. Log in to the **Payrails** portal.
2. Go to **Settings** → **Integrations**.
3. Select **Add instance** to create a new 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**.
* Continue to the next step.

***

## Step 2: Choose the provider

* Select **Authorize Net**.
* Continue to the next step.

<img src="https://mintcdn.com/payrails-42074109/ZzszXSV8HBVpGKdF/images/docs/authorize-net-image-01.png?fit=max&auto=format&n=ZzszXSV8HBVpGKdF&q=85&s=ac9859fd2ca241465e75fa86b6c97336" alt="A screenshot showing Authorize.net selected as the provider." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/authorize-net-image-01.png" />

***

## Step 3: Configure your Authorize.net integration

<Tip>
  **What you'll need from Authorize.net**

  Before you begin, make sure you can log in to the Authorize.net merchant interface. You'll copy your API credentials and set up webhooks there.
</Tip>

***

### Integration instance name

> An integration instance is a specific payment provider setup in Payrails. You can create multiple instances for different regions, currencies, or business needs. Choose a clear, consistent name, as it is used in routing.

**In Payrails**

* Enter an **Instance name** for your integration, for example `merchant_authorizenet`.

<img src="https://mintcdn.com/payrails-42074109/145W1v58K5wnDMNC/images/docs/orchestration/integrations/shared/integration-instance-name.png?fit=max&auto=format&n=145W1v58K5wnDMNC&q=85&s=470be58979509680650b0cbf8b5eecc4" alt="A screenshot showing the integration instance name field." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/orchestration/integrations/shared/integration-instance-name.png" />

***

### Payment methods

**In Payrails**

* Select **Card**, **Apple Pay**, **Google Pay** or any combination.

<img src="https://mintcdn.com/payrails-42074109/ZzszXSV8HBVpGKdF/images/docs/authorize-net-image-02.png?fit=max&auto=format&n=ZzszXSV8HBVpGKdF&q=85&s=d6276e518660305bf1ff5ef7a152e412" alt="A screenshot showing the Authorize.net payment method selection." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/authorize-net-image-02.png" />

***

### Credentials

**In Authorize.net**

1. Go to **Account** → **Settings** → **API Credentials & Keys**.
2. Copy the **API Login ID**.
3. Create a new **Transaction Key** and a new **Signature Key**, and copy them.

**In Payrails**

| Field | Value |
| :- | :- |
| **API Login ID** | Your Authorize.net API login ID |
| **Transaction Key** | Your Authorize.net transaction key |
| **Signature Key** | Your Authorize.net signature key. Payrails uses it to verify webhooks from Authorize.net. |

Payrails sends requests to the Authorize.net sandbox in test mode and to the live environment in live mode, so use the credentials for the matching account.

<img src="https://mintcdn.com/payrails-42074109/ZzszXSV8HBVpGKdF/images/docs/authorize-net-image-03.png?fit=max&auto=format&n=ZzszXSV8HBVpGKdF&q=85&s=9d16d003a2b29beb17415594353c7218" alt="A screenshot showing the Authorize.net credential fields." className="mx-auto block rounded-lg object-cover border border-gray-200" width="80%" data-path="images/docs/authorize-net-image-03.png" />

***

### Webhooks or notifications

<Info>
  Payrails uses provider webhooks or notifications to receive asynchronous
  payment status updates.
</Info>

<Warning>
  Create webhooks in the same mode (test or live) as your Payrails integration.
</Warning>

**In Payrails**

* Copy the **Notification URL** shown under **Account configuration** at the top of the integration form.

**In Authorize.net**

1. Go to **Account** → **Webhooks** and add an endpoint.
2. Paste the Payrails notification URL.
3. Select these events:
   * `net.authorize.payment.authorization.created`
   * `net.authorize.payment.authcapture.created`
   * `net.authorize.payment.capture.created`
   * `net.authorize.payment.priorAuthCapture.created`
   * `net.authorize.payment.refund.created`
   * `net.authorize.payment.void.created`
4. Set the webhook to **Active** and save it.

***

## Request fields for Authorize.net

Send these fields in the [authorize request](/reference/authorizeaction) for card payments, in addition to the standard authorize fields. **Required** fields must be present for the payment to succeed. Payrails sends **Optional** fields to Authorize.net when you include them. For more about meta fields, refer to [Meta fields](/docs/orchestration/meta-fields).

| Field | Status | Description |
| :- | :- | :- |
| `amount` | Required | Sent to Authorize.net as the amount and currency. |
| `instrument.networkTransactionReference` | Required | Merchant-initiated payments only. Sent as the original network transaction ID. Payrails stores it from the first payment. |
| `merchantReference` | Optional | Sent as the invoice number, up to 20 characters. |
| `meta.customer.email` | Optional | Sent as the customer email, with `holderReference` as the customer ID. |
| `meta.order.billingAddress`, `meta.order.deliveryAddress` | Optional | Sent as the bill-to and ship-to addresses. |
| `meta.order.lines` | Optional | Sent as the line items. |
| `meta.order.totalTax`, `meta.order.description` | Optional | Sent as the tax amount and order description. |
| `meta.clientContext.ipAddress` | Optional | Sent as the customer IP. |

***

## Enable the integration

**In Payrails**

* Select **Save account** to enable the integration.
* Confirm the integration shows as **Enabled**.

Your **Authorize.net** integration is now ready to process payments.

***

## Next steps

1. Run a test card payment in the Authorize.net sandbox.
2. Verify that:
   * The payment appears in the Authorize.net merchant interface.
   * The payment status updates correctly in Payrails.
3. Once verified in test mode, repeat the setup in live mode.

→ Continue to: [Test a payment](/docs/orchestration/payment-acceptance/test-payments)


## Related topics

- [Integrations](/docs/orchestration/integrations.md)
- [NetBanking via dLocal](/docs/orchestration/payment-methods/netbanking/dlocal.md)
- [NetBanking via Pine Labs](/docs/orchestration/payment-methods/netbanking/pinelabs.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.