Skip to content
This repository has been archived by the owner on Aug 26, 2022. It is now read-only.

configuration: "flow" parameter for baseline rules and enforcement #206

Open
adamdecaf opened this issue Sep 29, 2020 · 3 comments
Open
Labels
enhancement New feature or request

Comments

@adamdecaf
Copy link
Member

Customers Version: v0.5.0

What were you trying to do?
There are several general use-cases for Customers. One such case is a single funding account per namespace/organization that pays out to N Customers/Accounts. This is handy because the funds are always guaranteed to exist in the funding account and payouts require only ReceiveOnly status.

What did you expect to see?
There should be a configuration option to specify this flow: payouts that prevents debiting these Accounts and to never allow changing their status. We only need the one Validated Customer for funding.

@adamdecaf adamdecaf added the enhancement New feature or request label Sep 29, 2020
@adamdecaf
Copy link
Member Author

Let's add this to GET /configuration/customers as a flow enum.
The first values should be trial (default), payouts, and unrestricted.

@adamdecaf
Copy link
Member Author

cc @joshsadler does this look okay?

@joshsadler
Copy link
Member

@adamdecaf I love this.

@adamdecaf adamdecaf added this to To do in Current Work Sep 29, 2020
@adamdecaf adamdecaf added this to the v0.6 Release milestone Sep 30, 2020
@adamdecaf adamdecaf removed this from the v0.6 Release milestone Feb 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
No open projects
Current Work
  
To do
Development

No branches or pull requests

2 participants