Saved Successfully.

webcore certifi

NDC Certification Tool

NDC certification, from first call to sign-off. One place to run an NDC application against the airline's published use cases, every request and response captured as you go, checked against the rules for that step, and kept as the evidence behind the certification.

NDC certification, without the spreadsheet

Certification Tracking | Partner Onboarding | Evidence Packages

Most NDC certification programmes run on emailed XML, a shared spreadsheet and someone's memory of what "passed" meant three months ago. certifi replaces that with a single workspace: the airline publishes the programme, each partner organisation works through it against the live sandbox, and every message that proves a step is captured where the step lives. Nothing is certified on trust.

  • Levels
  • Categories
  • Use cases
  • Step requirements
  • Message capture
  • Rule validation
  • AI-assisted review
  • Capability matrix
  • Sign-off
webcore certifi NDC Certification Tool showing a certification level with its use cases and progress

Two audiences, one system

The airline runs the programme. The partner does the work.

certifi is deployed per airline and wears that airline's branding. The airline's team authors and publishes the programme, reviews submissions and signs them off. Partner organisations only ever see their own progress, their own evidence and their own feedback.

  • Airlines certifying agencies, aggregators and technology partners
  • Agencies and integrators working towards a carrier certification
  • Distribution teams onboarding a new partner in weeks, not quarters
  • Compliance teams who need the evidence, not an assurance
  • Support teams handling the questions certification generates

Inside the workspace

Everything the certification needs, in one place

A programme is four nested layers — level, category, use case, step. A use case passes only when every one of its steps passes, and a step passes only when the messages behind it do.

Know what is required

Published requirements per step

Each use case carries its requirements in full, so a partner is never guessing what "certified" means for a given message. Progress bars per level show exactly how far there is left to go.

Submit real evidence

Capture or upload

Messages are captured live as the partner works, or dropped in as request and response files per step. A step stays incomplete until both halves are present.

Fix it before submitting

Dry-run validation

A partner's own AI assistant can dry-run a request and response through the validators before anything is submitted, so a failed step costs a minute rather than a review cycle.

Get help in context

Docs where you are

A contextual help drawer carries the airline's own documentation next to the step being worked, maintained in the CMS rather than shipped in a release.

Author the programme

Levels, categories, use cases, steps

Build and edit the whole certification structure in the tool, with per-message-type step editors, and publish or hide any part of it while it is still being drafted.

Manage organisations

Partners and their members

Organisation manager, member administration and agent search, so the airline can see who is working on what and where each partner has stalled.

Review and sign off

Evidence attached

A partner submits a level for review; the reviewer approves in place with the evidence in front of them. Qualification status is visible per organisation at a glance.

Issue the record

Capability matrix

The capability matrix is generated from results, not typed up afterwards — printable per organisation, or globally across every partner in the programme.

Rule validation

Pass, or what is missing

Each step is validated against the rules defined for it. A failure names the specific expectation that was not met, rather than reporting a generic mismatch.

AI-assisted review

Advisory, never automatic

An AI reviewer reads the messages against the airline's own NDC documentation and returns a verdict, a summary, the issues it found and what to try. A warning downgrades a passed step to review — it never quietly passes one.

The messages, kept

Request and response per step

Every submitted request and response stays attached to its step and opens in an XML viewer, so a decision made months ago can still be re-examined.

Failures become tickets

Service desk integration

A failing step can raise a support ticket automatically, so a partner blocked on a carrier-side problem is not blocked silently.

Certification Copilot

Read-only partner API and MCP

A partner organisation can point its own AI assistant at certifi to browse the published programme, read its own progress and feedback, and dry-run validate XML before spending a submission.

Coach, not shortcut

By design

The Copilot cannot submit, cannot change a status, cannot see another organisation's data and cannot read the validation configuration. Certified evidence still comes from a real run.

Programme authoring API

Token-authenticated and audited

The airline side has its own write API and MCP server, so a programme can be built, imported or exported in bulk, with every change audited.

Re-certification campaigns

Pushed into delivery

A re-certification campaign can be pushed as tasks into a webcore nucleus project, with status changes flowing back automatically as the work is done.

Step by step

Every message checked against the rules for that step

A step is not a checkbox. It carries the requirement, the request, the response, the validator result and the reviewer's decision in one view — so the question "why did this pass?" always has an answer that does not depend on who was in the room.

Where a step involves a re-shop, a servicing call or an order change notification, the editor understands that message type specifically rather than treating every step as generic XML.

webcore certifi step detail showing the requirement, captured request and response, and the validation result
webcore certifi administration screen for reviewing a partner submission with its evidence attached

Review and sign-off

A decision your auditor can follow

Reviewers see the submission and the evidence together and approve in place. Qualification status per organisation, and the global capability matrix across every partner, are generated from what actually passed.

That matters twice over: the airline can answer what a given partner is certified for without a search through email, and the partner can prove it.

Programme administration

Author it, publish it, change it

Certification programmes move. New message types, new requirements, a level that turns out to be in the wrong order. certifi treats the programme as content the airline owns rather than a fixed release: build the structure, publish or hide any part of it, import and export a whole certification pack, and manage access with personal access tokens.

Sign-in rides your existing portal single sign-on, or runs standalone with its own registration and multi-factor authentication. One deployment can serve more than one airline, with an airline switcher for people who work across several.

webcore certifi programme administration screen for managing certification levels, categories and use cases

Works with

Part of the Webcore NDC toolchain

certifi is one of six Webcore products. These are the ones it shares real machinery with.

webcore latitude

The sandbox partners generate their certification evidence in. A certification step expectation and a regression test expectation use the same contract.

webcore nucleus

Re-certification campaigns become tasks in a delivery project, with status changes flowing back into certifi as the work completes.

webcore cmx

The NDC documentation the AI reviewer reads, and the help drawer partners see, is maintained as CMS content rather than hard-coded.

Put your certification programme in one place

We will show you an airline programme end to end, authoring, a partner submission, validation and sign-off.
Trusted by Virgin Atlantic, LATAM Airlines and TAP Air Portugal.