CardConnect is an out of the box plug-in that can be configured to process payments when completing an order on your Optimizely <<product-name>> website.
Note
<<product-name>> cannot test CardConnect with TokenEx in Sandbox, so if you want to test it, submit a ticket.
Go to **Admin ConsoleAdministration** \> **System** \> **Settings.**
Search for and select **Payment Gateway**.
Select **CardConnect** from the **Payment Gateway** menu.
Populate the fields listed below with the criteria provided via your CardConnect account.
The following settings are used to configure CardConnect as the payment provider in <<product-name>>:
<table class="TableStyle-Borders" style="margin-left: 0; margin-right: auto; width: 100%;" data-cellspacing="0"> <colgroup> <col style="width: 50%" /> <col style="width: 50%" /> </colgroup> <thead> <tr class="header TableStyle-Borders-Head-Header1"> <th class="TableStyle-Borders-HeadE-Regular-Header1">Field Name</th> <th class="TableStyle-Borders-HeadD-Regular-Header1">Description</th> </tr> </thead> <tbody> <tr class="odd TableStyle-Borders-Body-Row1"> <td class="TableStyle-Borders-BodyE-Regular-Row1">Merchant ID</td> <td class="TableStyle-Borders-BodyD-Regular-Row1">Enter the Merchant ID for the CardConnect account.</td> </tr> <tr class="even TableStyle-Borders-Body-Row1"> <td class="TableStyle-Borders-BodyE-Regular-Row1">API Username</td> <td class="TableStyle-Borders-BodyD-Regular-Row1">Enter the API Username for the CardConnect account.</td> </tr> <tr class="odd TableStyle-Borders-Body-Row1"> <td class="TableStyle-Borders-BodyE-Regular-Row1">API Password</td> <td class="TableStyle-Borders-BodyD-Regular-Row1">Enter the API Password for the CardConnect account.</td> </tr> <tr class="even TableStyle-Borders-Body-Row1"> <td class="TableStyle-Borders-BodyE-Regular-Row1">Production Endpoint</td> <td class="TableStyle-Borders-BodyD-Regular-Row1">Enter the Production Endpoint for the CardConnect account. The URL is multi-tenant, so it is going to be your company's URL, for example: yourcompany.cardconnect.com.</td> </tr> <tr class="odd TableStyle-Borders-Body-Row1"> <td class="TableStyle-Borders-BodyE-Regular-Row1">Sandbox Endpoint</td> <td class="TableStyle-Borders-BodyD-Regular-Row1">Enter the Sandbox Endpoint for the CardConnect account.</td> </tr> <tr class="even TableStyle-Borders-Body-Row1"> <td class="TableStyle-Borders-BodyE-Regular-Row1">Use Payment Gateway Vault</td> <td class="TableStyle-Borders-BodyD-Regular-Row1"><p><span>Enables using credit card tokens from the payment gateway that can be submitted to the ERP. This option should only be enabled if the ERP requires the payment card token to process a transaction as opposed to the authorization token. Default value: Yes.</span></p> <p><span>The Payment Gateway Vault token is stored in Token2.</span></p></td> </tr> <tr class="odd TableStyle-Borders-Body-Row1"> <td class="TableStyle-Borders-BodyB-Regular-Row1">Test Mode</td> <td class="TableStyle-Borders-BodyA-Regular-Row1">If Yes, CardConnect will be in test mode and no actual transactions will take place. Default value: On.</td> </tr> </tbody> </table>
️ IMPORTANT
<<product-name>> does **NOT** store sensitive credit card or profile information.