Receiz/Powered By/Verification primitive

Proof in the file.

Verify links (/v/...) are optional public convenience for that same file.

Official SVGOptional /v contextDeterministic verdicts

Verify Back to Receiz

Badge Preview

Asset

`/powered-by-receiz.svg`

Size

172 x 32

Use

Footer / report / portal

Embed Snippet

<a href="https://receiz.com/verify" target="_blank" rel="noopener noreferrer">
  <img src="https://receiz.com/powered-by-receiz.svg" alt="Powered by Receiz" width="172" height="32" />
</a>

Shipping Checklist

Keep the image source on `receiz.com`.
Badge clicks should use a record-specific /v/{{slug}}/{{code}}/{{pulse}}?a={{anchorId}} link when available (fallback: /verify).
Keep assetUrl as your own app route to the original asset bytes; do not point it to receiz.com.
Use the badge where proof matters: near payout/original evidence, not decorative-only locations.

Asset-linked payload example

Keep both URLs in the payload. Asset actions should open your app asset URL; the Powered by Receiz badge should open the record-specific Receiz verify URL.

{
  "assetId": "asset_93f42",
  "assetTitle": "Invoice #4082.pdf",
  "assetUrl": "https://app.example.com/assets/asset_93f42/original",
  "receizVerifyUrl": "https://receiz.com/v/{{slug}}/{{code}}/{{pulse}}?a={{anchorId}}",
  "badgeSrc": "https://receiz.com/powered-by-receiz.svg"
}

// UI wiring:
// - Primary file/open button -> payload.assetUrl (your app asset route)
// - Powered by Receiz badge -> payload.receizVerifyUrl (fallback: https://receiz.com/verify)

Add a branded Sign in with Receiz button and start OIDC + PKCE for passkey-first sign-in, magic-link fallback, and automatic account creation.

Need the full architecture and identity contract? Open Receiz Connect Guide.

Rendered Preview

Use /sign-in-with-receiz.svg on light UIs and /sign-in-with-receiz-light.svg on dark UIs.

<div
  class="receiz-login-embed"
  data-username="your_receiz_username"
  data-redirect-path="/auth/receiz/callback"
></div>
<script src="https://receiz.com/receiz-login-embed.js" async></script>

<!-- Callback route should exchange code at /api/oidc/token and map users by profile.sub -->

What Integrators Get

Passkey-only onboarding for new users, with no email required at first sign-in.
Seamless email sign-in available at any point, resolving to the same Receiz user identity.
Existing email-first users can add passkey later, and passkey-first users can add email later, without identity split.
Automatic Receiz account provisioning on first successful login from your app, for passkey or email.
Recipient magic-link flows can provision users in-line; afterward passkey and email both access the same account.
No passwords, no credential tables, and no password-reset support burden in your product.
Stable OIDC subject mapping (`sub`) so your local user records never split across login methods.
Standard OIDC/OAuth stack plus optional delegated Receiz action scopes for record/seal/verify APIs.

Public convenience Link Format (optional)

https://receiz.com/v/{{slug}}/{{code}}/{{pulse}}?a={{anchorId}}

This verify link (/v/...) is an optional public convenience route for that same sealed file.

Live Conformance Badges

Place these directly beside the Powered by Receiz badge in proof-heavy surfaces (receipt footer, evidence drawer, record detail sidecar): verification conformance first, then settlement, identity, issuance, interoperability, and world conformance.

Preview

Receiz live verification conformance status

Receiz live settlement conformance status

Receiz live interoperability conformance status

Trust row order: brand provenance first, then verification, settlement, identity, issuance, interoperability, and world conformance.

Placement Contract

Keep all seven badges on one horizontal row when space allows.
Use `12px-16px` gap and align to the same visual baseline.
If stacked on mobile, order: Powered by badge, verification, settlement, identity, issuance, interoperability, world conformance badges.

<a href="https://receiz.com/verify/conformance" target="_blank" rel="noopener noreferrer">
  <img src="https://receiz.com/api/verification/conformance/badge" alt="Receiz live verification conformance status" height="30" />
</a>

<a href="https://receiz.com/economy/conformance" target="_blank" rel="noopener noreferrer">
  <img src="https://receiz.com/api/economy/conformance/badge" alt="Receiz live settlement conformance status" height="30" />
</a>

<a href="https://receiz.com/identity/conformance" target="_blank" rel="noopener noreferrer">
  <img src="https://receiz.com/api/identity/conformance/badge" alt="Receiz live identity conformance status" height="30" />
</a>

<a href="https://receiz.com/issuance/conformance" target="_blank" rel="noopener noreferrer">
  <img src="https://receiz.com/api/issuance/conformance/badge" alt="Receiz live issuance conformance status" height="30" />
</a>

<a href="https://receiz.com/interoperability/conformance" target="_blank" rel="noopener noreferrer">
  <img src="https://receiz.com/api/interoperability/conformance/badge" alt="Receiz live interoperability conformance status" height="30" />
</a>

<a href="https://receiz.com/world/conformance" target="_blank" rel="noopener noreferrer">
  <img src="https://receiz.com/api/world/conformance/badge" alt="Receiz live world conformance status" height="30" />
</a>

Intent

One badge. One verdict.

The badge declares that everything is testable and the answer is deterministic: verified or failed.