Process Flow
This flow describes the Process at a high level. Preconditions- The user is currently authenticated.
- The user has at least one Storefront Gateway Account associated to their Storefront Gateway User ID.
- The user is the Primary of the Account’s associated Group.
- The end selects that they want to remove an account.
- The UI calls the Process, and Storefront Gateway returns a list of User with a list of their currently associated Accounts. Note: The Process response is a list of Storefront Gateway Account IDs. These are internal entity IDs that the user may not recognize. If it has not yet done this, the client application can call the GET /user/accounts API to retrieve the list of all the current User’s associated Storefront Gateway Accounts (each Account entity in the list includes its properties and attributes), and leverage that information to display a clear choice to the end user.
- The user confirms their selection on the UI, and the UI passes that selection back to the Process.
- Storefront Gateway checks whether or not the Storefront Gateway User entity is the Primary User of the Group to which the Account is associated. Note: An user cannot remove an account unless they are a Primary User of Group to which the Account entity is associated.
-
Storefront Gateway removes the Account (and all Subscriptions and Features under the Account) from the following:
- The Storefront Gateway Group with which the A/S/F hierarchy is associated.
- All Users entities currently in the same Group, including the current User.
- The Account, and its Subscriptions and Features (if any), are removed from the current User.
- The A/S/F hierarchy is also removed from any other Users in the same Group.
- The A/S/F is removed from the Group entity, and deleted entirely from the Storefront Gateway data store.
- Specified Account entity was not found.
- Current User is not the Group Primary for the specified Account.
Settings
This Process currently has no relevant settings that configure the Process API response or Process logic/behavior. However, additional settings may be introduced over the course of future releases.User Journey Diagram
This diagram illustrates the standard user journey using the Dissociate Billing Account Process.
Use Cases
The following use cases provide guided API walk-throughs of this Process for client developers:- Dissociate billing account
- Account dissociation errors
- Dissociate billing account
- Dissociate billing account errors

