1
Onboarding and Implementation Phases
Every PayNimble implementation moves through eight defined phases. Click any phase below to see responsibilities and the phase deliverable.
Phase 1: Discovery & Solutioning
Understanding your business before anything else
1–3
Days
PayNimble Drives
Conduct structured discovery sessions with financial and technical stakeholders
Document current payment flows, channels, and reconciliation process
Map your technology stack: ERP, billing system, CRM
Identify volume patterns, seasonal peaks, and key pain points
Deliver a written Discovery Summary with findings and recommendations
Client Provides
Access to key company personnel and project stakeholders
Payment metrics and technical data sharing
Target production date
Concurrence with project objectives and recommended technology implementation
Access to technical specifications from current systems (if applicable)
Phase Deliverable
Written Discovery Summary documenting payment environment and recommended solution configuration — signed off by both parties before Phase 2 begins.
Phase 2: Scope Concurrence & Contracting
Defining exactly what we're building and formalizing the agreement
2–5
Days
PayNimble Drives
Produce a formal Project Scope Document with deliverables and timelines
Define the full solution configuration: modules, channels, features
Provide contract package for review and execution
Client Provides
Review and approval of Project Scope Document
IT/technical resource availability confirmation for integration work (if applicable)
Executed agreements via DocuSign
Phase Deliverable
Project Scope Document with a mutually agreed timeline, defined deliverables, named project owners on both sides, and a confirmed go-live target date.
Phase 3: Configuration
Building your environment to specification
3–10
Days
PayNimble Drives
Configure the payment technology to your billing and payment specifications
Set up Merchant ID(s) and payment acceptance credentials
Configure payment software routing, fraud rules, and security settings
Client Provides
Brand assets (if applicable): logo files, approved colors, payer-facing language
Approval sign-off on configuration before integration begins
Phase Deliverable
Fully configured sandbox/test environment delivered with your branding, fee programs, and payment flows as specified. Client sign-off required before Phase 4.
Phase 4: Integration
Connecting your systems to the payment infrastructure
5–20
Days
PayNimble Drives
Manage end-to-end integration between payment tech and your ERP or billing system
Provide API documentation, webhook specifications, and technical guidance where applicable
Deploy technical resources including AI-assisted development where applicable
Validate data flows, transaction routing, and reconciliation feeds
Weekly status updates with open issue log and resolution timeline
Client Provides
Test environment access for your internal systems
Prompt review and sign-off on integration milestones to avoid timeline delays
Escalation path if issues arise
Phase Deliverable
Validated end-to-end data flow between applicable systems.
Phase 5: Testing
End-to-end validation before a single live transaction
3–7
Days
PayNimble Drives
Execute a full test plan across all channels: card, ACH, IVR, IntellAgent, portal, mobile
Test all transaction types: authorization, capture, refund, void, chargeback workflow
Validate fee program calculations for accuracy and regulatory compliance if applicable
Test reconciliation feeds, reporting outputs, and settlement data
Conduct fraud rule and velocity threshold validation if applicable
Client Provides
Participate in user acceptance testing (UAT) with AR and IT teams
Validate reconciliation outputs against your internal expected formats
Prompt issue reporting during the UAT window
Phase Deliverable
Test and confirm readiness for all channels, transaction types, and reporting outputs.
Phase 6: Training
Making sure every user is confident before day one
1–3
Days
PayNimble Drives
Conduct role-based training sessions: AR staff, administrative users, management reporting users
Train on exception handling: declined payments, ACH returns, chargeback workflow
Client Provides
Availability of all users who will operate the system on a recurring basis
Designation of an internal super-user who will own day-to-day platform administration
Sign-off that training is complete and all users are ready for go-live
Phase Deliverable
All operational staff trained and signed off. Internal super-user designated. Go-live authorization.
Phase 7: Go-Live
First live transactions — PayNimble is standing by
Day 1
+ 72-hr watch
PayNimble Drives
On-call availability on go-live day
Active monitoring of day-one transactions and authorization performance
Same-day resolution for any go-live issues — escalation as required
72-hour post-go-live monitoring with daily check-in
Client Provides
AR team lead and IT contact available on go-live day
Immediate reporting of any anomalies via agreed escalation path
Phase Deliverable
Confirmed successful day-one processing with authorization rates, transaction volumes, and reconciliation outputs validated. 72-hour check-in and issue resolution as applicable.
Phase 8: Post-Live Support
Ongoing relationship — the service that sets us apart
Ongoing
Permanent
PayNimble Drives
PayNimble principals serve as primary account managers
Business reviews scheduled on frequency of your choosing
Proactive monitoring and notification of processing anomalies
Access to new technology capabilities as they become available
Client Provides
Designated internal contact for ongoing account management
Participation in business reviews
Prompt communication of any business changes affecting payment processing needs
Phase Deliverable
Supporting your ongoing needs with expertise and dedicated care is our long-term commitment.
| Deployment Tier | Example Deployments | Typical Timeline |
|---|---|---|
| Simple | Standalone card present, PayNimble Gateway Virtual Terminal, certified software (VAR), Tap-2-Pay, Pay by Phone | 1–3 Weeks |
| Mid-Complexity | CAMPPS/PayNimble Gateway hosted checkout eComm, drop-in UI, IntellAgent widget, pre-existing ERP & shopping cart integrations, standard EBPP w/ billing file transmission | 3–6 Weeks |
| Enterprise / Multi-Factor | Custom API integration, multi-payment channel, advanced cardholder fee configuration (surcharging, service fee), custom reporting build, large database token migration, full-suite custom CAMPPS, multi-location semi-integrated card present | 6–12 Weeks |
2
Implementation Status Tracker
Use the tracker below to set the current implementation stage and share progress with your team.
Project Status Dashboard
Click any phase to see its detail and deliverables
0%
Select a phase above to see its detail and next steps
3
Responsibility Matrix
The following table provides a standard project ownership schedule.
| Area | PayNimble Owns | Client Owns |
|---|---|---|
| Project Management | Scope document, timeline management, issue log, status reporting, and milestone sign-off process | Named internal project owner; prompt approvals at each phase gate |
| Merchant Underwriting | KYC checklist delivery, application submission, approval management, Merchant ID activation | Complete application and financial documents; expedited execution of agreements |
| Platform Configuration | All CAMPPS and PayNimble Gateway/NMI configuration per agreed specification | Brand assets, fee structure approvals, and customer-facing language sign-off |
| System Integration | API/webhook specifications, integration project management, data flow validation | IT/developer resource, ERP/billing system access, deadline adherence |
| Testing and UAT | Full test plan execution, Test Completion Report, fraud and fee validation | UAT participation, reconciliation output validation |
| Staff Training | Role-based training sessions, quick-reference operations guide | Staff availability for all training sessions, super-user designation, training sign-off |
| Go-Live and Monitoring | On-call go-live day coverage, 72-hour monitoring window, Summary report | AR and IT leads available on go-live day; prompt reporting of any anomalies |
| Ongoing Account Management | Principal-level relationship management, ongoing business reviews | Designated ongoing contact; participation in business reviews |
4
Go-Live Readiness Checklist
Implementation advances to production when all line items are confirmed by both parties. Click items to track completion.
PayNimble Confirms
Merchant ID(s) fully approved and active
Platform configured and client-approved in sandbox
All integration data flows validated end-to-end
Test Completion confirmed by both parties
Fee programs validated for compliance
Fraud rules and velocity limits configured
Settlement and reporting feeds confirmed
All staff training complete with sign-off
PayNimble ongoing support model confirmed
Client Confirms
All required agreements executed
Configuration approved in sandbox environment
UAT completed and Test Acceptance confirmed
Reconciliation outputs validated against internal format
Internal user designation and training
AR team staff trained and signed off
IT/technical contact on-call for go-live day
Internal escalation path confirmed
Go-live date formally approved by leadership
5
Frequently Asked Questions
Common questions about how PayNimble implementations are scoped, run, and supported.
How long does implementation take?
It depends on the complexity of your deployment. Simple implementations — such as a virtual terminal, Tap-2-Pay, or certified software — typically take one to three weeks. Mid-complexity deployments involving a hosted eComm checkout, or off-the-shelf ERP integrations run three to six weeks. Enterprise or multi-factor implementations with custom API integration, advanced fee configurations, or full-suite CAMPPS or PayNimble Gateway deployments typically run somewhere in the six to twelve week timeline.
What do we need to have ready before implementation starts?
At the Discovery phase, we need access to your key financial and technical stakeholders, basic payment metrics and transaction data, your target production date, and access to technical specifications from your current systems if applicable. The resource allocation on your side comes during Integration, where your IT or developer resource with access to your ERP or billing system will be engaged.
Who manages the implementation process?
PayNimble manages every implementation directly. You will not be handed off to a generic support team. The same people who recommended your solution are the ones helping you install it.
What happens after go-live?
PayNimble provides proactive post-launch monitoring with daily check-ins. After that, we will remain your primary account managers on an ongoing basis — conducting business reviews at a frequency of your choosing, monitoring for processing anomalies, and providing access to new technology capabilities as they become available.
How do you handle system integrations with our ERP or billing platform?
We manage the end-to-end integration process, providing API documentation, webhook specifications, and technical guidance. We deploy technical resources — including AI-assisted development where applicable — for coding and integration work. Weekly status updates with an open issue log keep both sides aligned throughout.
What are we responsible for during implementation?
Your primary responsibilities are providing access to key personnel and systems, reviewing and approving deliverables at each phase gate promptly, and ensuring your IT resource is available during the integration sprint. A full responsibility matrix detailing PayNimble's ownership versus client ownership at each phase is available in the implementation guide.
Is there a formal contract and project scope before work begins?
Yes. Nothing proceeds to configuration until both parties have agreed upon a Project Scope Document that defines all deliverables, timelines, project owners on both sides, and a confirmed go-live target date.
How do you ensure the system is ready before go-live?
We execute a full test plan across all payment channels and transaction types — authorization, capture, refund, void, and chargeback workflow — plus validation of fee programs, reconciliation feeds, and fraud rules where applicable. No go-live authorization is issued until both parties confirm test completion.