Thanks Abel
In my opinion, the receipt would be an Attachment, rather than a Document, and it would be created as part of the management of the parent Payment resource. Probably we should consider adding an array of receipts as a specific property of payment. The related entity is normally the entity for which the payment is being made, so not sure if that is appropriate.
I plan to open a JIRA CR for this.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Mar 03, 2023 03:50
From: Abel Ruiz Huerta
Subject: Payment Receipt
Hi Vishrut,
I would say that the OpenAPI you need is TMF667 Document Management. In the resource model of this API you have a relationship with a 'related entity', which might be the related payment, provided by the TMF676 Payment Management.
You could also extend the TMF676, adding a direct reference to that document from the payment resource.
Regards,
------------------------------
Abel Ruiz Huerta
alvatross by SATEC
Original Message:
Sent: Mar 02, 2023 03:56
From: vishrut Goel
Subject: Payment Receipt
Which Open API Spec to be used for POST/GET for Payment Receipt ?
------------------------------
vishrut Goel
Bharti Airtel Ltd
------------------------------