Maher Fayad

Six Clovers

Payment portal, developer docs, and transaction flows connecting corporate finance teams to modern payment rails.

CaseContext

Product Designer

Problemto product

Finance and dev teams needed clear Web3 payment rails.

Portal, docs, and payment flows in one system.

Portal UX for corporate finance and developers.

Context

Six Clovers builds a borderless payment network. Its two audiences, corporate finance teams and the developers who integrate for them, needed very different front doors to the same rails.

What I did

I designed the portal information architecture, the developer documentation experience, and the payment transaction flows as one coherent system.

Key decisions
  • Finance-first language in the portal; protocol details live in the docs, never in the UI.
  • Transaction flows follow familiar banking patterns, initiate then review then approve, so treasury teams onboard without training.
  • Documentation structured as task-based guides rather than API reference dumps.
Result

Shipped portal UX and a documentation system serving both corporate finance users and integrating developers.

Six Clovers — SixClovers 0
Six Clovers — Sixclovers 1
Six Clovers — SixClovers 2
Six Clovers — Sixclovers 3
KeepGoing

What's next

Contactor browse
NextProject
Pexlp

A landing page for a creative agency that had to prove its design craft within the first scroll.

View case study
Contact
Discuss a project

Senior roles, freelance work, or design systems.