Skip to content
English - United States
  • There are no suggestions because the search field is empty.

Why are alarm permit payments not being processed through Connect?

There isn't a distinct, standalone "alarm permit" form or process in Connect — if you're running into this, it's really a general "why isn't this permit's payment processing?" question. Check the same things you'd check for any Connect payment issue:

  1. MuniciPAY isn't configured for that specific form. Payment is set up per form, not globally — each form needs its own Site ID, URL Key, and Product IDs. If they're missing, payment won't process.
  2. The form is still in API Testing mode rather than production — confirm this before go-live.
  3. 404 on the payment page — usually a misconfigured SDL Form Product ID or VAR setting, or the form ID (not form name) not being used correctly in the payment URL.
  4. dataID missing from the fee's trigger section — if the fee isn't calculating at all, confirm the triggering dataID is entered in the top section of the fee configuration.

If none of these explain it, get the specific error message and where it occurs, and escalate to SDL support with those details.