Refund Functionality - Issue#104

WG

ONGOING

PR#152 IN PROGRESS

Updates since before meeting:

• Alignment with Commonalities Notifications model Release Fall24 (sink, sinkCredential) (commit 4d03b24)

  • Orange (Ludovic) raise the point about notificationsBearerAuth, coming from Geofencing PR. Pedro will check internally with Jose and comments that the Access Token type was indicated as enum "bearer" to mark that thas is the format allowed to be used for the Access Token in the Authorization Header in the POST /callback.

• Fixing some typos in exceptions and descriptions (commits e2be576, 8d079e3 and a647dea)

• Discussion on paymentItemId: added an `id` in paymentDetails and coherently `paymentItemId` in refund Details (commit 9c723cd)

  • Some comments from Ericsson (Ajit, Barath) about the context of its use. Explained it is required when using paymentDetails to provide properly correlation for related refunds. In `refund` scope along with it it is also needed to indicate amount in order to be able to perform both full and partial item refunds.

Error Model aligment with Commonalities Meta-Release Fall24

WG

ONGOING

Related to Commonalities PR#213 - error_model_alignment. 

Attached within the Issue an Excel document to compile the proposed changes based on aforementioned PR (already agreed). Explained in the meeting the rationale applied and the proposed changes.

It needs WG Team review in the next days in order to agree in the changes finally applied.

Notifications Model aligment with Commonalities Meta-Release Fall24

WG

DONE

Covered within PR#152