Registration & Login

​

Real-World Example

​

Registration And Activation Flow

1. Public registration request: The user submits their name, email address, password, recaptcha verification, and Terms & Conditions acceptance. Gate: registration request is accepted.
2. Email verification: The platform sends an email verification link. Gate: the email address must be verified before onboarding access is granted.
3. Initial account creation: After successful email verification, the system creates the initial company user account and starts the onboarding flow. Gate: authenticated onboarding session is established.
4. Company profile setup: The user completes the company profile, including business identity, address, contact information, website, business category, and operational details. Gate: all required company profile fields are completed.
5. Business verification (KYB): The platform submits the legal business name and Tax ID/TIN to Middesk for verification. Gate: Middesk must return a verified company name and TIN match before onboarding can continue.
6. Membership plan selection: The user selects a membership plan. Gate: inactive membership record is created for the selected plan.
7. Billing and payment activation: Card or ACH details are collected through a secure Stripe payment flow, the platform verifies the Stripe payment record, and membership is activated only when the payment succeeds or an ACH payment enters processing. Gate: active membership status is established.
8. Set Up Wizard routing: After membership activation, the user is redirected to the Set Up Wizard to complete required setup items. Gate: required setup evaluation is completed.
9. Required setup completion: The user completes required setup items such as merchant processing, pay terms, Terms & Conditions defaults, import headers, and About Us configuration. Gate: required setup steps are complete.
10. Workflow access enabled: After all required setup steps are complete, the user receives file upload access and normal creditor workflow access.

​

Business Verification States

​

Membership Activation Rules

• A membership plan and valid billing method are required before activation.
• Card or ACH details must be collected through the secure payment-provider flow.
• Before changing membership state, the platform must verify that the payment belongs to the creditor and matches the expected amount, currency, and billing reference.
• A successful card payment or processing ACH payment may activate the membership and save the reusable membership payment method.
• A delayed ACH failure must change the related billing transaction to failed and return the membership to inactive.
• Repeated completion or provider-callback events must not create duplicate membership transactions.
• Membership activation does not bypass required Set Up Wizard blockers.

​

Required Setup After Registration

• Merchant payment processor: The company must have an active or verified merchant processor configuration.
• Pay Term Offers: Required pay-term percentages and first-payment timing must be configured.
• Terms & Conditions: A default Terms & Conditions profile must exist.
• Import Header Profiles: A CSV/import header profile must exist for account import mapping.
• About Us Profile: A default About Us profile must exist for consumer-facing company information.

• Sub Accounts.
• SFTP.
• Logo Profile & Embed Code.

​

Returning User Routing

​

Visual Flow

​

How It Should Work

• A user should register using a valid name, email address, password, recaptcha verification, and Terms & Conditions acceptance.
• The registration email address should be valid and unique.
• Registration and login passwords should satisfy the current security requirements.
• The platform should require email verification before onboarding access is granted.
• Login should only succeed when the credentials match an active creditor user with a verified email address.
• The system should create the initial company user only after successful email verification.
• Company profile setup should collect required business identity and operational information.
• The platform should verify the legal business name and Tax ID/TIN through Middesk before onboarding can continue.
• Membership activation should occur only after secure payment confirmation and platform verification of the canonical Stripe payment record.
• The user should be routed into the Set Up Wizard immediately after membership activation.
• The user should not receive file upload access until all required setup steps are complete.
• Returning users should resume onboarding at the next incomplete required step.
• Returning users should only receive workflow access after all required onboarding and setup requirements are complete.

​

How It Should Not Work

• It should not create an authenticated company account before email verification is completed.
• It should not create a second account for an email address that is already registered.
• It should not reveal whether a failed login was caused by an unknown email address or an incorrect password.
• It should not allow an inactive creditor user to enter the portal.
• It should not allow onboarding progression without verified email status.
• It should not allow company profile completion when Middesk verification fails or returns an unverified TIN result.
• It should not activate membership without successful payment processing.
• It should not allow file uploads or account workflow processing before all required setup steps are complete.
• It should not allow operational workflows before merchant processing, pay terms, import headers, Terms & Conditions, and About Us defaults are configured.
• It should not allow users to access another creditor company’s data after authentication.