Search Engine: Elastic

Article ID: 112269, created on Sep 13, 2011, last review on Jul 14, 2018

  • Applies to:
  • Odin Business Automation Standard 4.5


Since OBAS version 4.1.6 you may migrate to Authorize.Net Token.

This article describes the procedure to convert saved credit card details into Authorize.Net CIM tokens.

  1. Install and configure the Authorize.Net CIM payment plug-in.

  2. Download the attached script to the OBAS container.
  3. Create the credit card data backup of the tables aspc.plugin_pm and ss.sstore:

    ~# mysqldump aspc --tables plugin_pm > backup_plugin_pm
    ~# mysqldump ss --tables sstore > backup_sstore
  4. Retrieve the Authorize.NET CIM plug-in ID.

    The Authorize.NET CIM plug-in ID can be retrieved from the OBAS database with the following query.

    ~# hspc-sql -e "select id from plugin where template_id='OP_AnetCIM' and vendor_id=1"
    | id |
    | 10 |

    To get the Authorize.NET plug-in ID for the reseller, replace the vendor_id=1 with the reseller ID.

  5. Convert credit cards to Authorize Net tokens using the downloaded script

    # ./
    Script for migration credit card to Authorize Net tokens
    usage: -p X [-c -d]
    where options are:
            -p   Authorize Net plugin id configured in OBAS
            -c   Credit Card ID added in OBAS, if skiped all credit card will be migrated
            -d   Delete credit card after migration (without this option card will be disabled)

    To migrate all credit cards, only the plug-in ID is required. Use the plug-in ID that was retrieved in step 4.

    ~# ./ -p PLUGIN_ID

    Use the "-c" option to specify the list of credit card IDs. If this option is not specified, all credit cards will be migrated. To specify several credit card IDs, use this option multiple times.

    ~# ./ -p PLUGIN_ID -c 1 -c 2 -c 3

    Specify the "-d" option to delete credit card data after the migration. If you don't specify this option, credit cards will be disabled.

    ~# ./ -p PLUGIN_ID -d
  6. Remove the backup once you make sure that the migration completed successfully.

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 624ca542e40215e6f1d39170d8e7ec75 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF