Learn more about Authorize.net, including checking the service status, understanding what features are supported, setting up your account in Authorize.net, adding a webhook in Authorize.net, setting up Authorize.net in Checkfront, configuring address verification, testing with sandbox mode, configuring receipts, and understanding settlements & refunds.
Which plans include this feature?
Legacy: Soho, Pro, Plus, Enterprise
New: Available with the Growth (Subscription) or Managed plans only.
This payment provider is unavailable to accounts on the Starter or Growth (Per Booking) plan.
→ Learn more about our new plans or how to change your plan.
Where can I find this feature using the top menu?
Manage > Ecommerce Setup > Payment
What more do I need to use this feature?
- Admin permissions are required to manage Payment Providers.
- The following system Booking Form fields are required: Address, City, State/Province or equivalent, Postal Code/Zip or equivalent, and Country.
About Authorize.netBack to top
Authorize.net is a Payment Provider allowing merchants in the United States, Canada, United Kingdom, Europe & Australia to accept credit card payments through their website.
If you don't currently have an Authorize.net account, sign up here.
Visa and Mastercard have announced they are ending support for 3D Secure version 1.0.2 and will require 3D Secure version 2 to accept 3D Secure protected payments. This comes into effect as of October 14th, 2022.
As a result, your current payment provider, Authorize.net has announced that they will not be updating their 3DS version to 3DS version 2 and will be ending support for 3DS version 1.
What does this mean for my business?
Transactions without 3DS may fail for those Operators with banks in the UK/EU, where 3DS is required to meet Strong Customer Authentication (SCA) as part of the Payment Service Directive (PSD2) regulations.
For those not utilizing 3DS and not required by regulation to utilize 3DS (e.g. North American Operators), transactions should continue uninterrupted.
What do I have to do?
When do I have to make the change?
What if I don't want to select another provider?
Is this change going to impact refunding payments?
We don't anticipate any issues with processing refunds without 3DS, but we recommend that you reach out to Authorize.net through your merchant dashboard if you experience any issues with processing refunds once 3DS is disabled.
What if I can't refund payments through Authorize.net?
If you cannot refund through Authorize.net, you should be able to issue manual refunds through a new payment provider, which would refund the money from the connected bank account. Then you must align your reporting within Checkfront by refunding using a POS method.
We apologize for any inconvenience this causes, and if you have any questions, please feel free to reach out.
Checking the Service StatusBack to top
Check the status of Authorize.net services at any time here:
Supported FeaturesBack to top
The following is a list of standard Payment Provider features. Those available with the Authorize.net and Checkfront integration are marked as supported (✓).
|Live Payments||✓||The ability to process payments in real time.|
The ability to re-charge using previously provided payment information (tokens).
The ability to return a paid amount directly to the original payment method.
|✓||Customers remain on the Checkfront domain to input details. These details are sent to the provider to process the transaction without redirecting the Customer.|
|Customers are redirected to the Payment Provider’s domain to input details and process the transaction.|
Staff can take payment through the Booking Details page using new payment information.
Authorize.net allows you to use Checkfront to accept in-person payments with "triple track" readers that can be used for Staff payments only.
The provider holds the payment for a certain time without charging the card.
The ability to process test payments using your Checkfront account and Authorize.net before going live.
The ability to offer payments in more than one currency.
Payment Services Directive 2 (PSD2) compliant, including Strong Customer Authentication (SCA).
Authorize.net is ending support for 3D Secure cardholder authentication.
Merchants should stop using 3D Secure before October 14, 2022.
To continue using 3D Secure, we recommend moving to Stripe as your payment provider.
|Can be a secondary Provider?||X||
The ability to configure a primary provider for online payments and a secondary provider for Staff-side payments through the Booking Details page.
|Additional Payment Methods||X||
|Buy Now, Pay Later powered by Uplift||X|
|Capture and Send Zip / Postal Code and Address for Address Verification (AVS)||✓||
Capture Zip / Postal Code and Address to send to Authorize.net for Address Verification (AVS) to help prevent disputes and fraud.
Authorize.net is available to Operators in the following business locations:
The list of supported currencies can be found in the following article.
|Minimum Transaction Payment Amount||X||
The minimum payment amount for Authorize.net (0.00) applies to test and live transactions.
Setting up your account in Authorize.netBack to top
You’ll need your API Login ID and Transaction Key from your Authorize.net account to get started.
To obtain these, login to your Authorize.net account, select the Account tab and navigate to API Login ID and Transaction Key under Security Settings.
Copy your API Login ID. To retrieve the API Key, select New Transaction Key and click Submit.
You are then prompted to send a secure PIN to your email address. Select Request PIN. Check your email for the secure PIN, put it into the pop-up and then select Verify PIN. You will then be taken to your new Transaction Key.
Once you have the API Login ID and API Key, head back over to Checkfront.
Adding a webhook Authorize.netBack to top
To prevent an issue where the Payment Provider might hang during transaction processing, causing a Customer to submit again and create a double booking, it's possible to add a webhook in Authorize.net, which will notify Checkfront of completed payments.
In your Authorize.net Account menu, click on Webhooks under the Business Settings section.
From there, click on the Add Endpoint button and input the following URL:
[checkfront url] should be replaced with your account URL. From there, set the Webhook to send on the following event:
Setting up Authorize.net in CheckfrontBack to top
Depending on your locale, you may be presented with a couple of recommended Payment Providers.
Locate the Authorize.net tile and click on it to open the Setup window.
In the Add-on Setup modal, fill in your details and click Activate. A description of each field is available before.
Authorize.net Login IDBack to top
This is the login ID you obtained in the previous step.
Authorize.net KeyBack to top
This is the Transaction Key you obtained in the previous step.
Setting payments to Authorize & Capture or AuthorizeBack to top
Select whether you would like to Authorize & Capture your transactions or Authorize them only. The answer to this depends on how you operate your payment system. Most businesses will most likely use Authorize & Capture.
• Authorize & Capture This allows you to authorize the payable amount and charge the card immediately for a partial or full payment.
• Authorize Only This type of transaction creates an authorization with the card-issuing bank that holds the funds until you wish to capture them manually. An authorization is valid for 30 days until the transaction is captured or voided. If the authorization exceeds 30 days with no merchant action, its status will change to Expired, which means the transaction is no longer available for settlement.
Enable RebillingBack to top
Authorize.net CIM is a service that allows you to store sensitive customer information, in this case, credit card details, as a token for later use.
You can take a deposit at the time of booking and then charge the final balance later without needing to obtain the card details again.
Signed up for this service with Authorize.net? Then, check the Enable Rebilling box to enable this feature within Checkfront.
Learn more about Authorize.net's CIM service that supports rebilling:
Configuring address verification (AVS)Back to top
Billing Address and Postal / Zip code are captured and sent to Authorize.net, where Address Verification (AVS) checks are applied to help protect against disputes and fraud.
This is true for Customer-facing (Payment page) and Staff-side (add payment form) payments.
Ensure that your Booking Form (Manage > Layout > Booking Form tab) includes the Address and Postal / Zip code fields and that the fields are marked as required.
The Payment page's Billing Address and Postal / Zip code fields are prefilled with the value entered in the corresponding Booking fields.
The Staff-side Add Payment form includes these fields by default - no additional configuration is required.
Learn more about Address Verification (AVS) with Authorize.net:
Testing with Sandbox ModeBack to top
It’s highly recommended that you do an end-to-end test of your checkout before putting your site live. To do so, follow the setup instructions above and check Enable Sandbox Mode. You must also put your Authorize.net account in TEST mode.
To do this, return to your Authorize.net account and go to the Account menu. Look for the Security Settings section and click on the Test Mode link.
On the next page, flick the switch over to Test.
You will now see a confirmation above that the account is in Test Mode.
Once the payment module is enabled, remember to enable payment processing on the Payment page (Manage > Ecommerce) in your Checkfront dashboard.
Test TransactionsBack to top
Create a transaction as a Customer would and check to see that it shows up in your Checkfront account as paid. The transaction should also appear within your Authorize.net account. If you don’t have a website to test on yet, use the hosted booking page, e.g., https://yourcompany.checkfront.com/reserve/
Test Card NumbersBack to top
You can use the following test credit card numbers when testing your Authorize.net checkout:
You can use any CVC code and an expiry date in the future. Remember to take your account out of sandbox mode when finished.
Configuring receiptsBack to top
Response and Receipt URLsBack to top
Upon payment, Checkfront sends the Customer to a booking receipt page. You should, therefore, NOT supply a custom receipt page within Authorize.net. You should use the Default Receipt URL and the Default Relay Response URL to ensure the booking is completed.
Email ReceiptsBack to top
Checkfront can be configured (and is by default) to send Customers and Administrators email receipts. This provides more information on the booking that Authorize.net can supply. Turning off email receipts within Authorize.net is generally recommended so your Customers don’t get multiple receipts simultaneously.
Understanding settlement & refundsBack to top
Transactions over 120 days Old
If a transaction is 120 days or older, then Authorize.net will not allow it to be refunded. A new transaction will have to be paid to your Guest for the refund amount through your Authorize.net dashboard, and a POS refund will need to be added to the booking in Checkfront.
Authorize.net does batch settlements to your account daily. When a payment is processed, it goes to the status of Captured. At the end of the day, all transactions are posted and changed to the status of Settled.
You can see unsettled transactions by logging into your Authorize.net account and clicking Unsettled Transactions in the left-hand sidebar.
Unsettled Transactions cannot be partially refunded, they can only be voided, so they don’t settle. If you wish to make a partial refund, you must wait until the next day, when the transaction has been settled. In the Unsettled Transactions section, you can check if a transaction is unsettled in your Authorize.net account.
Common Issues & SolutionsBack to top
Listed here are common errors you may come across when using Authorize.net: