# Connecting with API keys

> This connection method links to Authorize.Net using API keys instead of OAuth. Rather than logging in to Authorize.Net and authorising the connection, you enter

This connection method links to Authorize.Net using **API keys** instead
of OAuth. Rather than logging in to Authorize.Net and authorising the connection,
you enter your **API Login ID** and **Transaction Key** directly. Use it when the
OAuth flow is not an option — for example, you do not have account-owner access, or
the account was provisioned through a reseller.

:::note[Tip]
Everything after the credentials step — connection options, webhooks, and
troubleshooting — is identical to the OAuth connection. This page covers only the
credentials, then points you back to the main guide.
:::

## Find your API credentials in Authorize.Net

1. Log in to the [Authorize.Net Merchant Interface](https://account.authorize.net/).
2. Open the **Account** menu, then **Settings**.
3. Under **Security Settings**, select **API Credentials & Keys**.
4. Your **API Login ID** is shown on this page. Note it down.
5. To obtain a **Transaction Key**, select **New Transaction Key**, complete the
   verify-your-identity step, and record the key that is generated.

   :::caution[Please note]
   A Transaction Key is shown only once, at the moment it is created. Copy it
   immediately. If you generate a new Transaction Key, any system still using the
   previous key will stop working unless you keep the old key enabled during the
   changeover.
   :::

## Enter the credentials

1. When prompted to connect, enter your **API Login ID** and **Transaction Key**
   into the matching fields in the Authorize.Net panel.
2. **Save**. The connection is tested and, when the credentials are valid, you are
   shown a green **"Connected to Authorize.Net"** message. If the credentials are
   rejected, re-check that they were copied exactly and that the Transaction Key has
   not been superseded.

## Everything else

The remaining setup — **connection options** (Enable ACH, Require address (AVS),
Require CVC), the **webhooks** configuration (including the Webhooks Signature Key),
and **common issues after connecting** — is the same as for the OAuth connection.

See the [Connecting with OAuth](/payment-providers/authorize-net-connect/) guide for those
steps, and the [Authorize.Net FAQs](/payment-providers/authorize-net-faqs/) for
troubleshooting.