Skip to main content
Going live means more than creating a production instance — it includes onboarding Data Recipients and, if applicable, meeting regulatory obligations. This comprehensive checklist covers technical readiness, operational preparedness, and regulatory compliance to ensure a smooth production deployment.

​
Understanding Responsibilities

Before diving into the checklist, it’s important to understand what Fiskil manages versus your responsibilities.
  • Secure, standards-compliant data disclosure
  • Consent management flows and optional consumer dashboard
  • Authentication and authorization services (OIDC, scopes, tokens)
  • Operational logging, audit trails, and retention
See our FAQ section for detailed information on compliance responsibilities.

​
Pre-Go Live Checklist

Complete these steps before onboarding Data Recipients to ensure your Data Provider is production-ready.
1

Technical Preconditions

Ensure your Resource Server meets all technical requirements:
  • Resource Server implemented and tested in staging
  • Authentication validated: JWT signatures checked, aud/iss claims enforced
  • Error model and pagination consistent with Fiskil standards
2

Production Instance Setup

Configure your production environment:
  • Production instance created in Console
  • Custom domain configured and DNS propagated
  • Branding and policies reviewed in Console
3

End-to-End Testing

Validate all systems work together correctly:
  • End-to-end consent flows validated in staging (consent creation, token issuance, API calls)
  • Evidence captured (logs, screenshots) for audit purposes
  • Request Logs reviewed in Console; Log Drains configured if using external SIEM
  • Metrics reviewed for latency, error rates, and throughput under test load
4

Operational Readiness

Ensure your team is prepared to support production operations:
  • Monitoring and alerting configured on Logs and Metrics (if forwarding to external tools)
  • Teams trained on accessing Logs and Metrics in the Console
  • Procedures established for responding to Data Recipient support requests
  • Escalation processes defined for internal issues or Fiskil support
5

Compliance & Regulatory Validation

Complete required compliance steps for your market:
  • Conformance tests completed for your compliance profile (e.g., CDR, FDX)
  • Redirect URIs registered and verified for both staging and production
  • Regulatory approval or certification completed (if required)
If you are not going live with a compliance profile but require regulatory onboarding, contact the Fiskil team for support with validation and registry/integrator requirements.

​
Go Live Process

Once you’ve completed the pre-go live checklist, follow these steps to onboard Data Recipients and monitor your production deployment.
1

Onboard Data Recipients

Begin integrating with trusted recipients:
  • Add trusted Data Recipients in the Console (direct integrations or registry-approved apps)
  • Validate consent flows and data exchange with each recipient
  • Start with a small number of recipients to monitor system behavior
Begin with trusted Data Recipients you’ve worked with during testing to ensure smooth initial deployments.
2

Monitor Initial Traffic

Closely observe your first production data exchanges:
  • Monitor first production traffic in Logs and Metrics to confirm stable operation
  • Watch for any unexpected error patterns or performance issues
  • Validate that all consent flows work as expected in production
  • First production traffic successfully processed with stable metrics
3

Scale Recipient Onboarding

Gradually expand your recipient network:
  • Continue onboarding additional Data Recipients as confidence grows
  • Maintain monitoring and support processes as volume increases
  • Document any lessons learned for future onboardings
If your market requires specific regulatory or registry onboarding:
  • Work with Fiskil to complete regulator or registry onboarding (e.g., ACCC in Australia)
  • Provide evidence of conformance testing where required
  • Coordinate timelines with your compliance team and Fiskil support
  • Validate your Resource Server against relevant API standards (e.g., CDR, FDX)
  • Capture test evidence (logs, metrics, error handling) for regulatory review
Common issues and solutions during go live:
  • DNS propagation delays: Allow 24-48 hours for DNS changes to fully propagate
  • Certificate validation: Ensure TLS certificates are properly configured and not expired
  • Recipient integration failures: Review logs for authentication or scope issues
  • Performance concerns: Monitor metrics and adjust instance resources if needed
Your instance is technically live once created in production. The final milestone is successfully onboarding Data Recipients and confirming stable traffic patterns.