Proof in the file.

• 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.

{
  "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.

The same person can start on any surface, continue on a custom domain, and sign into your app without becoming a second account.

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 -->

• One user across passkey and email, with no split identity.
• No passwords, no credential tables, and no password-reset support burden in your product.
• The same account can begin on any surface or custom domain and still resolve to one user in your app.
• 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 identity.
• Existing email-first users can connect passkey later from Account, 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.
• 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.