Include metadata in createPayment function of payment method handler

[Draykee]

Description

The metadata that was created in the webhook controller, is passed to the createPayment method of the stripe payment handler but ignored when the actual Payment entity is getting created.

Breaking changes

Screenshots

You can add screenshots here if applicable.

Checklist

📌 Always:

• I have set a clear title
• My PR is small and contains a single feature
• I have checked my own PR

👍 Most of the time:

• I have added or updated test cases
• I have updated the README if needed

Summary by CodeRabbit

• New Features
  • Payment creation now includes additional metadata in the returned information, providing more comprehensive details for each transaction.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	Jul 24, 2025 6:14pm

[coderabbitai]

Walkthrough

The change updates the createPayment method within the Stripe payment handler to include the full metadata object in its return value. Previously, only amount, state, and transactionId were returned; now, metadata is also included. No public API or exported signature was altered.

Changes

File(s)	Change Summary
packages/payments-plugin/src/stripe/stripe.handler.ts	Added metadata to the object returned by createPayment method.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error https://github.com/npm/cli/issues
npm error A complete log of this run can be found in: /.npm/_logs/2025-07-24T18_14_25_391Z-debug-0.log

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f2af49e and a7604e4.

📒 Files selected for processing (1)

• packages/payments-plugin/src/stripe/stripe.handler.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (20)

• GitHub Check: e2e tests (24.x, sqljs)
• GitHub Check: e2e tests (20.x, mysql)
• GitHub Check: e2e tests (22.x, sqljs)
• GitHub Check: e2e tests (22.x, mysql)
• GitHub Check: e2e tests (22.x, postgres)
• GitHub Check: e2e tests (20.x, sqljs)
• GitHub Check: e2e tests (20.x, postgres)
• GitHub Check: e2e tests (22.x, mariadb)
• GitHub Check: e2e tests (20.x, mariadb)
• GitHub Check: codegen / codegen
• GitHub Check: unit tests (24.x)
• GitHub Check: build (24.x)
• GitHub Check: build (22.x)
• GitHub Check: unit tests (22.x)
• GitHub Check: publish_install (macos-latest, 24.x)
• GitHub Check: build (20.x)
• GitHub Check: publish_install (windows-latest, 24.x)
• GitHub Check: publish_install (windows-latest, 20.x)
• GitHub Check: publish_install (ubuntu-latest, 20.x)
• GitHub Check: publish_install (ubuntu-latest, 24.x)

🔇 Additional comments (1)

packages/payments-plugin/src/stripe/stripe.handler.ts (1)

54-66: LGTM! Metadata is now properly included in the Payment entity creation.

The change correctly addresses the PR objective by ensuring the metadata parameter passed to createPayment is included in the returned object. This allows the metadata created in the webhook controller to be properly utilized when creating the Payment entity.

The implementation is clean and consistent with how other methods in this handler return metadata (as seen in the createRefund method).

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[michaelbromley]

Thanks!