Please try now, appears the system was confused, it created the service with one username but indicated another in the backend, likely caused by an initial provision fail but the backend had already saved information on your account and didn't overwrite this when a subsequent attempt succeeded...