Skip to content

How it works

From an agreed scope to evidence you can act on

A journey check follows the same path every time. The scope is agreed in writing, a person reviews the evidence, your team makes any change, and a follow-up check of the same journey shows what changed.

The seven steps

  1. 01

    Authorize

    The merchant approves the storefront and the agreed scope. An agency needs documented merchant approval.

  2. 02

    Scope in writing

    We confirm the product, variant, quantity, market, supported checks, price and timing. Nothing is charged before you accept.

  3. 03

    Check

    We run the agreed journey in a real browser through checkout entry and capture evidence at each assessed step.

  4. 04

    Review

    In a journey check, a person reviews the evidence and the interpretation before the report is sent.

  5. 05

    Report

    Tested, observed and expected for each finding, with explicit unassessed steps, in an agency-branded report.

  6. 06

    Your fix

    Your team or agency decides on and applies any change. We do not alter the storefront.

  7. 07

    Follow-up check

    We check the same agreed journey again and report what changed, or why the comparison is inconclusive.

Who does what

Safeliant

  • Confirm feasibility and the supported checks in writing before quoting.
  • Run the agreed journey, review the evidence and send the report.
  • Run one follow-up check of the same scope after your change.

Your team

  • Provide merchant authorization and the agreed product inputs.
  • Decide on and apply any fix.
  • Tell us when the change is ready for the follow-up check.

When a follow-up check counts

The follow-up check runs the same agreed product, variant and quantity, so you see which findings resolved. A finding counts as resolved only on that same scope: if a step is blocked, the product is unavailable or the scope has changed, the result is reported as inconclusive, never as fixed.

Repeating the checks

Agency plans repeat the same checks across client stores.

Recurring checks run from the schedule Safeliant generates for your existing CI, cron or server environment.

For you, in four steps

  1. 01

    Request a scope

    Tell us the storefront, product and the change or problem. You get a reference straight away.

  2. 02

    Agree scope and quote

    We confirm authorization, supported checks, price and timing in writing. Nothing is charged before you accept.

  3. 03

    Check and review

    We run the agreed journey. A person reviews the evidence and sends the report.

  4. 04

    Your fix, then a follow-up check

    Your team makes a change. We check the same journey again and report what changed.

Tell us the journey you want checked

A request gets a reference straight away. We reply in writing with supported scope, price and timing before any work. It creates no subscription or charge.