Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Scope Enhancement - Line Eligibility for Carrier Billing Service #94

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Scope Enhancement - Line Eligibility for Carrier Billing Service #94

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions ...tation/API proposals/APIScopeEnhancement_Line-Elegibility-For-CarrierBilling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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. <br><em> NOTE: That shall be added by the Working Group. </em> |