Authorize.Net

Accept Hosted payment page

The plugin uses Authorize.Net's Accept Hosted page. Tourtify asks Authorize.Net for a payment page for the booking amount, with an invoice number and your booking reference, and sends the traveller there. Card details stay on Authorize.Net's page. Its own receipt is switched off, so the traveller comes straight back to your website and gets your booking emails instead.

A declined card can be tried again on the same page. Authorize.Net's page token lasts 15 minutes, so Tourtify keeps the checkout open for 12 and a traveller never lands on an expired page.

One settlement currency

Each Authorize.Net account settles in one currency, chosen when the account is opened. The plugin takes USD, CAD, GBP, EUR, AUD and NZD, and appears at checkout for tours priced in those. Charge only in the currency your own account settles in. The plugin's status panel warns you if your website's main currency isn't one of them.

How a payment is confirmed

Authorize.Net sends the traveller back without any result, so Tourtify looks the payment up itself. It finds your invoice number among the account's unsettled transactions and reads that transaction's details, checking that the invoice number matches. A captured or settled transaction confirms the booking. A transaction held by Authorize.Net's fraud filters is flagged for your team: approve or decline it in the Merchant Interface. Voided and expired transactions close the payment.

Tourtify checks when the traveller returns and every five minutes after, for up to 26 hours.

Webhooks for instant confirmation

In the Merchant Interface, add a webhook endpoint for the URL shown in the plugin with the events for a captured payment and for fraud approvals and declines. Then create a signature key and paste it into the plugin. Each delivery's X-ANET-Signature (HMAC-SHA512) is checked with that key. The event names the transaction, which Tourtify then reads directly from Authorize.Net, so a forged message can't mark anything paid.

Without the webhook, payments still confirm through the regular checks.

Refunds and voids

Authorize.Net only refunds transactions that have settled, usually the day after the payment. For a settled card payment, Tourtify sends a full or partial refund using the card's last four digits from the transaction. For a payment that hasn't settled yet, Tourtify voids it instead, which gives back the whole amount; a partial refund before settlement is refused with a message to try again once it has settled.

Payments that weren't made by card can't be refunded from Tourtify. Refund them in the Merchant Interface, then choose "I refunded it in the provider's dashboard" on the booking.

Sandbox and live

Authorize.Net's sandbox is a separate account you create at developer.authorize.net. In Test mode Tourtify uses the sandbox and no real money moves; Live uses your production account. Your API login ID and transaction key are checked with Authorize.Net before they are saved.

Setting up Authorize.Net

1. 1Create a sandbox account. Sign up at developer.authorize.net and copy the API login ID and transaction key from Account › Settings › API Credentials & Keys.
2. 2Connect in Test mode. On the Payments page, add Authorize.Net, paste both and choose Test.
3. 3Add the webhook. In Account › Webhooks, add the plugin's URL with the listed payment events. Create a signature key under API Credentials & Keys and paste it into the plugin.
4. 4Make a sandbox booking. Pay with one of Authorize.Net's test card numbers and check the booking confirms.
5. 5Switch to Live. Update the API login ID and transaction key with your production ones, paste the production signature key and choose Live.