This topic provides information on setting up and configuring Aptify to integrate with CardPointe.
This article is divided into below sub-topics:
- Creating new Payment Type for Hosted iFrame Tokenizer
- Configuring the CardPointe merchant account
- Hosted iFrame Tokenizer
- Configuration specific to Aptify Smart Client
Creating new Payment Type for Hosted iFrame Tokenizer
Note: Below steps are common for both the Aptify Web and Aptify Smart Client applications.
- Log into Aptify as an "Admin User".
- Go to Order Entry Administration Application.
- Right click Payment Types service and select the "New Payment Types Record" option. 
- Fill in the following details:
- Name - As per your choice
- Type - Hosted iFrame Tokenizer
- Check the Inflow, Active, Web Enabled and Allow "Save for Future Use" checkboxes as per your requirement.
- Fill in the required information in the other tabs.
- Save and close the record. 
Note: After creating the above new payment type, run the following process flows to apply changes to Aptify Web.
- Generate HTML5 Web Entity Metadata for the Payment Types entity.
- Generate HTML5 Web Form Template UI Parts for the form template, Payment Information Control Template_Credit Card CardPointe Payment Transaction
- Generate HTML5 Web UI Part Metadata Items for All UI part metadata items.
Configuring the CardPointe merchant account
- Log in to Aptify as an "Admin User".
- Go to Order Entry Administration Application.
- Right click Merchant Accounts service and select the New Merchant Accounts Record option. 
- In the General tab, fill in the details as mentioned below:
- Fill in the Merchant Account Name field as CardPointe
- Set the Authorization Type as AuthOnly/AuthCapture, depending on your requirement.
- Set Fraud Check Level, Fraud Check Threshold, Do AVS Check and AVS Threshold fields as per your requirement.
- The following checkboxes have to be checked:
- Is Active?
- Do CSC Check (if required)
- Use Additional Parameters
- Use Reference Transactions
- In the PlugIns tab, fill in the following details exactly as given below. It is recommended to copy and paste the below values to avoid errors.
- Authorization Assembly - ElectronicPayment.CardPointe
- Authorization Object - CRM.ElectronicPayment.CardPointe
- Authorization Class - Aptify.Applications.OrderEntry.Payments.ElectronicPayment.CardPointe.ElectronicPaymentCardPointe
- Capture Assembly - ElectronicPayment.CardPointe
- Capture Object - CRM.ElectronicPayment.CardPointe
- Capture Class - Aptify.Applications.OrderEntry.Payments.ElectronicPayment.CardPointe.ElectronicPaymentCardPointe
- In the Attributes tab, fill in the following details:
- GatewayLocation - Base URL of CardPointe Gateway RESTful web services. (For example, https://fts-uat.cardconnect.com/cardconnect/rest)
- Username - Provided by CardPointe
- Password - Provided by Cardpointe
- OperationMode - As per requirement
- MerchantID - Provided by Cardpointe
- In the Payment Types tab, add the necessary payment types to be used for payment, including the newly created payment type for the Hosted iFrame Tokenizer. 
- In the Currency Types tab, add the necessary currency type records. 
- Save and Close the record.
Hosted iFrame Tokenizer
With the introduction of Cardpointe in Aptify 7.1, the Hosted iFrame Tokenizer is also integrated with Aptify Smart Client, Aptify Web and e-Business. The Hosted iFrame Tokenizer helps to reduce Payment Card Industry (PCI) Data Security Standards (DSS) audit scope by providing a secure iFrame. The iFrame is embedded into online checkout page to accept and transmit sensitive payment data to CardSecure (CardPointe platform's P2PE-validated encryption and tokenization solution) for tokenization.
A new HTML page has been built with embedded JavaScript, called, HostedTokenizerPaymentForm.html. This new page is used to design and develop a new checkout page for all the Aptify applications. It is the preferred mode of checkout for payments that use the CardPointe merchant account. The iFrame in the HTML file has the CardPointe's Hosted iFrame Tokenizer embedded.
<iframe id="tokenframe" name="tokenframe" frameborder="0" scrolling="no" width="600"
height="200" src="https://fts-uat.cardconnect.com/itoke/ajax-tokenizer.html?useexpiry=true&usecvv=true&enhancedresponse=true&invalidcreditcardevent=true&invalidexpiryevent=true&css=select%2Cinput%7B%0Aborder%3A%201px%20solid%20%23ccc%3B%0Aborder-radius%3A4px%3B%0Afont-size%3A14px%3B%0Afont-weight%3A%20400%3B%0Aline-height%3A%201.65em%3B%0Abackground%3A%20%23f9f9f9%3B%0Afont-family%3A%20Roboto%2C%20arial%2C%20sans-serif%3B%0Afont-color%3A%23304457%3B%0Atext-indent%3A0.33em%3B%0Aheight%3A32px%3B%0Amin-width%3A70px%3B%0Amargin-bottom%3A%2020px%3B%0Acolor%3A%20%23555%3B%0Apadding%3A%204px%3B%0Abox-sizing%3A%20border-box%3B%0Abox-shadow%3A%20inset%200%201px%203px%20rgba(0%2C0%2C0%2C.1)%3B%0A%7D%0Aselect.error%2C%0Ainput.error%7B%0Aborder%3A%201px%20solid%20%23db5c71%3B%0A%7D%0Aselect%3Afocus%2C%0Ainput%3Afocus%2C%0Aselect%3Ahover%2C%0Ainput%3Ahover%7B%0Aborder-color%3A%20rgba(82%2C168%2C236%2C.8)%3B%0Abox-shadow%3A%20inset%200%201px%203px%20rgba(0%2C0%2C0%2C.1)%2C%200%200%208px%20rgba(82%2C168%2C236%2C.6)%3B%0Aoutline%3A%20none%3B%0A%7D%0A%23ccexpiryyear%7B%0Amargin-left%3A%2010px%20!important%3B%0A%7D%0A%23ccnumfield%7B%0Awidth%3A%20230px%3B%0A%7D%0Alabel%7B%0Afont-family%3A%20Roboto%2C%20arial%2C%20sans-serif%3B%0Afont-size%3A14px%3B%20%0Afont-weight%3A400%3B%20%0Acolor%3A%23555%3B%0Adisplay%3A%20block%3B%0Amargin-bottom%3A%205px%3B%0A%7D%0Alabel%2Bbr%7B%0Adisplay%3A%20none%3B%0A%7D">
</iframe>
The "src" attribute of the iFrame contains the Tokenizer's URL provided by Cardpointe. The section of the URL marked in red is to be replaced with the base URL of the CardPointe Gateway provided by CardConnect. The URL consists of various parameters which corresponds to the fields on the form such as CVV and Expiry. It customizes the requirements for response from CardPointe's side and add custom CSS.
For example, when the useexpiry and usecvv fields are set to true in the parameters, the payment form would show the CVV and Expiry fields. Read More for information on customizing the Hosted iFrame Tokenizer.
In the below image, the section marked in red shows the Hosted iFrame Tokenizer provided by CardPointe as per the URL entered above:
Once the user fills in the card details and clicks outside the section of the iFrame, anywhere on the Payment form, the token gets generated. This token is used for making the payments, thereby, eliminating our application's access to the card details.
Configuration specific to Aptify Smart Client
- Make sure that you are using the latest version of Internet Explorer (IE) on the machine where Aptify Smart Client is installed.
- Make sure that the Internet Explorer has Cardconnect URL added to its trusted sites. Following are the steps to add the Cardconnect URL. Open IE → Go to Setting → In the Internet Options → Select Security tab → Select Trusted sites → click sites → add <<base URL of the CardPointe Gateway>> → click close.
If the setting is not present, then add it as Administrator user. - Run the Object Repository Synchronizer utility in case the iFrame and its images are not displaying properly.
Comments
Please sign in to leave a comment.