Prepare your records and staff for launch
Plan the work between your agency and GovPayPlan before live collection begins. Identify source balances, payment references, staff responsibilities, and the reports finance needs. CSV exchange is available on every plan; Enterprise adds API, webhook, SFTP, and single sign-on options.
Implementation sequence
Use this sequence to coordinate agency staff and the GovPayPlan team. Confirm support for a named third-party system and the required exchange before selecting an integration.
Evaluate with test data
Request a test account, invite agency staff, and run simulated payments. No card or bank information is required for the test account.
Confirm records and exchange method
Identify the source case or billing system, record references, and reporting needs. Choose staff-managed CSV exchange or confirm the Enterprise integration required for your workflow.
Register, configure, and train
Merchant registration verifies the agency and payout bank account. Portal configuration, staff permissions, and live training proceed in parallel.
Launch and reconcile
Publish the portal link on the agency website and notices. Finance staff review payment records, exports, and the settlement statement for the first payout under the selected plan.
Agency readiness checklist
Check the items your team has reviewed or download a working copy. The checklist is planning guidance, not an API specification or a commitment to a launch date. Checked items are not saved when you leave or reload this page.
Source systems and records
Prepare the information needed to discuss data exchange with GovPayPlan.
Exchange method and access
Select an approach that fits the plan and the agency’s workflow.
Configuration and test review
Review the intended workflow in the test account before publishing it.
Registration, launch, and payout review
Coordinate registration, configuration, and training, then review the live reporting cycle.
Prepare an integration review
Send the information below to [email protected]. Our team can confirm the supported approach for your agency’s systems.
- Agency name
- Current case management, billing, or finance system and version
- eCourtDate products currently used, if any
- Record reference used for balances and payments
- Data to import and reports to export
- Preferred approach: staff-managed CSV, REST API, webhooks, SFTP, or integration to confirm
- Identity provider, if Enterprise single sign-on is required
- Questions to resolve before configuration
Review the draft in your email application before sending. Do not send passwords, access tokens, payment credentials, or personal payment records.
Implementation review questions
Name an implementation lead and operations, finance, IT, and purchasing contacts. Operations validates collections and training; finance approves account structure and reconciliation; IT confirms access and exchange; purchasing coordinates agreement review. Registration and bank verification also need authorized contacts. Establish owners before scheduling launch.
Use fictional or sanitized records with the formats and edge cases your staff need. Simulated payments require no card or bank information. Do not upload live credentials, sensitive case details, or personal information without agency authorization and an agreed handling process. A representative sample does not need to identify real people.
Validate payment references, balances, receipts, permissions, installments, and required imports or integrations. Include an exception and have finance inspect export fields and the expected settlement workflow. Assign owners to unresolved issues. Complete registration, verified payout details, training, and agency approval before publishing live links.
Inventory links, notices, QR codes, recurring arrangements, and posting jobs. Agree when each changes, which system owns final balances, and who checks new records. Confirm whether existing enrollments or saved methods can move; do not assume automatic transfer. Test the cutover with operations and finance before setting the public launch date.
Confirm bank details, the plan schedule, and available-funds threshold. Match the deposit to its statement, inspect transactions and adjustments, and verify posting exports against the source system. Reconcile cash and checks through the separate agency deposit process. Review Distributions control totals separately from settlement.
Review the agency implementation
Request a test account and identify the staff responsible for source records, configuration, and reconciliation. Confirm technical requirements with our team before go-live.