Open APIs

Team.. We have a need to map existing customer creation interface to TMF 629. In the current interface we have couple of information captured while preparing customer create request payload.

1. National ID for the customer

2. For scenario where customer having a corporate connection, an indicator whether payment would be made by customer/subscriber her/hemself or would be done by their organisation

Any guidance, what entity/attribute we can use to map such requirements? I want to avoid customising TMF 629 specs to include such information as they seem to be valid requirement.

Hi Chinmohan

For

1. For National ID, you could assume Related party in Customer with Individual using polymorphic discriminators.
2. For payment, it depends if it could well stay with the billing behaviour, hence via billing account. The customer model has account references to link that.

Let me know your thoughts or any other clarifying inputs for your use case.

Hope this is of some help 🙂

Team.. We have a need to map existing customer creation interface to TMF 629. In the current interface we have couple of information captured while preparing customer create request payload.

1. National ID for the customer

2. For scenario where customer having a corporate connection, an indicator whether payment would be made by customer/subscriber her/hemself or would be done by their organisation

Any guidance, what entity/attribute we can use to map such requirements? I want to avoid customising TMF 629 specs to include such information as they seem to be valid requirement.