camaraproject/CarrierBillingCheckOut

Release v0.2.1

Closed this issue · 0 comments

Problem description
As stated in MOM-2024-02-21, checking internally API Publication in TEF, it has been advised that callback notifications endpoints has the same operationId "paymentNotification" for 1-STEP and 2-STEP generating some problems, so as different name will be given in order to avoid publication topics. This is not functional topic but a format one, so it will be managed as a fix.

Expected behavior
Rename operationId for callbacks

  • 1-STEP: createPaymentNotification
  • 2-STEP: preparePaymentNotification

Alternative solution
N/A

Additional context
Managed as a Fix for Release v0.2.0, generating Release v0.2.1