Partner Portal UI

Date: 2025-07-17 · Duration: 103.83999633789062 min Organizer: Nader Attendees: Mike, Nader, Raymond

Summary

• Luqra’s mid account secured by Michael allows processing millions through high-risk merchant sub-accounts, enhancing revenue potential.
• Galt expansion includes a 13-location restaurant generating $1.5M in volume and motorsports ticketing, increasing merchant referrals significantly.
• Identifying a third-party virtual bank provider is crucial for automated splitting of payments between partners and merchants.
• The split payment system requires robust loan tracking to avoid overpayment, capturing total loan amount and payment timelines.
• Custom forms will replace the Pay Engine widget for enhanced branding and control in partner portal development.
• A review highlighted the need to include missing merchant table data points such as DBA and sales rep information for comprehensive insights.
• Partner user authentication logic and streamlined merchant application processes are essential for improving user flow in the portal.
• Status management requires enum-based types and clear status messaging for effective communication of transaction statuses.
• Monthly transaction data should be used for clarity in reporting rather than lifetime values, improving visibility into performance metrics.
• A demo with Galt is set to confirm portal functionality and gather feedback from stakeholders for iterative improvements.

Action Items

• Michael Wright Schedule demo call with Galt and his sales team to review partner portal (22:48) Create group chat in Slack with Nader and Showbeat to discuss split payment implementation (08:05) Follow up with Pay Engine about risk category information and POS integration solutions (27:19)

Nader Atrchin Talk to Alexander about merchant table data requirements including DBA, status enums, and merged table functionality (01:14:31) Test split payment functionality and understand virtual bank provider APIs (12:14) Schedule calls with Martin/Ahmad and Alexander/Sparsh to review progress (01:38:00) Send meeting invite for tomorrow’s follow-up session (01:35:31)

Raymond Ehizoba Complete remaining form components and integrate directly with Pay Engine API (01:29:04) Implement status message display functionality with clickable interface (01:08:01) Focus on business logic implementation over styling details (01:32:22) Use single source of truth for UI components from main application (01:13:28)