We’re looking for a specialized fintech/payments development agency (not a generic dev shop) to help us build an MVP for a payments control plane. This is a multi-tenant B2B platform that sits above payment providers and gives our B2B clients (platforms) a single API and console to manage PayIns, PayOuts, and PayOps workflows. The MVP focus is the “core control plane”: tenant model, roles/permissions, provider-agnostic integration layer (adapter pattern), event/webhook processing with idempotency, an internal ledger/transaction model, and the operational console (onboarding/configuration/transaction visibility/export). PayOuts will follow immediately after MVP, but for the MVP we care most about building the foundations correctly so additional rails/providers can be added without rewrites. Important: PayZentric will choose market sequencing and which PSPs/rails to prioritize when the timing is right. We are not looking for a team to “pick” our PSPs. We are looking for a team that can build a provider-agnostic platform and then implement whichever PSP(s)/rail(s) PayZentric selects. What we’re building is not a simple checkout page or single-merchant integration. It’s a platform that must be auditable, reconcilable, operable, and safe under real-world failure modes (retries, duplicates, out-of-order events, partials, reversals). We will only move forward with teams that have deep, proven experience building payments platforms end-to-end (payins, payouts, and payops), including ledger modeling and reconciliation patterns. If your team’s background is primarily general web apps, this won’t be a fit. What we need from the MVP at a high level: a single API for incoming payments (PayIns) and, soon after, outgoing payouts (PayOuts); a web console for onboarding, basic configuration (methods enabled, simple limits), viewing transactions/payouts, and exporting data for finance/reconciliation. We’ll share a more detailed concept document after we shortlist. Must-have experience includes: marketplace/platform payments, multiparty payment flows and/or mass payouts, operational/back-office tools, KYC/KYB workflow integration (via third parties is fine), basic risk/config logic, internal ledger/transaction modeling, and some level of reconciliation against provider reporting. We also expect comfort designing multi-tenant B2B/SaaS systems, clean documented APIs, and admin consoles for ops teams. Screening note: shortlisted teams will be asked to do a technical deep dive where you walk through your proposed ledger posting rules, idempotency/webhook processing approach, and reconciliation strategy (including how mismatches/backfills are handled). We’re looking for concrete implementation depth, not just high-level architecture slides. How we like to work: once shortlisted, we share the concept document; your team reviews and asks questions; you propose a realistic MVP cutline and a phased plan; you provide an estimate with hours by area and clear deliverables. If we proceed, we expect weekly progress updates, clear mapping of hours to deliverables, and source code in repos we control from day one (we own the IP). We also expect a paid discovery/spec sprint before build. If the technical deep dive confirms fit, we’ll move into a 1–2 week paid discovery phase to produce a concise technical MVP spec (service map, high-level ERD/data model, event contracts, ledger posting rules, recon workflow, tenancy/RBAC model) and a delivery plan with milestones, acceptance criteria, and definition of “production-ready.” We are not looking for a licensing dependency on an agency “platform.” If you propose reusing internal components, they must be delivered into a PayZentric-owned codebase with full source and no ongoing licensing/hosted dependency. What to include in your proposal: 2–4 relevant examples of platform/marketplace payments work (especially payouts and back-office tooling), which providers/PSP APIs you’ve integrated, team composition and who would actually be assigned, your proposed stack, and how you scope/estimate MVPs of this complexity (including a rough timeline to a first usable release).