Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
ACQ Sprint 80, ACQ Sprint 81
-
2
-
EBSCO - FSE
Description
Overview
We need to implement the transaction APIs that talk to the storage module.
POST /finance/invoice-transaction-summaries
- Proxy to POST /finance-storage/invoice-transaction-summaries
- Idempotent - if a summary already exists the storage module will return it
POST /finance/payments
- Proxy to POST /finance-storage/transactions
- Out of scope - we might want to add some "retry" logic here in the future.
POST /finance/credits
- Proxy to POST /finance-storage/transactions
- Out of scope - we might want to add some "retry" logic here in the future.
See the wiki for details.
Also see this spike page for additional context.
Scope
- Payments
- Credits
- invoice transaction summaries
- While we might want to add some retry logic at some point, for now these endpoints mostly just proxy to storage.
Acceptance Criteria
- APIs are defined and Implemented
- Raml / ModuleDescriptors are created/updated
- Unit tests are added
- API tests are updated
TestRail: Results
Attachments
Issue Links
- blocks
-
MODINVOICE-109 Create payment or credit when Invoice marked as 'Paid'
-
- Closed
-
- clones
-
MODFIN-70 Create transaction APIs - Allocations, Transfers, Encumbrances
-
- Closed
-
- has to be done after
-
MODFISTO-28 Transaction Calculations - Payments/Credits
-
- Closed
-
-
MODFISTO-46 Update transaction schema
-
- Closed
-
- has to be done before
-
MODINVOICE-113 Call awaiting-payment API upon invoice approval
-
- Closed
-
- relates to
-
MODFIN-112 Shouldn't allow negative payments or credits
-
- Closed
-
-
MODFISTO-87 Able to apply transactions after all or nothing operation was performed
-
- Closed
-
-
UXPROD-2167 Value management through transactions Part 2 - Payments, Credits and limits
-
- Closed
-