@odd waffle
Actually, SE didn't have to convert any currency in the process--that is all handled between the financial orginazations involved. USD has been a centralized currency in the markets for YEARS as one of the baselines.
The shift is more likely to simply get out of their POL database because it was either proprietary or otherwise not capable of handling scripting like so many other databases that are so easliy manageable with a simple language like SQL. Moving to a more stremalined and manageable database model will allow them to automate and otherwise streamline all processes, potentially reducing downtime and reducing daily operating costs considerably.
So, from that viewpoint, migrating the data makes perfect sense. But then that poses an even bigger problem. You need a secure connection to a CC processor for completing transactions. It appears in the old system, they were sluffing off the process to regional offices (US payments showed up as being from their CA division and not Tokyo), so they were processing US payments through a US processor in US dollar amounts via a secure connection between that office and that regional CC processor. After this move, they may have a streamlined database capable of using simple query and update statements to pull/update that data on the fly. They could potentially arrange to make a secure connection from Tokyo to a US CC processor, poll the necessary data from the new database (such as Square Enix USA, CA details, $12.95 USD, other necessary details) to build the XML string to process the payment directly from Tokyo, on behalf of the US division plunking that money into the US divisions bank accounts--effectively doing the same thing without having to suynchronize all the data to the US first for local processing and then synching it back to JP.
There may be some legal constraints to this though...if so, the system should still be much more efficient at transfering just the required info to the regional office for processing to bypass those constraints and then sling it back to Tokyo. Less data means shorter transfers and less downtime, and by being able to use a more robust scripting language it allows more automation as well which results in less payroll cost in the end.
