A Point & Pay receipt does not establish permit issuance

Separate the transaction from the permit decision

A permit workflow may request payment at application, completeness review, plan review, inspection, issuance, renewal, amendment, appeal, or another locally defined stage. The payment event should identify the agency, record type, application or permit identifier, payer, fee schedule and version, line items, amount, channel, processor reference, time, and transaction status. It should not change a regulatory status unless the authorized workflow permits that exact transition.

The permit record needs its own decision chain: jurisdiction, applicable code or rule, application version, completeness, reviews, conditions, inspections, findings, approvals, authorized official, issue date, effective status, and later changes. Payment can be a prerequisite within that chain. It is not evidence that every prerequisite was satisfied or that an authorized official issued the permit.

Reconcile fees without hiding exceptions

A successful checkout is only one transaction state. Agencies also need to account for pending authorization, settlement, processor rejection, duplicate charge, partial payment, convenience fee, cash or check, waiver, refund, chargeback, void, transfer between records, and corrected fee calculation. Applicant-facing status should distinguish those events plainly and avoid saying paid when the agency ledger or processor has not reached the defined state.

Reconciliation should connect each processor transaction to the agency receivable, permit record, accounting entry, deposit, adjustment, and exception. Unmatched items need an owner and disposition rather than a forced match. When a fee changes after plan review or an application is withdrawn, the record should preserve the original assessment, revised authority, communication, refund or balance, and final accounting result.

Test channel and workflow failures together

Point & Pay lists several payment channels. A buyer test should follow one representative permit through online and assisted payment, then introduce difficult cases: the wrong record number, duplicate browser submission, processor timeout, approved charge with failed portal callback, partial fee, payment after a deadline, mobile receipt, refund, chargeback, and a permit later denied. The two systems should reconcile without granting a status the permit authority did not approve.

Roles matter during exception handling. Applicants, cashiers, reviewers, inspectors, supervisors, finance staff, payment administrators, and system support may see or change different fields. Test who can assess, waive, collect, refund, transfer, reconcile, reopen, issue, suspend, and correct a record, and retain the reason and prior value for each authorized change.

Keep provider evidence within payment scope

Point & Pay's official page establishes public positioning for government payment services and names permits and licensing as use cases. It does not establish an agency's configured channels, processor settlement, fee authority, accounting treatment, accessibility, security, legal compliance, permit decision, or service outcome. Published customer and scale statements remain provider claims unless independently verified for the buyer's use.

Civic Permit Review reviewed the registered source on August 12, 2026 and did not operate a government implementation or inspect a transaction. Buyers should verify contracted scope, fee configuration, interfaces, accessibility, security, settlement timing, refunds, reconciliation, audit history, retention, and applicant communication with representative records and accountable permitting, finance, legal, accessibility, and technology owners.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Civic Permit Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.