Cyrious has partnered with FreedomPay to provide users with a modern, secure credit card payment solution used in the Online Payments feature and the credit card changes in Control 6.0. Although the entry form will look different from what customers are accustomed to, the same information is needed in any Control version - address and credit card details.

The entry window where credit card details are entered is referred to as a Hosted Payment Page (or HPP). FreedomPay creates, manages, and makes the webpage available for businesses to access (referred to as hosting). Since credit card details are entered directly in FreedomPay's HPP, your customer's credit card number bypasses Control's database completely.

There are 3 areas in Control that use FreedomPay's HPP:

1. The Online Payment feature
2. The Add Card option on a contact's record
3. The Run New Credit Card option on any payment entry window

Modifying your logo, header bar color, and background color during the FreedomPay boarding process will change the look of the HPP in all 3 places that it's used.

Here's an example of the credit card entry form in previous versions of Control compared to the HPP in Control 6.0 along with descriptions of it's corresponding fields.

The biggest change in Control 6.0 involved re-writing the credit card module to work with credit card tokenization. Tokenization is the process of creating a random string of characters, called a token, that's a substitute for sensitive data - which is a credit card number in our case. That token is only good for the Control store that creates the token.

Here's an example:

Credit card number: 4444 3333 2222 1111

Changes to Token: 8756 8514 6397 1111 (the last 4 digits are usually the same so that you know which card it replaces)

Here's how the tokenization process works:

1. A credit card number is keyed into FreedomPay's HPP through Control and submitted.
2. FreedomPay's tokenization system generates a token for the credit card that was passed to it.
3. The token is passed back to Control and can be saved to the contact's record for future use.
4. When the Control user is ready to use the customer's saved credit card, Control passes the token to FreedomPay's vault.
5. FreedomPay knows which credit card is linked to a token and passed the credit card number to Elavon/NXGen for processing.

Inside of Control, the user never sees the customer's credit card number after submitting it to FreedomPay. Instead, they see the payment information shown below.

1. Card on File: the type of card, the last four digits of the token (and the credit card number), the card's expiration date, and the cardholder's name
2. Billing Address: the address linked to the credit card
3. Token Expiration: the date the token expires (tokens are only stored in FreedomPay's vault for 24 months)

Contributor: Cyrious Software

Date: 10/28/2016

Version: Control 06.00