RICE Pay

We’ve published the official transparency information for RICE Pay Transfer Router v1. This update includes: - Official Base contract address - BaseScan source verification link - GitHub source code and README - Fee logic documentation - Gas fee clarification - Audit status disclosure The contract is source-verified on BaseScan, but it has not yet completed a third-party security audit. This is an important transparency step for RICE Pay. Users and developers can now inspect how the USDC transfer router works on-chain before interacting with it. BaseScan: https://basescan.org/address/0x1dD8667e22F9fAb8C2Be7E2021fAE0C8FB5457Ba#code Transparency page: https://ricepay.app/transparency GitHub: https://github.com/WonJo-Jung/RICEpay_web/tree/main/packages/contracts

We just shipped a major documentation update for RICE Pay: **Getting Started Guide v3.1.** While RICE Pay is engineered for friction-free, non-custodial USDC transfers, our data and user feedback highlighted a brutal truth: the app itself isn’t the bottleneck—**initial Web3 onboarding is.** For everyday users, concepts like setting up self-custody wallets, selecting the Base network, and balancing ETH for network fees feel like a terrifying maze. To systematically reduce this friction, we redesigned our onboarding documentation from the ground up. ### 🛠️ What’s inside the update: * **The "Digital Stamp" Analogy:** To eliminate cognitive overload, we stripped away heavy crypto jargon. We now frame ETH on Base as a simple **"digital stamp"** ✉️ required to deliver your USDC envelope. * **Clear Financial Guardrails:** Instead of using vague terms like "low gas fees," we provided an explicit baseline: *"Just $1 to $2 worth of ETH is more than enough for multiple transfers."* This drastically cuts down user anxiety during their first exchange withdrawal. * **Friction-Minimized 3-Step Checklist:** We streamlined the guide into a tight, actionable checklist synced perfectly with our UI flow, emphasizing a stress-free **1 USDC test transfer** first. * **Non-Custodial Transparency:** We heavily reinforced that RICE Pay never touches private keys or seed phrases—positioning self-custody as an empowering asset-control feature rather than a technical chore. We also designed and integrated a clean, minimalist infographic right at the top of the page so beginners can digest the entire framework in under 10 seconds before reading. 👉 **Explore the full guide here:** **https://ricepay.app/getting-started** --- **💬 To the product leads and Web3 builders here:** What unique UX hacks on our new flow! 👇

RICE Pay is a non-custodial USDC transfer app on Base. iOS is live on the App Store, and Android testing is being prepared through Google Play. The current MVP focuses on saved recipients, clearer recipient confirmation, transparent capped fees, and a non-custodial flow where RICE Pay does not hold user balances. I’m trying to validate one core question: Would people who already send USDC use a separate transfer app like this, or are wallets like MetaMask, Coinbase Wallet, and Rabby already enough? I’m especially interested in feedback around: - saved recipients - transfer anxiety - recipient confirmation - fee transparency - whether this is the right first layer for a broader USDC payment experience I’m looking for iOS users who can test a very small transfer, Android users willing to join the Google Play test group, and honest criticism from people who understand stablecoin payments or wallet UX. If this sounds relevant, I’d appreciate your feedback.