Merged
Conversation
pairs with backend fix that moves rail enrollment to webhook time. cross-region moveToLevel now requires explicit crossRegion=true flag. only set when user clicks "Verify now" on a different region — automatic calls (fetchCurrentStatus, polling) never set it.
REVERIFYING is treated as approved for all access checks — user retains existing provider access while re-verifying for a new region. added to APPROVED_STATUSES set (single source of truth) so all downstream readers (useKycStatus, useQrKycGate, useIdentityVerification, KycStatusItem, etc.) automatically handle it correctly.
…less handling 1. add REVERIFYING to exclusion list in status-transition effect so it doesn't close the progress modal if received via websocket during SDK completion 2. handle REVERIFYING + no token same as APPROVED — call onKycSuccess instead of showing misleading "Could not initiate verification" error
fix: thread crossRegion flag for cross-region KYC
The 4 reward/surprise PostHog events (surprise_moment_shown, reward_claim_shown, reward_claimed, reward_claim_dismissed) were instrumented on PerkClaimModal but that component only renders for "Card Pioneer" perks. The actual surprise moment perks (Rewards v2 - Surprise 35c/65c) are claimed inline on the QR payment success screen, which had zero PostHog instrumentation. Added: - REWARD_CLAIM_SHOWN + SURPRISE_MOMENT_SHOWN when perk UI appears after successful QR payment (useEffect with hasTrackedShow ref) - REWARD_CLAIMED after successful mantecaApi.claimPerk() - REWARD_CLAIM_DISMISSED on unmount if shown but not claimed These events unblock KR2 measurement for Rewards v2.
CodeRabbit caught that hasTrackedPerkShown and perkClaimedRef survive resetState(), so a second QR payment in the same session would skip analytics tracking. Move refs before resetState and clear them there.
fix: instrument reward analytics on QR payment page
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- add actionType to InitiateSumsubKycResponse type - handle bridge-direct: skip SDK, show preparing modal, backend handles submission - handle manteca action: open SDK with action token (questionnaire only) - add isActionFlow flag to disable multi-level for action flows (cross-region LATAM uses action, not multi-level workflow) pairs with backend feat/applicant-actions branch.
Brave identifies as Chrome in its User-Agent string, causing PostHog to misclassify Brave users. Given our crypto-native audience, Brave usage is likely 5-15% of traffic — currently invisible in analytics. Uses navigator.brave.isBrave() API to detect Brave and sets a browser_override person property in PostHog for accurate breakdowns.
…ection feat(analytics): detect Brave browser in PostHog
- revert animations submodule to main (accidental change from worktree init) - reset isActionFlow in bridge-direct early-return to prevent stale state
only close SDK when onApplicantActionStatusChanged fires with reviewStatus === 'completed', preventing premature closure on intermediate action events
feat: handle applicant action responses for cross-region KYC
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Branch Sync
main is 5 commits ahead of dev.
Commits to sync:
• fix: thread crossRegion flag for explicit cross-region KYC requests
• fix: only send crossRegion flag when true, omit for same-region
• feat: add REVERIFYING to approved statuses and SumsubKycStatus type
• fix: address review — REVERIFYING exclusion in status effect + token-less handling
• Merge pull request #1874 from peanutprotocol/fix/rail-enrollment-timing
Auto-generated by Chip 🐿️