How to deliver to Front-end developers the behavior spec of a component?

I am working on a new "component" for the company product that I work. The component is like an expansion panel which will have some call to actions that the user has to complete. This actions, the description of the action and the titles will change depending on what stage the user is, like initial state, pending state and approved. So my question is, how to communicate this states to developers because is like how is the behavior of the expansion panel on the different states I am not sure if I have to created different uses cases to solve question from them like "What happen if the user do this?" "What happen if the user do this another thing plus this" I don't know how to deliver that information to developers. in uses cases? in a table on a document in word? This is an example of the "cases" so the component will change depending of the case:

CASE 1: User choose UPLOAD ID, has to wait to be upgraded to KYC1 and notified that his ID was approved.

CASE 2: User choose UPLOAD ID but decide in the same session to try with another option. He tries to Add a top up card and his card is not 3D secure, so he has to do the microtransaction and wait for the code.

CASE 3: User choose UPLOAD ID but decide in the same session to try with another option. He tries to Add a top up card and his card is 3D SECURE, so he is updated to KYC1 and will be notified about his ID that was approved on the notification bell.

Thank you! I hope I explain me well.