-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(events): Add payment reject audit events #6465
feat(events): Add payment reject audit events #6465
Conversation
Changed Files
|
Hey @AnishKacham , For the UI in the screenshot, you can find the docs to set up Kafka, kafka-ui (the interface in the screenshot) and ClickHouse using Docker Compose here: https://github.com/juspay/hyperswitch/tree/main/crates/analytics/docs and then try generating said events and monitor logs in kafka-ui. Also the docs are self-explanatory but still if in any doubt ping us in this slack channel |
Hey @tsdk02 , I have everything setup for viewing the audit events. But I'm unsure of how to generate them. I've asked on the slack channel as well. Which endpoint do I hit from postman? I checked the hyper switch api reference buy did not find anything specific to "PaymentReject" |
Hey @AnishKacham, I have confirmed with the concerned team, and |
I'll make the changes |
Hey @AnishKacham, a gentle reminder to add the changes to this PR, so it can be merged |
ca7fe0d
to
43cf2b5
Compare
Done. Let me know if something needs to be addressed. |
43cf2b5
to
c2eb699
Compare
c2eb699
to
a69ea2f
Compare
Rebased because of merge conflicts |
a69ea2f
to
4cc668b
Compare
Co-authored-by: Anish Kacham <f2010091@hyderabad.bits-pilani.ac.in>
Co-authored-by: Anish Kacham <f2010091@hyderabad.bits-pilani.ac.in>
Type of Change
Description
Pass along request_state to payment_core
Modify the UpdateTracker trait to accept request state
Modify the PaymentReject implementation of UpdateTracker to generate an event
Additional Changes
Files changed
crates/router/src/core/payments/operations/payment_reject.rs
crates/router/src/events/audit_events.rs
Motivation and Context
Resolves #4669
How did you test it?
This requires FRM related flows to be tested, and may not be tested locally.
Checklist
cargo +nightly fmt --all
cargo clippy