Layer
Merchant Experience
Risk
Revenue
Brand & Settlement
A templated platform gets merchants onboarded fast but i doesn’t stay flexible once pricing, risk, and retention — the things that actually separate one ISO from another — run on infrastructure someone else owns.
Scaling ISO merchant services on a shared template means every roadmap request waits behind someone else’s priorities, and a competitor on the same platform can copy your pricing logic within a release cycle.
None of this means starting from zero. Card network certification, EMV compliance, and settlement rails are solved problems worth integrating, not rebuilding. The parts worth owning are the ones where an ISO actually competes — pricing, risk, and how the platform feels to merchants and sales agents. The moment growth depends on features baked into someone else’s white label payment solutions, you’ve handed away control of your own margin.

Fabrice Forget
Chief Product Officer, PitchBook
We feel very lucky to have found SPD Technology as our partner. Over the last 10 years, they have totally surpassed our expectations, and day after day we have received incredible value from the team. Here is the secret sauce, just put together your best ideas in your requirements and there is nothing they can’t do!
Every ISO moving off white label payment solutions faces the same question: what needs to be owned, and what’s safe to integrate? The split isn’t about building everything — it’s about owning what actually differentiates you.
Layer | What to Build | What to Integrate |
|---|---|---|
Merchant Experience | Portfolio Management & Merchant Onboarding — the workflow your sales agents and merchants actually experience | Card Network Connectivity — Visa, Mastercard, and network-level certification |
Risk | Underwriting & Risk Logic — your own risk appetite, tuned to the verticals you serve | EMV & Device Certification — terminal compliance every processor has solved |
Revenue | Pricing & Residuals Engine — the commission logic that sets your margin directly | KYC/AML & Identity Verification — established providers already handle this reliably |
Brand & Settlement | Merchant-Facing Brand Experience — dashboards and reporting that feel like your product | Settlement & Payout Rails via Payment Orchestration — infrastructure integrated cleanly, not rebuilt |
Merchant Experience
Risk
Revenue
Brand & Settlement
Portfolio Management & Merchant Onboarding — the workflow your sales agents and merchants actually experience
Underwriting & Risk Logic — your own risk appetite, tuned to the verticals you serve
Pricing & Residuals Engine — the commission logic that sets your margin directly
Merchant-Facing Brand Experience — dashboards and reporting that feel like your product
Card Network Connectivity — Visa, Mastercard, and network-level certification
EMV & Device Certification — terminal compliance every processor has solved
KYC/AML & Identity Verification — established providers already handle this reliably
Settlement & Payout Rails via Payment Orchestration — infrastructure integrated cleanly, not rebuilt
We’ve built exactly this kind of platform before. Here’s the proof.
For five years, SPD Technology collaborated with Poynt to build and maintain reseller-facing payment platforms. Over two years, our engineering team decoupled their Reseller Portal from a legacy monolith, allowing independent sales partners to manage hardware fleets and merchant accounts without system downtime.
SPD Technology engineered the Aggregated Merchant Portal for Blackhawk Network. The system onboarded over 8,000 enterprise businesses within two years, providing unified payment management, clearing, and reconciliation across fragmented retail networks.
Onboarded through a portfolio management platform built for BlackHawk Network, with automated compliance checks built in.
Onboarding time cut from 7 days to under 24 hours for that same merchant portfolio network.
A reseller portal extracted from a monolithic system for Poynt over a two-year engagement.
We build the platform pieces that let you see exactly what owning ISO payment processing actually looks like — before a single line of scope gets written.
A single portfolio view is what we build to keep routing and reporting coherent as merchant IDs multiply across your book — so a growing transaction volume across multiple merchants doesn’t turn into a growing mess in how it’s tracked. Our guide to merchant lifecycle management covers the architecture behind this.
Residual and commission calculations run automatically once we build this layer, which removes the manual reconciliation that quietly eats margin every cycle. The payoff shows up before commissions ever go out: a clear way to compare pricing structures and control processing costs against agents and sub-agents.
We build branded onboarding structured around how you actually sell, with OFAC, EIN, and SSN checks embedded in the flow from day one, before problems have a chance to surface downstream. The result is onboarding logic built around broader Payment Acceptance requirements from the start, so approvals move fast without compliance getting cut short.
Scoring and approval logic gets tuned to the specific verticals your portfolio actually serves, not forced into rules built for someone else’s book — that’s how we approach every underwriting build. Your team ends up with logic that reflects your own risk appetite and the regulatory exposure specific to every vertical you support.
Whether the portfolio holds 80 merchants or 8,000, the reporting layer runs on data infrastructure you own, which we build specifically so visibility into performance and revenue never hits the ceiling of a fixed dashboard template as the book grows. That same layer can also surface additional services and recommendations your team can act on directly.
PCI DSS and KYC/AML requirements get engineered directly into the platform’s core logic in every build we deliver, keeping electronic payments secure and processing systems compliant as new merchants and verticals come online. None of it slows down onboarding or adds a manual review step your team has to work around.
Domain depth, built on reseller and portfolio platforms specifically.
Proven architecture work on the Reseller Portal for Poynt and the Aggregated Merchant Portal for BlackHawk Network, specifically for organizations managing many merchants under one brand — the exact structure an ISO’s own portfolio platform has to support.
Thousands of merchants move through onboarding with OFAC, EIN, and SSN checks engineered directly into the flow, not a manual review process that becomes a bottleneck as the portfolio grows — the same automation an ISO’s own onboarding pipeline needs to hold up at scale.
When a platform needs to come off a monolith without an all-at-once cutover, that’s exactly the kind of decoupling work SPD Technology has already done — extracting a live reseller portal from dependent, tightly-coupled services while migration and new feature work ran in parallel.
Adyen-certified engineers and a KYTE partnership for PCI compliance keep payment and compliance expertise built into the platform core, not treated as a separate line item — so underwriting logic, risk rules, and audit readiness get designed together from day one instead of bolted on afterward.
We follow a structured four-stage software development process designed specifically for payment platform projects.
We audit your current platform setup, processor connections, and sales agent workflows to map exact functional boundaries between your custom core logic and external API integrations. This assessment clarifies how ISOs work with payment processors and other service providers before development starts.
Our system architects design the underlying microservices, database schemas, and API abstraction layers that connect your custom database securely to processors, KYC vendors, and banking rails.
Engineering teams build your custom core components using modern frameworks while establishing staging environments and automated data migration pipelines to transfer legacy merchant records safely.
We execute a phased deployment to live production servers, continuously validating PCI DSS security boundaries before handing over full codebase ownership or providing long-term maintenance support.
By Independent Organizations
SPD Technology designs and develops transformative software solutions that drive innovation, new revenue streams, and market leadership.
An ISO should build proprietary software for merchant onboarding, underwriting risk engines, portfolio analytics, and agent residual calculations. Conversely, standard functionality like point of sale integrations, payment terminals, and credit card terminals should usually be integrated via third-party APIs instead of built from scratch to avoid unnecessary development overhead.
White label payment solutions are pre-packaged SaaS software suites that ISOs rebrand to offer basic gateway and merchant portal functionality. An ISO outgrows these systems when rigid onboarding workflows slow sales growth, or when fixed residual structures prevent complex commission splits for larger sales teams. At that point, the platform itself becomes the ceiling — not the sales team’s ability to close new merchants.
Yes. Custom platform cores can incorporate specialized marketplace logic, such as multi-vendor payment splitting, automated sub-merchant verification, and custom payout scheduling. Integrating these capabilities into your platform allows your sales organization to recruit and support complex e-commerce and SaaS marketplace clients effectively.
Staying on a generic platform leaves your core business logic dependent on an outside vendor’s product roadmap. Building a custom platform core ensures you own your software codebase, retain full database control, and can add specialized underwriting or pricing capabilities whenever market opportunities arise.
Most ISOs move off a templated platform in phases rather than all at once, launching core onboarding and residual tools within months while legacy merchant data transfers incrementally in the background. The full timeline still shifts with portfolio volume, data complexity, and how many third-party APIs are involved — but nothing requires waiting for a single cutover date.
SPD Technology focuses on building your proprietary platform core while connecting your software to existing certified payment gateways and acquirers. We integrate established network interfaces and EMV device management tools rather than wasting client capital re-certifying standard hardware rails. Becoming an ISO involves a formal registration process and typically requires insurance to cover potential losses, which is another reason to integrate certified rails instead of rebuilding them.
From our blog