# PayGo (Paywise Light) Product Specifications, Meeting Synthesis, and Agent Handoff Backlog The strategic alignment meeting conducted on November 7 established the product scope, functional architecture, and operational rollout plan for **PayGo** (also referenced as Paywise Light). PayGo is designed as a lightweight point-of-sale (EPOS) replacement application and payment ecosystem. It connects merchant retail operations, field delivery fleets, and web portals directly to bank-settled digital payment processing through the main Paywise infrastructure. --- ## 1. Executive Product Vision and Brand Identity PayGo addresses the need for rapid, low-friction digital payment processing at physical points of sale and during field operations. Rather than functioning as a digital wallet that holds customer balances, PayGo operates as a secure transaction pipeline. Funds captured through card payments or tap-to-pay are pushed directly to the merchant's linked bank account via their primary Paywise business account. ### Brand Identity and Market Positioning The visual identity and slogan reflect fast throughput and zero-friction customer interactions: * **Product Branding**: Named **PayGo**, featuring a dual-color brand identity combining green for "Go" and blue for "Pay". * **Brand Slogan**: *"Pay and go your way"*, serving as both the promotional tagline and the theme for idle screen animations. * **Target Audience**: Retail storefront cashiers, mall kiosk operators, delivery drivers, customer service representatives (CSRs), and consumers seeking rapid checkout without cumbersome registration. * **Core Design Philosophy**: High transaction velocity. Point-of-sale interactions must complete within seconds, eliminating manual code entries and one-time password (OTP) delays at the terminal. --- ## 2. Merchant Mobile App Architecture and Workflows The merchant application is optimized for quick entry and hands-free payment verification on counter devices and mobile smartphones. It runs in an active shift mode that removes redundant login prompts during routine sales. ### Point-of-Sale Payment Generation Interface When accepting a payment, the merchant opens the app, inputs the transaction amount, and clicks create. The interface presents payment execution choices structured by operational priority: * **Tap to Pay (Primary Default)**: Uses smartphone/tablet Near Field Communication (NFC) capabilities, allowing customers to tap their phone or contactless card directly against the merchant's device. * **Dynamic QR Code Generation (Primary Secondary)**: Renders a scannable QR code on the merchant's screen for customers scanning with their mobile app or smartphone camera. * **Payment Link Generation (Secondary Priority)**: Positioned below the main buttons with lower visual hierarchy. Designed for remote customer service sales or messaging apps when the customer is not physically standing at the counter. ### Hands-Free Audio Notifications and Post-Payment Actions To support busy cashiers who cannot continually monitor screen displays during customer service, PayGo includes immediate audio and visual feedback controls: * **Audio Status Alerts**: A toggleable text-to-speech notification engine that verbally announces "Transaction Successful" along with the authorized payment amount. * **Post-Payment Screen Flow**: Upon payment authorization, the application offers two immediate actions: * **Show / Share Receipt**: Displays a digital transaction receipt with one-tap options to share via messaging or allow staff to photograph proof of payment. * **Return Home**: Resets the display immediately to the payment entry screen for the next customer. ### Device Pairing, Key Binding, and EPOS Replacement PayGo serves as a direct software replacement for legacy Electronic Point of Sale (EPOS) hardware terminals. Merchants manage multi-terminal store environments through centralized controls: * **Centralized Key Generation**: Store owners generate unique device keys within the central Paywise web portal. * **Terminal Binding**: Cashiers download the PayGo application on store phones or tablets, enter the portal key, and link the terminal to the store account without gaining access to administrative financial settings. * **Read-Only Profile Access**: Staff members can view branch profile information in the app, but profile edits and bank account linking remain restricted to the web portal. * **Transaction Logging**: Cashiers can inspect real-time logs of successful and failed shift payments, with options to re-generate or share receipts. --- ## 3. Customer Mobile Checkout Experience The customer-facing workflow maximizes payment speed while maintaining bank-grade transaction authorization. ### Tiered Frictionless Onboarding To prevent delays in retail checkout lines, PayGo eliminates upfront Know Your Customer (KYC) documentation for card-based purchases: | Onboarding Stage | Information Requested | Functional Behavior | | :--- | :--- | :--- | | **Transactions 1 & 2** | None (Card details provided at checkout) | Immediate payment execution; card credentials saved securely for future one-tap payments. | | **Transaction 3 Onward** | Light prompt for Email Address and Name | Soft account conversion prompt after repeated usage without interrupting the active purchase. | ### Security Protocols and Biometric Authorization PayGo combines smartphone security features with backend bank verification protocols: * **Biometric Authorization**: Customers authorize payments using smartphone fingerprint recognition, bypassing static PINs or manual passwords. * **3-D Secure (3DS) Compliance**: Backend authorization engages 3DS protocols. Any mandatory SMS verification codes received by the customer are issued directly by their card-issuing bank rather than the PayGo application. * **Customer Payment Log**: Consumers can review past PayGo transactions across all participating merchants within their app profile. --- ## 4. Web Portal Integration and Multi-Screen Display Setup For merchants operating desktop terminals or browser-based point-of-sale setups, PayGo integrates directly into the Paywise web portal. ### Desktop Portal and Payment Link Management * **Persistent Web Portal Access**: Terminal computers maintain active portal sessions for store shifts. * **Payment Link Types**: Merchants can generate three distinct payment link options through the web interface: 1. **One-Time Payment Links**: Single-use links that expire after payment. 2. **Recurring Payment Links**: Links with fixed amounts and configurable active time durations. 3. **Open Payment Links**: Links where the customer manually inputs the payment amount. * **Secondary Customer Screen Driver**: Portal setups can drive a secondary display (such as a customer-facing tablet or second screen). The secondary screen displays an animated PayGo logo screen saver in idle mode, presents the dynamic QR code during transaction generation, displays transaction success confirmations, and renders digital receipts before returning to standby. --- ## 5. Client Case Study: Global Trade (GTC) Operational Integration The meeting analyzed the retail footprint of **Global Trade (GTC)** to ground PayGo's feature set in real-world merchant requirements. ### GTC Operations and Delivery Fleet Challenges GTC operates seven local retail locations across Trinidad, comprising three flagship stores and mall kiosks across Town Center Mall, Trinity City Mall, Eastgate Mall, and Tree City Mall. Historically, 95% of GTC orders were paid in cash collected by delivery drivers, creating severe robbery risks. Legacy card terminals (such as RBC Links machines) were decommissioned due to high fixed hardware fees relative to transaction volume. Additionally, GTC required a mechanism to sell fixed-price packages online outside of traditional WordPress e-commerce integrations. ### PayGo Implementation Plan for GTC 1. **Delivery Driver Fleet Deployment**: Drivers equipped with smartphones running PayGo can accept Tap to Pay or present dynamic QR codes on delivery. Alternatively, dispatchers can issue pre-delivery payment links paired with free delivery promotions to incentivize online digital payments. 2. **Agent Portal Conversion**: GTC locations will be onboarded as **Paywise Agents**. This upgrades their terminal UI, enabling store and kiosk staff to accept cash and card payments, process utility bill payments for foot traffic (earning commission), and drive retail volume under secure conditions. --- ## 6. Technical Notes and System Dependencies * **3DS Payment Gateway Migration**: The development team is finalizing the integration of a new primary payment gateway supporting 3DS protocols (currently used for bill payments) by the end of the month to resolve transaction failures and enable infrastructure scaling. * **QR Code Format Discrepancy**: Clarified that personal account QR codes can only be scanned using the native Paywise application, whereas business account QR codes support universal camera scanning to launch web checkout pages. * **Phil's Payment Request Utility**: The mobile app and portal payment generation flows must integrate with Phil's multi-option payment request backend module. * **Idle Logo Screen Saver**: Graphic design and animation assets are required for the standby logo transition ("Pay and go your way"). * **Agent Onboarding Schedule**: A technical setup session is scheduled for Monday after 5:00 PM with the development team (Miguel) to configure the desktop Agent portal. --- ## 7. Structured Agent Handoff Task Backlog This backlog provides a complete list of prioritized tasks for human and autonomous agents executing the PayGo roadmap. ### Mobile App Development Backlog * Build Merchant payment input interface featuring primary **Tap to Pay** and **QR Code** triggers, with lower-priority **Payment Link** option. * Implement native NFC Tap to Pay hardware bridge and dynamic QR code generation component. * Integrate text-to-speech audio notification module broadcasting "Transaction Successful" and the paid amount. * Build post-transaction view providing **Show / Share Receipt** (image/text export) and **Return Home** reset triggers. * Implement key-based device pairing workflow to bind merchant mobile devices to primary Paywise web accounts. * Implement Customer fingerprint biometric authorization module for payment execution. * Build progressive onboarding trigger soliciting customer email/name following the 3rd payment. * Implement read-only merchant profile screen and customer transaction history module. ### Web Portal and Desktop POS Backlog * Develop secondary screen output manager to push QR codes, success states, and digital receipts to customer-facing secondary displays. * Create animated PayGo logo screen saver for standby terminal displays featuring the tagline *"Pay and go your way"*. * Build terminal device management portal tab to generate, name, and revoke merchant device authorization keys. * Implement web interface for generating One-Time, Recurring (fixed amount + duration), and Open payment links. ### Payment Gateway and Backend Infrastructure Backlog * Complete migration to the primary 3DS-compliant payment gateway by month-end. * Build direct settlement pipeline transferring authorized card transactions to merchant bank accounts. * Standardize business QR code formatting to ensure direct camera scanning opens web payment links. * Integrate backend hooks with Phil's payment request feature set. ### Client Onboarding and Operational Backlog (GTC Deployment) * Execute Monday post-5:00 PM technical session with Miguel to configure the desktop Agent portal for GTC. * Onboard GTC's 7 retail locations (Town Center Mall, Trinity City Mall, Eastgate Mall, Tree City Mall) as Paywise Agents for card/cash POS processing and bill payments. * Roll out mobile PayGo application across GTC's delivery fleet for driver card acceptance and payment link distribution.