Verification

How Miaise verifies.And what it means for you.

The rest of the practice management category treats verification as a checkbox you tick once at signup. We treat it as the load-bearing trust mechanism, because if it isn't real, nothing else we claim on this site is.

The short version

When you submit a certification to your Miaise profile, a real person on our side checks it against the issuing board's public registry. We deep-link the badge on your public booking page straight to that registry, so anyone who clicks can confirm it against the board themselves, not against us. When a credential lapses, the badge falls off your public booking page automatically. That's it. No paid seal, no third-party trust-badge vendor, no theater.

Scope, honestly

What's verified, what's on file, what's private.

Public on your booking page

Certifications

Board certifications and modality credentials, hand-checked against the issuing organization's public registry. Categories include board certification (NCBTMB BCTMB), craniosacral therapy, lymphatic drainage, sports massage, oncology massage, prenatal, medical/clinical massage, Asian bodywork, and others.

Each verified certification renders as a badge on your public booking page, with a link straight to the issuing board's lookup tool. Lapsed certs auto-remove.

On file with you, not public

License, insurance, CEU

Your state license, liability insurance certificate, and continuing-education tracking all live inside your Miaise account. They're not surfaced on the public booking page in v1. Your license and insurance are yours to carry, and we track the renewal dates so you keep them current.

Renewal reminders, expiry tracking, and CEU progress run in-app, so a license or insurance lapse never catches you at the wrong time.

Always private

Documents and numbers

The certificate scans you upload, the certification numbers themselves, your insurance policy document, your license document. Held in BAA-covered Cloud Storage with row-level access controls. Never rendered on a public page, never shared with another therapist or client.

The mechanism

Primary source, every time.

The pattern is borrowed from the public-licensing world. Federation of State Massage Therapy Boards runs Look Up a License. State boards run their own lookups. NCBTMB runs the board-certification registry. Each of those is the source of truth, accessible to anyone with a browser. We check against them, and we link to them.

  1. 01

    You submit

    You upload the certification document and the certification number when you set up your profile. The document is private on our side; the number gets used for the lookup and stays private after.

  2. 02

    We check

    A real person on the Miaise side checks the credential against the issuing organization's public lookup. If the lookup says active and matches your submission, the certification becomes verified. If anything doesn't line up, we ask you about it directly.

  3. 03

    We deep-link

    The badge that renders on your public booking page links to the issuing organization's public lookup for that specific credential. Anyone who clicks the badge can run the verification themselves. The proof isn't a paid seal. It's the link.

The failure mode

Lapse, and the badge falls off.

Each verified certification carries the expiry date the issuing board sets. Some lapse never (board certifications with no expiration). Some renew on a one-year, two-year, or three-year cycle. We store the expiry on the record.

The public booking page filters expired certifications out of the rendered badge row automatically, in real time, on every page render. There's no nightly cron, no manual sweep, no admin queue. The badge is on the page only as long as the credential is still current.

This is the failure mode that proves the verification mechanism is real and not theater. A static "verified" badge that stays on the page after a credential lapses is a marketing claim. A badge that disappears the day the credential expires is an enforcement mechanism.

Most of your booking-page visitors in v1 are people who already know you. They got the link from you directly, from a referral, from a business card, from your instagram bio. They aren't comparison-shopping you against another therapist on a marketplace. They already trust you.

So the v1 audience for the verification badge isn't really them. It's you. The mechanism's two real jobs in v1 are:

  • Liability cover for you. A public page advertising a credential you no longer hold is the kind of thing a board complaint is made of. Auto-removal on lapse means you can't accidentally leave a stale badge claiming you're in good standing when the paperwork says otherwise.
  • A signal about us. The same rigor we apply to verifying you is the rigor we apply to the rest of the product. The /security page and our public BAA path follow from the same posture.

For the licensed therapist

What this means for you.

A note about v2

The verification surface gets bigger.

When Miaise opens the client-side marketplace, the audience for verification changes. A cold client searching for a therapist on the Miaise marketplace will be deciding between practitioners they don't know yet. At that point the credential badge is doing work for the client, not just for the therapist.

That's when the verification surface expands. License-status badges, insurance-on-file flags, identity verification, and the rest of the marketplace trust stack ship alongside the client-discovery features. v2 is gated on a 50-to-200 paying therapist cohort and on the legal and ops scaffolding that real marketplace operation requires.

We mention this here because shipping the verification claim in v1 with a smaller surface than v2 is the right scope decision, and we want to be upfront about it.

Related

The rest of the trust posture.

The same rigor applies across security architecture, subprocessors, and the BAA path. The security overview shows where your client records live and who can touch them.