Authorize.net API Gateway
ProEvents Manager Pro - Authorize.netRequires Events Manager Pro. Compare plans
The Authorize.net API gateway adds card fields to your booking form and charges the card through your Authorize.net merchant account when the form is submitted. The payment is authorized and captured in one step, and the booking is approved straight away.
Read what to know before choosing Authorize.net first: card numbers pass through your own site with this gateway.
- Events Manager Pro 3.2.7 or later and the Events Manager Pro - Authorize.net plugin, both activated. This page describes add-on 1.2.
- An Authorize.net merchant account, and a sandbox account for testing.
- Your site served over HTTPS. In live mode the gateway is switched off on a site without it, and admins see a notice on the booking form saying so.
Set up the gateway
-
In your Authorize.net account, find your API Login ID and create a Transaction Key and a Signature Key. Authorize.net explains where in How do I obtain my API Login ID and Transaction Key and What is a Signature Key. Creating a new key can disable the old one, so store them safely.
-
In WordPress, go to Events then Payment Gateways and click Authorize.net API.
-
Open the [Live] API Keys/Notifications tab and enter the API Login ID, Transaction Key and Signature Key. Enter your sandbox account's three values on the [Test] API Keys/Notifications tab. Click Save Changes.
The three credential fields, with the webhook address and events under Payment Notifications.
-
Create the webhook, described below, so that refunds and voids reach your site.
-
Go back to Events then Payment Gateways and click Activate under Authorize.net API.
-
The gateway starts in test mode. Make a test booking with a sandbox test card, then click Enable Live Mode in the banner above the tabs.
Create the webhook
Without a webhook, payments still work, but a refund or void made in Authorize.net won't change the booking. Events Manager doesn't create the webhook for you.
-
Make sure the Signature Key is saved. Notifications are checked against it, and are refused without one.
-
On the API tab for the mode you are setting up, under Payment Notifications, copy the address after Your Webhooks Endpoint url is:
https://example.com/wp-json/events-manager/v1/gateways/authorizenet_api/notifyThe address on the Test tab ends in
/notify_test. -
In your Authorize.net account, add a webhook with that address. Authorize.net's steps are in How do I add or edit webhook notifications.
-
Select these two events and set the webhook to active:
Event What Events Manager does with it net.authorize.payment.refund.createdCancels the booking and records a Refunded transaction. net.authorize.payment.void.createdCancels the booking and marks its transaction Voided.
Do this once in your live account and once in your sandbox account, each with its own address.
Settings
The General Options tab has four settings:
| Setting | What it does |
|---|---|
| Gateway Title | The name in the payment method menu. Default Credit Card. |
| Booking Form Information | Text shown with the card fields. |
| Success Message | Shown when the card has been charged. On a new install the default text mentions being redirected, which doesn't happen with this gateway, so replace it with your own confirmation wording. |
| Manually approve completed transactions? | Leaves paid bookings at Pending for you to approve. Bookings must also need approval in your booking settings. |
There are no expiry settings, because a booking never waits for payment. The [Test] API Keys/Notifications tab also has the Limited Test Mode settings.
What the customer sees
Choosing this payment method shows Card Number, Expires (month and year) and CVV in the booking form. It takes cards only.
When the form is submitted the card is charged for the booking total. Authorize.net receives the amount, the booking ID as the invoice number, the event name as the description, and the customer's name and billing address. The address comes from the booking form fields you link under Common User Fields for Gateways in Events then Forms Editor, and is what Authorize.net's Address Verification Service checks. No itemized lines, tax amount or email address are sent, and the charge is made in your merchant account's currency.
If the charge fails, the customer sees Authorize.net's reason above the form and no booking is kept. They can correct the card and submit again.
The gateway works in Multiple Bookings Mode and for bookings you add in wp-admin. It can't be a Quick Pay button.
Refunds and voids
Refund or void a transaction in your Authorize.net account. There is no refund button in WordPress. With the webhook in place:
- A refund cancels the booking and records a Refunded transaction with a negative amount. This happens for any refund amount, so a partial refund also cancels the booking. Approve it again by hand if the customer is still attending.
- A void cancels the booking and changes its transaction's status to Voided.
Disputes and chargebacks are not reported to your site.
Troubleshooting
Admins see a notice that the gateway "will only work if your site is using SSL and has been disabled"
The gateway is in live mode and the booking page was loaded without HTTPS. Serve the site over https://.
"There was an error processing your payment, no response received from our payment processor. Please try again later."
Your server could not reach Authorize.net. Check with your host that outgoing connections to Authorize.net are allowed.
Payments are declined in test mode
The values on the [Test] API Keys/Notifications tab must come from a sandbox account, not your live account, and the other way round.
Refunds in Authorize.net do not cancel bookings
Check that the Signature Key is saved on the tab for that mode, that the webhook address is the one shown on that tab, and that both events are selected and the webhook is active.