Connecting with API keys

This connection method links Shuttle 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.

📘
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

Log in to the Authorize.Net Merchant Interface.
Open the Account menu, then Settings.
Under Security Settings, select API Credentials & Keys.
Your API Login ID is shown on this page. Note it down.
To obtain a Transaction Key, select New Transaction Key, complete the
verify-your-identity step, and record the key that is generated.

🚧
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 in Shuttle

When prompted to connect, enter your API Login ID and Transaction Key
into the matching fields in the Shuttle Authorize.Net panel.
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 PayPal, Enable ACH, Require
address, Require CVC), the webhooks configuration (including the Signature Key),
and common issues after connecting — is the same as for the OAuth connection.

See the Connecting with OAuth guide for those
steps, and the Authorize.Net FAQs for
troubleshooting.