Case studiesBusiness finance software

Peanuds: business onboarding and multi-currency account workflows

Peanuds needed to connect business onboarding with day-to-day account and card workflows. Shahzaib’s engineering work brought those journeys into a dashboard backed by Weavr’s financial-service integration.

Business
Peanuds
Sector
Business finance software
Scope
Onboarding, accounts and spending controls
Contributor
Shahzaib
Editorial illustration: three blank payment-card forms in a dark holder
AI-generated editorial illustration of the project’s domain.

Opening an account and operating it were parts of one journey.

Business account access begins with onboarding and verification steps, then continues into balances, transactions, cards and spending decisions. A fragmented journey leaves users and support teams reconstructing account state across systems.

Different people inside a company also need different permissions. The application had to represent access and spend controls alongside the account information used for routine work.

Connect onboarding to accounts, cards and role permissions.

The Next.js, React and TypeScript application connected KYB and KYC onboarding workflows to the account dashboard. Node.js services integrated with Weavr for the financial-service layer.

The product exposed EUR, GBP and USD account information, card and transaction workflows, and role-based access and spending controls. Provider integration and application permissions were treated as connected requirements.

What the workflow includes

  • Carry business and identity-verification steps through onboarding.
  • Present EUR, GBP and USD account information.
  • Connect card and transaction workflows to Weavr.
  • Apply role permissions and spending controls in the application.

Project details

Peanuds floating UI showing a VISA card, EUR balance, money-flow chart and account details on a dark interface

Project materials showing the workflows and interfaces described in this case.

The business dashboard carried access rules into daily use.

The delivery joined onboarding and account operation in one product, with permissions represented in the daily workflow. The case describes the application and provider integration; regulated services and their terms are defined by the relevant provider.

What this means for the technology owner.

Financial-service integrations require clear responsibility boundaries. The operating record should identify provider accounts, webhook handling, permission rules and reconciliation paths. A team taking over the application needs that context before it changes how money-related state is displayed or updated.

How to hand over software to a new team →

Next.jsTypeScriptReactNodeKYB/KYCMulti-currencyOpen Banking APIVisaWeavr

Project contribution: Shahzaib. The scope described above identifies the work behind this case.

Editorial review: Ego Eimi · Updated September 6, 2026 · About the team

Your technology

Start with the business

Your business depends on it.

Tell us which system matters, what has changed and who controls it. We will define a reviewable next step. Read Foundation and the commitments and evidence.