Skip to main content

Certification Process for New Integrations

Certification Process for New Integrations

Written by Product Management

Certification Process

For each new supplier integration, we require partners to complete a comprehensive certification process to ensure quality, reliability, and seamless user experience. This process consists of two key components:

  1. API Certification via NACT (Nezasa API Certification Tool) - Automated validation of your Connect API implementation

  2. UI Test Cases - Manual testing of the complete user experience through Trip Builder

  3. QA test - Nezasa QA team will run E2E tests as well to ensure the integration works as expected in the extended environment

Certification Requirements

We expect partners to provide:

  • Certification report from NACT

  • Evidence of completed UI test cases (screenshots and documentation)

Our team will review all provided documentation within 7 working days and share feedback.

Once the certification requirements are met the QA tests are planned. QA testing is scheduled in coordination with your Partner Product Manager, based on sprint capacity and team availability. Timelines are agreed on a per-project basis.


API Certification with NACT

NACT (Nezasa Automated Certification Tool) is a self-service certification platform that validates Connect API implementations in 3-5 minutes with instant, detailed feedback - eliminating wait times for manual Nezasa reviews or extensive UI testing.

NACT enables partners to:

  • Test unlimited times during development without restrictions

  • Receive precise error reports with debugging tools (including cURL commands)

  • Get immediate compliance status with specific issue identification

  • Validate implementations in 3-5 minutes instead of waiting for manual reviews


UI Test Cases

Overview

UI test cases are designed for comprehensive testing of supplier integrations through the Trip Builder user interface. These tests validate the complete user experience and ensure seamless integration with your systems based on our Engineering Acceptance Criteria.

All tests must be executed through the Trip Builder interface to validate end-to-end functionality.

Detailed test cases can be found in the following pages:

Test Execution Guidelines

Documentation Requirements:

Provide screenshots for each major step and all expected results. Add explanatory notes for any deviations, issues, or observations during testing.

For Booking Test Cases:

  • Itinerary ID

  • Booking Reference

  • Screenshots showing booking confirmation

For Cancellation Test Cases:

  • Original Itinerary ID and Booking Reference

  • Cancellation Reference (if different)

  • Screenshots showing component status change

Important: Nezasa will not be liable for non-refundable bookings made during certification testing.


Certification Review Process

  1. Submit Documentation: Provide your complete NACT certification report and UI test case evidence

  2. Nezasa Review: Our team reviews all documentation within 7 working days

  3. Feedback: We share detailed feedback on any issues or required improvements

  4. Iteration: Partners address feedback and resubmit if necessary

  5. QA: Once all requirements are met, we schedule QA testing

  6. QA feedback and iteration: We share feedback (if applicable) for final fixes.

  7. Certification: Once the feedback is addressed, the integration is certified


For questions or support during the certification process, please contact your Partner Product Manager

Did this answer your question?