‹ Back

VIRGOPAY BUSINESS

A consumer brand applied to a product with approvals

Fig. 01 / Screen · 2024
VirgoPAY Business — create quote: source and target currency with an optional developer fee
VirgoPAY Business — quote details: a live active-quote countdown with created and expiry times

Business came after Pay and took its brand directly. That was deliberate: same company, same promise, and a merchant deciding whether to route money through us benefits from recognising the consumer product they already trust.

Fig. 02 / Screen · 2024
VirgoPAY Business — Roles Management: a per-section permission matrix with read, edit, create and delete toggles for each role
A brand built for one person, meeting a product with roles.

What it did not carry was structure. Pay's design assumed one person acting alone; Business has entities, senders, beneficiaries, corridors and people with different authority over the same money. Most of the year went into the parts Pay never needed.

Fig. 03 / Screen · 2024
VirgoPAY Business — beneficiaries: a pending-approval list with initiator and approver, and an approved beneficiaries list
Seeing a payment and being able to release it are not the same permission.

The real work was approval. A beneficiary is added by one person and approved by another, and the interface has to make that split visible without making it feel like distrust. The question was never where things sit on the screen but which of them exist for whom — and whether someone who can see a settlement should be able to act on it.

Fig. 04 / Screen · 2024
VirgoPAY Business on mobile — the beneficiaries pending-approval list, a beneficiary profile marked pending review, and the create-new form
Add, review, release — the same split of authority, carried onto mobile.
Next project

Cyclopes

EdTech · Brand + UI · 2019

Designing trust for an algorithm that picks your school

View project