1. Preparation
Locate the file containing your encrypted public-private key pair (ending in .pfx) and copy it to the staging area on your web server.
2. Install the Certificate via MMC
Open the Windows command prompt, type
mmc.exe, and press Enter.Once the Microsoft Management Console opens, go to File > Add/Remove Snap-In.
(Figure 1): Microsoft Management Console "Add or Remove Snap-ins" menu.
Select Certificates and click Add.
Choose Computer account, click Next, select Local computer, and click Finish.
(Figure 2): Certificates Snap-in wizard: Selecting "Computer account."
(Figure 3): Certificates Snap-in wizard: Selecting "Local computer."
Click OK to return to the main console.
(Figure 4): Certificates snap-in added to the MMC console root.
Expand the Personal folder, then right-click on the Certificates sub-folder.
(Figure 5): The MMC Personal Certificates folder.
Select All Tasks > Import.
In the Import Wizard:
Click Next.
Browse to and select your .pfx file.
Click Next.
Select Place all certificates in the following store.
Ensure the store is set to Personal and click Next.
Click Finish.
(Figure 6): Completing the Certificate Import Wizard.
Note: Your certificate should now appear in the list of Personal Certificates.
3. Bind the IIS Endpoint
Once the certificate is installed, you must bind your endpoint in IIS.
Open the IIS Console.
Select the ClientPay site in the left sidebar.
(Figure 7): The imported certificate visible in the Personal folder.
Click Bindings in the far-right Actions pane.
(Figure 8): Accessing "Site Bindings" in the IIS Actions pane.
Add a new HTTPS binding:
Note: You cannot change an existing HTTP binding to HTTPS. You must create the new HTTPS binding first, then delete the original one.
Assign the Port (must be 443, 444, 8080, or 32321).
Leave Host name empty and IP address at "All Unassigned" unless you have a specific requirement.
Warning: If using an AffiniPay-generated .pfx, you may see a warning regarding an intermediate certificate. Click OK and ignore this.
(Figure 9): IIS intermediate certificate warning.
4. Test the Connection
After completing the steps above, please email [email protected] to request a connection test.
Success: Our team will confirm the process is complete.
Errors: Our team will work with you to troubleshoot any remaining issues.