As described above with reference to FIG. 2, the user interface 200 can include user interface element(s) to enable the configuration of a subscription. In at least one example, a user can interact with the user interface element 226, as illustrated in FIG. 4A. In some examples, the user interface element 226 can be associated with an actuation mechanism and the application 140 can detect an interaction therewith (e.g., actuation thereof). In at least one example, the subscription management component 116 can receive an indication associated with actuation of the actuation mechanism (e.g., from the application 140) and can cause a subscription user interface 400 to be presented via the user interface 200, as illustrated in FIG. 4B. In at least one example, the subscription user interface 400 can be presented via an embedded browser, a modal window, a pop-up, an overlay, a section of the user interface 200, or a new user interface. In some examples, the subscription user interface 400 can be presented by the communication platform (e.g., the subscription management component 116). In some examples, the subscription user interface can be presented by a third-party platform (e.g., via an API). For instance, the subscription user interface can be presented by the third-party platform modal that enables a user to be authenticated using OAuth via an API.
