With all of the user insights/requests and a little researched it came to light that these extra parameters are crucial and play an important role for the Sales-Rep making the sale through the app.
Quick note before you dive in
Quick note before you dive in
Quick note before you dive in
Click on the sections to quickly navigate to the showcase
WizPay - Payment solution for B2B commerce
Scaling to a monthly transactional volume of $5 million+
Click on the sections to quickly navigate to the showcase
WizPay - Payment solution for B2B commerce
WizPay - Payment solution for B2B commerce
Overview
WizPay started as a simple ‘Collect Payment’ button—but as business needs grew, it evolved into a modular, standalone payment layer. Designed to handle diverse B2B use cases, it now supports flexible terms, automated flows, and seamless integration across platforms.
What did we solve and why?
What did we solve and why?
The need and the problems in a traditional payment service, and why it can't be used?
The need and the problems in a traditional payment service, and why it can't be used?
🤯 Complexity of B2B payment processes
Payments in wholesale businesses often involve varied payment terms (Net 30, Net 50, custom agreements) which traditional payment solutions fail to support flexibly.
⌛️ Delays in payment collection
Traditional methods requiring phone calls to collect card information are time-consuming and cumbersome.
🤖 Integration gaps with accounting and ERP systems
Lack of seamless syncing between payment processes and accounting/ERP systems creates duplicate work and the risk of errors in financial reporting.
⛑️ Security concerns
Wholesale payments involve high transaction volumes and large sums; security vulnerabilities can result in substantial financial risks.
🔻 Handling of payment disputes and declines
Payment disputes and card declines increase operational overhead and delay revenue recognition.
🥶 Cost management in high-volume Transactions
Typical payment processors charge fees that are not structured for the wholesale model, leading to higher cost burdens.
🤯Complexity of B2B payment processes
Payments in wholesale businesses often involve varied payment terms (Net 30, Net 50, custom agreements) which traditional payment solutions fail to support flexibly.
⌛️Delays in payment collection
Traditional methods requiring phone calls to collect card information are time-consuming and cumbersome.
🤖Integration gaps with accounting and ERP systems
Lack of seamless syncing between payment processes and accounting/ERP systems creates duplicate work and the risk of errors in financial reporting.
⛑️Security concerns
Wholesale payments involve high transaction volumes and large sums; security vulnerabilities can result in substantial financial risks.
🔻Handling of payment disputes and declines
Payment disputes and card declines increase operational overhead and delay revenue recognition.
🥶Cost management in high-volume Transactions
Typical payment processors charge fees that are not structured for the wholesale model, leading to higher cost burdens.
Payment blocks - Scalable plug and pay design tags
How a single wireframe was scaled to encompass almost 8-10+ B2B payment usecases
How a single wireframe was scaled to encompass almost 8-10+ B2B payment usecases
Invoice handling and various payment collection methods
Recurring payments/ Subscriptions
Send payment link via emails
Invoice handling and various payment collection methods
Recurring payments/ Subscriptions
Send payment link via emails
Authorize and Void cards
Custom refunds back to source/credits
Authorize and Void cards
Custom refunds back to source/credits
Sneak peak into live-prod
Sneak peak into live-prod
Sneak peak into live-prod
WizPay flows catering to multiple use cases of b2b payments
WizPay flows catering to multiple use cases of b2b payments
For better experience please switch to tab/web:)
Results & Impact
120+ customers
Small and mid-sized SMBs across the US wholesale market.
$5.3 Million +
Monthly transactional volume on WizPay, the number keeps increasing as we speak!
120+ customers
Small and mid-sized SMBs across the US wholesale market.
$5.3 Million +
Monthly transactional volume on WizPay, the number keeps increasing as we speak!
Results & Impact
120+ customers
Small and mid-sized SMBs across the US wholesale market.
$5.3 Million +
Monthly transactional volume on WizPay, the number keeps increasing as we speak!
120+ customers
Small and mid-sized SMBs across the US wholesale market.
$5.3 Million +
Monthly transactional volume on WizPay, the number keeps increasing as we speak!
Offline mode- Reducing sync block time by 15 mins
Offline mode- Reducing sync block time by 15 mins
Overview
Offline Mode was a critical feature aimed at supporting sales reps who work in low or no network zones ie, trade expos, warehouses, and remote field operations.
The Challenge
The Challenge
Initial Offline experience was under the hood, lesser informed to the end users
Initial Offline experience was under the hood, lesser informed to the end users
⌛️ Initial sync was heavy and time-blocking
Syncing all required data took time, and in its early form, it blocked the UI.
🫣 No visibility during sync or offline state
Users didn’t know what data was synced or what actions were safe to perform.
⌛️Initial sync was heavy and time-blocking
Syncing all required data took time, and in its early form, it blocked the UI.
🫣No visibility during sync or offline state
Users didn’t know what data was synced or what actions were safe to perform.
The tech solution
We disintegrated the sync data based on how quickly each type could be processed—prioritizing essentials like customers and orders, and deferring heavier media into later stages.
Fragmented sync states
The need and the problems in a traditional payment service, and why it can't be used?
Offline settings and fragmented visible sync process
Offline settings and fragmented visible sync process
Visible/Informative sync updates
Results & Impact
15-30+ minutes
Time saved by implementing incremental sync.
40% Increase
In active usage of offline mode post implementation of sync updates
Notifications - Task manager card UX
Overview
Task Manager Notifications are contextual, in-app alerts designed to keep users informed and in control. Triggered across the platform, they deliver concise summaries, relevant background process details, and clear CTAs—making them both informative and immediately actionable.
The Challenge
The Challenge
The internal pain points emerged as the platform scaled as the major internal channel for our customers
The internal pain points emerged as the platform scaled as the major internal channel for our customers
Scattered System Updates
Important actions (like price updates or modifier approvals) were buried across tools or email threads.
Lack of Context
Users had to switch screens to understand what a task was about.
Scattered System Updates
Important actions (like price updates or modifier approvals) were buried across tools or email threads.
Lack of Context
Users had to switch screens to understand what a task was about.
"Atoms" of a notification card
We designed Task Manager as a lightweight notification system built on three core atoms: category, state, and action. This structure made it easy to scan, understand, and respond—without leaving context.
The notification card structure with it's components and their states
Web hover action
Mobile responsive action bars
Learnings and Takeaways
From zero to something real—this journey has meant diving deep into systems thinking, collaborating across functions, and obsessing over B2B work flows. I’ve worked with multiple PMs, engineers, and stakeholders along the way, shaping workflows that actually hold up in the wild. This isn’t the full picture—just a slice. More to come, more to show.
WizPay - Payment solution for B2B commerce
Scaling to a monthly transactional volume of $5 million+
Click on the sections to quickly navigate to the showcase
The tech solution
We disintegrated the sync data based on how quickly each type could be processed—prioritizing essentials like customers and orders, and deferring heavier media into later stages.
Fragmented sync states
The need and the problems in a traditional payment service, and why it can't be used?
Offline settings and fragmented visible sync process
Offline settings and fragmented visible sync process
Visible/Informative sync updates
Results & Impact
15-30+ minutes
Time saved by implementing incremental sync.
40% Increase
In active usage of offline mode post implementation of sync updates
Notifications - Task manager card UX
The notification card structure with it's components and their states
The notification card structure with it's components and their states
The notification card structure with it's components and their states
"Atoms" of a notification card
We designed Task Manager as a lightweight notification system built on three core atoms: category, state, and action. This structure made it easy to scan, understand, and respond—without leaving context.