Skip to main content

Authorize.net

ProRequires Events Manager Pro. Compare plans

Events Manager Pro can charge cards through your Authorize.net merchant account. The customer types their card details into your booking form and is charged when they submit it.

There are two Authorize.net gateways:

Authorize.net APIAuthorize.net AIM
Comes withThe Events Manager Pro - Authorize.net add-onEvents Manager Pro itself
StatusCurrentLegacy. Labeled Legacy Gateway in the gateways list
Talks to Authorize.net withAuthorize.net's current APIThe older AIM method
Refund and void notificationsWebhookWebhook or Silent Post
Sends itemized lines and the customer's emailNoYes
Can ask Authorize.net to email a receiptNoYes

Use Authorize.net API for a new setup. When you install the add-on on a site that already uses Authorize.net AIM, it copies your AIM settings and credentials to the new gateway. You then activate the new gateway and deactivate the old one.

What to know before choosing Authorize.net​

  • Card numbers pass through your site. Unlike the Stripe, PayPal and Square gateways, the card number, expiry date and security code are posted to your WordPress site and sent on to Authorize.net from your server. They are not stored: only the card type and last four digits are kept. Your site must use HTTPS, and this places more of the card industry's security requirements (PCI DSS) on you than a hosted form does.
  • No payment page or deposits. Neither gateway can be used on the payment page or for partial payments.
  • Any refund cancels the booking, including a partial one.
  • Disputes are not recorded. Handle chargebacks in your Authorize.net account and update the booking yourself.
  • There is no unpaid state to manage. A card is charged while the form is submitted, and a failed charge leaves no booking behind.