We're aware of credit check failures resulting in HTTP 503 responses. We're investigating the cause and will update further shortly.
Our engineers have identified the cause with our vendor and have now resolved this issue.