Implementation
Days or weeks. Not months, and not years.
Timelines are a proxy for how much work a vendor has already done. With 100+ solution integrations delivered and 40+ third-party systems connected in production, most implementations are a configuration exercise.
The four phases
What actually happens, in order
- 01
Discuss
Our payment experts gather your detailed requirements — departments, payment types, business rules, fee policy, reporting needs and the back-office systems in play.
- Requirements session with the departments involved
- Review of current channels, volumes and pain points
- Fee policy and disclosure decisions
- Reconciliation and deposit requirements captured up front
- 02
Integrate
We create the connections from our systems to yours. With 100+ integrations already in production, this is usually configuration rather than construction.
- Integration built and tested by the Government Window team
- Standalone option available where no integration exists
- Balance lookup and payment posting validated end to end
- Minimal effort required from agency IT
- 03
Implement
We set up and test your system, configure your branding and business rules, and train your staff before you go live.
- Branded payment site configured to match your jurisdiction
- Business rules, fee schedules and messages configured
- End-to-end testing across every channel you're launching
- Staff training on payments, reporting, voids, refunds and reconciliation
- 04
Support
Our multilingual, in-house call center is available for your residents and your staff, and we keep optimizing after go-live.
- Resident and staff support handled by our in-house team
- Phone and chat Mon–Fri 8am–5pm ET, email 24/7/365
- Online help available 24/7 in your payment dashboard
- Ongoing adoption guidance and configuration changes as your needs change
Who does what
What we need from you, and what we handle
The most common reason payment projects stall is that the agency underestimated its own workload.
Your team
approximately a handful of hours across the project.
- One requirements session with the departments going live
- A named point of contact for the back-office system
- Review and sign-off on the configured payment site
- Participation in end-to-end testing
- Attendance at staff training
Government Window
everything else, at no cost to the agency.
- Business rule, fee schedule and message configuration
- Branded payment site build
- Integration development and testing
- Reporting and reconciliation field configuration
- Test plan execution across every channel
- Staff training delivery
- Go-live sequencing and post-launch monitoring
Sequencing
Start with one department. Add the rest on the same platform.
Jurisdictions that try to migrate every department on one date create a single point of failure and a very long testing window. The pattern that works is sequential.
A typical sequence
- One department goes live — usually the one with the highest transaction volume or the loudest pain, since that produces the clearest signal.
- Finance validates a full cycle of reconciliation and deposits before anything else moves.
- The next department is added to the same platform, inheriting the configuration decisions already validated.
- Within a year, the jurisdiction typically has one portal for residents, one dashboard for staff and one deposit for finance.
What to decide before the requirements session
- Which departments are in scope for phase one
- Your fee policy and how it will be disclosed
- Which identifiers residents will search by
- Which fields your reconciliation actually matches against
- Who has authority to process voids and refunds
- Your settlement and deposit schedule
Bring those six answers and the requirements session takes an hour instead of three.
Questions