Connect and verify a provider account
What It Does
Account setup establishes which provider account the credential reaches before the gateway can use it. Secret storage and the database have separate failure boundaries. Durable verification records explain success or the reason setup failed.
The Flow
When Something Fails
Return the refusal to the creation wizard. The request creates no account link. Roll back failed creation. No incomplete database setup commits. Reject fields that do not fit the declared method without logging their values. If secret creation succeeds before database refusal, cleanup is requested separately. Schedule cleanup of the new secret after database failure; failed job startup waits for job recovery. A committed verification job may still await its start. Record check failure and its provider reason. The account is not made usable by a failed first verification. Rollback preserves the prior saved state and fails the check job. A repeated check can contact the provider again. An unsuccessful provider setup leaves no saved provider endpoint reference. Rhythm can hold an endpoint that the provider has not begun calling.
Open Design Questions
The browser acceptance evidence does not prove wrong-key recovery within the wizard. Endpoint registration can leave a local endpoint that the provider does not call.