So, here is the insight in the current situation.
As we know, script we bought still used blockchain.info API, but an improved one on script side, to optimize requests, and don't overwhelm the limitations. We knew already, that we need to change the API at some point, which we actually did start already.

We did not plan the traffic to grow this fast, so the API got blocked much earlier, than we could switch to new one.

Currently developer is working his ass off to implement the "BlockTrail" API - https://www.blocktrail.com/api
Which will be able to handle our sizes. I have already spoken to BlockTrail, and they are positive we can switch to them with no worries about limitation problems. They also will warn early, if there is an issue with limits, so we can actually be ready for situations like this.

Good News for Investors
Database saves every payment and deposit, which has been left out due to API down-time. This means, as soon as API is implemented, every missing payment will get sent.
This also means, that new deposits are still possible, we can programmatically trace every incoming deposit, and add them to the table in a matter of click.

Stay tuned for more info.