no, the software stops as soon as it goes through, so no fruad.
one more question, same subject.
So currently we have a system that actually stores customers cc info on our side and we process payments by passing that cc info on our system to the gateway and then the gateway charges them.
We are moving to a new system using the same gateway however, instead of storing the cc info on our side and passing that info to the gateway every month, this new system will store the cc info and then we will id customers on our side to the gateway side using a secure token. That way we don't have to worry about compliance or so much security on our side and we let the gateway handle that.
However there has to be an initial passing of the current credit card info from our current system to our gateway before we go to the token system. Do we need authorization to do this or since they are already customers and approved of being charged in our current terms, is that enough to protect us in order to do this one initial pass of info to the gateway and then the gateway stores it, assigns a token and then we go to the token system?
Keep in mind, the gateway we are using for this new token system is the exact gateway and merchant id we are currently using now, so we are simply changing the method by which we do transactions and moving the cc info off our side and onto the gateway side.
Thanks for your help!