From 8f4f0a9b3db3c3d8693cf59f1581a48e7f77a293 Mon Sep 17 00:00:00 2001 From: Jorge Garcia Hospital <129095857+jgarciahospital@users.noreply.github.com> Date: Tue, 1 Oct 2024 12:20:16 +0200 Subject: [PATCH] Create APIScopeEnhancement_Line-Elegibility-For-CarrierBilling.md --- ...ancement_Line-Elegibility-For-CarrierBilling.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 documentation/API proposals/APIScopeEnhancement_Line-Elegibility-For-CarrierBilling.md diff --git a/documentation/API proposals/APIScopeEnhancement_Line-Elegibility-For-CarrierBilling.md b/documentation/API proposals/APIScopeEnhancement_Line-Elegibility-For-CarrierBilling.md new file mode 100644 index 0000000..4305ff5 --- /dev/null +++ b/documentation/API proposals/APIScopeEnhancement_Line-Elegibility-For-CarrierBilling.md @@ -0,0 +1,14 @@ + +| **Field** | Description | +| ---- | ----- | +| API name | [Carrier Billing CheckOut](https://github.com/camaraproject/CarrierBillingCheckOut) | +| New API name | (New API) Line Elegibility Check for Carrier Billing | +| Scope Enhancement owner | Telefonica | +| Scope Enhancement summary | Including the functionality of elegibility check for Carrier Billing API | +| Technical viability | Operators usually check the subscriber's elegibility when a third party applciation (merchant) requests access to a sensitive service like Carrier Billing. Basically, the operator implements some business rules to enable (or not) a given subscriber to be elegible for a given service. The business rules are specific to each operator and shall be kept as an internal policy. This validation is commonly executed during the proper service consumption, so that an error response is raised if user is not elegible for this service. The proposal is to separate such funcionality in an specific API that can help differencing the proper service execution from the prior elegibility check, taking advantage of the same validations that operators already do in the service. Thus, mechants can customize their paywalls so the "carrier billing" payment option is not presented for those users that are non-elegible.| +| Commercial viability | By validating subscriber's eligibility before execution, applications can improve user experience, reduce operational costs, enhance efficiency, utilize data for future optimization and build customer loyalty. This approach prevents late-stage errors, saves resources, and promotes a smoother, more effective digital service.| +| YAML code available? | No | +| Validated in lab/productive environments? | No | +| Validated with real customers? | YES | +| Validated with operators? | NO| +| Supporters in API Backlog Working Group | List of supporters.
NOTE: That shall be added by the Working Group. |