[SDK Scheme Adaptor] Extend Payee requestToPay API process to support the validation of the payer details (3pts)

[PaulGregoryBaker]

Goal:

As a DFSP Using SDK and RTP use case
I want to SDK to support RTP
so that continue to use the SDK to connect to Mojaloop for this use case.

Acceptance Criteria:
Payee Outbound modifcations

• Verify that a separate AUTO_ACCEPT_R2P_PARTY configuration is used for request to pay
• Verify that a PUT \RequestToPay API end point is available to proceed after that Party information is returned when the AUTO_ACCEPT_R2P_PARTY option is false.
• Verify that the Authentication type is supplied in the POST \requestToPay
• Verify that the homeTransactionId is renamed to homeRTPtransactionId

Payer Inbound modification

• Verify that the POST \transactionRequest is update to
  • include that authentication type
  • Add the homeTransferRequestId to the sync response
  • Rename the TransferAmount to TransactionRequestState
• Verify that the AuthenticationType is included on the POST /requestToPayTransfers
• Verify that homeRTPtransactionId is added as an optional parameter to the POST \transactionRequest sync response
• Verify that this end-to-end request to pay flow is functionally tested function

Tests

• Functional Tests need to be added to test this use case.

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:

• API Snippets
  • SDK Outbound
    • Add PUT /requestToPay endpoint in SDK Outbound API in api-snippets
    • Rename homeTransactionId to homeR2PTransactionId in POST /requestToPay
    • Add Authentication type to POST \requestToPay to SDK Outbound
    • Rename requestToPayState to currentState in requestToPayResponse
    • Add getPartiesResponse in requestToPayResponse
    • Add transactionRequestResponse in requestToPayResponse
    • Remove authenticationType in requestToPayResponse
  • SDK Backend
    • Add authentication type to POST \transactionRequest
    • Rename the TransferAmount to TransactionRequestState
    • Add homeR2PTransactionId to POST \transactionRequest sync response
• Payee Outbound
  • Implement PUT /requestToPay handler in SDK
  • Add config param AUTO_ACCEPT_R2P_PARTY to SDK and use it in requestToPay handlers
  • Add homeR2PTransactionId to corresponding handlers
  • Add Authentication type to POST /transactionRequests calls in requestToPay handlers
• Payer Inbound
  • Add authentication type to FSPIOP inbound /transactionRequests to pass to the core backend
  • Rename the TransferAmount to TransactionRequestState
  • ?? Verify that the AuthenticationType is included on the POST /requestToPayTransfers
  • Add homeR2PTransactionId as an optional parameter to the POST \transactionRequest sync response

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:

• feat(mojaloop/3345): enhance payee requesttopay apis api-snippets#162
• feat(mojaloop/3345): enhance requesttopay sdk-scheme-adapter#445
• feat(mojaloop/3345): added requesttopay happy path and reorganised sdk test collections testing-toolkit-test-cases#121

Follow-up:

• N/A

Dependencies:

• N/A

Accountability:

• Owner: TBC
• QA/Review: TBC

[mdebarros]

Hey team! Please add your planning poker estimate with Zenhub @PaulGregoryBaker @vijayg10