Adding events for Payment Reject

[lsampras]

Created from #4525

This covers adding events for Payment Reject operation

This event should include the payment data similar to PaymentCancel

It should also include any metadata for the event
e.g reason for payment rejection, error codes, rejection source etc

[aadityasinha-dotcom]

Hi @lsampras can I work on this issue?

[lsampras]

Hey @aadityasinha-dotcom , this is already claimed by @subhajit20,
You can check for similar issues in the tracking issue #4525

[aadityasinha-dotcom]

@lsampras sure np!!

[subhajit20]

hey @lsampras can I take this issue?

[Rutam21]

@swangi-kumari This issue has been inactive for a long time now. I want to take this up. Please assign this to me. Thanks.

cc: @srujanchikke

[gorakhnathy7]

Hey @subhajit20 Are you still working on this issue?

[AnishKacham]

Hey, I would like to work on this issue. The other issue I was assigned is approved and only left to be merged.

[gorakhnathy7]

Hey @AnishKacham Assigned to you, as this was inactive for a while.

[AnishKacham]

@lsampras How do I know what all metadata to send in the audit event. I understand that PaymentCancel audit event is given as an example.
Is there any place where the different fields of PaymentData struct are documented to understand which fields can go as a metadata for a PaymentReject?

[lsampras]

Hey @AnishKacham,
This is a bit subjective the goal is to capture all relevent context available with that change/transition,
you can start off with an empty event and reviewers can point out any fields that need to be added or removed from the event...