[01] 4.8 Handle Rejections (from Payee)

[elnyry-sam-k]

Goal:
As a Switch
I would like the Rejections (from Payee) to be handled
so that the rejected transfers by FSPs can be catered for as expected.

Tasks:

• Implementation for Handling Rejections (from Payee) in
  • Rejections based on Kafka events are implemented [@ggrg]
  • ML-API-adapter to produce rejection events [@ggrg]
  • ML-API-adapter to cater for fulfill rejections via API calls [@ggrg]
  • Fulfill handler consumes rejection and produces position event
  • Position event handler to consume rejection: decrement position and produce notification, produce transfer
  • Transfer handler to consume rejection and update transfer state to reject
• Unit Tests [@ggrg]
• Integration Tests
• Code coverage [@ggrg]
• Test Rejections end-to-end [@ggrg]

Acceptance Criteria:

• Rejections based on Kafka events are implemented
• ML-API-adapter to produce rejection events
• ML-API-adapter to cater for fulfill rejections via API calls
• Fulfill handler consumes rejection and produces position event
• Position event handler to consume rejection: decrement position and produce notification, produce transfer
• Transfer handler to consume rejection and update transfer state to reject
• Rejection functionality is tested end-to-end

Dependencies:

• None currently

Accountability:

• Owner @mdebarros
• QA/Review

Pull Requests:

• Feature/310 Handle Payee Rejections ml-api-adapter#45

[elnyry-sam-k]

Moving this over to next Sprint as this Sprint is overloaded (at 150%) and doesn't look like we'll get to this and had additional work in deploying 3.3 codebase and fixing bugs related to that (Items #403 , #392