feat: reimagined registration and onboarding (residence step, Unlock payments, home checklist, region-restricted screens) - #2834
Merged
42 commits merged intoAug 28, 2026
Conversation
A user whose ID was rejected for its jurisdiction hits one of four endings today, and none of them is honest. Two offer a retry that can never pass (the drawer's "Retry verification"; the identity-verification page's "Let's try that again"), and two route to support over a block support cannot lift (the home card; the bank gates' "We couldn't unlock this"). Replace all four with one screen that explains the block, names no country, offers no retry, offers no support link, and hands the user the part of the app that still works. The CTA is the design decision. With retry and support both gone, the button's only remaining job is to point at a capability the user keeps — so it routes to send/request rather than dismissing. That is also the promise the copy makes, so peer-to-peer must stay open for this cohort; this change does not gate anything, but it does depend on that. Enforced at the choke point, not per call site. Six gates open InitiateKycModal, and each computes its variant from a rail gate that cannot see WHY identity failed — a region-restricted user reads as `needs-identity` and would be offered "Unlock now" straight back into the Sumsub SDK. Short-circuiting inside the shared component makes that impossible for a future call site to miss. Also marks the two region reject labels terminal, so no surviving surface can contradict the new screen with a retry button. That fixes a pre-existing bug beyond this cohort: UnlockedRegions hardcodes isTerminalRejection's three inputs to null (a documented casualty of the capabilities migration), so EVERY terminal rejection — fraud, sanctions, age — currently renders "Let's try that again" there. Copy names no country in any of the four locales, so a change to the Sumsub list needs no re-translation and no deploy.
The InitiateKycModal short-circuit re-implemented KycRegionRestrictedModal inline — same title, icon, content and CTA, ~30 lines of it. Call the component instead. Duplication was the point, not the line count: the whole change rests on every surface telling a region-restricted user the same thing, and two independent definitions of that screen are two things that can drift. Now there is one. Caught by the code-analysis bot flagging InitiateKycModal's MDD jump (41.5 → 55.5) on the first push.
Every terminal rejection — fraud, sanctions, age, forgery — currently
shows "Let's try that again" on /profile/identity-verification, and a
"Retry verification" button in the identity drawer. Neither can pass.
Root cause: UnlockedRegions hardcoded all three of isTerminalRejection's
inputs to null/undefined during the capabilities migration, because the
capability model carries no per-verification Sumsub history. The check
therefore always returned "retryable" and the terminal branch never
rendered. The drawer never had a terminal branch at all.
The history was never the right source. The backend already folds the
decision (Sumsub RETRY → ACTION_REQUIRED, FINAL → REJECTED) and now says
outright whether a retry is worth offering, so read that instead of
reconstructing it from raw labels and attempt counts.
These get a DIFFERENT ending from region-restricted, deliberately:
region-restricted explain fully, no support link — support cannot
lift a jurisdictional block
terminal explain nothing, offer support — naming fraud or
sanctions carries compliance exposure and tips off
the people it describes, and a human CAN review a
misclassification
Both are terminal, so neither offers a retry.
Also guards the home card banner on isRegionRestricted: that branch
returns before reading `step`, so the region card was silently replaced
by a CTA routing to /shhhhh.
KycFailed takes onContactSupport as a prop rather than reading
ModalsContext, keeping it presentational like its siblings — reading the
context directly broke an unrelated suite that renders it bare.
The whole /setup flow was a single pageview, so per-screen funnels were impossible, and browser/hardware Back ejected users from the flow losing all progress. - every rendered step fires signup_step_viewed (screen_id, step_index, total_steps, nav_type), making per-screen funnel analysis possible - the active step is mirrored to ?screen= via shallow History API updates, so Back walks the steps like the in-app chevron - the URL is a mirror, never a source of truth: the entry step is still chosen by determineInitialStep and the first mirrored step replaces the history entry, so a stale ?screen= from a reload or shared link cannot route into a step whose prerequisite state is missing - steps that forbid back (sign-test-transaction: the passkey already exists) neutralize popstate by restoring their own entry - ?screen is distinct from ?step=signup, which stays an entry-only contract that skips the invite gate
New 'residence' screen between username and passkey, per the reimagined onboarding flow: legal residence is asked before the account exists, so it can prequalify the provider rail and KYC requirements. - country selector prefilled from IP geo as a suggestion only (never auto-advances, never triggers restriction by itself) - "Have documents from more than one country?" reveals a second selector - residences under regulatory restriction (CN, IR, RU, BY, GB) get a generic heads-up before any passkey or account exists: bank transfers and card issuing unavailable; the screen names no country. Exits: "Continue anyway" or "Notify me when it is available" (email capture, stored as PostHog person properties until a pre-account endpoint exists) - answer persisted to the API (update-user residenceCountry / secondResidenceCountry) after account creation, fire-and-forget - analytics: signup_residence_selected / _restricted_shown / _restricted_continued / _notify_submitted; the step is picked up by the existing signup_step_viewed mirror automatically - copy added to all four locales
Full-restriction list grows to the provider-corroborated set: KP, SY, CU (refused by every US-linked provider) and HK (Sumsub rejects HK documents, so no KYC can pass) join CN, IR, RU, BY, GB. Two new advisory tiers with their own screen, copy varying by what still works: - card-only restriction (Rain prohibited issuance): IN, TR, UA, VE, VN, IL, IQ, MM, NP, NI. Banking still works. UA is country-wide per Rain's issuance list; Crimea/Donetsk/Luhansk are additionally sanctions-blocked, but a country picker cannot see regions. - banking-only restriction (Bridge does not onboard): DZ, BI, JP, TN. The card still works. The residence selector now supplements countryData (the add-money destination list, which omits sanctioned countries) so restricted residents can answer truthfully and actually reach the heads-up. New analytics event signup_residence_partial_shown with restriction_type. Copy in all four locales.
New useResidenceRestrictions hook reads the server-derived residenceRestrictions block from /get-user (authoritative), falling back to the redux setup residence for the pre-account window. Not a feature flag by design: regulatory availability is durable per-user state served with the user, not a rollout knob. - ActivationCTAs: a fully restricted residence (no bank rails AND no card) hides the "Unlock payments" verify CTA — the ID check behind it could only end on a terminal rejection. Partial restrictions keep it, since one half of the unlock still works. - CardLaunchCTA: residence check joins the visibility gate, avoiding a banner flash before the next /card-info response reflects the declared residence (the server's isEligible now covers it durably).
The regions rework: regions survive as presentational groups, but every
row is a concrete product with a live status chip, and the unlock verb
attaches to products ("SEPA transfers · Unlock"), never to abstract
regions.
- Everywhere group leads: Peanut-to-Peanut payments (Always on) and the
Peanut card as its own row routing to /card. The card is a global
product gated by residence eligibility, not a regional rail — which
removes the old screen's Europe-tap → /card hijack by construction
(a bank-method tap can only start bank KYC; pinned by test).
- Region groups follow the rail's real geography: Brazil (PIX & bank
transfers), Argentina (QR & transfers), United States (ACH & Wire),
Mexico (SPEI), Europe (SEPA). LATAM never appears — it stays what it
is, an internal KYC-level bucket. Rest-of-world's provider-less dead
end is gone; the Everywhere group carries that meaning honestly.
- Merged rows split automatically when statuses diverge: a Bridge-only
user sees "PIX QR payments · Active" + "Bank transfers · Unlock".
- Residence anchor row (declared/verified from the new /users/me
residence block) explains why the list looks the way it does, and
the user's own region floats to the top under Everywhere.
- Residence restrictions render as quiet honesty: restricted rows say
Not available and stop being tappable; the always-on row survives.
- All KYC modal machinery (unlock/processing/action-required/rejected/
provider-rejection, multi-phase flow) is carried over unchanged from
UnlockedRegions.view, which stays in place untouched to avoid
conflicting with PR #2778.
Product decision: a method that isn't active simply says Unlock, even when the provider will ask for something after the tap — the ask surfaces in the action-required modal, not as a scarier chip. The one exception stays: a verification in review shows Processing, since offering Unlock on an in-flight check would be dishonest the other way.
Three v1 shortcuts upgraded to full versions:
- Residence change flow: the anchor row's Change action opens a
country picker that saves the declared residence immediately (it is
advisory). When a verified residence exists and the pick differs,
the modal says plainly that current methods keep working until
re-verification with new-country documents, offered as an explicit
"Save & re-verify now" action over the existing restart-identity
primitive — never a silent side effect. Pending changes surface on
the row ("Update to {country} pending re-verification"). Restricted
picks warn inline. New residence_changed analytics event.
- Method-worded unlock sheet: UnlockMethodModal replaces the
region-worded UnlockRegionModal on this screen. The sheet talks
about the product the row promised ("Unlock SEPA transfers") and is
honest about both possible costs: covered verifications switch on
right away, anything else shows its requirements before the SDK.
- Server-served restriction tiers: the signup residence step and the
restrictions hook now read GET /config/residence-restrictions via
useResidenceRestrictionSets (module-cached, bundled mirror as the
instant fallback), so compliance can tune the lists with an API
deploy and no app release.
Deliberately NOT upgraded: the restricted-country notify email still
lands on the PostHog person — real storage needs a pre-account table
and DB migration, out of reach for this environment.
Home now mirrors the Unlock payments screen's status language with a
capped three-item to-do list (GettingStartedChecklist):
1. Create your account — always pre-checked, with the username line
2. Add money — label follows residence (PIX in Brazil, SEPA in Europe,
SPEI in Mexico, bank in the US, generic elsewhere); while unverified
the subtitle carries the honest KYC cost ("one-time ID check · about
10 min") and verification triggers contextually inside add-money;
done at the funded milestone
3. Get your Peanut card when the residence is eligible; otherwise the
slot goes to Make your first payment (QR scanner), so nobody sees a
dangling card step
Renders nothing once all three are done. Interrupt cards (provider
rejection, email block) keep their dedicated ActivationCTAs rendering;
only the happy-path funnel card is replaced. The outbound spend-chooser
became unreachable (its job moved into the checklist's third slot) and
is removed — TS narrowing proved the dead path.
New analytics: home_checklist_viewed (with third_item), and
home_checklist_item_clicked. Copy in all four locales, drift-aligned
with existing "Add money" / "Make your first payment" / "Get started"
translations per locale fallback chain.
…n-hk-0z0a4n' into claude/app-registration-onboarding-xo3iex # Conflicts: # src/components/Home/ActivationCTAs.tsx # src/components/Home/__tests__/ActivationCTAs.test.tsx
…mode
Three expectation-management gaps closed (the fourth suspect — decision
notifications — turned out to already exist: kyc.approved/rejected/
action_required dispatch push + in-app + email from the webhook side
effects, so nothing was added there).
- Unlock payments shows an in-review line while identity is processing:
"ID check in review since {date}" from identityVerification.submittedAt,
with a reassurance body. After 7 days it escalates to "This is taking
longer than usual. Message us and we'll chase it" (opens support).
Deliberately not on home.
- Deposit screens state arrival expectations per rail, honest about the
ceiling but leading with the typical case: ACH "usually 1 business
day, sometimes up to 3" (Nacha: ~80% settle within one day), SEPA
within 1 business day, SPEI/PIX/Faster Payments within minutes.
- Verification-outage mode behind the kyc-verification-down PostHog
flag: InitiateKycModal (the six-gate choke point) short-circuits to
"Verification is temporarily down" with a notify-me CTA that tags the
person for a comeback push, outranking every variant including the
region screen; Unlock payments shows the banner and stops bank-method
taps from opening the unlock sheet. Built for the invisible-outage
failure mode the KYC_SDK_LAUNCH_* events were added for.
Reason-code audit (no code change needed): every user-facing
CapabilityReason code the resolver emits already has a localized entry
in all four catalogs, document_rejected deliberately renders the BE's
instruction-specific prose, and unknown codes fall back to BE prose.
Copy in all four locales; 13 new/updated tests across the Unlock
payments and InitiateKycModal suites.
- GettingStartedChecklist: unknown card eligibility no longer shows the
card step — first-payment (always valid) renders until the server
confirms, with a test for the undefined case
- ResidenceChangeModal: re-seed the selected country each time the modal
opens (it stays mounted); a failed user refetch after a successful save
no longer traps the user or leaks an unhandled rejection; country
labels and sort now use the active locale like the residence row
- UnlockPayments: bank rows render disabled during a verification outage
instead of looking tappable under the degraded banner; submitted-date
label pinned to UTC (SSR hydration); removed an unused render-written ref
- Residence step: collapsing the second-country selector clears the
stored value so an invisible pick is never persisted or tracked
- SignTestTransaction: inspect updateUserById's { error } result (it maps
API failures, it doesn't throw them)
- KycFailed: terminal renders now require onContactSupport at the type
level (the retry button is gone, support is the only action)
- useSetupStepUrlSync: ref sync moved to a layout effect
- i18n: residence chip 'Verificada' in both Spanish locales (Verified
added to CONTEXT_DIVERGENT); pt-BR UK message names UK residents
- api.openapi.json synced from the API branch (update-user residence
fields, /users/me residence contract) and types regenerated
- deleted the unreachable UnlockedRegions.view (route renders
UnlockPayments; nothing imports it)
- test hermeticity: residence suites mock the restriction-sets fetch;
popstate no-op test now exercises the !target guard; loading-state and
catalog-order assertions added
…ater - useSetupStepUrlSync only listens for popstate while mirroring is enabled, so a history pop can't drive setup state before the entry step renders - Residence second-country clear moved out of the setShowSecondCountry updater (React may replay updaters; side effects stay in the handler)
…ck, PWA theme - manifest theme_color/background_color #000000/#ffffff → #FAF4F0: the black strip on Android came from the PWA theme color, not the native status bar (that fix, fa4b486, is already on this branch) - residence heads-up sub-views no longer repeat the step description; the select view renders it itself (descriptionInView step flag) - passkey 'Learn more' on sign-test-transaction opens an in-app explainer sheet (what/backup/privacy + full-guide link) instead of ejecting to the browser mid-signup; localized in all four catalogs - Add/Withdraw/Send/Request share one two-column grid width - profile menu: Peanut Card row hidden when residence-restricted or server-ineligible; menu label renamed to Unlock payments; Payment limits menu item removed (merged below) - limits merged into Unlock payments: active Manteca groups show an inline monthly usage bar, active Bridge groups the per-transfer cap, plus a Payment limits row linking the full /limits detail (3 new tests) - declared residence localStorage mirror (signup + change-modal writes): Unlock payments and the restrictions hook fall back to it when the server copy isn't available, with a Not confirmed chip (renamed from Unverified in all locales) - Unlock payments drops the duplicated in-body title (NavHeader keeps it)
…racy
- Unlock payments regroups by shared KYC flow: South America (Brazil +
Argentina — one Manteca verification opens both) and North America
(US + Mexico — one Bridge verification opens ACH/Wire and SPEI), with
country names kept on every row; Europe unchanged. LATAM deliberately
not used as a label — it would claim Mexico
- inline limits now attach per row (BRL/ARS allowance bars, shared
Bridge per-transfer cap deduped per group)
- confirmed copy in all four locales: screen description ('Everything
you can use today, and what opens after ID verification.'), home
first-payment note ('Send a few dollars to any @username. It lands
in seconds.'), and the non-custodial backup intro (account wording,
risk + remedy)
- backup instructions accuracy: iOS 18 Passwords app path, Android GPM
passkey wording (no phantom sync toggle), and a third-party
password-manager note rendered under the steps
The two highest-leverage actions lead the menu: Invite friends first, Unlock payments right under it (bank icon instead of globe-lock), out of the settings block below.
…idence mirror per account - DotFaceAvatar: deterministic generative avatar from the username (5 palette backgrounds x 5 eye styles x 5 mouths x blush = 625 faces), currentColor strokes so the theme supplies the outline. Used ONLY for the user's own identity: the home chip and the self profile header. Counterparties keep the initials avatar, where letters help tell contacts apart. Localized aria-label; determinism pinned by test. - CodeRabbit round: the declared-residence localStorage mirror is now keyed per account (unscoped legacy value removed, never migrated), so a second login on the same device can't inherit the previous account's country; the setup init effect now depends on the code and step params it reads instead of the searchParams object, so ?screen= mirroring can never re-run determineInitialStep mid-flow
…fest refresh Chrome applies <meta name="theme-color"> immediately in both browser tabs and installed PWAs, overriding the cached manifest theme_color. Without it, devices that installed the app before the manifest color fix kept the black strip until Chrome's day-scale manifest re-check.
The avatar SVG rendered inline, so baseline whitespace pushed it off center inside the home chip; the wrapper is now a flex box and the SVG a block filling it. On the backup screen the no-backup warning moves from under the steps list to directly below the non-custodial section.
Vertical card padding drops from p-4 to py-3 on every menu row, including the inline show-full-name toggle row, so the group stays uniform at the shorter height.
South America and North America each collapse to one row: Brazil and Argentina share a single Manteca verification and the US and Mexico a single Bridge one, so two rows implied two unlocks where there is only one. The rows still split under the QR-only overlay, where the two countries genuinely differ. Rows now carry a list of limit refs so the merged South America row surfaces both the BRL and ARS allowances. The Everywhere group always states that Peanut-to-Peanut payments have no limit — the one limit fact that exists before any unlock, since regional allowances are assigned per user at verification. Changing residence now invalidates the card-info and limits queries alongside the user refetch, so card availability recomputes from the new country instead of serving a cached answer. The card chip also drops its waitlist-grant condition: eligibility (residence-driven) decides availability; the grant only gates activation on /card, which matches the profile menu and checklist logic.
The unlock modal and the default initiate-KYC modal now carry the "before you start" content: which documents to have ready, how long the check takes, and the heads-up that a follow-up document can be requested. The Manteca path (Brazil and Argentina) gets the extended list with the tax ID and the regulatory questions. The old one-line modal went straight to the SDK with no preparation.
…dits Four pieces from the onboarding proposal: The signup finish now pauses on an account-ready screen instead of auto-redirecting: it names what works with no ID (receive, send to any @username, hold a balance) and plants the ID-check expectation (one check, about 10 minutes, review can take 1 to 3 business days) before home ever asks. Login flow still redirects straight in. The advisory verification pre-empt on the bank rails stops being a non-closable trap. The rail is still enabled until the effective date, so the modal now offers an informed choice: Complete now, or Do this later, which really continues the transfer; the deadline names when later stops being an option. The post-submit checking modal is dismissible: no more preventClose, the CTA reads Close and notify me, and after 90 seconds the copy admits the check is probably getting a closer look. Door and username copy: the landing pitch says account instead of wallet and makes the global promise explicit, the recover link says account, and the username step frames the handle as the thing friends pay, an account number you can say out loud. All copy in en, es-419, es-AR, and pt-BR.
The cross-region variant of the initiate-KYC modal (a verified user unlocking Brazil or Argentina from add-money, claim, or withdraw) went straight to the SDK with no preparation, and that path is exactly the extended one with the tax ID and regulatory questions. Both SDK-bound variants now carry the checklist, and the Manteca call sites pass the extended path.
The change modal reads residence.nextChangeAllowedAt from /users/me: while the escalating cooldown runs it states the date the next change becomes allowed and disables saving a different country. Re-saving the current country stays allowed. Server enforcement lives in the API; the snapshot and generated types pick up the new field.
The limit footers under each unlock group (the P2P no-limit line, the monthly usage bars, the per-transfer cap) sit on primary-3, the light lavender the app already uses for info surfaces, so they read as information attached to the group rather than another tappable row.
The generated avatar grows to read as a face: 24px in the home chip (28px on desktop) and 88px on the profile header. Account management moves where it belongs: the Show my full name toggle and the Delete account link now live on the Personal details page, the toggle only when a name exists to show or hide. The profile menu drops both rows. A new About Peanut page (profile menu, under Exchange rates & fees) links every policy from the legal registry plus the security disclosure, and shows the app version from package.json. Policy titles stay in English, the legal names of the documents, matching the re-consent modal; the page chrome is localized in all four languages.
It now closes the block after the card, badges, and points rows; the following block starts with Language.
Exchange rates & fees joins the top block under Unlock payments, and About Peanut closes the settings block under Back up your account. The standalone second group is gone.
The residence copy drops "citizenship": providers gate on where you legally live, and the question now says exactly that while keeping the document anchor (the one your documents show) so a passport holder abroad still answers with the country their KYC documents will prove. Both the signup step and the change modal, in four languages. Menu: the top block is now Unlock payments, Peanut card, Exchange rates and fees; the second block is Invite friends, Your badges, Points, Personal details.
The face grows to 48px and the pill to match (56px tall), with side padding cut so the avatar sits nearly flush; the username steps up a text size to balance.
The pill returns to its original 32px (36px desktop) height; the face fills it at 30px, the most the 1px-bordered pill holds, sitting flush against the left edge.
When the signup residence step holds two countries, it renders a per-country availability comparison (derived from the restriction tiers and the same static rail map Unlock payments uses) plus truth-first guidance: both entries must be genuine legal residences, providers verify the declaration including proof of address, the order only changes what shows first and never eligibility, and the second country stays usable later. No backend involved. The second declared residence also mirrors into account-scoped localStorage at signup, since the API stores but does not yet return it. On this device, Unlock payments tags both regions as yours, and restriction hiding softens to the intersection: an offer disappears only when BOTH residences rule it out, so a restricted primary no longer hides rails the second country's documents can legitimately pass. Safe by construction, restrictions never grant anything; a fresh device degrades to primary-only until the API exposes the field.
…y back-nav, shared localized residence options Unlock payments now short-circuits region-restricted users to the one honest region screen instead of an unlock offer whose SDK run can only repeat the rejection; the InitiateKycModal choke point never covered this surface. Backing out of an add-money country sub-view keeps the returnTo origin instead of dropping it with a hardcoded push, so the later backs return to the caller rather than falling through to home. Both residence selectors (signup step and change modal) share one localized, locale-sorted options builder, so es and pt users see translated country names at signup and the two lists cannot drift. readReturnTo delegates path normalization to isSameRoute, the one trailing-slash rule. The localStorage residence mirrors are read once per account via useMemo, and the legacy-key cleanup runs once per session instead of on every read.
…n-onboarding-xo3iex
The Sprint 157 locale-sync work on dev added marketing-subset catalogs that must mirror the app catalogs; our copy changes regenerate them.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Warning Review limit reached
On-demand reviews are free for the next 25 days. After that, they cost $0.25 per reviewed file. Or wait 5 minutes for your next included review. View limit detailsLimit details: You’ve used all 2 included reviews currently available. Your 57 included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (87)
Comment |
Collaborator
Author
|
@coderabbitai review |
Contributor
|
Contributor
Code-analysis diffPainscore total: 7451.93 → 7609.64 (+157.71) 🆕 New findings (467)
…and 447 more. ✅ Resolved (418)
…and 398 more. 📈 Painscore deltas (top movers)
|
Contributor
🧪 UI test report — ✅ all greenSuites
📊 Coverage (unit)
⏱ 10 slowest test cases
|
innolope-dev
marked this pull request as draft
August 27, 2026 12:35
innolope-dev
added a commit
that referenced
this pull request
Aug 28, 2026
CI's eslint runs the whole repo; my local pass was scoped to the files I had touched at that point, before the onboarding merge brought in three more — the same blind spot that hid the red util test earlier. Three of #2834's files import twMerge straight from tailwind-merge, which the DS bans because the raw version doesn't know the DS token groups and silently drops the classes it can't place. That is not hypothetical on DotFaceAvatar: its face colors are now `fill-avatar-*` / `text-avatar-*` utilities, exactly the shape the wrapper exists to protect. Also drops a Card import left unused when the name-visibility row became a ListItem. eslint: 4 errors -> 0. typecheck, ds-lint and 481 tests across the touched areas still green.
innolope-dev
added a commit
that referenced
this pull request
Aug 28, 2026
…e device No backend change was needed after all — I was wrong about that. /users/me has returned `residence.declaredSecond` since 2026-08-26 (peanut-api-ts, the same review round as the onboarding work): the handler computes it via secondDeclaredResidenceOf and the response schema declares it, so Fastify serializes it today on dev/staging. #2834's comment — "device mirror until the API returns it" — was written before that landed and was never revisited. So the swap now reads the durable server value and falls back to the device mirror only where it is absent: the window before that BE reaches production (it is on dev, not yet on main), or a stale cached user. That closes Chip's fresh-device case, where the mirror does not exist and the reorder wiped the outgoing country. Two tests: a swap with no mirror at all, and a mirror holding a stale country the server disagrees with. Both assert the request body, since asserting the mirror is what let the earlier half-fix look green. Note the FE OpenAPI snapshot does NOT carry declaredSecond — it was hand-carried from #2834 and predates the field. The hand-written ApiUser type is what the app reads, so it is typed there; regenerating the snapshot against a live BE is worth doing separately.
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
1 participant
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.
Frontend half of the registration/onboarding rework. BE: peanutprotocol/peanut-api-ts#1429 (merge that first — every dependency here degrades gracefully without it, but the full experience needs the residence endpoints). Supersedes #2778 and #2775 (their three commits are merged here unchanged — both can be closed when this merges).
Signup flow
signup_step_viewedanalytics + URL step mirroring — every setup step fires a funnel event (screen_id,step_index,nav_type), and the active step mirrors to?screen=via shallow History API so browser/hardware Back walks the steps instead of ejecting the user from/setup. The URL is a mirror, never a source of truth: reload still routes throughdetermineInitialStep, and points of no return (post-passkey) neutralize popstate.GET /config/residence-restrictionswith the bundled mirror as instant fallback.Unlock payments (replaces Unlocked Regions)
UnlockedRegions.view.tsxleft untouched on disk.UnlockMethodModal).Home
Region-restricted rejection screens (from #2778, unchanged)
Localization
Verification