You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 26, 2022. It is now read-only.
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.
Customers Version:
v0.5.0What 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
ReceiveOnlystatus.What did you expect to see?
There should be a configuration option to specify this
flow: payoutsthat prevents debiting these Accounts and to never allow changing their status. We only need the oneValidatedCustomer for funding.