Checkout widget transaction hash

[Yash094]

[Dashboard/Portal] Feature: Return transaction hash in Checkout Widget iframe events

Notes for the reviewer

• The checkout widget iframe now includes a transactions array in both success and error postMessage events.
• This array contains { chainId, transactionHash } objects for all relevant on-chain transactions.
• For error events, the transactions array may contain partial data if the error occurred mid-flow.
• Documentation for the iframe integration has been updated to reflect these changes.
• A new example HTML file (TRANSACTION_HASH_EXAMPLE.html) is included for easy testing.

How to test

1. Open apps/dashboard/src/app/bridge/checkout-widget/TRANSACTION_HASH_EXAMPLE.html in a browser.
2. Perform a successful checkout and observe the transactions array in the success event log on the right.
3. Trigger an error (e.g., by using an invalid payment method or insufficient funds) and observe the transactions array (if any) in the error event log.

---

Slack Thread

 

---

PR-Codex overview

This PR adds transaction hash information to the checkout widget iframe's success and error events, enabling developers to track on-chain transactions associated with payments made through the widget.

Detailed summary

• Updated onSuccess and onError handlers in CheckoutWidgetEmbed.client.tsx to include transaction hashes.
• Enhanced documentation in page.mdx with examples for success and error events.
• Created TRANSACTION_HASH_EXAMPLE.html to demonstrate event logging.
• Added changeset in .changeset/checkout-widget-transaction-hash.md for release notes.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[changeset-bot]

🦋 Changeset detected

Latest commit: e7949ea

The changes in this PR will be included in the next version bump.

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
docs-v2	Ready	Preview, Comment	Dec 26, 2025 8:15am
nebula	Ready	Preview, Comment	Dec 26, 2025 8:15am
thirdweb_playground	Ready	Preview, Comment	Dec 26, 2025 8:15am
thirdweb-www	Error		Dec 26, 2025 8:15am
wallet-ui	Ready	Preview, Comment	Dec 26, 2025 8:15am

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch cursor/checkout-widget-transaction-hash-fc5f

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 53.19%. Comparing base (ec73f1f) to head (e7949ea).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8589   +/-   ##
=======================================
  Coverage   53.19%   53.19%           
=======================================
  Files         922      922           
  Lines       61480    61480           
  Branches     4032     4032           
=======================================
  Hits        32706    32706           
  Misses      28676    28676           
  Partials       98       98           

Flag	Coverage Δ
packages	53.19% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

size-limit report 📦

Path	Size
@thirdweb-dev/nexus (esm)	105.66 KB (0%)
@thirdweb-dev/nexus (cjs)	319.47 KB (0%)

[github-actions]

This PR has been inactive for 7 days. It is now marked as stale and will be closed in 2 days if no further activity occurs.