OweMotionOweMotion

Fictional demo. No real customer data. Payment and contact actions are disabled. This fixture illustrates the shape of a Verified Living Link for a Carpet & Flooring job.

OweMotion Verified Living LinkFixture — ActivePayment pending

Sample Flooring Install

Install complete — payment pending

BusinessExample Home Services
CustomerExample Client
TemplateCarpet & Flooring
LocationGeneral Service Area
Link stateActive fixture
Last updatedMay 8, 3:00 PM

Verification standard

Every Verified Living Link answers six questions.

1

Who sent this?

Example Home Services — a fictional OweMotion workspace used for illustration. In a real link, you would see the actual business name here.

2

Why am I seeing this?

This page was sent because Example Home Services completed a fictional flooring install for Example Client and is showing the job status, proof trail, and invoice context.

3

Is this current?

This fixture is static. In a real Verified Living Link, the status, proof count, and payment state reflect the workspace record as of the last update timestamp.

4

What proof exists?

5 proof records have been captured: before-install condition, material confirmation, install progress, final carpet installed, and installer completion note.

5

What is safe to do?

In this fixture, payment and contact actions are disabled. In a real link: review the proof, then pay through the Stripe-hosted payment form, or contact the business directly if anything is unclear.

6

What if I am unsure?

Contact the business directly at the number or email you have on file. A real OweMotion link will never ask for your card number, password, or login credentials through the link.

For Example Client

Your flooring install is complete.

This page was sent because Example Home Services completed a fictional flooring install and is showing the job status, proof trail, invoice context, and next step.

What happened?

Your service area carpet was installed on May 8. The crew arrived, removed the old carpet, installed the new material, fitted the transition strip, and cleaned up.

What proof was captured?

Five proof records were captured: request, material confirmation, before condition, install progress, and final walkthrough note.

What do I owe next?

Review the proof below. Payment of $1,240.00 completes the job record. Payment is disabled in this fixture.

Current state

Job statusComplete
Proof status5 records captured
Review statusPending customer review
Payment statusPending — $1,240.00
Next actionReview proof and complete payment

Proof trail

What was recorded.

5 proof records captured across this job.

Request captured

Captured

May 3, 2:14 PM

Carpet install request received from Example Client. Living room, 320 sq ft.

Material selection confirmed

Captured

May 6, 3:45 PM

Carpet style and color confirmed. Material ordered and confirmed in stock.

Before condition documented

Captured

May 8, 9:20 AM

Before-install photo taken. Existing carpet and subfloor condition recorded.

Install progress captured

Captured

May 8, 11:30 AM

Mid-install photo captured. New carpet laid across 320 sq ft, transition strip in progress.

Final walkthrough recorded

Captured

May 8, 2:51 PM

After-install photos submitted. Cleanup confirmed. Installer completion note filed.

Timeline

Every step, in order.

Request received

Done

May 3, 2:14 PM

Example Client submitted a flooring install request.

Quote prepared

Done

May 4, 10:30 AM

Quote of $1,240 prepared for materials, labor, and cleanup.

Material confirmed

Done

May 6, 3:45 PM

Carpet selection confirmed. Material ordered.

Install scheduled

Done

May 8, 9:00 AM

Install window confirmed for May 8, morning.

Arrival confirmed

Done

May 8, 9:12 AM

Crew on site. Pre-install walkthrough complete.

Install progress captured

Done

May 8, 9:20 AM – 2:48 PM

Before-install condition documented. Carpet installed, transition strip placed, area cleaned.

Final proof captured

Done

May 8, 2:51 PM

After-install photos submitted. Installer completion note recorded.

Invoice prepared

Done

May 8, 3:00 PM

Invoice of $1,240 prepared and attached to job record.

Payment pending

Pending

May 8, 3:00 PM

Invoice open. Payment not yet received. Customer review requested.

Invoice context

$1,240.00

Invoice total — payment pending

Materials$480.00
Labor$680.00
Cleanup$80.00
Total$1,240.00

Review the proof above, then complete payment to close the job record.

Real payment actions use Stripe-hosted payment forms. OweMotion must never collect raw card numbers, CVC, or expiry data directly through any link surface.

Safe actions

What you can safely do.

Actions are disabled in this fixture. In a real Verified Living Link, these actions would be scoped to the specific job and recipient.

Review proof

See the 5 proof records captured during this job.

Pay invoice — Stripe-hosted

Real payment flows through a Stripe-hosted form. OweMotion never handles card data directly.

Contact the business directly

Use the number or email you have on file for Example Home Services. A real link will never ask for your password or card number.

Business view

What the business sees.

The same events that power this customer page give the business a complete picture without extra data entry. Events are truth. Snapshots are derived.

Request

Received May 3

Schedule

Executed May 8

Proof

5 records captured

Status

Install complete

Obligation

$1,240.00 owed

Payment state

Pending

Verified Living Link — honest boundary

What this link does and does not do.

What it does

  • Shows context before asking for action.
  • Shows proof before asking for payment.
  • Makes the job status and evidence easy to understand.
  • Gives fallback verification guidance if you are unsure.
  • Keeps proof, status, and payment context in one place.

What it does not do

  • Guarantee the link is safe.
  • Legally verify the business identity.
  • Create operational truth — it reflects it.
  • Replace Stripe, legal review, insurance, or compliance verification.
  • Collect card numbers, passwords, or login credentials.

Links are surfaces. Events are truth. Snapshots are derived.

Developer / internal

This is the static fixture demo at a fixed route. The read-only runtime fixture below proves the dynamic token route shape at /trust/v/[token].

View read-only runtime fixture →

One link. The whole proof trail.

This is what one living link can do.

One link for the customer. One truth for the business. Proof, status, and payment in one flow.