Pay-by-Link

Shareable payment links for merchants — and the Nass E-Payment admin that runs the platform behind them

2026·Product Design

Background

Pay-by-Link is a Nass E-Payment service that lets merchants create and share payment links — customers pay without a full storefront integration. Merchants need a focused portal to manage links, brands, and day-to-day sales; Nass needs an admin to onboard merchants, configure the platform, and govern access at scale.

I designed two connected surfaces: a merchant portal for link creation and brand presentation, and a Nass admin for operations, roles, localization, and automation — one visual language so the product reads as one system, not two unrelated apps.

Brand anchor for the merchant and admin experience.

The Problem

Payment-link products often split awkwardly: merchants get a bare link generator while branding, status, and link management live in different tools; operators configure the platform in yet another UI with no shared patterns.

Without a clear merchant overview and a disciplined admin for roles, locale, and automations, support load grows — merchants can’t self-serve brand or link changes, and Nass staff lack a single place to see who can do what.

Pay-by-Link merchant overview before deeper flows — Merchant home — metrics and navigation need to anchor link management without clutter.

Merchant & admin UI

I treated Pay-by-Link as a small design system across two portals: shared tables, forms, status chips, and settings patterns so merchant and admin screens feel like siblings under Nass E-Payment.

The sections below walk through merchant flows (overview, links, brand) and Nass admin (overview, roles, localization, automation configuration).

Merchant overview

01 / 07

The merchant home surfaces link activity, balances, and quick paths into payment links and settings — enough context to act without opening every sub-page first.

Pay-by-Link merchant dashboard overview — Merchant overview — KPIs and navigation tuned for daily link operations.

Payment links

02 / 07

A dedicated payment links view: create, copy, filter, and track link status so merchants can run campaigns and one-off charges from one scannable table.

Pay-by-Link merchant payment links list — Payment links — list, actions, and status for shareable checkout URLs.

Brand settings

03 / 07

Merchants configure logo, colors, and checkout presentation so shared links match their brand — self-serve without Nass support for every tweak.

Edit brand — visual identity controls tied to the customer-facing link experience.

Admin overview

04 / 07

The Nass admin overview gives operators platform-wide visibility — merchants, volume, and entry points into configuration — before diving into roles or automations.

Pay-by-Link Nass admin overview — Admin overview — operational density with clear hierarchy for platform staff.

Roles & access

05 / 07

Role-based access is explicit: who can configure merchants, edit automations, or manage localization — so permissions are auditable, not implied by menu hiding.

Pay-by-Link admin roles and permissions — Roles — permission matrix and assignment for Nass operators.

Localization

06 / 07

Locale and copy settings live in admin so Arabic, Kurdish, and English (and related RTL) can be managed centrally without redeploying merchant UI.

Pay-by-Link admin localization settings — Localization — language and regional strings managed in one place.

Automation configuration

07 / 07

Named automations (notifications, webhooks, workflows) get a configure screen with clear steps and validation — operators see what a rule does before it runs in production.

Pay-by-Link admin automation configuration — Configure automation — stepped setup with explicit naming and scope.

Results · Key takeaways

Pay-by-Link is documented as a dual-portal product direction: merchants own links and brand; Nass owns platform config, access, locale, and automations — with shared components so both sides feel like one Nass E-Payment offering.

Pay-by-Link payment links at a glance — Core merchant workflow — creating and managing shareable payment links.

Key takeaways

Payment links are the product — merchant UI should center the link lifecycle (create, share, track); everything else supports that loop.
B2B fintech needs two audiences in one system — merchant simplicity and admin depth only work when tables, forms, and status patterns align across portals.
Platform config belongs in admin, not in merchant settings — roles, locale, and automations need first-class screens or support becomes the integration layer.