RICE Pay Transparency
Public contract information for RICE Pay's non-custodial USDC transfer router.
Status Summary
Status: Active beta contract
Network: Base
Source Code: Verified on BaseScan
Audit Status: Not audited yet
Custody: Non-custodial design
Contract Address
Contract Name: RICE Pay Transfer Router
Network: Base
Contract Address:
0x1dD8667e22F9fAb8C2Be7E2021fAE0C8FB5457Ba
BaseScan:
https://basescan.org/address/0x1dD8667e22F9fAb8C2Be7E2021fAE0C8FB5457Ba#code
GitHub Source Code
The Solidity source code for the RICE Pay Transfer Router v1 is publicly available on GitHub.
GitHub:
https://github.com/WonJo-Jung/RICEpay_web/tree/main/packages/contracts
What This Contract Does
The RICE Pay Transfer Router is designed to route USDC transfers without custodying user balances.
When a user initiates a transfer, the contract pulls the approved USDC amount from msg.sender and immediately routes the funds to:
- the recipient
- the RICE Pay fee wallet
The contract is not designed to hold user funds like a vault or escrow.
Fee and Gas
RICE Pay service fee:
0.39%, with a minimum fee of 0.25 USDC and a maximum fee of 3.90 USDC.
Network gas fee:
Gas is separate from the RICE Pay service fee. Gas is paid by the user through their wallet to the Base network. RICE Pay does not receive gas fees.
Trust Signals
The v1 transfer router has:
- No owner
- No proxy
- No admin function to change fees
- Immutable USDC token address
- Immutable fee recipient address
- Fixed fee logic in the contract
- Source code verified on BaseScan
Allowance Policy
RICE Pay does not require unlimited USDC approval.
The intended flow is exact-amount approval for each transfer. This helps reduce allowance-related risk for users.
Security Notice
Source verified does not mean audited.
The contract source code is public and verified on BaseScan, but it has not yet completed a formal third-party security audit.
RICE Pay plans to pursue an external review or limited-scope audit before meaningful transaction volume.
If a serious issue is found, RICE Pay will stop directing users to the affected contract, mark it as deprecated in the documentation, and publish a new verified contract address.