r3.2

Release Notes

This public release contains the definition and documentation of

• Carrier Billing v0.5.0
• Carrier Billing Refund v0.3.0

The API definition(s) are based on

• Commonalities v0.6.0
• Identity and Consent Management v0.4.0

Carrier Billing v0.5.0

Carrier Billing v0.5.0 is the first public release version for v0.5.0 of the Carrier Billing API.

• This version contains significant changes compared to v0.4.0:

  • Removal of 401 - AUTHENTICATION_REQUIRED
  • New pattern for x-correlator
  • Addition of a new section # Additional CAMARA error responses in info.description field
  • Addition of 404 - INVALID_SINK in createPayment and preparePayment endpoints
  • Addition of 404 - IDENTIFIER_NOT_FOUND in createPayment, preparePayment, confirmPayment and cancelPayment endpoints
  • Addition of 404 - NOT_FOUND in validatePayment endpoint
  • Removal of 403 - CARRIER_BILLING.INVALID_PAYMENT_CONTEXT in retrievePayment and retrievePayments endpoints

• API definition with inline documentation:

  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Added

• New section # Additional CAMARA error responses in info.description field in #229.
• 404 - INVALID_SINK error in createPayment and preparePayment endpoints in #229.
• 404 - IDENTIFIER_NOT_FOUND error in createPayment, preparePayment, confirmPayment and cancelPayment endpoints in #217.
• 404 - NOT_FOUND error in validatePayment endpoint in #217.
• New test for invalid x-correlator in Gherkin .feature files in #230.
• Error 404 testing scenarios in Gherkin .feature files for createPayment, preparePayment, confirmPayment, cancelPayment and validatePayment in #230.

Changed

• New pattern for x-correlator and model aligment with Commonalities in #229.
• Update Gherkin .feature files with Commonalities testing guidelines in #230 and #236.
• Update test for invalid sink in Gherkin .feature files for createPayment and preparePayment endpoints in #230.
• Error schema model alignment with Commonalities in #236.

Fixed

• N/A

Removed

• 401 - AUTHENTICATION_REQUIRED error in #229.
• 403 - CARRIER_BILLING.INVALID_PAYMENT_CONTEXT error in retrievePayment and retrievePayments endpoints in #226.
• Test @*_403.02_phoneNumber_token_mismatch in Gherkin .feature files for retrievePayment and retrievePayments in #230.

Carrier Billing Refund v0.3.0

Carrier Billing Refund v0.3.0 is the first public release version for v0.3.0 of the Carrier Billing Refund API.

• This version contains significant changes compared to v0.2.0:

  • Removal of 401 - AUTHENTICATION_REQUIRED
  • New pattern for x-correlator
  • Addition of a new section # Additional CAMARA error responses in info.description field
  • Addition of 404 - INVALID_SINK in createRefund endpoint
  • Removal of 403 - CARRIER_BILLING.INVALID_REFUND_CONTEXT

• API definition with inline documentation:

  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Added

• • New section # Additional CAMARA error responses in info.description field in #229.
• 404 - INVALID_SINK error in createRefund endpoint in #229.
• New test for invalid x-correlator in Gherkin .feature files in #230.

Changed

• New pattern for x-correlator and model aligment with Commonalities in #229.
• Update Gherkin .feature files with Commonalities testing guidelines in #230 and #236.
• Update test for invalid sink in Gherkin .feature file for createRefund endpoint in #230.
• Error schema model alignment with Commonalities in #236.

Fixed

• N/A

Removed

• 401 - AUTHENTICATION_REQUIRED error in #229.
• 403 - CARRIER_BILLING.INVALID_REFUND_CONTEXT error in #226.
• Test @*_403.02_phoneNumber_token_mismatch in Gherkin .feature files in #230.

New Contributors

• N/A

Full Changelog: r2.2...r3.2

r3.1

Release Notes

This release contains the definition and documentation of

• Carrier Billing v0.5.0-rc.1
• Carrier Billing Refund v0.3.0-rc.1

The API definition(s) are based on

• Commonalities v0.6.0-rc.1
• Identity and Consent Management v0.4.0-rc.1

Carrier Billing v0.5.0-rc.1

Carrier Billing v0.5.0-rc.1 is the first release-candidate version for v0.5.0 of the Carrier Billing API.

• This version contains significant changes compared to v0.4.0:

  • Removal of 401 - AUTHENTICATION_REQUIRED
  • New pattern for x-correlator
  • Addition of a new section # Additional CAMARA error responses in info.description field
  • Addition of 404 - INVALID_SINK in createPayment and preparePayment endpoints
  • Addition of 404 - IDENTIFIER_NOT_FOUND in createPayment, preparePayment, confirmPayment and cancelPayment endpoints
  • Addition of 404 - NOT_FOUND in validatePayment endpoint
  • Removal of 403 - CARRIER_BILLING.INVALID_PAYMENT_CONTEXT in retrievePayment and retrievePayments endpoints

• API definition with inline documentation:

  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Added

• New section # Additional CAMARA error responses in info.description field in #229.
• 404 - INVALID_SINK error in createPayment and preparePayment endpoints in #229.
• 404 - IDENTIFIER_NOT_FOUND error in createPayment, preparePayment, confirmPayment and cancelPayment endpoints in #217.
• 404 - NOT_FOUND error in validatePayment endpoint in #217.
• New test for invalid x-correlator in Gherkin .feature files in #230.
• Error 404 testing scenarios in Gherkin .feature files for createPayment, preparePayment, confirmPayment, cancelPayment and validatePayment in #230.

Changed

• New pattern for x-correlator and model aligment with Commonalities in #229.
• Update Gherkin .feature files with Commonalities testing guidelines in #230.
• Update test for invalid sink in Gherkin .feature files for createPayment and preparePayment endpoints in #230.

Fixed

• N/A

Removed

• 401 - AUTHENTICATION_REQUIRED error in #229.
• 403 - CARRIER_BILLING.INVALID_PAYMENT_CONTEXT error in retrievePayment and retrievePayments endpoints in #226.
• Test @*_403.02_phoneNumber_token_mismatch in Gherkin .feature files for retrievePayment and retrievePayments in #230.

Carrier Billing Refund v0.3.0-rc.1

Carrier Billing Refund v0.3.0-rc.1 is the first release-candidate version for v0.3.0 of the Carrier Billing Refund API.

• This version contains significant changes compared to v0.2.0:

  • Removal of 401 - AUTHENTICATION_REQUIRED
  • New pattern for x-correlator
  • Addition of a new section # Additional CAMARA error responses in info.description field
  • Addition of 404 - INVALID_SINK in createRefund endpoint
  • Removal of 403 - CARRIER_BILLING.INVALID_REFUND_CONTEXT

• API definition with inline documentation:

  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Added

• • New section # Additional CAMARA error responses in info.description field in #229.
• 404 - INVALID_SINK error in createRefund endpoint in #229.
• New test for invalid x-correlator in Gherkin .feature files in #230.

Changed

• New pattern for x-correlator and model aligment with Commonalities in #229.
• Update Gherkin .feature files with Commonalities testing guidelines in #230.
• Update test for invalid sink in Gherkin .feature file for createRefund endpoint in #230.

Fixed

• N/A

Removed

• 401 - AUTHENTICATION_REQUIRED error in #229.
• 403 - CARRIER_BILLING.INVALID_REFUND_CONTEXT error in #226.
• Test @*_403.02_phoneNumber_token_mismatch in Gherkin .feature files in #230.

New Contributors

• N/A

Full Changelog: r2.2...r3.1

r2.2

Release Notes

This release contains the definition and documentation of

• Carrier Billing v0.4.0
• Carrier Billing Refund v0.2.0

The API definition(s) are based on

• Commonalities v0.5.0
• Identity and Consent Management v0.3.0

Carrier Billing v0.4.0

Carrier Billing v0.4.0 is the first public release version for v0.4.0 of the Carrier Billing API.

• This version contains significant changes compared to v0.3.1, and it is not backward compatible:

  • Error model aligment with commonalities, which implies use of normalization values (i.e. enums) for status and code
  • Removal of 403 - INVALID_TOKEN_CONTEXT
  • Removal of 5XX errors
  • Addition of 403 - CARRIER_BILLING.INVALID_PAYMENT_CONTEXT for GET endpoints
  • Addition of applicable 422 traversal exceptions
  • Addition of 429 - TOO_MANY_REQUESTS

• API definition with inline documentation:

  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Added

• Added # Identifying the phone number from the access token section within info.description from Commonalities guideline in #202.
• Added 403 - CARRIER_BILLING.INVALID_PAYMENT_CONTEXT for GET endpoints, to deal with the case where 3-legged Access Token is not valid for payment context, that is paymentId is not related to the phone number associated to the token in #202.
• Added applicable 422 traversal exceptions in #202.
• Added 429 - TOO_MANY_REQUESTS to API endpoints in #202.
• Added Gherkin Testing Linter in #191.
• Generate Tests for 429 Error in #206.

Changed

• Updated # Authorization and authentication section from ICM guideline in #202.
• Error model aligment with commonalities. Normalization values (i.e. enums) for status and code. In #202.
• Updated testing plan in #202.
• Update API specification version and servers.url in #206.
• Update Test Definitions API version in #206.
• Update sink format to uri in #206.

Fixed

• Updated accessTokenExpiresUtc description in #202.
• Some clarifications on descriptions in #202.
• Update @{operationId}_403.01_invalid_token_permissions test wording to be more generic in #206.
• Fix CARRIER_BILLING.INVALID_DATE_RANGE description in #206.

Removed

• Removed 403 - INVALID_TOKEN_CONTEXT in #202.
• Removed 5XX errors in #202.
• Removed sinkCredential from API responses in #206.

Carrier Billing Refund v0.2.0

Carrier Billing Refund v0.2.0 is the first public release version for v0.2.0 of the Carrier Billing Refund API.

• This version contains significant changes compared to v0.1.1, and it is not backward compatible:

  • Error model aligment with commonalities, which implies use of normalization values (i.e. enums) for status and code
  • Removal of 403 - INVALID_TOKEN_CONTEXT
  • Removal of 5XX errors
  • Addition of 403 - CARRIER_BILLING_REFUND.INVALID_REFUND_CONTEXT for GET endpoints
  • Addition of applicable 422 traversal exceptions
  • Addition of 429 - TOO_MANY_REQUESTS

• API definition with inline documentation:

  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Added

• Added 403 - CARRIER_BILLING_REFUND.INVALID_REFUND_CONTEXT for GET endpoints, to deal with the case where 3-legged Access Token is not valid for refund context, that is refundId is not related to the phone number associated to the token in #202.
• Added applicable 422 traversal exceptions in #202.
• Added 429 - TOO_MANY_REQUESTS to API endpoints in #202.
• Added Gherkin Testing Linter in #191.
• Generate Tests for 429 Error in #206.

Changed

• Updated # Authorization and authentication section from ICM guideline in #202.
• Error model aligment with commonalities. Normalization values (i.e. enums) for status and code. In #202.
• Updated testing plan in #202.
• Update API specification version and servers.url in #206.
• Update Test Definitions API version in #206.
• Update sink format to uri in #206.

Fixed

• Updated accessTokenExpiresUtc description in #202.
• Some clarifications on descriptions in #202.
• Update @{operationId}_403.01_invalid_token_permissions test wording to be more generic in #206.
• Fix CARRIER_BILLING_REFUND.INVALID_DATE_RANGE description in #206.
• Fix some Error exceptions CARRIER_BILLING... to CARRIER_BILLING_REFUND... in #206.

Removed

• Removed 403 - INVALID_TOKEN_CONTEXT in #202.
• Removed 5XX errors in #202.
• Removed sinkCredential from API responses in #206.
• Remove Content-Last-Key and X-Total-Count from retrieveRefund and retrievePaymentRemainingAmount operations as they are not applicable in #206.

New Contributors

• N/A

Full Changelog: r1.3...r2.2

r2.1

Release Notes

This release contains the definition and documentation of

• Carrier Billing v0.4.0-rc.1
• Carrier Billing Refund v0.2.0-rc.1

The API definition(s) are based on

• Commonalities v0.5.0-rc.1
• Identity and Consent Management v0.3.0-alpha.1

Carrier Billing v0.4.0-rc.1

Carrier Billing v0.4.0-rc.1 is the first release-candidate version for v0.4.0 of the Carrier Billing API.

• This version contains significant changes compared to v0.3.1, and it is not backward compatible:

  • Error model aligment with commonalities, which implies use of normalization values (i.e. enums) for status and code
  • Removal of 403 - INVALID_TOKEN_CONTEXT
  • Removal of 5XX errors
  • Addition of 403 - CARRIER_BILLING.INVALID_PAYMENT_CONTEXT for GET endpoints
  • Addition of applicable 422 traversal exceptions
  • Addition of 429 - TOO_MANY_REQUESTS

• API definition with inline documentation:

  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Added

• Added # Identifying the phone number from the access token section within info.description from Commonalities guideline in #202.
• Added 403 - CARRIER_BILLING.INVALID_PAYMENT_CONTEXT for GET endpoints, to deal with the case where 3-legged Access Token is not valid for payment context, that is paymentId is not related to the phone number associated to the token in #202.
• Added applicable 422 traversal exceptions in #202.
• Added 429 - TOO_MANY_REQUESTS to API endpoints in #202.
• Added Gherkin Testing Linter in #191.

Changed

• Updated # Authorization and authentication section from ICM guideline in #202.
• Error model aligment with commonalities. Normalization values (i.e. enums) for status and code. In #202.
• Updated testing plan in #202.

Fixed

• Updated accessTokenExpiresUtc description in #202.
• Some clarifications on descriptions in #202.

Removed

• Removed 403 - INVALID_TOKEN_CONTEXT in #202.
• Removed 5XX errors in #202.

Carrier Billing Refund v0.2.0-rc.1

Carrier Billing Refund v0.2.0-rc.1 is the first release-candidate version for v0.2.0 of the Carrier Billing Refund API.

• This version contains significant changes compared to v0.1.1, and it is not backward compatible:

  • Error model aligment with commonalities, which implies use of normalization values (i.e. enums) for status and code
  • Removal of 403 - INVALID_TOKEN_CONTEXT
  • Removal of 5XX errors
  • Addition of 403 - CARRIER_BILLING_REFUND.INVALID_REFUND_CONTEXT for GET endpoints
  • Addition of applicable 422 traversal exceptions
  • Addition of 429 - TOO_MANY_REQUESTS

• API definition with inline documentation:

  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Added

• Added 403 - CARRIER_BILLING_REFUND.INVALID_REFUND_CONTEXT for GET endpoints, to deal with the case where 3-legged Access Token is not valid for refund context, that is refundId is not related to the phone number associated to the token in #202.
• Added applicable 422 traversal exceptions in #202.
• Added 429 - TOO_MANY_REQUESTS to API endpoints in #202.
• Added Gherkin Testing Linter in #191.

Changed

• Updated # Authorization and authentication section from ICM guideline in #202.
• Error model aligment with commonalities. Normalization values (i.e. enums) for status and code. In #202.
• Updated testing plan in #202.

Fixed

• Updated accessTokenExpiresUtc description in #202.
• Some clarifications on descriptions in #202.

Removed

• Removed 403 - INVALID_TOKEN_CONTEXT in #202.
• Removed 5XX errors in #202.

New Contributors

• N/A

Full Changelog: r2.1...r1.3

r1.3

This release contains the definition and documentation of

• Carrier Billing v0.3.1
• Carrier Billing Refund v0.1.1

The API definition(s) are based on

• Commonalities v0.4.0
• Identity and Consent Management v0.2.0

Carrier Billing v0.3.1

Carrier Billing v0.3.1 is a public release (patch release for v0.3.0) of the Carrier Billing API.

• This version contains documentational updates compared to v0.3.0, being backwards compatible:

  • Added a section # Generic Clarification about optional parameters within API Spec info.description field

• API definition with inline documentation:

  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Main changes since r1.2

Added

• New section # Generic Clarification about optional parameters within API Spec info.description field in #183

Changed

• Update README.md with new wiki domain for the Sub-project in #182

Fixed

• N/A

Removed

• N/A

Carrier Billing Refund v0.1.1

Carrier Billing Refund v0.1.1 is a public release (patch release for v0.1.0) of the Carrier Billing Refund API.

• This version contains documentational updates compared to v0.1.0, being backwards compatible:

  • Added a section # Generic Clarification about optional parameters within API Spec info.description field

• API definition with inline documentation:

  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Main changes since r1.2

Added

• New section # Generic Clarification about optional parameters within API Spec info.description field in #183

Changed

• Update README.md with new wiki domain for the Sub-project in #182

Fixed

• N/A

Removed

• N/A

New Contributors

• N/A

Full Changelog: r1.2...r1.3

r1.2

This release contains the definition and documentation of

• Carrier Billing v0.3.0
• Carrier Billing Refund v0.1.0

The API definition(s) are based on

• Commonalities v0.4.0
• Identity and Consent Management v0.2.0

Carrier Billing v0.3.0

Carrier Billing v0.3.0 is the first public release for v0.3.0 of the Carrier Billing API.

• This version contains significant changes compared to v0.2.1, and it is not backward compatible:

  • Within notifications, callback concept named as webhook has been replaced by the terms sink and sinkCredential in accordance with the updated CAMARA Design Guidelines (Adoption of CloudEvent Subscription Model within MetaRelease Fall24 (v0.4.0))
  • Exceptions has also been aligned with Commonalities MetaRelease-Fall24 (v0.4.0), so as some excepctions has changed their HTTP and/or status values.
  • Version designed to work jointly with Carrier Billing Refund API

• API definition with inline documentation:

  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Main changes since r1.1 - rc

Added

• Basic Test cases definition in #174

Changed

• Update User Stories in #172
• Update README.md with meeting info and template alignment in #177
• Update filename to kebab-case format in #178

Fixed

• Align 401 Exception Codes with CAMARA Commonalities in #178
• Align Exceptions naming model with CAMARA Commonalities in #178
• Fix sink property description in #178
• Adjust version and servers.url values aligned with Release Mabagement Commonalities in #178
• Fix externalDocs.url value in #178
• Fix missing required Request Body for confirmPayment operation in #178

Removed

• N/A

Carrier Billing Refund v0.1.0

Carrier Billing Refund v0.1.0 is the first public release for v0.1.0 of the Carrier Billing Refund API.

• This version defines a new API:

  • Initial version covering the following functionality and related endpoints:
    • New endpoint createRefund, both total and partial refunds
    • New endpoint retrieveRefunds
    • New endpoint retrieveRefund
    • New endpoint retrievePaymentRemainingAmount
    • Support for Instance-based (implicit) subscription notification mode

• API definition with inline documentation:

  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Main changes since r1.1 - rc

Added

• Generate User Stories in #172
• Basic Test cases definition in #176

Changed

• Update README.md with meeting info and template alignment in #177
• Update filename to kebab-case format in #178

Fixed

• Align 401 Exception Codes with CAMARA Commonalities in #178
• Align Exceptions naming model with CAMARA Commonalities in #178
• Fix sink property description in #178
• Adjust version and servers.url values aligned with Release Mabagement Commonalities in #178
• Fix externalDocs.url value in #178

Removed

• N/A

New Contributors

• N/A

Full Changelog: v0.2.1...r1.2

r1.1

This release contains the definition and documentation of

• Carrier Billing v0.3.0-rc.1
• Carrier Billing Refund v0.1.0-rc.1

The API definition(s) are based on

• Commonalities v0.4.0
• Identity and Consent Management v0.2.0

Carrier Billing v0.3.0-rc.1

Carrier Billing v0.3.0-rc.1 is the first release-candidate version for v0.3.0 of the Carrier Billing API.

• This version contains significant changes compared to v0.2.1, and it is not backward compatible:

  • Within notifications, callback concept named as webhook has been replaced by the terms sink and sinkCredential in accordance with the updated CAMARA Design Guidelines (Adoption of CloudEvent Subscription Model within MetaRelease Fall24 (v0.4.0))
  • Exceptions has also been aligned with Commonalities MetaRelease-Fall24 (v0.4.0), so as some excepctions has changed their HTTP and/or status values.
  • Version designed to work jointly with Carrier Billing Refund API

• API definition with inline documentation:

  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Added

• N/A

Changed

• Support for non-negative amount and taxAmount values in #152
• Adoption of CloudEvents Subscription Model replacing webhook by sink and sinkCredential concepts as well as aligning callback endpoint for notifications in #152
• Aligment of Exceptions with Commonalities MetaRelease Fall24 in #152
• Alignment of Authorization and authentication section with I&CM MetaRelease Fall24 in #152

Fixed

• Clarifications on descriptions and editorial enhancements in #152

Removed

• N/A

Carrier Billing Refund v0.1.0-rc.1

Carrier Billing Refund v0.1.0-rc.1 is the first release-candidate version for v0.1.0 of the Carrier Billing Refund API.

• This version defines a new API:

  • Initial version covering the following functionality and related endpoints:
    • New endpoint createRefund, both total and partial refunds
    • New endpoint retrieveRefunds
    • New endpoint retrieveRefund
    • New endpoint retrievePaymentRemainingAmount
    • Support for Instance-based (implicit) subscription notification mode

• API definition with inline documentation:

  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Added

• Added new Carrier Billing Refund API with the functionality aforementioned indicated (create a refund, query details of a given refund or a list of refunds, retrieve the amount not yet refunded of a given payment, support for implicit-based subscription) in #152
• Aligned with Commonalities and I&CM MetaRelease Fall24 in #152

Changed

• N/A

Fixed

• N/A

Removed

• N/A

New Contributors

• N/A

Full Changelog: v0.2.1...r1.1

v0.2.1

Changelog CarrierBillingCheckOut

Table of Contents

• v0.2.1

Please be aware that the project will have frequent updates to the main branch. There are no compatibility guarantees associated with code in any branch, including main, until it has been released. For example, changes may be reverted before a release is published. For the best results, use the latest published release.

v0.2.1

Fix over the first release

• API definition with inline documentation:
  • View it on ReDoc
  • View it on Swagger Editor
  • OpenAPI YAML spec file

Added

• N/A

Changed

• N/A

Fixed

• Fix operationId name of callbacks to be unique.

Removed

• N/A

New Contributors

• N/A

What's Changed

• release-v0.2.0 by @PedroDiez in #141
• Create MOM-2024-02-07.md by @PedroDiez in #138
• Update CHANGELOG.md by @PedroDiez in #142
• Create MOM-2024-02-21.md by @PedroDiez in #143

Full Changelog: v0.2.0...v0.2.1

v0.2.0

Changelog CarrierBillingCheckOut

Table of Contents

• v0.2.0

Please be aware that the project will have frequent updates to the main branch. There are no compatibility guarantees associated with code in any branch, including main, until it has been released. For example, changes may be reverted before a release is published. For the best results, use the latest published release.

v0.2.0

Initial baseline contribution

• API definition

Please note

• this "release" is tagged to be the first release of this API.
• there are ongoing discussions about new features/enhancements so API evolution is expected.

Added

• Initial version covering the following functionality and related endpoints:
  • One-Step Payment:
    • New endpoint createPayment
  • Two-Step Payment:
    • New endpoint preparePayment
    • New endpoint confirmPayment
    • New endpoint cancelPayment
    • New endpoint (optional, depending on business case need): validatePayment
  • Obtain Payment(s) information:
    • New endpoint retrievePayments
    • New endpoint retrievePayment
  • Support for Instance-based (implicit) subscription notification mode both in One-Step and Two-Step Payment procedures

Changed

• N/A

Fixed

• N/A

Removed

• N/A

New Contributors

• N/A

Full Changelog: https://github.com/camaraproject/CarrierBillingCheckOut/commits/v0.2.0