Banks · Fintechs · Micro-Credit · PSPs · Stable-Coin Issuers
Structured Merchant Data for Underserved Low-Ticket Segments
A data infrastructure layer that supports not replaces your underwriting process.
Compliance & operational boundaries
Two layers, clearly separated
MCBuse owns the infrastructure and data layer. Licensed partners own regulated execution and underwriting decisions.
Infrastructure Layer
MCBuse Accountabilities
- Merchant-facing software deployment
- Data capture & structure pipelines
- Pre-qualified visibility profiles
Regulated Layer
Partner Accountabilities
- Regulated payment execution & settlement mechanics
- Safeguarding, KYC/KYB, and AML compliance ownership
- Credit underwriting & final lending distribution decisions
Review API Data Fields
Example fields (illustrative)
- Merchant business category
- City (Berlin / Munich)
- Transaction volume tier
- Average ticket size band
- Days active since onboarding
Strict privacy restriction: surfaces Level 1–2 info only per the Global Data Classification Framework; Level 3–5 fields remain internal-only.