DBC: Credit Cards
DB/c is currently integrated with both CyberSource and Authorize.net. If you are going to accept credit cards from your customers on your site(s), you will need to contact one of those two gateway service providers and set up an account for your funds to be routed properly.
AUTHORIZE.NET CONFIGURATION
The configuration for Authorize.Net requires two key pieces of information: your Merchant API Name & API Transaction Key. Please refer to the instructions below on how to create/obtain this information from your Authorize.Net Merchant Interface.
To get started, please reach out to Authorize.Net to set up an account, https://www.authorize.net/sign-up/pricing.html or 888.323.4289
There are two options:
- Recommended: All-in-One Option - If you don't have a merchant account (to ensure you get paid), select this option. We can set you up with both a merchant account and a payment gateway.
- Payment Gateway Only - If you already have a merchant account, sign up for this plan. (You must have a merchant account to connect to the Authorize.Net platform).
Once you have your Authorize.Net Merchant Interface, you can proceed with the next step.
Getting Your Authorize.net Transaction Key
To use Credit Card Terminal, you’ll need your Transaction Key for Authorize.Net. If you don’t already have your Transaction Key, you must get a new one from Authorize.Net.
Warning: Authorize.Net does not allow the retrieval of an existing transaction key. Following these instructions will get a new transaction key and disable any old transaction key. If you have other software, such as a shopping cart or web site, that uses the Authorize.Net Transaction Key, you will need to update that software with the new Transaction Key within 24 hours, otherwise credit card processing in the other software will be disabled. In this situation, you may wish to get your transaction key from the configuration for your existing software rather than obtaining a new key from Authorize.Net.
The following instructions for finding your Transaction Key are from Authorize.Net’s Merchant Integration Guide.
The Transaction Key is a 16-character alphanumeric value that is randomly generated in the Merchant Interface and works in conjunction with your API Login ID to authenticate you as an authorized user of the Authorize.Net Payment Gateway when submitting transactions from your Web site. Like the API Login ID, the Transaction Key is a sensitive piece of account information that should only
be shared on a need-to-know basis.
How to Obtain a Transaction Key
Log into the Merchant Interface at https://secure.authorize.net
- Select Settings under Account in the main menu on the left
- Click API Credentials & Keys in the Security Settings section
- Reference an existing API Login ID (with saved transaction key) or create new.
- To create new, select Obtain: New Transaction Key. (Enter the secret answer to the secret question you configured when you activated your user account.) Click Submit. The Transaction Key for your account is displayed on a confirmation page.
IMPORTANT: Be sure to record your Transaction Key immediately in a secure manner or copy it immediately to a file in a secure location as it is not always visible in the Merchant Interface like the API Login ID. Once you navigate away from the confirmation page there will be no other way to access the Transaction Key in the Merchant Interface. You would have to generate a new Transaction Key.
It is highly recommended that you create a new Transaction Key regularly, such as every six months, to strengthen the security of your payment gateway account. You will then need to communicate the new Transaction Key to your Web developer immediately to update your Web site integration code. Failure to do so will result in a disruption in transaction processing.