Skip to content
This repository has been archived by the owner on Jan 10, 2025. It is now read-only.

Billing Platform - STRIPE Sub-accounts administration UI #3180

Open
ClaudeROSSI opened this issue Jun 13, 2022 · 1 comment
Open

Billing Platform - STRIPE Sub-accounts administration UI #3180

ClaudeROSSI opened this issue Jun 13, 2022 · 1 comment
Assignees
Labels

Comments

@ClaudeROSSI
Copy link
Contributor

In BILLING Settings, when BILLING_PLATFORM module is enabled, the billing settings tab should grant the admin the possibility to see a list of sub-accounts. This list will show data provided by the new BILLING endpoints.

Interfaces:
image.png

The list should show the columns:

  • ID
  • accountID (internal ID of the stripe subaccount)
  • Status (IDLE, PENDING, ACTIVE)
  • User Name (Name of the business owner)

The account link is not shown. This information is sent by mail to the business owner when triggering the onboarding process.

The list should allow adding a new subaccount - so we have on the top of the list a "Add Sub-account" button opening a dedicated popup. This popup allows (at least) to select the (future) business owner of the sub-account.
By pressing "Save" a sub-account gets created with the initial state (i.e.: IDLE)

On each line, when the state is IDLE we should be able to trigger the onboarding process by calling the corresponding onboard endpoint.
This action transitions the status from IDLE to PENDING, populates the accountLink property and sends it by mail to the owner.

It should be possible to edit the subaccount to change the userID. When the status is PENDING no additional action is possible.

The onboarding process is done via some STRIPE wizard and returns the final accountID. Once we have it the state is set to ACTIVE.

Only the admin can add/edit/onboard a subaccount. There is no plan to allow deleting a subaccount for now!

@ClaudeROSSI
Copy link
Contributor Author

@RohanAntony: Just created that issue for the onboarding process. Let me know if you need more details.

@Ninjeneer: Shall we add an ERROR state to handle the situation where the onboarding process fails?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants