|
-->Not sure exactly what the environment is. You are talking -->about a terminal, -->but you are also talking about web based software and stuff. Both. The 5250 terminal transactions would be 'handled' by programs polling the payment processing server waiting for the next transaction, which authorizes over public network using SSL. My idea of handling this is using the iSeries data queue and socket connection to this payment server also hosted in house. My test results of just the payment piece is 3-4 seconds. If I add overhead for terminal based responses I think still reasonable times. I have seen a good PC solution for this but it replaces existing screen interfaces. I am looking for the nut & bolts really. The internet based transactions (card not present) are a more direct interaction to that same payment processing server. thanks, -mark
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.