Rather than building a single, generic multi-recipient payment flow, I designed two distinct transfer experiences Multiple Transfer for Retail users and Bulk Upload alongside Multiple Transfer for Corporate users both sharing the same underlying design system but structured around the fundamentally different ways each user type thinks about sending money to more than one recipient.

The Retail Multiple Transfer flow was designed for the individual who occasionally needs to split a payment across a handful of recipients a salary advance to two employees, rent and utilities paid together, or splitting funds between family members. The experience is personal, manual, and conversational: users add recipients one at a time, see each beneficiary card appear inline, and confirm the full list before a single authentication step clears all transfers in one go. The interface keeps every recipient visible simultaneously so the user can review the full picture before committing.

The Corporate experience required an entirely different architecture. A corporate finance team managing payroll for 200 staff members, or disbursing vendor payments across dozens of accounts, cannot add recipients one at a time. For them, I designed a Bulk Upload flow a CSV or Excel file upload with a validation layer that catches errors (duplicate account numbers, mismatched beneficiary names, missing reference codes) before any transaction is initiated. Once validated, the file generates a structured payment batch that flows directly into the Maker-Checker approval workflow. Corporate users also retain access to the manual Multiple Transfer option for ad-hoc multi-recipient payments where a spreadsheet would be overkill.