Design
/
7 - 19 October 2026
ArtoPay Payout Links
Designing a payout-link experience that connects merchant setup, recipient account confirmation, and transfer tracking.
(Project details)
Company
Ojire
Role
UI/UX design and interactive prototyping
Year
7 - 19 October 2026
Connecting merchants and payout recipients
I designed an interactive Payout Links prototype for ArtoPay using OpenAI Codex. The experience lets merchants prepare a fixed-amount payout using recipient contact details, while recipients enter and confirm their receiving account through a separate link.
The prototype connects merchant creation, optional approval, email communication, recipient verification, and payout tracking.

The design challenge
The proposed flow removes the need for merchants to collect bank details before creating a payout link. This shifts account entry to the recipient, creating a need for clear verification, review, and status feedback.
The design needed to explain what each person should do next—and distinguish submitting receiving details from successfully receiving money.
Creating and reviewing a payout link
The merchant enters the amount, recipient contact details, description, and expiry. Additional options include a purpose, reference, internal notes, and approval before sharing.
A review step brings the recipient, amount, and link settings together before confirmation. Funding information provides context without implying that creating the link has already transferred money.

Review the recipient, payout amount, and settings before confirming the link.
Supporting approval before sharing
When approval is required, the link remains unavailable for recipient claims until approved. A rejected request includes a reason, while eligible links can be shared, resent, or cancelled before processing.
This makes approval a distinct step in the payout lifecycle.

Approval controls determine when a payout link becomes available to its recipient.
Connecting the journey through email
I also designed email templates for the payout invitation and recipient verification code.
The payout invitation highlights the merchant, amount, expiry, and a clear “Receive payout” action. The verification email supports the next step: confirming the recipient’s contact before they enter their receiving account.
The prototype includes email previews and simulated resend actions, making the communication part of the flow available for review. No real emails are sent.
payout email

verification-code email

Email connects the payout invitation with recipient verification and account setup.
Guiding the recipient
The recipient journey moves through contact verification, receiving-account entry, and a final review.
Before confirming, recipients can check the bank, masked account number, account name, and payout amount. Where saving recipient details is requested, consent is optional; declining does not block the payout.



Recipients verify their contact and review their receiving account before continuing.
Making payout progress clear
Confirming a receiving account moves the prototype into Processing. A separate result then shows Completed or Failed, so submitting details is not presented as proof that funds have arrived.
Expired, cancelled, rejected, and unapproved links block claims. Processing and completed links also prevent another claim from starting.

processing screens

completed screens

Status feedback separates account submission, transfer processing, and the final outcome.
Bringing the flow to life with Codex
I used Codex to build a working frontend prototype covering merchant and recipient interactions, form validation, approval states, and alternate outcomes.
The prototype makes these behaviors explorable. Payments, email delivery, verification codes, and bank checks are simulated, and demo records are stored locally in the browser.
Deliverable and production considerations
The deliverables include an interactive prototype and supporting documentation of the flows, validation, states, and remaining production decisions.
Production requirements—including verification policies, approval permissions, funding timing, fees, and transfer-provider integration—still require team confirmation. The prototype demonstrates the proposed experience rather than a live money-transfer service.
Next project

