Skip to content

identity: point the verification iframe at the identity-verification route - #2011

Draft
AngelPaella wants to merge 1 commit into
mainfrom
angel/eng4-337-route-path
Draft

identity: point the verification iframe at the identity-verification route#2011
AngelPaella wants to merge 1 commit into
mainfrom
angel/eng4-337-route-path

Conversation

@AngelPaella

Copy link
Copy Markdown
Contributor

Part of ENG4-337. Pairs with the backend rename in Paella-Labs/crossbit-main.

CrossmintIdentityVerification frames a Crossmint-hosted route. That route is moving from /sdk/unstable/kyc-verification to /sdk/unstable/identity-verification, so the SDK's copy of the path moves with it. The two have to ship together or the component frames a dead URL.

Why now

Nothing consumes the route yet, and client-sdk-base has not published the identity surface (latest on npm is 2.6.0, which predates the feature). Renaming the path costs nothing today. Once 2.7.0 is out and integrators have it in a lockfile, it stops being free.

What is not in here

The kyc:* event keys stay. Every event-key namespace in this repo is a kebab-case domain noun (payment-method:, order:, payment:, quote:, ui:), never a camelCase feature name, and payment-method:selected already ships from a route directory called payment-method-management. The wire has never mirrored a product-surface name, so kyc: is the domain noun and it is already correct.

The parent still never calls handshakeWithChild(), so the child's events go out blind. That belongs with the target-origin decision in ENG4-354, not here.

Changeset

None added on purpose. The identity feature is unreleased and the open release PR already queues it as client-sdk-base@2.7.0, so this path change rides that changeset.

Verification

pnpm test:vitest --filter @crossmint/client-sdk-base --filter @crossmint/client-sdk-react-ui

@changeset-bot

changeset-bot Bot commented Aug 6, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 0151a37

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant