How does online payment work in SDL Connect?

Payment Processor

Connect uses MuniciPAY (Autoagent) as its payment processor.

Key Rule: Payment Is Configured Per Form, Not Globally

There's no global payment setup. Each form needs its own Site ID, URL Key, and Product IDs configured in the form's Payment block.

How It Works for Applicants

1. The applicant reaches the Payment block during submission.
2. They're directed to MuniciPAY to complete payment.
3. Supported methods: credit card, eCheck, Apple Pay, Google Pay.
4. A receipt is emailed after payment.

Counter payments (in-person) are recorded on the General tab of the submission. A USB point-of-sale terminal connects via the "Swipe Credit Card" button on the Fees tab.

Fee Configuration Requirements

• Most critical rule: a fee won't appear on a permit at all if the dataID is missing from the top trigger section of the fee — even if it's present in the calculation section below.
• Fees don't trigger if the field value is 0 — it requires a value greater than 0.
• "Additional fee" types won't apply unless other fees have already calculated.
• Fees are locked once a permit reaches "Issued" status — no additions or modifications after that point.

Certificates with Fees

Certificates with fees must be generated from the Closure tab, not the Attachments tab — generating from Attachments skips the fee entirely.