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 want a local copy of the events affecting a given stripe payment, so to aid debugging payments (e.g. customer service trying to shed light on order issues).
What
Add log entries for each payment transition handled by the intents controller.
The content you are editing has changed. Please copy your edits and refresh the page.
elia
changed the title
track all the attempts made on stripe as Solidus log entries (check if there's a way to know if a payment update is stale, given they can come also from webhooks and have latency)
Track all the attempts made on stripe as Solidus log entries
Feb 13, 2023
Does this belong to a record in a Spree::LogEntry ? Should we just store it or is there more logic around it ? Should it be displayed somehow in admin ?
@loicginoux yes, it's related to LogEntry, to which Spree::Payment is connected. In terms of showing the entries they are already visible through the admin in the details page of the payment, although there's surely room for improvement.
elia
changed the title
Track all the attempts made on stripe as Solidus log entries
Track webhook intent events as Solidus log entries on the corresponding payment
Mar 7, 2023
Why
We want a local copy of the events affecting a given stripe payment, so to aid debugging payments (e.g. customer service trying to shed light on order issues).
What
Add log entries for each payment transition handled by the intents controller.
Dependencies
The text was updated successfully, but these errors were encountered: