Authorize.net is a legacy service and is not available for new customers.
For our customers who still currently use Authorize.net, we are providing this page to answer any current questions.
Authorize.net FAQs and How To's
Click the arrow next to each topic to learn more
How do I find my Authorize.net API login?
How do I find my Authorize.net API login?
First, you will need to verify that your Authorize.net API login is correct. The API login is not the same login as your Authorize.net account login.
Find your API Login
Log in to your Authorize.net account
Click on Account on the top navigation
Click on API Login ID and Transaction Key under the Security Settings section.
Your API login ID will be a series of numbers and letters.
Copy that login and type it in the Customer Payments section in the DaySmart Appointments section the password field is not necessary so you can delete that field. Keep the tran key field.
When I process transactions with Authorize.net I get a reason code. What does it mean?
When I process transactions with Authorize.net I get a reason code. What does it mean?
The error you are receiving is from Authorize.net. You can look up a description of your reason codes by checking out their list of response codes.
When using Authorize.net as my payment gateway, what type of account should I select, Web Merchant or Retail Merchant?
When using Authorize.net as my payment gateway, what type of account should I select, Web Merchant or Retail Merchant?
There are two types of accounts to choose from:
Web Merchant
This type of account is what works with the scheduling system. It is for online credit card transactions.Retail Merchant
This type of account is for processing credit card transactions within your company/organization (i.e. via a card swipe machine).
If you process transactions online and in your retail location, you will need both accounts. There are different fees and liabilities for each one.
Updating Response, Receipt, or Return URLs
Updating Response, Receipt, or Return URLs
You may need to update your gateway account to include the proper return URL. This URL is used by the gateway in order to return the Customer back to the DaySmart Appointments system is properly processed.
To configure the Return URL for the DaySmart Appointments system, you will put together the base URL for your Customer View (example https://booknow.appointment-plus.com/) and then append one of the following return paths:
Authorize.net: ap_api/authorizenet_return.php
Log in to your gateway account, locate the Response/Receipt URL page, and enter URLs into the available fields. You can have multiple response URLs associated with your gateway account. The below links are example URLs. Based on where your account is located in the system, you may see a variation of these URLs.
For example, you may be logged in to https://account5.appointment-plus.com/.
The Default Return URL should be based on the URL where you log in to your scheduling account. Below is an example of how you will enter this address. Your URL may start with account5 or account. That is the part of the URL you will want to customize for your account.
You will need to append the following destination page:
Authorize.net: ap_api/authorizenet_return.php
The Default Relay Response URL should be based on the URL where you log in to your scheduling account.
You will need to append one of the following destination pages:
Authorize.net: ap_api/authorizenet_return.php
The Additional return URL (third entry) should be based on the URL where you log in to your scheduling account. Check the address after you log in and use the first part (account, account5, etc) up to the .com section of the site's address:
Example URL: https://account.appointment-plus.com
Appointment Payment Options
The system provides additional flexibility when prompting Customers for payment on the Customer View. These options are found in the Customer Payments section of Settings.
Customers can be given the option to pay when they are making the Appointment or at the time the service is rendered.
If you are using the "prompt but don't process" method, Customer with an existing credit card token on file, it won't prompt them to enter their credit card information. You can set it so that it always prompts for credit card information, even if the Customer already has one on file.
If you are using Events, you can have the system prompt only for Services, prompt only for Events, or prompt for both types of activities.
Returns/Refunds
If a Customer needs a credit card refund, you must utilize your gateway account terminal.
Credit Card Processors
Processor: Authorize.net
Currency Options USA
Credit Card Capture: No
Required Credentials
Processor: Authorize.net
Login: Login
Password: not applicable
Tran Key: Transaction Key
NOTE: The Tran Key is the term for a Transaction Key for Authorize.net clients. The Tran Key is a unique sequence of numbers and letters that Authorize.net gives to their clients. This key is sent to Authorize.net with any transaction you process to link to your account.
How to do I integrate credit card processing for Authorize.net?
How to do I integrate credit card processing for Authorize.net?
To integrate credit card processing into the POS system, you need an account with an online credit card processor.
For Authorize.net - depending on the merchant processor, may be used for payment transactions outside the USA.
You can enter the credentials into the Customer Payments section of Preferences:
Click Settings.
Click Customer Payments.
Locate the POS section and enter the information from your merchant account.
Click Update.