- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Credit Card Storage - Convert from Local Storage (Vaulting) to SPS Vault
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-10-2010 12:02 PM
With 7.3, does anybody know if its possible to convert from the local Vaulting Service/Storage to SPS Vault?
Thanks,
Kris
Re: Credit Card Storage - Convert from Local Storage (Vaulting) to SPS Vault
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-10-2010 02:23 PM
Besides the loss of credit card information that was stored locally, you'd also face some transactional issues: we keep track of a VaultGUID, but we don't keep track of which vault it came from, so if you were to switch, I'd expect problems when looking at older transactions.
We didn't get the chance to write that utility.
Re: Credit Card Storage - Convert from Local Storage (Vaulting) to SPS Vault
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-10-2010 02:45 PM
I anticipate the transaction loss - I'm actually working on an upgrade and migration from a 3rd party CC module to SPS Vault. I'm just looking for the intermediate step that hopefully doesn't include manual input.
So basically, there's currently no way to import existing information into Sage Vault?
Re: Credit Card Storage - Convert from Local Storage (Vaulting) to SPS Vault
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-12-2010 08:10 AM
If you can do a little programming, you can register as a developer on the Sage Payment Solutions web site and get their documentation for the vaulting services.
Write a program that reads the CCAN and EXP DATE from the exiting CC service and stores them in the vault. The returned GUID can then be stored in MAS500 tables using code like this:
-- Move converted data into production tables -- -- INSERT INTO tccVault (VaultGUID, EncCC, EncExp) -- SELECT VaultGUID, EncCC, EncExp -- FROM #tccConvert INSERT INTO tciAddress (AddrKey, AddrLine1, AddrLine2, AddrLine3, AddrLine4, AddrLine5, AddrName, City, CountryID, CRMAddrID, Fax, FaxExt, Phone, PhoneExt, PostalCode, Residential, StateID, TransactionOverride, UpdateCounter) SELECT AddrKey, AddrLine1, AddrLine2, AddrLine3, AddrLine4, AddrLine5, AddrName, City, CountryID, CRMAddrID, Fax, FaxExt, Phone, PhoneExt, PostalCode, Residential, StateID, TransactionOverride, UpdateCounter FROM #tccConvert INSERT INTO tccCustCreditCard (CreditCardKey, AddrKey, CreateDate, CreditCardName, CustKey, ExpirationMonth, ExpirationYear, MaskedAcctNo, VaultGUID, TenderTypeKey) SELECT CreditCardKey, AddrKey, CreateDate, CreditCardName, CustKey, ExpirationMonth, ExpirationYear, MaskedAcctNo, VaultGUID, TenderTypeKey FROM #tccConvert -- Update Default credit cards for each customer UPDATE tarCustAddr SET CreditCardKey = t.CreditCardKey FROM tarCustAddr a JOIN tarCustomer c ON a.AddrKey = c.DfltBillToAddrKey JOIN #tccConvert t ON c.CustKey = t.CustKey WHERE t.IsDefault = 1
Note the code is just an example, you'll have to modify it to work for you.
I also commented out the code inserting into tccVault, you are storing the data in SPS's vault and have a GUID as the link to the data.
MAS500, Principal Designer
Irvine, CA


