Jump to content


Credit Card Encryption + others

  • Please log in to reply
3 replies to this topic

#1 ChrisPols



  • Members
  • Pip
  • 4 posts

Posted 22 July 2004 - 06:10 AM

Hi everyone,
We just upgraded from MOM version 3 all the way to MOM version 5. Having some major issues, which hopefully someone here can let me know how to fix.

The first major problem we're having is the credit card encryption. In MOM v 3, there was no encryption. Being in South Africa, we don't have the ICASS options to choose as the banks do not support the methods used by MOM. We had a programme created for us to copy from the CMS.DBF file, all the card numbers into another .txt file. This file was formatted correctly and then sent to our bank for processing. Now with the version 5, it's encrypted the card into a 48 digit sequence. Obviously this is playing havoc with the system in place, and we've had to revert back to version 3 until we can sort this out. I was hoping there was a "Don't encrypt" button somewhere, but alas not. Is there a program that was made after version 4 was brought out to decrypt this number? I've got someone looking into decrypt it, as I found how it's being done, so if he gets it working this will fix my major problem.
Other problems are small.
1. When entering the "Shipping method' after entering the credit card details, instead of jumping to the next box on the right, it jumps back onto either the Credit Card number, or the card type. This creates confusion with our call centre or immediately start to type, and replacing the card number. Very irritating.
2. How can we change all screens with the $ symbol with our South African rand symbol R.

Many thanks,


#2 Guest_B_*

  • Guests

Posted 03 August 2004 - 03:09 AM

Buy the ICCAS and contact Dydacomp regarding the txt files that this produces.
You then need your coder to extract the card information from these files rather than the cms.dbf.
You will then have to reformat your response file so that Mom reads back the authorisation codes. Dydacomp Quality assurance have documentation on this, ask support to contact them for this information.

Dollar signs to R- Dydacomp can change this as customisation.

#3 Chris



  • Members
  • Pip
  • 4 posts

Posted 04 August 2004 - 03:56 AM

Hey B,

We've figured this out by having a Visual Foxpro program made to read the dbase file and convert it to a duplicate file but decrypted (obviously renamed something else) This works fine for us now.

Re: the customisation, they won't do it for us, and have told us to speak to MOM Helpers, but they will only make a customisation on the printer output, and not on the screens themselves. One those things we have to deal with I suppose.

Cheers for getting back to me..


#4 notehead


    Advanced Member

  • Members
  • PipPipPip
  • 52 posts

Posted 07 September 2005 - 07:03 AM

If you talk to your sales rep and really bug them they will actually quote you a price for the customization. As MOM is license driven each customer has customization that is activated by thier license number. Even if you don't see it.

If you could post your decryption technique I would appreciate it. If not posted publically post it privately. I am not actually interested in cc cards but rather the stockmem table and would guess that the technique is the same or similar.


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users