Arion Pay

Context

Payment and account products are judged in seconds: hierarchy, copy, and confirmation patterns signal whether users should continue. Ambiguity in amounts, timing, or outcomes drives abandonment and support tickets.

Overview

Arion Pay spans web and mobile with flows for payments, balances, and account management. Nightcoders emphasized primary-action clarity, progressive disclosure for secondary detail, and parity between platforms so training and support stay simple.

Challenge

The experience needed to feel current without sacrificing the sobriety people expect around money movement. Every screen had to answer: what am I doing, what will happen when I confirm, and how do I back out safely?

Delivery approach

We organized screens around a single dominant action per view, surfaced fees and timing in plain language where the product required it, and treated confirmations as explicit commitments—not subtle footnotes. Web and mobile share the same mental model so users are not relearning flows on each device.

Technical & operational notes

Financial flows used explicit confirmation steps and restrained visual hierarchy so users always know what will happen next. Parity between web and mobile reduced training burden for support teams explaining the product.

Scope & deliverables

• Payment and transaction flows
• Account visibility and settings
• Web + mobile parity
• Security-minded interaction design

Operational value

Trustworthy financial UX reduces hesitation and support load; we do not cite transaction volumes, conversion rates, or revenue impact we cannot substantiate. For comparable engagements, the next conversation is usually reconciliation rules, processor constraints, and who owns error messaging when a third party declines a payment.