This is an old revision of the document!
Table of Contents
TWBS Credit Card Token/Profile Version Primer
Authorize.Net Specific Information
- Customer Information Manager (CIM) Activation – Prior to adding new customer/payment profiles to the system either via entry or card migration for upgrades, an end-customer representative will be required to log onto the Authorize.Net account via the website and activate the Customer Information Manager (CIM) functionality. If this is not done, card entry/migration will fail.
- Payment Profile Limitation per Customer Profile – There is a maximum of 10 payment profiles (cards) that can be stored on each customer profile (business partner) in Authorize.Net. During card migration, the application will migrate the default card for the BP first, then up to the next 9 cards in order of unique ID assigned. Any cards above the 10 allowed will not be migrated. To add a new payment profile to a customer profile that has 10 payment profiles, one of the existing payment profiles would need to be removed.
CyberSource Specific Information
- Recurring Billing Function Activation – Prior to adding new customer/payment profiles to the system either via entry or card migration for upgrades, an end-customer representative will be required to contact CyberSource and request that the Recurring Billing function be enabled on their CyberSource account. If this is not done, card entry/migration will fail.
When contacting CyberSource to activate the Recurring Billing functionality, please specify that they use the 16-character token length option.
- Contact the Processing Center on the CyberSource Account to Determine Any Daily Transaction Limits Prior to Card Migration – Creation of a new payment profile, either by manually entry or card migration, counts as a $0 transaction. Once the daily transaction limit on the processing center account and the number of cards to be migrated are known, if the number of cards to be migrated exceeds the daily transaction limit, please contact TWBS via support ticket to discuss options. It is also advisable that the customer notify the processing center in advance before the profile migration to make them aware of the large number of transactions that will be executed against the gateway account in a short period of time to let them know the source of the activity.
- Review Card Address Info and Use of AVS Exemption from Prior TWBS CC Version if Upgrading – Address information passed into Recurring Billing profiles is AVS validated. If the address information saved and passed is not correct, but perhaps was not noticed because the Exclude from AVS Checking option had been selected for processing in the previous version of TWBS CC, the migration of that card will fail depending on the AVS acceptance settings on your CyberSource account. The Exclude from AVS Checking option isn't available in the latest version of TWBS CC.
Card Cleanup Prior to Upgrade to TWBS CC Tokenized Version – Highly Recommended
Expired cards will migrate to the gateway. Due to some of the gateway limitations discussed in the gateway specific sections, it is advised that prior to the card migration that the data be cleaned up. This can be identifying the cards that are already expired and providing the data to the customer to determine which cards need to be updated followed by removal of all cards that aren’t update and remain expired. Other customers may simply choose to remove all cards that have already expired.
Selection Query to determine how many cards have expired prior to the current month (SQL)
SELECT * FROM [@TWBS_CC_BPCC] WHERE CONVERT(INT,RIGHT(U_ExpirationDate,2)) < CONVERT(INT,RIGHT(YEAR(GETDATE()),2)) OR (CONVERT(INT,RIGHT(U_ExpirationDate,2)) = CONVERT(INT,RIGHT(YEAR(GETDATE()),2)) AND CONVERT(INT,LEFT(U_ExpirationDate,2)) < CONVERT(INT,LEFT(MONTH(GETDATE()),2)))
Query to remove cards that have expired prior to the current month (SQL)
DELETE FROM [@TWBS_CC_BPCC] WHERE CONVERT(INT,RIGHT(U_ExpirationDate,2)) < CONVERT(INT,RIGHT(YEAR(GETDATE()),2)) OR (CONVERT(INT,RIGHT(U_ExpirationDate,2)) = CONVERT(INT,RIGHT(YEAR(GETDATE()),2)) AND CONVERT(INT,LEFT(U_ExpirationDate,2)) < CONVERT(INT,LEFT(MONTH(GETDATE()),2)))
Selection Query to determine how many cards have expired prior to the current month (HANA)
SELECT * FROM “@TWBS_CC_BPCC” WHERE CAST(RIGHT(“U_ExpirationDate”,2) as INT) < CAST(RIGHT(YEAR(NOW()),2) as INT) OR (CAST(RIGHT(“U_ExpirationDate”,2) as INT) = CAST(RIGHT(YEAR(NOW()),2) as INT) AND CAST(LEFT(“U_ExpirationDate”,2) as INT) < CAST(LEFT(MONTH(NOW()),2) as INT))
Query to remove cards that have expired prior to the current month (HANA)
DELETE FROM “@TWBS_CC_BPCC” WHERE CAST(RIGHT(“U_ExpirationDate”,2) as INT) < CAST(RIGHT(YEAR(NOW()),2) as INT) OR (CAST(RIGHT(“U_ExpirationDate”,2) as INT) = CAST(RIGHT(YEAR(NOW()),2) as INT) AND CAST(LEFT(“U_ExpirationDate”,2) as INT) < CAST(LEFT(MONTH(NOW()),2) as INT))
BP Associated Card Gateway Data Migration Time Factors
- Authorize.Net profile conversion is approximately 2-3 seconds per card (approx.. 1200/hour)
- CyberSource profile conversion is approximately 1-2 seconds per card.
Please remember to factor that migration timeframe into any estimates provided for the time to complete the upgrade process.
Verification of the Card Gateway Data Migration Process
During the card migration process, the SAP status bar will provide an update on the progress of the migration (“Migrating credit card 2418 of 2600” for example). At the completion of this process, if any of the cards failed the migration to the gateway, the status bar will present the user with an error (red) message stating “Credit Card information migration failed.” Any cards that failed the migration process will have their encrypted card # replaced with a message starting with the text “Migration failed for…” Example: “Migration failed for C130000-C130000 VISA4-You cannot add more than 10 payment profiles.”
To determine how many cards failed the migration process you can run the following query:
SELECT * FROM [@TWBS_CC_BPCC] WHERE U_CardNumber NOT LIKE '%success%'
A list of the cards that failed migration can be provided to the customer as these cards will not be visible in the front end of the application because they will not be stored in the new user table for payment profile information
