Processor Role
Processors handle the regulated and card-network-sensitive parts of merchant payments: underwriting, card acceptance, tokenization, settlement, chargebacks, refunds, disputes, payment security, and merchant risk controls.
Dream OS should provide the merchant-facing software layer: onboarding screens, status tracking, analytics, store orders, business dashboards, support workflows, and partner routing.
Boundary
Dream OS should not store raw card numbers, CVV codes, or act as the merchant acquirer unless properly approved and structured.
Processor Capabilities Needed
A strong processor partner should support small business onboarding, hosted checkout, API integrations, webhooks, dispute workflows, risk monitoring, and reporting.
- Hosted checkout or tokenized components
- Merchant onboarding/KYB
- Settlement reporting
- Refund and chargeback tools
- Webhook event verification
Dream OS Capabilities Provided
Dream OS adds merchant acquisition, dashboard visibility, campaign engagement, store activity, lead tracking, and customer analytics around the processor relationship.
- Merchant dashboard
- Order management
- Campaign-driven commerce
- Analytics and lead reporting
- Partner application routing
Processor Decision Matrix
| Question | Why It Matters | Preferred Answer |
|---|---|---|
| Can they underwrite merchants? | Dream businesses need approval before taking payments. | Yes, processor handles underwriting. |
| Can they support marketplace or connected accounts? | Dream may route many businesses through one platform experience. | Yes, with sub-merchant or connected-account tools. |
| Can they tokenize payment data? | Reduces PCI burden on Dream OS. | Yes, no raw card storage required. |
| Can they manage disputes? | Chargebacks are processor/card network matters. | Yes, merchant and platform visibility available. |
| Can they support bank partnerships? | Dream wants banks involved across regions. | Yes, flexible sponsor or referral model. |
Processor Revenue Model
Dream OS can monetize merchant processing through referral fees, rev-share, platform fees, sponsored packages, or bank-funded bundles. Any model must be disclosed properly and approved by the partner agreement.
- Per-merchant referral
- Basis-point processing share
- Monthly technology fee
- Bank-subsidized growth package
Risk Controls
Processors will care about industry type, chargeback ratios, refund behavior, prohibited products, fraud, identity verification, and transaction volume.
- Business category screening
- Velocity monitoring
- Refund/dispute ratios
- Manual review queues
- Prohibited product controls
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.