Which gateway is *that*?
You're leaving out a LOT of information from the bigger picture here, and that information would seem to be quite crucial to help get the *best* solution to your client's business needs, even if said *best* solution doesn't come in the box they think it should come in.
Well, you're asking a complex question:
a) if you're blindly accepting unauthorized credit cards to complete your online orders, then you have NO way of immediately rejecting fraudulent orders, and no way of protecting yourself against address-validation failures. Your customers will *think* they've paid, when in fact they've not.
b) and the only way to store card information for processing via another system requires that you build your own bespoke PERFECTLY SECURE and FULLY PCI-COMPLIANT (yes, that means a whole NEW round of QA assessments and fees) including your own non-internet-connected servers for processing and handling the card details.
Even if you dare to store the information encrypted, you're not allowed to store that on an internet-connected server.
But, this isn't the place to discuss all the PCI Compliance requirements or regulations.
Clearly you're not interested in any of US telling you that you can't do what you're wanting to do the way you're wanting to do it.
Besides, even if we did have exact code and encryption logic for you to use, we could NOT post it publicly or it'd immediately invalidate its security and safety.
So, pick an order export addon plus an appropriate existing payment module, and feel free to write your own means of dealing with the data. Just be certain you understand all the risks you're subjecting both yourself and your client to by doing so.
I still submit to you that your client is better served by connecting their store directly to existing live gateway for handling payments. And it'll cost THEM a whole lot LESS to do, and be up and running WAY faster than the route you've described.



Reply With Quote
