parallel infrastructure

2nd or perhaps 3rd (n programmable) processors

rotate processors on TBD algorithm

more than 1 payment processor per bank account, so all funnel into the same account.

load sharing between the two (or three) processors on some basis determined by the algorithm.

To get the buy rates we need from the processors, we have to achieve certain volumes, so we can't have one in perpetual standby.

have to record the processor used for each order and/or transaction. 

Timing is important for when the switchover happens to avoid switching in mid-order
processor assigned to order when order is created
algorithm says change processors
now order is one processor, and subsequent related transactions may run on the current processor which may be different


assign by
communities table
restaurants table
depending on configuration (use_location_gateways)

algorithm change over will occur asynchronously, driven by a cron job on a regular schedule

must ensure that we don't start an order on one processor, and then switchover, then run additional transactions on another processor