Conformator

Prove that open banking APIs work as the rules say.

Conformator gives regulators and the banks, payment service providers and third-party providers they supervise one place to test APIs against the agreed standard, review the results and issue signed conformance reports, on your own infrastructure, built on the Open Bank Project.

A conformance report, as anyone can check it

CR-2026-7K3QX9MD

Signature valid

Example Bank: Account information API

Passed suite AIS-PROVIDER, version 2 · Issued 14 November 2026 · Valid until 13 November 2027

TestWhat it checksOutcome
AIS-CONSENT-001A consent can be created and read backPass
AIS-ACC-003Accounts are listed with a valid consentPass
AIS-ACC-007An expired consent is refusedPass
SEC-FAPI-012Access tokens are bound to the client's certificatePass
ORG-SEC-002A named person is responsible for securityPass
AIS-TXN-010Transactions older than 90 daysWaived to March 2027

Signed with Ed25519 · key 2026-01 · the signature can be checked without this site

From the rules to a signed report

  1. DefineRecord the rules as requirements, and the tests that check each one, grouped into versioned suites.
  2. AdmitRegister each participant and give it a space of its own, kept apart from everyone else's.
  3. TestParticipants run the suites against their own sandbox systems, whenever they like, as often as they need.
  4. ReviewParticipants submit their results with evidence; reviewers assess and an independent approver decides.
  5. ReportApproval issues a signed conformance report that anyone can check by its reference.

For everyone in the ecosystem

The regulator

  • Turn the rules into tests anyone can read
  • Admit participants and follow their progress
  • Review evidence, waivers and appeals
  • Issue, supersede and withdraw reports

Participants

  • Test sandbox systems at any time
  • See every request and response, and why a test failed
  • Fix, run again and submit when ready
  • Show customers and partners a report they can check

Everyone else

  • Read the public test catalogue
  • Check any report by its reference
  • Check a report's signature with the published key
  • See which version of the rules a system met

A closer look

Any standard

Your rules, not ours

Start a suite from an OBP API version, from an OpenAPI file, or from the address of one. Berlin Group, UK Open Banking, the Open Bank Project's own APIs or your national standard all work the same way. Conformator suggests the codes, names and test IDs, so a first suite takes minutes.

  • Berlin Group NextGenPSD2
  • UK Open Banking
  • Open Bank Project
  • FAPI security profile
  • Your national standard
  • Any OpenAPI document

Tests as steps

Tests that read like the rules

Each test is a short list of steps: send a request, check the answer, keep a value such as a consent's id for the next call. Answers are checked against the suite's OpenAPI schema too. Opey, the AI assistant, helps staff write and explain tests.

AIS-ACC-003  Accounts are listed with a valid consent

1  POST /consents
   expect 201
   keep consentId from the body

2  GET /accounts
   with Consent-ID: {{consentId}}
   expect 200, and at least one account
   check the answer against the OpenAPI schema

Real conditions

Tested as a real partner would

The runner calls each participant's system over mutual TLS, with its own certificate and as its own client, just as a third-party provider or a bank would. Security checks of authorisation servers use the OpenID Foundation's conformance suite. Every result keeps the requests and responses, with secrets hidden, so a failure explains itself.

  • PassEvery step did what the test expects
  • FailThe system answered, but not as it should, and the result says how
  • BlockedThe test could not go on, and the result says whose side stopped it
  • ReviewedEvidence and organisational tests, decided by a person

Review

Human judgement, on the record

Some rules need a person to decide: a security policy, an audit record, a named officer. Reviewers assess the evidence, participants can ask for a time-limited waiver or appeal a result, and an approver who did not assess the submission makes the final decision. Every step is kept with who, when and why.

  • Separation of dutiesNobody reviews and approves the same submission
  • WaiversWith an end date, shown wherever the outcome is
  • AppealsThe only way an automated result can change
  • Audit trailDecisions are added, never overwritten

Reports

Reports anyone can trust

Each report is digitally signed and has a short reference. Customers, partners and other regulators can check it on the public site, or check its signature with the published key without visiting the site at all. Reports expire, and can be superseded by a newer one or withdrawn.

  • SignedEd25519 signatures over the canonical report
  • PublicAnyone can check a report by its reference
  • VersionedA report names the exact suite version it passed
  • ExportableResults and dashboards download as CSV and JSON

Getting started

Easy to try

A Getting started page shows administrators, the regulator's staff and participants their steps, one at a time, with their progress so far. An example suite and a fake bank come with it, so a first run has something to pass within minutes.

  1. Connect Conformator to OBP-APIDone once, by an administrator.
  2. Add the example suiteRequirements, tests and a fake bank to test.
  3. Run itWatch each test pass, and see why when one does not.

Built on the Open Bank Project

Conformator has no database of its own. Every record lives in OBP-API, so it inherits a platform that banks and regulators already trust.

What Conformator records

Every record is a dynamic entity in OBP-API, so you can read it through the same APIs, Roles and tools as the rest of your sandbox. The catalogue, the participant register and the reports live in one central space. Everything about a participant's testing lives in that participant's own space.

The central space

The test catalogue

  • conformator_requirementOne clause of the rules, which tests trace back to
  • conformator_suiteA versioned set of tests for one kind of system and one family of APIs
  • conformator_testOne test: what it checks, the requirements it covers and what counts as a pass

Participants and reports

  • conformator_participantAn organisation taking part: a bank, payment service provider, fintech or third-party provider
  • conformator_participant_decisionA step in a participant's lifecycle, from admitted to graduated
  • conformator_reportAn issued conformance report, public by its reference
  • conformator_report_eventA report superseded or withdrawn

Each participant's space

Recorded by the participant

  • conformator_systemA sandbox system to be tested, with no secrets
  • conformator_pairingTwo participants agreeing to be tested together, for interoperability
  • conformator_runOne run of a suite version against a system
  • conformator_resultThe outcome of one test in one run, never changed
  • conformator_scheduleRegular runs of a suite, for regression checks
  • conformator_submissionA system put forward for the regulator's review
  • conformator_evidenceEvidence for a test a person decides, with files attached
  • conformator_waiver_requestA request to waive one test
  • conformator_appealA challenge to a result or a decision

Recorded by the regulator

  • conformator_review_assignmentA reviewer assigned to a submission
  • conformator_assessmentA reviewer's verdict on evidence, or on a disputed result
  • conformator_waiver_decisionThe decision on a waiver, with its end date
  • conformator_appeal_decisionThe outcome of an appeal
  • conformator_approvalThe final decision on a submission, by an independent approver

Why Conformator

Conformator is Latin for "one who shapes", from conformare, "to shape alike". The regulator sets the shape, and Conformator checks that each participant's API fits it.

Talk to us

Setting up an open banking sandbox, or a conformance programme for the firms you supervise? Tell us about it, and we will show you Conformator testing against your own standard.

contact@tesobe.com