> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.ressto.co/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to Find Authorize.Net API Login ID, Transaction Key, and Signature Key

# How to Find Authorize.Net API Login ID, Transaction Key, and Signature Key

To connect Authorize.Net to your restaurant dashboard, you need the **API Login ID** and **Transaction Key**. The **Signature Key** is also required if your integration uses it for webhook verification.

## 1. Log In to Authorize.Net

1. Open the [Authorize.Net Merchant Interface](https://account.authorize.net/).
2. Sign in using your merchant account credentials.
3. Make sure you are accessing the correct account and environment.


![](https://storage.crisp.chat/users/helpdesk/website/-/f/e/c/2/fec2bb2c3e13f800/image_1kvlvs3.png =900x700)

## 2. Find Your API Login ID

1. Select **Account** from the main navigation.
2. Under **Security Settings**, open **API Credentials & Keys**.
3. Locate your **API Login ID**.
4. Copy the ID and store it securely.

The API Login ID identifies your merchant account for API transactions. It is not your Merchant Interface login username.

## 3. Generate Your Transaction Key

1. On the **API Credentials & Keys** page, select **New Transaction Key**.
2. Review the option to disable the existing key immediately.
3. Select **Submit** to continue.
4. Complete the requested identity verification using your PIN.
5. Copy and securely store the newly generated Transaction Key.

||| Important: The Transaction Key is displayed when it is generated and may not be viewable again. If you lose it, generate a replacement. Replacing keys can affect existing integrations, so update the restaurant dashboard accordingly.


## 4. Generate Your Signature Key

1. On the **API Credentials & Keys** page, select **New Signature Key**.
2. Review the option to disable the existing key immediately.
3. Select **Submit** and complete the requested identity verification.
4. Copy and securely store the generated Signature Key.

The Signature Key is used by supported Authorize.Net integrations to verify message hashes, including webhook notifications. Make sure it is configured if your integration requires webhook signature verification.

## 5. Enter the Credentials in Your Restaurant Dashboard

1. Log in to your restaurant dashboard.
2. Go to **Settings → Payments → Payment options**.
3. Open **Manage gateways** and select **Authorize.Net**.
4. Enter the credentials in the matching fields:
   * **API Login ID:** Your Authorize.Net API Login ID.
   * **Transaction Key:** Your generated Transaction Key.
   * **Signature Key:** Your generated Signature Key, if this field is provided and required by your integration.
5. Review the values and click **Save**.

Only enter the credentials requested by the Authorize.Net gateway configuration.

## 6. Important Security Notes

* Keep the Transaction Key and Signature Key confidential.
* Store generated keys securely because they may only be displayed once.
* Generating replacement keys may affect your existing integration. Coordinate the update to avoid payment interruptions.
* Test payment processing and webhook verification before accepting live payments.

**Official Authorize.Net guides:**

* [API Login ID, Transaction Key, Signature Key, and Public Key](https://support.authorize.net/knowledgebase/article/000001271/en-us)
* [Authorize.Net Webhooks documentation](https://developer.authorize.net/api/reference/features/webhooks.html)