


All you need to do to process cards is to send an https post in XML format. This means that I cannot use other messaging format such us NDC or D912.Ī is very easy to use.
CREDIT CARD TERMINAL POS SOFTWARE
One thing I know is that ISO 8583 is the essential financial messaging protocol because most of the banking switching software system, for my region, use only these messaging format. When I read a Authorize.Net page, I found the routine of Credit Card Processing.ĭo i need to follow this whole procedure no matter whether my project is big or small, international running or domestic running?ĭo I really need to follow this procedure to make payment process with POS - Terminal Devices ? So what I would like to know is which will be the best solution and how the system architecture will be? As for me, I assume that my system is not as big as international payment processing and will start working as a domestic small system. Let's say, whenever customer buy goods from my department store, staff from this store will stripe customer's financial cards and make payment transaction.įor those similar system, most of the forums say that it should be considered to use third party API such as:īut I think that those APIs should use for those kind of system which will go to international payment processing.

I have a project in which I need to interact with POS - Terminal Devices and magnetic/chip cards.
