Authorize.net handles online checkout on the booking site and payment requests, and console card payments. The Authorize.net card on the Payment gateways tab has an API credentials section and a Fraud filter guidance section.
Getting started
Navigate to Purchases > Payment settings, open the Payment gateways tab and pick Authorize.net.
Step-by-step guide
Add credentials
- In API credentials, click Add test credentials or Add live credentials.
- Enter the API Login ID and Transaction Key. The live pair is in the Authorize.net Merchant Interface under Account, then Settings, then API Credentials and Keys; the test pair comes from your sandbox account.
- Click Save, then Activate on the set you want in use.
Enable the Transaction Details API
When Authorize.net does not answer a charge in time, the booking site holds the booking with a pending payment and confirms the outcome with Authorize.net a few minutes later. That check needs the Transaction Details API enabled on your Authorize.net account, and Off The Couch tests for it every time you save credentials.
The result shows in the Active gateway panel on the left of the tab.
| State | What the panel shows |
|---|---|
| Enabled | No note. Automatic verification is on |
| Not enabled | A note asking to enable the Transaction Details API, with the menu path |
| Could not confirm | A note saying the check could not be completed |
To enable it, open the Authorize.net Merchant Interface and go to Account, then Settings, then Security Settings, then Transaction Details API. If the setting is not in your account's interface, Authorize.net support can enable it. Then save your credentials here again to re-run the check.
Review the fraud filters
Open Fraud filter guidance. Authorize.net's address verification and card code filters decide when a mismatch declines a charge. Strict settings decline customers whose billing zip or security code cannot be verified, and each rejected attempt can leave a temporary hold on the customer's card. The recommendation is to decline only on genuine mismatches, not on unprocessed or unavailable results. The filters live in the Merchant Interface under Account, then Settings.
Reference
| Element | Description |
|---|---|
| API Login ID, Transaction Key | The credential fields, one pair per mode |
| Live ready, Live not set | Badge on the API credentials section |
| Transaction Details API note | Shown in the Active gateway panel until the check passes |
Good to know
- A pending Authorize.net payment is not a failure. The customer sees a "Payment being verified" message and cannot resubmit. Within a few minutes the platform checks with Authorize.net: a charge that went through is recorded and the booking confirms with its emails; a charge that did not go through releases the slot once the Incomplete booking timeout on booking site settings has passed. Each outcome is listed under Cart errors on the Carts page.
- Without the Transaction Details API the check cannot run. The slot is released after the timeout and a critical cart error is logged, so verify the charge in the Authorize.net dashboard before charging the customer again.
- Saved cards and card-on-file requirements are not available on Authorize.net.
FAQ
Q: A transaction on my Authorize.net account shows Pending. What should I do?
A: Nothing yet. The charge did not get an answer from Authorize.net in time, so the booking is held while the platform confirms the outcome. Within a few minutes it flips to paid, or the slot is released after the incomplete booking timeout. If the Active gateway panel shows a note about the Transaction Details API, enable it first.
Q: Valid cards are being declined. Why?
A: Almost always the fraud filters. Follow the guidance above and relax the address verification and card code filters so that only genuine mismatches decline.