How Siblings Software built Viking Services' payment operations dashboard

Who is Viking Services?

Viking Services supports independent sales organizations and midsize merchants across the Midwest with next-generation payment processing. Their operations team juggles underwriting, risk, and settlement troubleshooting for hundreds of merchants. To scale without sacrificing service quality, Viking needed a smarter way to orchestrate data from their legacy back-office tools into a single source of truth.

The leadership team asked Siblings Software to partner with their architects and deliver a modern front-end that would sit on top of their existing APIs. The mandate was clear: improve transparency for merchants and internal agents, surface compliance flags sooner, and create space for future roadmap items such as predictive revenue forecasting.

It is the type of engagement that separates payments programs that ship from the ones that drift — the data already existed, the controls already existed, and what was missing was the surface a human could act on at 8:30 in the morning.

The situation we walked into

Viking's operations leaders had a roomful of tools doing the right work in isolation, and no surface that pulled them together. Risk lived in one system, KYC documents in another, settlement state in a third, chargeback dispute notes in a shared drive. Every one of those tools had been the right call when it was bought; the cost only became visible when the team grew past the point where one analyst could remember the path through all of them.

• Disparate homegrown tools made it hard for Viking analysts to read merchant health at a glance.
• Compliance staff were checking PCI DSS checkpoints on manual spreadsheets, which raised the chance of a missed alert during a busy week.
• Onboarding hand-offs between sales and operations required duplicate data entry that consistently delayed activation.
• Leadership lacked consolidated KPIs to plan staffing for the next phases of growth.

How we approached it

1. Discovery sprints: we co-led joint interviews with Viking's merchant success team, prototyped the critical workflows in Figma, and validated usability with real data instead of stand-in fixtures.
2. Incremental delivery: Angular components were built in parallel with API contract hardening on Viking's .NET side, which meant weekly releases into staging instead of one big-bang reveal.
3. Quality foundations: Cypress scripts guarded the complex reconciliation paths first, and the QA automation specialist owned the regression suite from day one rather than hand-testing the long tail.
4. Knowledge transfer: we ran enablement sessions and paired engineering with Viking's internal developers so the dashboard would not be a black box on day 43.

We embedded accessibility from the outset following WCAG 2.1 AA guidelines, which mattered because operations teams use these tools every day for hours at a time.

What we delivered

The dashboard is a single Angular workspace organized around the work an operations analyst actually does in a day: review the queue, clear flagged items, move new merchants through onboarding, and explain settlement timing to a merchant on a phone call. Behind the surface, NgRx holds the cross-module state so the same merchant looks consistent whether the analyst opened it from a chargeback alert or from the onboarding tab.

• Merchant 360 view consolidating risk profile, KYC documents, processing history, and chargeback timeline.
• Onboarding workflow with automated document validation, e-signature prompts, and a progress board that replaced the email chain.
• Compliance alert center surfacing PCI DSS checkpoints as states the team could action, with audit trails of who reviewed what and when.
• Settlement and reconciliation views with anomaly highlights instead of static reports.
• Executive KPI surface blending transaction volume, chargebacks, and SLA adherence for staffing and capacity planning.
• A reusable design system Viking now extends across the rest of their digital roadmap.

Cadence and rituals

The squad ran two-week sprints with a demo and retro at the end of each one and a shared velocity dashboard Viking's leadership could read without translation. Discovery happened in week one alongside the first standups, not before them. By week two, real Angular components were landing in Viking's staging environment, and the team could point at the screen during a stakeholder review instead of describing what was coming.

Ownership and overlap

Every sprint had a Viking architect on the standups for the modules they owned on the .NET side. Our two Angular engineers paired with Viking's internal developers, not just our own. That overlap was the reason the API contracts hardened in pace with the dashboard rather than weeks behind it.

Quality on the inside

Cypress suites covered the reconciliation paths first because that was where regression risk lived, then expanded outward as features stabilized. Azure DevOps pipelines gated every build on lint, unit tests, and the smoke E2E suite, and the QA seat owned the test data lifecycle in staging so engineers were not improvising fixtures on a Friday afternoon.

Knowledge handoff

From the first sprint we wrote architecture decisions down so a Viking engineer joining a year later would be able to read them. Pairing sessions were calendared, not optional. By the time the dashboard went current, the design system, NgRx state model, and component library were ones Viking's own engineers could extend without us in the room.

Outcomes that moved the needle

• New-merchant onboarding cycle dropped 42%, from twelve business days to seven, after document validation and e-signature prompts replaced the manual chain.
• 3x increase in actionable compliance alerts surfaced per week, because PCI checkpoints stopped living in spreadsheets.
• 98% dashboard adoption across internal account teams within the first month — the kind of number that only moves when the tool is actually faster than the workflow it replaced.
• 35% drop in payment reconciliation escalations after the anomaly views replaced static reports.
• Live executive KPIs blending transaction volume, chargebacks, and SLA adherence, which Viking used to plan staffing for the next two growth phases.
• A reusable design system that became the foundation for phases two and three of the digital roadmap.

The engagement was sized and run inside our broader software outsourcing company playbook for dedicated nearshore squads, with the same delivery shape we use today for Angular development outsourcing programs.

Services & capabilities

• Product discovery & UX prototyping
• Angular component engineering
• API contract collaboration with Viking's .NET team
• Automated testing & release management
• Knowledge transfer and enablement

Technology stack

• Angular 15 & TypeScript
• NgRx state management
• Bootstrap 5 & Tailwind-inspired utilities
• RESTful integrations with .NET and SQL Server
• Azure DevOps pipelines & Cypress automation

Related stories

• Sur Technology Holdings payment gateway
• Bari B2B wholesale platform
• All Siblings Software case studies

Frequently asked questions

Five questions buyers most often ask about the Viking engagement — the ones we found ourselves answering on the second and third sales calls.

Ready to build your own payments dashboard?

Whether you are modernizing an existing merchant portal or designing a brand-new experience, our team brings deep fintech context, disciplined delivery, and a human approach to collaboration. We frequently help payment facilitators, ISVs, and marketplaces launch compliant, high-performing platforms their customers actually want to log into.

Talk to us about your roadmap — we can usually spin up a discovery session within a few days and help you scope the first release with confidence.

Schedule a consultation