Unico Connect PRD Example (2026)

Migrant workers sending money home face a broken system: high fees (averaging 6.5% of amount), opaque exchange rates with hidden margins, and transfer delays of 2.4 days, forcing families to wait for essential funds or resort to insecure informal channels. This pain is quantified: a worker loses $15 per $200 transfer versus fair market rates, and spends 45 minutes in-person for KYC, eroding their time and trust.

The business case is 2 million migrant workers in the India-UAE corridor (source: World Bank Migration Data 2023) × 12 transfers/year (assumption — validate with user interviews before funding) × $15 saved per transfer versus incumbent average fee (source: World Bank Remittance Prices Worldwide Q4 2024) = $360M/year in value delivered to users. If adoption reaches only 40% of estimate: $144M/year. Build cost is $48K (source: regional cost benchmarks for India-based Bubble/Xano team, 6 weeks at $8K/week).

This product IS a mobile-first remittance MVP with no-code backend for rapid compliance and payout integrations. It is NOT a multi-currency banking account, a cryptocurrency exchange, or a platform for business invoicing — funds move sender-to-recipient only via regulated rails.

Wise solves this by offering mid-market FX rates and low fees for tech-savvy users who prioritize cost over agent access. Remitly solves this by focusing on migrant corridors with cash pickup networks for recipients without bank accounts. Traditional banks (e.g., HSBC) solve this by providing trusted branding but with high fees and slow service for existing customers.

Our wedge is UPI payout in India because 300 million Indian users already use UPI for daily transactions (source: NPCI 2024 data), and no major cross-border player supports it directly, reducing recipient friction from bank visits.

WHO / JTBD: When a migrant worker in the UAE finishes a work shift, they want to send money to their family in India with low cost, full fee transparency, and instant receipt — so their family can pay bills without losing a portion to hidden charges or waiting days for clearance.

BEFORE: Raj, a construction worker in Dubai, needs to send 1,000 AED to his wife in Mumbai. He visits a bank branch during his lunch break, waits 20 minutes, presents his passport and visa for manual KYC, receives a quoted exchange rate with a 3% margin he doesn’t understand, pays a 50 AED fee, and is told the transfer will take 3 business days. His wife must visit her bank to withdraw the funds, paying another 100 INR charge.

COST:

Annual impact per worker: 12 transfers × $13 loss × 2 million workers = $312M in fees and margin loss. Adding 45 minutes × 12 trips = 9 hours/year in lost productivity per worker ($180 at $20/hr wage). This feature targets recovering $15/transfer in saved cost and time.

AFTER: Raj opens Unico Connect on his phone, completes KYC in 5 minutes by uploading his Emirates ID and a selfie, sees a live FX rate with zero margin, enters 1,000 AED, selects his wife’s UPI ID, and confirms. His wife receives funds in her mobile wallet within 90 seconds, with a notification.

JTBD statement: “When I need to send money home, I want to complete the transfer quickly with low fees and full transparency, so my family receives the funds without delay or hidden costs.”

Integration Map:

• Reads: User data (Bubble UI → Xano DB), FX rates (Stripe API), KYC results (External provider API), transaction status (Razorpay API).
• Writes: User profiles (Xano DB), transaction records (Xano DB), payout instructions (Razorpay API), referral codes (Xano DB).

Core Mechanic: User completes KYC via liveness check, links sender bank account via UPI or account number, enters amount and recipient country, sees locked FX rate, confirms, and funds are pulled via Stripe, routed to Razorpay for local payout to bank/UPI, with status tracked in real-time.

Primary User Flow:

1. Onboarding: ID upload + liveness check → KYC approval in <2 minutes.
2. Send flow: Amount entry → country selection → FX display → recipient detail entry (mobile number for UPI) → confirmation → status tracking.
3. Payout: Automated to recipient’s linked bank/UPI within 90 seconds.

Key Design Decisions:

• Use Bubble for frontend to enable rapid UI changes without native app delays.
• Use Xano as backend for no-code logic, scaling to ~10k transactions/month initially.
• Integrate Stripe for UAE AED collections and Razorpay for INR payouts to leverage existing regulatory licenses.

Scope Boundary: This MVP handles only UAE (sender) to India (recipient) corridor with AED to INR transfers. All other corridors are out of scope. Admin dashboard is read-only for monitoring, no manual intervention.

Critical Path Integration: Razorpay UPI payout API contract finalization (owner: CTO, due: week 2), KYC provider selection (owner: Compliance Lead, due: week 1).

ASCII Wireframe Screens:

┌─────────────────────────────────────────────────────────────────┐
│ KYC Onboarding                                    [Skip →]      │
├─────────────────────────────────────────────────────────────────┤
│ Upload Emirates ID Front:        [Choose File]    [✅ Uploaded] │
│ Upload Emirates ID Back:         [Choose File]    [⬜ Pending]  │
│ Live Selfie Check:               [Start Camera]   [⬜ Pending]  │
│ Status:                          Verifying...      [2 min est]  │
└─────────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────┐
│ Send Money                                        [Cancel]      │
├─────────────────────────────────────────────────────────────────┤
│ Enter Amount (AED):              [1,000          ] [Max: 5,000] │
│ Recipient Country:               India ▼          [Fee: $2.50]  │
│ Exchange Rate:                   1 AED = 22.65 INR [Locked 10s] │
│ Recipient Gets:                  22,650 INR       [Via UPI]    │
│ Recipient UPI ID:                [97865xxxxx@okhdfcbank ]       │
│                                   [Confirm Send →]              │
└─────────────────────────────────────────────────────────────────┘

Phase 1 — MVP (6 weeks)
US#1 — KYC Onboarding

• Given a new user opens the app
• When they upload Emirates ID front/back and complete a liveness check
• Then KYC status updates to “verified” within 120 seconds with 100% consistency — zero tolerance (launch-blocking)
• If story fails, users cannot send money, blocking all transactions.
• Validated by Compliance Lead against 50-sample test batch.

US#2 — Send Money Flow

• Given a verified user with linked UAE bank account
• When they enter 1,000 AED, select India, and confirm recipient UPI ID
• Then they see a locked FX rate with ≤0.7% margin, and transaction initiates with 95% success rate within 5 seconds
• If story fails, funds may be stuck in processing, requiring manual escalation.
• Validated by Product Manager against 20 live transactions.

US#3 — Payout Execution

• Given a completed transaction
• When payout is triggered to Indian UPI ID
• Then recipient receives funds within 90 seconds p95, with notification, and status updates in app
• If story fails, recipient does not get funds, leading to support tickets and reputational damage.
• Validated by Ops Lead against 20 live payouts.

US#4 — Transaction History

• Given a user has sent money
• When they view transaction history
• Then they see all past transactions with status (completed/failed) and fee breakdown, with ≥99.5% accuracy
• If story fails, users cannot reconcile transfers, increasing support calls.
• Validated by QA against 100 synthetic transactions.

Out of Scope (Phase 1):

Phase 1.1 — 4 weeks post-MVP:

• Add bank transfer payout as fallback option
• Enhance admin dashboard with alerting for failed transactions
• Integrate with CRM for referral tracking

Phase 1.2 — 8 weeks post-MVP:

• Expand to Saudi Arabia-UAE corridor
• Add bulk send for multiple recipients
• Advanced compliance reporting for audits

Primary Metrics:

Guardrail Metrics (must NOT degrade):

What We Are NOT Measuring:

• Number of app downloads (vanity; doesn’t indicate active senders)
• Social media mentions (no direct correlation with transaction volume)
• Time spent in app (could be due to confusion, not engagement)
• Total transaction value (inflated by large one-off transfers; we focus on frequency and cost savings)

Risk 1 — RBI Payment Aggregator License Not Obtained

• Probability: Medium Impact: High
• Trigger: Launch attempt without RBI PA license → causes payout block via Razorpay → which leads to failed transactions for Indian recipients → resulting in user churn and legal penalties.
• Mitigation: Apply for RBI PA license through Razorpay’s partner program (owner: Compliance Lead, deadline: week 4). If not cleared by week 6, launch is blocked; fallback to manual escrow account with increased cost and delay.

Risk 2 — UAE Central Bank KYC Non-Compliance

• Probability: Low Impact: High
• Trigger: Onfido verification fails UAE regulatory audit → causes mandatory shutdown → which leads to frozen funds and reputational damage.
• Mitigation: Pre-launch validation with UAE legal counsel (owner: Legal, deadline: week 3). If breached, switch to regulated UAE KYC provider with 2-week integration delay.

Risk 3 — Low User Adoption Due to Trust Deficit

• Probability: Medium Impact: Medium
• Trigger: New brand lacks credibility vs. Wise/Remitly → causes <10% conversion from signup to first send → which leads to CAC exceeding LTV → resulting in unsustainable growth.
• Mitigation: Implement referral system with cash incentives for early users (owner: Growth Lead, deadline: week 5). If D30 adoption <5% of target, pivot to partner white-label for established brands.

Risk 4 — Razorpay UPI Payout API Reliability

• Probability: Medium Impact: High
• Trigger: Razorpay API downtime >0.1% → causes payout delays >5 minutes → which leads to recipient complaints and support overload → resulting in loss of trust.
• Mitigation: Cache successful payout receipts for 24 hours, implement retry logic with exponential backoff (owner: Backend Lead, deadline: week 4). If failure rate >2% in any week, integrate backup payout provider.

Kill Criteria — we pause and conduct a full review if ANY are met within 90 days:

1. Transaction success rate remains below 90% at D90.
2. Cost per transfer exceeds $10.00 at D90 (no savings delivered).
3. KYC completion time exceeds 10 minutes at D90 (user friction too high).
4. Regulatory clearance (RBI PA license) not obtained by launch date.

Integration Map (Detailed):

• Bubble Frontend: Handles UI, user input, and displays real-time data. Communicates via REST API to Xano.
• Xano Backend: Manages user database, transaction logs, referral codes, and business logic. Exposes APIs for:
  • User management (CRUD)
  • Transaction initiation and status
  • KYC webhook handling
• External Services:
  • Stripe: Processes AED payments from UAE bank accounts, provides FX rates.
  • Razorpay: Handles INR payouts to Indian bank/UPI, compliance reporting.
  • Onfido: Executes KYC verification (ID scan + liveness).
• Data Flow: User → Bubble → Xano → Stripe (pull funds) → Xano → Razorpay (push payout) → Recipient.

Assumptions vs Validated Table:

Decision: Backend architecture choice
Choice Made: Xano (no-code) over custom Node.js server
Rationale: Xano provides built-in database, API endpoints, and scalability to 10k transactions/month within 6-week timeline; custom code would require 3+ months and dedicated backend engineer. Rejected Firebase due to weaker query capabilities for compliance reporting.

Decision: FX rate sourcing
Choice Made: Stripe’s FX API over custom aggregator
Rationale: Stripe offers real-time rates with 0.5% margin for our volume, compliant reporting, and existing integration path; custom aggregator would add compliance overhead and latency. Wise API was rejected due to exclusivity clauses.

Decision: KYC provider
Choice Made: Onfido (global) over India-specific provider
Rationale: Onfido supports UAE ID documents and liveness checks with 98% accuracy, essential for UAE corridor; India-only providers lack UAE coverage. Cost is $1.50/verification, acceptable for MVP.

Decision: Payout method priority
Choice Made: UPI first over bank transfer
Rationale: UPI reduces recipient friction to seconds vs. hours for bank credits, and 85% of Indian recipients have UPI (source: NPCI 2024); bank transfers added as fallback but not optimized in MVP.

Decision: Admin dashboard scope
Choice Made: Read-only monitoring over manual transaction controls
Rationale: Manual controls would require 24/7 ops team and increase compliance risk; read-only logs allow compliance checks without operational burden. Manual intervention deferred to Phase 1.1.

Before / After Narrative:
Before: Raj, after a 12-hour shift in Dubai, takes a bus to a money transfer agent on Friday evening. He waits in line for 30 minutes, presents his passport and work visa, fills a paper form, and is quoted 1 AED = 22.20 INR—a 3% worse rate than online. He pays 1,000 AED plus a 50 AED fee, gets a receipt, and texts his wife that money will arrive in 3 days. She visits her bank on Monday, pays 100 INR to withdraw, and loses 600 INR to fees and poor FX.
After: Raj opens Unico Connect on his phone during his lunch break, scans his Emirates ID and takes a selfie (approved in 90 seconds), enters 1,000 AED, sees 1 AED = 22.65 INR (no margin), enters his wife’s UPI ID, and taps send. His wife gets a notification 45 seconds later, confirms the credit in her phone wallet, and pays a bill immediately—saving 600 INR and 3 days of worry.

Pre-Mortem:
It is 6 months from now and this feature has failed. The 3 most likely reasons are:

1. Users couldn’t complete KYC without assistance because Onfido’s liveness check failed for low-light mobile conditions common among migrant workers, and our support team lacked regional language capabilities, causing a 40% dropout at onboarding.
2. We shipped Phase 1 but the wedge capability (UPI payout) was delayed due to Razorpay API constraints, forcing recipients to use bank transfers that took 6 hours, neutralizing our speed promise and leading to negative word-of-mouth.
3. Competitor Wise launched a UPI integration 4 weeks before us, leveraging their existing brand trust, and captured 70% of our target user base through targeted ads in UAE labor camps.

What success actually looks like:
Six months post-launch, users refer friends because “it just works”—they show screenshots of instant receipts to coworkers. The team stops hearing complaints about hidden fees or delayed funds. In a board review, the CEO says, “We’ve saved migrant families $2M in fees, and our NPS is 65, driven by trust in transparency.” Operations sees support tickets drop below 20/week as transactions self-serve, and compliance reports clear audits without manual intervention.