You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are creating a refund using stripe version "^17.0.0".
we are calling stripe.refunds.create function and we pass some information in the metadata object.
when the refund is been created we get in the response the metadata.
however when we receive the notification for charge.refunded the metadata obj is empty obj.
To Reproduce
we are creating a refund using stripe version "^17.0.0".
we are calling stripe.refunds.create function and we pass some information in the metadata object.
when the refund is been created we get in the response the metadata.
however when we receive the notification for charge.refunded the metadata obj is empty obj.
Expected behavior
getting the metadata from charge.refunded event
Code snippets
No response
OS
macOs
Node version
Node v18.19.1
Library version
17.0.0
API version
2024-10-28.acacia
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
we are creating a refund using stripe version "^17.0.0".
we are calling stripe.refunds.create function and we pass some information in the metadata object.
when the refund is been created we get in the response the metadata.
however when we receive the notification for charge.refunded the metadata obj is empty obj.
To Reproduce
we are creating a refund using stripe version "^17.0.0".
we are calling stripe.refunds.create function and we pass some information in the metadata object.
when the refund is been created we get in the response the metadata.
however when we receive the notification for charge.refunded the metadata obj is empty obj.
Expected behavior
getting the metadata from charge.refunded event
Code snippets
No response
OS
macOs
Node version
Node v18.19.1
Library version
17.0.0
API version
2024-10-28.acacia
Additional context
No response
The text was updated successfully, but these errors were encountered: