Routing Purpose
Processor routing allows Dream OS to match businesses with the right payment partner instead of forcing every merchant into one path. This supports the open bank model and lets Dream OS route based on industry, geography, business size, processing needs, risk level, and partner rules.
Strategic Benefit
Routing keeps Dream OS flexible and prevents lock-in to one processor or bank.
Routing Logic
| Routing Factor | Example Logic | Reason |
|---|---|---|
| Location | Atlanta businesses may route to a local pilot bank partner. | Supports regional bank strategy. |
| Industry | Restaurants may route to a POS-friendly processor. | Better product fit. |
| Risk Level | Higher-risk categories require enhanced review or no routing. | Protects partner relationships. |
| Business Size | High-volume merchants may route to enterprise processor options. | Better economics and support. |
| Bank Relationship | Business can choose its bank or see approved options. | Supports open ecosystem. |
| Feature Need | Store-only, ACH, payout, or treasury needs may route differently. | Avoids mismatched partners. |
Merchant Choice
Routing should support business choice whenever possible, while still respecting partner rules and compliance restrictions.
- Show available partners
- Explain service ownership
- Disclose fees or referral relationships where required
- Avoid implying approval
- Allow status tracking
Risk-Based Holds
Some businesses should not be automatically routed to payments. They should enter review first.
- Incomplete profile
- Prohibited products
- Unclear ownership
- Suspicious activity
- High refund/dispute risk
Bank-safe rule: Dream OS can recommend or route to approved partners, but final approval belongs to the bank or processor.
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.