Hello Jonathan,
Apologies for the confusion caused here.
Anonymous in my view, Customer can come and make the payment for his own account for his friend's relatives account. So here, the customer can enter his account or friends information to proceed with the due payment.
The due amount can be his monthly/quarterly bill comprises of mobile bill/broadband bill/TV or any other services associated with the account.
The use case here is customer needs to enter either account number/landline number/ mobile number associated with his billing account. After validating the input, the customer can pay how much amount he want w.r.t that account. Here validation means just validate whether the given input (landline/mobile number) is associated with any account or not, if so we will return the client with the corresponding account number.
Since we have no idea of who actually paying on this account, that's why I called this call as anonymous.
I have verified the TMF 666 Account Management (/billingAccount/{id}) which could retrieves the billing account Entity. I feel this can be best suited, though I just need to return the billing account id to confirm the validation. Here {id} can be either mobile number/phone number/billing account id. Hope I am going in right direction.
------------------------------
veera chopperla
BT Group plc
------------------------------
Original Message:
Sent: Nov 29, 2021 03:53
From: Jonathan Goldberg
Subject: TMF Open API For Customer Input Validation
Sorry Veera, but I'm still not clear what exactly you are trying to achieve:
- What sort of payment is this (postpaid bill, prepaid topup, deposit, payment of one-time charge during order, etc.)
- What does it mean - anonymous - if the end user is entering some details they are surely no longer anonymous
Please clarify the exact business use case and your suggested user interaction flow. This will help discover which APIs might be relevant.
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
Original Message:
Sent: Nov 29, 2021 00:00
From: veera chopperla
Subject: TMF Open API For Customer Input Validation
Hello Jonathan,
We have anonymous payment usecase, where customer needs to enter either phone number or mobile number or account number to make the payment.
After success validation, the payment can be taken from the customer.
Please suggest which API operation can be suitable for this.
------------------------------
veera chopperla
BT Group plc
Original Message:
Sent: Nov 27, 2021 13:39
From: Jonathan Goldberg
Subject: TMF Open API For Customer Input Validation
Hi Veera
Can you clarify in more detail what your use case is?
Are you trying to identify a customer by contact telephone number, or a particular bill document, or what?
There could be many possible APIs relevant, depending on your exact use cases, e.g.
- TMF629 Customer Management
- TMF637 Product Inventory
- TMF666 Account Management
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
Original Message:
Sent: Nov 24, 2021 22:15
From: veera chopperla
Subject: TMF Open API For Customer Input Validation
Hi Team,
I have a requirement to expose Open API spec to validate the customer entered input data.
The input data can be either (Landline number/ Account Number/ Mobile Number). Post validating the data, application will allow the customer make the payment.
Can somebody recommend if any Open API spec available for this requirement.
We will get only one input here and output will be validation success or failure kind of API.
------------------------------
veera chopperla
BT Group plc
------------------------------