Yikes, I'm getting the same thing, I didn't realize the error was happening after clicking on a payment button. It looks strange on the backend as well, now that I know what to look for. It could be a bug or it could be an error in how I've set things up, so I've emailed support, and will update if/when this gets resolved!