PayHOA Payment Processor Setup: Connect Payments & Verify Webhooks

Connect the payment processor inside PayHOA’s Payments or Integrations area, complete the processor’s identity and bank verification, then confirm PayHOA is sending webhooks to the correct URL and that PayHOA is receiving successful 200 responses. Finally, run a real test payment and confirm the event shows as “delivered” in the processor’s webhook logs and as “paid” in PayHOA.

 

Connect a payment processor in PayHOA

 

• Go to: PayHOA Admin area → Settings (or Company/Association Settings) → Payments or Integrations.
• Select the available processor option and click Connect or Enable online payments.
• Complete the processor onboarding:
  • Business details: legal HOA/management company name, EIN, address.
  • Identity verification: authorized signer info. If this fails, double-check name format, DOB, address, and that no VPN is used.
  • Bank account: routing and account number for deposits. Some processors require micro-deposit confirmation.
• Back in PayHOA, confirm payment methods are enabled:
  • ACH/eCheck (bank transfer) and or Card (credit/debit).
  • Fees: confirm who pays fees (homeowner vs HOA) and whether convenience fees are allowed in the state.

 

Verify webhook settings (what they are and how to confirm)

 

• Webhook meaning: an automatic message the processor sends to PayHOA when something happens (payment succeeded, failed, refunded). If webhooks are wrong, payments may deposit but not update ledgers.
• Find webhook area: in the processor dashboard → Developers or Webhooks.
• Confirm the Webhook URL matches exactly what PayHOA provides (no extra spaces, correct https, correct environment).
• Confirm the webhook is subscribed to the right events:
  • Payment succeeded
  • Payment failed
  • Refund issued
  • Dispute or chargeback (if cards are enabled)
• Confirm the signing secret (shared key used to prove the webhook is real) is entered in PayHOA if PayHOA asks for it. If the secret is rotated, PayHOA must be updated.
• Send a test webhook from the processor and check the delivery result:
  • Success looks like: HTTP 200 response.
  • Common failures: 400 (bad signature or missing fields), 401 (wrong secret), 404 (wrong URL), 500 (PayHOA side issue).

 

Final validation (even if everything is already set up)

 

• Run a real $1 test (or smallest allowed) from a homeowner test account.
• Confirm in processor dashboard the payment is succeeded and the webhook shows delivered.
• Confirm in PayHOA the payment posts to the correct owner ledger, correct assessment, and correct deposit batch.
• If deposits are correct but PayHOA does not update, the issue is almost always webhook URL, secret, or blocked delivery.

 

When to contact support

 

• Processor support: identity verification stuck, bank verification failing, webhook deliveries not reaching PayHOA.
• PayHOA support: webhook shows 200 delivered but PayHOA does not mark invoices paid, ledger mapping is wrong, or events are not recognized.