[5] feat(checkout): transaction status and details pages#786
Merged
Conversation
🦋 Changeset detectedLatest commit: aba5b13 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
tomiiide
changed the title
Add vitest coverage for the session HTTP client and sessions store. Rename the page-local StepActionsList to ExecutionStepActionsList to drop the duplicate component name, and document the Host session memoization contract.
tomiiide
force-pushed
the
checkout/04-checkout-deposit
branch
from
c98fb00 to
d62fd06
Compare
tomiiide
force-pushed
the
checkout/05-checkout-status
branch
from
b3b04db to
efd930a
Compare
Drop duplicate ExecutionProgress* components and export the canonical ExecutionStatusCard/StatusIcon/useExecutionRows stack instead. Also stop shipping src in the published widget tarball.
Gate the Transak debug logger to development (integrator bundlers dead-code-strip it from production) and drop the wallet address from its payload. Read onError/close/cancel/openDepositFlow through latest refs in the SDK init effect so an unstable callback identity no longer tears down and remounts the iframe mid-session. Document useMeshBalance as a non-wired stub that callers must not gate funding on.
Scan all live pending records (not just the connected wallet's key) in useResumeKey and useIsCheckoutBusy, so a deposit-keyed record stays visible once a wallet connects; add useResumeKey regression coverage. Move the useResumeRecord expiry check into useMemo. Hoist the cash/exchange default source token to a shared constant and document the deny-list assumption. Serve exchange/card funding logos from the @lifi/types assets instead of an external CDN.
Expose remainingMs from useFrozenQuote and drop the duplicate per-second interval in TransferDepositPage. Gate the preview-only deposit-error kinds (which render mocked amounts) to development so production only renders the kinds the status poll actually produces (unexpected, address-expired).
Replace the removed ExecutionProgressCards with a checkout-local component built on the canonical widget execution-status primitives.
tomiiide
force-pushed
the
checkout/05-checkout-status
branch
from
efd930a to
f7260d8
Compare
ExecutionStatusCard renders motion's m-components, which stay hidden without a LazyMotion feature provider. Declare motion and wrap the checkout execution card like the widget's own execution page.
tomiiide
changed the title
chybisov
approved these changes
Jul 7, 2026
chybisov
left a comment
chybisov
left a comment
Member
There was a problem hiding this comment.
Approved. Known findings are tracked and deferred to a single fix pass on feat/widget-checkout after the stack merges; Transak onramp session field to be validated in QA before main.
Base automatically changed from
checkout/04-checkout-deposit
to
feat/widget-checkout
July 7, 2026 13:41
…out/05-checkout-status # Conflicts: # packages/widget-checkout/package.json # packages/widget-checkout/src/CheckoutRouter.tsx # pnpm-lock.yaml
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
2 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.
Which Linear task is linked to this PR?
Why was it implemented this way?
This is PR 5 of 8 in a stacked split of the original
feat/widget-checkoutbranch (formerly the single ~16k-line draft #727). The work is broken into reviewable layers that merge bottom-up intofeat/widget-checkout; each PR targets the branch below it.Adds the transaction status, details and status-screen pages (execution status, step list, transfer details) and restores the full router. Completes the widget-checkout flow.
Visual showcase (Screenshots or Videos)
Checklist before requesting a review