Hi all,
Thanks for the reports!
It looks like this issue was caused by a configuration error with one of our payment processors though has since been resolved (thanks for the follow-up to help confirm, Ivanx!)
Anyone else that was previously having issues should be able to try again now.