Studio needs three keys from your Authorize.net account to take card payments into it. They come from the Authorize.net Merchant Interface, and it takes about five minutes.
Get the three keys
- Sign in at account.authorize.net with the login for your merchant account. You need the account owner or an administrator.
- API Login ID. Go to Account → Settings → Security Settings → API Credentials & Keys. The API Login ID is shown at the top. Copy it.
- Transaction Key. On the same page choose New Transaction Key, answer your security question, and copy the key. It is shown only once. If another website already uses your Transaction Key, choose to keep the old key working instead of turning it off right away, or that website stops taking payments.
- Public Client Key. Go to Account → Settings → Security Settings → Manage Public Client Key. Create one if there is none, and copy it. This key is not a secret: it lets the card form send the card straight to Authorize.net, so the card number never reaches Studio.
Connect them in Studio
- Go to Settings → Payments and choose Authorize.net.
- Paste the API Login ID, Transaction Key and Public Client Key.
- Choose Live account. (A sandbox test account takes test cards only, so it cannot be used to take real payments.)
- Click Check keys and switch to Authorize.net. Studio tests the keys with Authorize.net first. If anything is wrong you see why, and nothing changes.
Good to know
- A blank box keeps the key already saved. Studio never shows a saved Transaction Key back to you.
- Once you have taken payments, refunds and saved cards stay with that merchant account. Studio will not switch to another account's keys in its place. Contact support if you are changing merchant accounts.
- Your provider's processing rate is between you and them, and Authorize.net does not report it to Studio, so it does not appear in Studio's reports.