Migrating to a New Processing Accounts

Migrating to a New Processing Accounts

Module: Payment Proc Accounts
Path: Campaign > Payment Proc Accounts
Topic: Payment Processing Accounts
Version(s): 5.1 & up
Editions: All

Migrating to a New Payment Proc Account

Points to Note

  1. Credit Card (not tokenization) payment profiles can be converted 
  2. Tokens can only be used with the payment account they are created in. Can NOT be converted from one payment account to another.
    1. switching to a new payment account means any payment profile that has been tokenized will have to
      1. have customer contacted for a new payment profile 
        OR
      2. have a payment schedule kept active to process payment for these orders
        1. review continuity and installments setup in your system
  3. Once the migration is completed, the following places have to be updated:
    1. payment schedules
      1. you have the option to create new payment schedules for the new payment account if processing via the old payment account still
      2. don't forget to select campaigns if adjusting an existing payment schedule. once you adjust payment account the system will automatically deselct existing campaign selections.
    2. campaign default account (if set)
      1. you have the option to create new campaigns for the new payment account if processing via the old payment account still
      2. if you are creating new campaigns you may need to create a new source as well
    3. product group default account (if set)
      1. you have the option to create new product groups for the new payment account if processing via the old payment account still
    4. script payment account
    5. order import schedules
      1. vendors importing orders into your system need to make sure to update PAY_PROC_ACCT
      2. if a new campaign/source was created for the new payment account confirm the order import schedule(s) are updated for campaign/source as well as pay proc account
    6. customer portal payment account
  4. Refunds can only be done via the original payment account of the capture. If the capture is on an old payment account not being used, a check will need to be sent to the customer for the refund amount. You will have to mark the refund as refund accepted in OrderLogix and it's recommended to make a note on CS Events for the customer record, so agents know a check was mailed to the customer.




Copyright 2024
Revised 9.15.2024

    • Related Articles

    • Migrating to a New Processing Account

      Module: Payment Processing Accounts Path: Campaigns > Payment Data > Payment Processing Accounts Topic: Migrating to a New Processing Account Version(s): 5.1 & up Editions: All What Are Payment Processing Accounts? Payment Processing Accounts are ...
    • Authorize.Net - Payment Processing Account With Tokenization

      Module: Payment Processing Account Topic: Authorize.Net Payment Processing Account with Tokenization Version(s): Version 5.1 & up Editions: All Editions Setup The Payment Processing Account Token Generation feature is optional and turned on by ...
    • NMI - Payment Processing Account With Tokenization

      Module: Payment Processing Account Topic: NMI Payment Processing Account with Tokenization Version(s): Version 5.1 & up Editions: All Editions Tokenizing Your Payments The Payment Processing Account Token Generation feature is optional. This feature ...
    • Braintree - Payment Processing Account Token Generation

      Module: Braintree Payment Processing Account Token Generation Topic: Braintree Payment Processing Account Token Generation Version(s): Version 5.0 Editions: All Editions What Is Braintree A Braintree is a payment gateway that processes the various ...
    • WARNING: PAY_PROC_ACCT has the value "X". Multiple accounts exist for this PAY_PROC_ACCT.

      Message: WARNING: PAY_PROC_ACCT has the value "X". Multiple accounts exist for this PAY_PROC_ACCT. Explanation:  The Payment Processing Account name specified matches more than one Payment Processing Account. Suggested Resolution: Rename one or both ...