ACH/Wire Position
ACH and wire activity should not be improvised inside Dream OS. These are bank-sensitive rails that require authorization, account verification, fraud screening, audit records, limits, and partner approval. Dream OS should support request workflows and status tracking while the bank or approved treasury partner handles actual movement.
Control Standard
No ACH or wire movement should occur without verified authorization, bank partner controls, and documented approval.
ACH Use Cases
Potential future ACH use cases should be limited and partner-controlled.
- Business subscription payments
- Processor settlement support
- Reward payout funding
- Vendor/sponsor transfers
- Bank-verified account movement
Wire Use Cases
Wire activity is higher risk and should generally be reserved for large approved institutional flows.
- Large sponsor funding
- Approved event funding
- Treasury transfers
- Bank-to-bank movement
- High-value partner settlement
Required Controls
| Control | Purpose | Owner |
|---|---|---|
| Account verification | Confirm bank account belongs to the right business or sponsor. | Bank/processor/KYB vendor. |
| Authorization records | Document consent for debit/credit activity. | Bank/processor with Dream OS recordkeeping. |
| Transaction limits | Reduce loss from fraud or error. | Bank/processor partner. |
| Dual approval | Require more than one approval for high-value movement. | Dream OS admin + partner. |
| Audit logging | Preserve evidence of who requested, approved, and processed movement. | Dream OS + bank/processor. |
| Exception review | Investigate returns, failed transfers, reversals, or disputes. | Bank/processor with Dream OS support. |
Admin Workflow
Dream OS should create an internal request and review workflow instead of directly executing bank transfers.
- Request submitted
- Business/sponsor verified
- Purpose documented
- Admin review
- Partner approval
- Status updated
Fraud Signals
ACH and wire activity should be blocked or delayed when suspicious signals appear.
- Recent account change
- Unverified owner
- High-value first transfer
- Mismatch between business and bank account
- Urgent pressure or unusual destination
Dream OS stays the growth layer. Regulated partners handle the financial rails.
This architecture is designed to protect Dream OS, participating businesses, customers, banks, processors, and sponsors by keeping regulated money movement inside approved financial infrastructure.