Give residents practical ways to pay
Online portals, payment links, counter terminals, kiosks, ACH and mobile acceptance for public services.
Public Payments & Government Technology
Selective Pay helps cities, counties, utilities, courts and public agencies connect online, counter, kiosk, mobile, recurring and ACH payment workflows around the systems, departments and reporting requirements already in place.
Online portals, payment links, counter terminals, kiosks, ACH and mobile acceptance for public services.
Coordinate departments, locations, merchant accounts, service types, reference numbers and settlement destinations.
Improve transaction visibility, funding reconciliation, refund controls and reporting across agencies and revenue categories.
Why Public Payments Are Different
Government payments can cross departments, funds, locations, software systems and service channels. A strong payment structure improves resident convenience while preserving the controls, references and settlement detail the agency needs.
Utilities, permits, taxes, court costs, fines, parks, public records, licenses and facility payments may all require different data and settlement paths.
Service charges, convenience fees, refunds and reversals must align with applicable law, agency policy, card-brand rules and contractual requirements.
Each payment may need a department, fund, case, permit, account, citation or customer reference so finance teams can reconcile deposits accurately.
Build the Right Public Payment Mix
Selective Pay evaluates the full transaction path and then recommends the processor, gateway, devices, portal and reporting model that best support the agency.
Offer practical payment options without creating unnecessary friction or staff workload.
Support the controls needed to authorize, route, settle, report and reconcile public payments.
Public Payment Models We Support
We tailor the payment environment to the service type, department structure, transaction volume, reference data, resident experience and technology already in place.
Taxes, permits, licenses, public records, fees, departments, locations and centralized payment reporting.
Recurring billing, account numbers, online portals, ACH, card-on-file, kiosks and payment-reminder workflows.
Citations, court costs, probation fees, bonds, public-safety payments and case-level reference requirements.
Facility fees, bonds, deposits, electronic monitoring and payment streams that may sit outside inmate communications platforms.
Registrations, rentals, memberships, events, concessions, mobile acceptance and seasonal payment activity.
Separate funding, shared technology, location controls, consolidated visibility and coordinated implementation.
A Practical Public Payment Review
We begin with the agency's current systems, departments and policies, identify the gaps and design a payment plan around operational continuity and accountable reporting.
Document which departments collect payments, how residents pay, which references are required and how transactions reach finance.
Evaluate statements, portals, gateways, terminals, ACH, fee programs, refunds, contracts, procurement requirements and system restrictions.
Define merchant accounts, departments, permissions, payment methods, reference fields, settlement destinations, reporting and migration sequence.
Coordinate configuration, portal and device testing, staff training, public communication and ongoing support after launch.
What We Review
Online, counter, phone, kiosk, mobile, recurring, ACH, payment links and the services collected through each channel.
Billing, court, utility, permitting, ERP, accounting, portal, gateway and virtual-terminal systems that must support the transaction.
Monthly volume, average ticket, card-present versus card-not-present activity, debit, commercial cards, ACH, refunds and seasonality.
Convenience or service charges, agency policy, resident disclosures, card-brand requirements, applicable law and contractual restrictions.
Departments, funds, merchant accounts, deposits, references, funding schedules, adjustments and accounting handoff.
Contracts, RFP requirements, security review, accessibility, system ownership, training, timelines and change-management needs.
Compliance note: Government fee programs, disclosures and payment policies can depend on applicable law, agency authority, card-brand rules and contractual requirements. Selective Pay helps structure the payment environment but does not provide legal advice.
Frequently Asked Questions
Often, yes. We first determine which gateways, processors, devices, hosted payment options and data fields the current system supports. Compatibility is confirmed before any recommendation.
Potentially. The design may use separate merchant accounts or settlement destinations under one coordinated processing and reporting relationship, depending on agency policy and accounting requirements.
That depends on applicable law, agency authority, payment channel, card type, network rules, processor capabilities and required disclosures. We review the proposed program and coordinate with the acquiring and legal stakeholders before implementation.
Yes, when the gateway or portal supports the required ACH workflow. Authorization, account validation, returns, recurring permissions and reconciliation should be designed before launch.
Yes, depending on the merchant-account and system architecture. We review separate settlement, shared reporting, department references, funding destinations and accounting needs.
Start with three recent processing statements, department and payment-type lists, current processor and gateway, agency systems, transaction channels, fee policies, contracts and the largest reconciliation or service issue.
Make Public Payments Work Better
Selective Pay will review your statements, departments, payment channels, systems, fee policies, settlement structure and reporting before recommending the next step.