Migrate > Take the first steps after WebSphere Commerce migration > Migrating from a previous payment implementation > Migrating to the Paymentech plug-in

Migrate from the Paymentech cassette to the Paymentech plug-in

To migrate from using the Paymentech cassette to using the Paymentech plug-in, you set up a new payment method that uses the Paymentech plug-in and disable the payment method that uses Paymentech cassette.

Before you begin

You must have already performed the WebSphere Commerce migration from 5.6 or 5.6.1 to 6.0. The migration process uses data from WebSphere Commerce 5.6 or 5.6.1 to populate the related database tables in WebSphere Commerce 6.0, such as EDPORDER and EDPPAYINST. If you started migrating WebSphere Commerce before all of the pending orders were processed using the Paymentech cassette, continue to maintain the Payment Manager to process them.

You must also have migrated Payment Manager from 5.6 or 5.6.1 to WebSphere Commerce Payments 6.0. The Payment Manager migration script only migrates the data in Payment Manager, it does not migrate the data in WebSphere Commerce.

You can process existing orders using the Paymentech cassette. All new orders use the Paymentech plug-in. Depending on the status of any pending orders when the migration was performed, after orders that were placed using the cassette payment method have been processed, migrate the payment information to the EDPORDER, EDPPAYINST, PPCPAYINST, and PPCEXTDATA database tables.

Procedure

1. Query the POLICY table:

   select policy_id, policyname, policytype_id, storeent_id, properties from policy where policytype_id = 'Payment' and policyname ='VISA'
   

   The output is similar to the following example:

   POLICY_ID POLICYNAME POLICYTYPE_ID STOREENT_ID 
   ****      'VISA'     'Payment '    -10001      
   
   PROPERTIES
   'profileName=WCPPlugin_Paymentech&cassetteName=Paymentech&attrPageName=StandardCreditCard&display=true&compatibleMode=true'
   

   Note the values of the storeent_id and properties.

2. Query the POLICYDESC table:

   select policy_id, language_id, description, longdescription from policydesc where policy_id in (select policy_id from policy where 
   policytype_id = 'Payment' and policyname = 'VISA') and language_id = -1 
   

   The output is similar to the following example:

   POLICY_ID LANGUAGE_ID DESCRIPTION LONGDESCRIPTION
   ****      -1          'VISA'      'VISA Payment'
   

   Note the values of the short and long descriptions. Choose different values when you create a new payment policy.

3. Prevent the old policy from displaying on shopping pages.

   update policy set PROPERTIES='attrPageName=StandardVisa&paymentConfigurationId=default
         &display=false&compatibleMode=false' where policy_id=oldPolicyID;
   

   Where:

   oldPolicyID

   Is the policy_id returned is step 1.

4. Query the POLICY table to determine an unused payment policy_id: select max(policy_id)+1 as policy_id from policy

   The number returned is referred to as newPolicyID in the following steps.

5. Insert the payment policy in the POLICY table.

   insert into policy (policy_id, policyname,policytype_id,storeent_id,properties) values 
    (newPolicyID,'VISACard','Payment',storeent_id,'attrPageName=StandardVisa&paymentConfigurationId=default&display=true&compatibleMode=false');
   

6. Insert the payment policy in the POLICYDESC table.

   insert into policydesc (POLICY_ID,LANGUAGE_ID,DESCRIPTION,LONGDESCRIPTION) values 
    (newPolicyID,-1,'VISA Credit Card Payment','VISA Card Payment');
   

   The value of the description will display to shoppers on shopping pages.

   Repeat this step for each language that the store supports.

7. Register the policy in the POLICYCMD table:

   insert into policycmd (policy_id, businesscmdclass) values (newPolicyID, 'com.ibm.commerce.payment.actions.commands.DoPaymentActionsPolicyCmdImpl') 
   insert into policycmd (policy_id, businesscmdclass) values (newPolicyID, 'com.ibm.commerce.payment.actions.commands.EditPaymentInstructionPolicyCmdImpl') 
   insert into policycmd (policy_id, businesscmdclass) values (newPolicyID, 'com.ibm.commerce.payment.actions.commands.QueryPaymentsInfoPolicyCmdImpl') 
   

   This step enables the payment policy to use the Payment plug-in controller.

8. Configure the Paymentech plug-in.
   

What to do next

Complete any outstanding payment transactions using the Paymentech cassette. New orders can only be placed using the Paymentech plug-in.

Related concepts

Paymentech plug-in

Paymentech plug-in batch states

Related tasks

Configure the Paymentech plug-in

Configure a merchant to access the Paymentech gateway

Migrate from the WCPayments plug-in using the Paymentech cassette to the Paymentech plug-in

Schedule Paymentech jobs

Related reference

Troubleshoot: Recovering Paymentech processing errors

PPCPaymentechBatchCtrlCmd

PPCPaymentechGetCtrlCmd

+

Search Tips   |   Advanced Search