Administration Guide for Oracle Billing Insight > Configuring the Payments Module >

Configuring Page Encryption for Payment Pages

The page encryption feature guarantees that credit card sensitive data such as card number and CVV code is sent to the gateway directly instead of processing in the Oracle Billing Insight application.

You must configure page encryption for each merchant account and payment gateway that you use and leave page encryption enabled.

Follow the steps in this topic to configure page encryption for the following payment gateways:

• Configuring Page Encryption for PayPal Payflow Pro
• Configuring Page Encryption for Chase Paymentech Orbital
• Configuring Page Encryption for CyberSource

Configuring Page Encryption for PayPal Payflow Pro

Follow these steps to configure page encryption for use with PayPal Payflow Pro.

To configure the page encryption feature for PayPal Payflow Pro

1. Configure the PayPal Payflow Pro merchant account:
   1. Log into PayPal Manager with your merchant user and password. Click Service Settings, and click Set Up to configure hosted checkout pages.
   2. Under the Silent Post for Data Transfer section, make sure that the value of Use Silent Post is set to Yes. (Do not check the Void transaction when my server fails to receive data sent by the silent post option, otherwise the transaction will be voided automatically.)
2. Add the following parameters to the PayPal Payflow Pro payment gateway configuration in the Command Center.

   Command Center Gateway Configuration Parameters for PayPal Payflow Pro	Value to Specify
   PayPal Hosted Pages URL	The URL where the payment request will be sent. When page encryption is enabled, card-sensitive data will be sent to this URL directly. For test transactions, specify: https://pilot-payflowlink.paypal.com For live transactions, specify: https://payflowlink.paypal.com

3. When you go to live production with Oracle Billing Insight, change the value of the PayPal Hosted Pages URL parameter to the URLs for live transactions.

Configuring Page Encryption for Chase Paymentech Orbital

Follow these steps to configure page encryption for use with Chase Paymentech Orbital.

To configure the page encryption feature for Chase Paymentech Orbital

1. Configure the Chase Paymentech Orbital merchant account:
   1. Log into Orbital Virtual Terminal with your merchant user and password. Click ADMIN, and Hosted Pay Page Admin.
   2. Configure the Hosted Payment Form. Be sure to select Hosted Payment Form as the Hosted Solution. Also check the option for Enhanced Response.
2. Verify that the following parameter is set in the Chase Paymentech Orbital payment gateway configuration in the Command Center.

   Command Center Gateway Configuration Parameters for Chase Paymentech Orbital	Value to Specify
   Hosted Secure ID	The Secure Account ID used for the Chase Paymentech Orbital hosted payment form. See your Chase Paymentech Orbital Integration Consultant for the value.

Configuring Page Encryption for CyberSource

Follow these steps to configure page encryption for use with CyberSource.

To configure the page encryption feature for CyberSource

1. Configure the CyberSource merchant account:
   1. Log into the CyberSource Business Center with your merchant user and password. Select Tools & Settings, and under select Profiles under Secure Acceptance.
   2. Click Create New Profile and create a new Secure Acceptance Profile.

      Choose Silent Order Post as the integration method, and choose Payment Tokenization from the list of Added Value Services.

   3. Find the profile ID under the profile name and make note of it; you will need this information when you configure the CyberSource gateway settings in the Oracle Billing Insight Command Center.
   4. Click the profile name you just created to view Profile Settings, and then click Payment Settings. Add all payment methods to support for page encryption (add all of the payment methods supported in Oracle Billing Insight).

      Be sure to select the Fails AVS check and Fails CVN check options for Automatic Authorization Reversal.

   5. Click Security and click Create New Key. Create a new key for page encryption.

      Make note of the Access Key and Secret Key; you will need to add both pieces of information to the payment gateway configuration parameters in the Command Center.

   6. Click Promote to Active to promote the profile.
2. Add the following parameters to the CyberSource payment gateway configuration in the Command Center:
   1. Log into the Oracle Billing Insight Command Center, and add the following information you just created in the CyberSource Business Center to the gateway configuration for CyberSource.

      Command Center Gateway Configuration Parameters for CyberSource	Value to Specify
      CyberSource access key	Specify the Access Key value generated for the page encryption key when configuring the profile in the CyberSource Business Center.
      CyberSource profile ID	Specify the Profile ID generated when you created the new profile in the CyberSource Business Center
      Cyber Source security key	Specify the Secret Key value generated for the page encryption key when configuring the profile in the CyberSource Business Center.
      CyberSource Standard Transaction Endpoint	The URL where the payment token creation request will be sent. When page encryption is enabled, card-sensitive data will be sent to this URL directly. For test transactions, specify: https://testsecureacceptance.cybersource.com/silent/pay For live transactions, specify: https://secureacceptance.cybersource .com/silent/pay
      CyberSource Update Payment Token EndPoint	The URL where the payment token update request will be sent. When page encryption is enabled, card-sensitive data will be sent to this URL directly. For test transactions, specify: https://testsecureacceptance.cybersource.com/ silent/token/update For live transactions, specify: https://secureacceptance.cybersource .com/silent/token/update

3. When you go to live production with Oracle Billing Insight, change the value of the CyberSource Standard Transaction EndPoint and CyberSource Update Payment Token EndPoint parameters to the URLs for live transactions.