Test your implementation before go-live

Before promoting your instance to Production, validate it in staging using the tools Fiskil provides.

Functional testing

• Postman collection — run an end-to-end flow with Fiskil's official Postman collection: create consents, retrieve tokens, and inspect your Resource Server responses.
• Mock data recipient — simulate the recipient side of a data-sharing flow: create consents, browse consumer data, and test revocation, without involving a real accredited recipient.
• Request logs — every API call is recorded, so you can validate payloads, verify that responses respect granted consent scopes, and debug errors.
• Metrics — track throughput, latency, and error rates to establish a performance baseline before go-live.
• Product Portal API test — verify your product reference endpoints directly from the Console. See Testing your Products API.

Compliance tools

If your instance uses a regulated compliance profile — in Australia (CDR), for example — Fiskil's compliance tools help validate that required endpoints are implemented correctly, responses match the mandated schemas, consent flows meet regulatory expectations, and reporting obligations can be demonstrated. If your instance doesn't use a compliance profile, functional testing with Postman and request logs is sufficient.

Regulatory reporting

In Australia (CDR), data holders report to the regulator periodically. Most of the metrics you need — consumer requests, product requests, and refusals by error code — are available in the Console's Analytics tab. See Regulatory reporting.

When to involve support

Contact support when you're ready to run compliance validation — the team will help identify your framework, the required tests, and coordinate any certification effort — or if staging results don't match what you expect.