Help Center
    Getting started

    Set up and manage your HOA Guardrail subscription

    Choose the association's plan and billing interval, then subscribe by card or by entering the HOA checking account's routing and account numbers securely in Stripe Checkout.

    Step by step

    Use this sequence as a practical board checklist.

    1. 1

      Sign in as an authorized HOA administrator or declarant for the association that will hold the subscription. A homeowner-only account cannot start or change the HOA's software subscription.

    2. 2

      Open the HOA dashboard, then go to HOA Settings and select Billing. Trial and subscription reminders may also link directly to the same Billing tab.

    3. 3

      Confirm the HOA's lot count and recommended plan, then choose Monthly or Annual billing. Review the displayed price and billing interval before continuing.

    4. 4

      Select Subscribe Now or Start Subscription. HOA Guardrail opens Stripe's secure hosted checkout for the association and selected plan.

    5. 5

      Choose Card to use an HOA payment card, or choose US bank account to pay by ACH. For manual bank setup, enter the routing number, account number, account-holder details, and authorization requested by Stripe. An online-banking username or password is not required.

    6. 6

      Complete any verification Stripe requests. Depending on the bank, Stripe may verify the account automatically or provide a manual verification path. Keep the Stripe window open until it confirms that the setup was submitted.

    7. 7

      Return to HOA Guardrail and review the subscription status. Card confirmation is usually prompt; an ACH bank payment can remain processing for several business days. Do not start a second subscription while the first bank payment is pending.

    8. 8

      After activation, return to HOA Settings → Billing to review renewal information and invoices. Use Manage Billing for supported payment-method, plan, or cancellation actions in Stripe's billing portal.

    What to know

    These distinctions prevent the most common workflow mistakes.

    Card

    An HOA credit or debit card entered in Stripe Checkout. HOA Guardrail does not receive or store the full card number.

    US bank account

    ACH payment using the association checking account's routing and account numbers. This supports boards that do not have an HOA card or online-banking credentials available.

    Bank verification

    Stripe's confirmation that the entered bank account can be used. The available automatic or manual path depends on Stripe and the bank.

    Processing

    A normal temporary state for ACH. Access and billing status update after Stripe reports the final payment outcome; submission alone is not proof that funds settled.

    Billing portal

    Stripe's hosted page for an existing subscription. It is different from the initial subscription checkout and from HOA Guardrail's member-payment tools.

    Before you finish

    Pause for one final evidence and access review.

    The subscription belongs to the intended HOA and was started by an authorized association administrator.

    The lot count, plan, price, and monthly or annual interval were reviewed before checkout.

    The payment method belongs to the association or is otherwise authorized for this subscription.

    Routing and account numbers were entered only in Stripe's hosted checkout, never in an HOA Guardrail message or support request.

    Any ACH verification request was completed and a processing payment was allowed to finish before another checkout was attempted.

    The Billing page shows the expected subscription status, renewal information, and invoice history after confirmation.

    Troubleshooting

    Start with the visible status and preserve the underlying history.

    Still need help?

    Signed-in administrators can open Help & Support, or email [email protected]. Include the HOA name, selected plan and interval, approximate checkout time, whether Card or US bank account was selected, the visible status, and any non-sensitive error text. Never include full card or bank numbers, bank-login credentials, MFA codes, verification codes, microdeposit amounts, or provider tokens.