Thank you for your follow up questions @jstaab !
The bogus gateway does not have a cap on it for the amount of test orders it can process. If you are seeing an error that the checkout is disabled while attempting to process a test order through the bogus gateway, this means that an attempt to make a live order was made and the checkout was automatically disabled. This can be re-enabled by our Partner support team under their discretion.
I can also absolutely recognize the importance of being able to test out draft orders. If you are integrating an app or developing an API that needs access to that ( @arsuceno ), our Partner Support can also review the request and add on a limited number of transactions that can be tested through that method. Is this ideal for developers like yourself? No it isn’t and we know that. Hopefully our developers can come to a better middle ground between limiting abuse of our development stores and allowing our developers access to a full testing environment without having to ask our support to unlock those features for them. In the interim I do suggest connecting with our partner support team and open a dialogue with them about the needs for your development store. With legitimate business use cases considerations can be made.
Please continue to provide your feedback, the more feedback we receive on things like this the better chance we have at making a change! I want you to know that my replies here are not meant to mitigate the importance of your concerns, but to ensure you have workable solutions you can use for now.