The Payment Processing Account Token Generation feature is optional, and turned off by default so it would need to be enabled by a programmer as there isn't an option to "turn it on" by a user in the GUI. This feature allows tokenization of payment methods within OrderLogix, in order to securely process payments for the customer. Tokenization replaces sensitive data with non-sensitive data and is used to safeguard a card's PAN (primary account number) by replacing it with a unique string of numbers. This secure token, can then also be stored in the customer's payment profiles on the customer's detail center for future billing use.
There are multiple places within OrderLogix to take into consideration when it comes to generating and managing tokens. The first step is to set up the payment processing account that the tokens will be created through. This article will show you how to set up and manage this feature for the "Authoriz.Net" payment gateway.
Payment Processing Account Set up:
Navigate to Company Data>Payment Data>Payment processing accounts
and click the edit pencil icon next to the one you are modifying or the add new button to create a brand new account:
Once you enter all of the required fields for the account, and ensure that the "Allow Tokenization" checkbox is selected you can save the settings and then move on to associating to desired script(s).
Where to Find The Values in Authorize.Net
- Login to your Authorize.Net Account
- Select the Account tab
- Scroll down to Security Settings
- Scroll down to General Security Settings
- Select Manage Public Client Key
- Client Public Key = Client Key
- Select API Credentials & Keys
- API Login ID = API Login ID
- Transaction Key = Transaction Key
- Confirm Password = Transaction Key
Navigate to Company Data > Advertising > Maintain Scripts > edit Script
or Create New
> click on the "Payment" tab
Allow Real Time CC Authorization must be selected in order to select the payment processing account for pre-auth during manual order entry.
You have the option to require authorization and set the max amount of processing attempts allowed before denying the order.
You will notice when you allow real time auth for pre-authorizations, not only does the standard "payment processing account" display but now there is also a "payment processing account" for tokenization's and these MUST be the same.
If you have 2 different accounts selected, you will see the following message appear:
During Order Entry
, after you have completed the billing information section you will select the credit card pay type from the dropdown
for payment method.
Click set Payment and enter the credit information in the popup
***FName, LName, and Email are required fields before being eligible to Set Payment***
- Click save to prepare order for payment - Token = Pending
- Token is set once pre auth is processed or order is submitted if no pre auth is required
- Submit the order to navigate to the order detail screen.
Each order can only have one pre-auth
Order Detail Screen:
Once on the Order Detail Screen
you will see the credit card information is not displayed, instead you will see the token generated by the gateway.
Customer Detail Screen:
You will see a generic card number on the lister page with the expiration date.
Edit the payment profile and you will see
- payment type
- the token
- the account the token is associated to
- the expiration date
- if it is a debit account
- token details (you can use these to easily find the customer on the gateway)
Importing orders with tokens:
A Token generated via different payment gateways can be used for continuity or one time billing, and imported via either the OrderLogix API or Order Import v4.
To accompany the Token, the following must also be sent:
- the method of payment = CC.
- the credit card type.
- the credit card expiration date.
- the name of the Payment Processing Account, as set up in OrderLogix.
OrderLogix API Details:
The Billing Agreement ID will be passed in the XML element.
The name of the Payment Processing Account will be passed in the XML element.
The method of Payment (CC) will be passed in the XML element.
The credit card type will be passed in the element.
The card expiration date will be passed in the XML element.
Authorize.Net Your PPA
Payment Gateways will have different formats of information that needs to be passed in the token field, please see integrated list formats below:
CustomerID,Payment ProfileID,CC Last 4
- CustomerID = Authorize.Net Customer ID,
- Payment ProfileID = Authorize.Net Payment Profile ID,
- CC Last 4 = last 4 digits of the credit card being used