mojaloop
[Mojaloop Connector] Enable home transaction Id to be provided on the outbound PUT \transfers
Goal:
As a DFSP connecting to Mojaloop through the Mojaloop connector
I want to attach my transaction Id to the transfer (HomeTransactionID) at the time of accepting the terms of the transfer, as I am not able to provide this reference when the transfer is innitialised
so that more easiy search and reconcile my transfers.
Background As a Payer DFSP innitiating a transfer using the POST \transfers endpoint on the outbount Mojaloop Connector API, I am not able to provide the hometransactionId, as it is only created after the terms of the transfer have been presented to my customer. I would like to provide this ID in the PUT /transfers.
Acceptance Criteria:
- [ ] Verify that the SDK Outbound API is updated to optionally include the hometransactionid in the PUT \transfers
- [ ] Verify that the Mojaloop Connector is enhanced to make use of and update the transferid-hometransactionid mapping
- [ ] Verify that golden path tests are enhanced to test this result.
- [ ]
Complexity: <High|Medium|Low> > A short comment to remind the reason for the rating
Uncertainty: <High|Medium|Low> > A short comment to remind the reason for the rating
Tasks:
- [ ] TBD [ @? ]
Done
- [ ] Acceptance Criteria pass
- [ ] Designs are up-to date
- [ ] Unit Tests pass
- [ ] Integration Tests pass
- [ ] Code Style & Coverage meets standards
- [ ] Changes made to config (default.json) are broadcast to team and follow-up tasks added to update helm charts and other deployment config.
- [ ] TBD
Pull Requests:
- [ ] TBD
Follow-up:
- N/A
Dependencies:
- N/A
Accountability:
- Owner: TBC
- QA/Review: TBC
Why we need it? In the outbound P2P flow, after the terms of the transfer has been presented, a reservation of the funds is performed in their backend system. To implement our ideal integration, later confirmation or rejection of the reservation, must include the reference to that reservation.