Customer-held authority
The customer-controlled account holds the authority to approve a payment. RICE Pay does not hold a master key that can move funds on its own.
Customer-controlled payment security
Your funds move only when you approve.
RICE Pay is designed so it cannot independently access, withdraw or redirect customer funds. Every supplier payment begins with a clear review of the recipient, amount and fees—and moves only after the customer authorizes it.
A signature for every payment
Signing in opens the workspace; it does not send money. Each payment requires a separate customer authorization.
Review before approval
The recipient, payment amount and applicable fees are shown before the customer signs the transaction.
Verifiable settlement
A completed USDC transfer is recorded on-chain, providing a transaction record that can be checked independently.
Security architecture
No personal browser wallet. No RICE Pay master key.
RICE Pay uses Particle Network’s non-custodial smart-account infrastructure. Particle documents a 2-of-2 MPC-TSS model in which key shares remain separate and signing is initiated by the user. Smart-account technology then turns that authorization into an on-chain transaction.
How a payment is authorized
- An authorized business user signs in with the account linked to the company workspace.
- RICE Pay prepares the supplier, amount and fee information for review.
- The customer checks the payment instruction and explicitly approves it.
- Particle Network’s signing infrastructure produces the required authorization without giving RICE Pay the customer’s full private key.
- The smart account executes the authorized USDC transfer and the result is recorded on-chain.
Signing in is not signing a payment. Account access and transaction authorization are separate actions. Opening RICE Pay does not give the service permission to move funds.
Clear authority
Every participant has one defined security role.
Separating approval, conversion, execution and recordkeeping reduces ambiguity over who can act at each stage.
Customer
Controls account access, verifies the supplier and payment details, and authorizes each transaction.
RICE Pay
Prepares the payment request, displays the information to review, relays the authorized instruction and organizes payment records. It cannot authorize a payment in place of the customer.
Conversion partner
Handles supported fiat-to-USDC conversion, business verification and transaction controls under its own regulated process.
Particle Network and Base
Provide the signing, smart-account and on-chain execution infrastructure used to carry out and verify an authorized transfer.
End-to-end protection
Security before, during and after every payment.
RICE Pay places a clear verification point at each stage of the supplier-payment workflow.
Before approval
- Business and supported-route checks
- Supplier and wallet details displayed for verification
- Payment amount and applicable fees shown upfront
At authorization
- Separate customer approval for the transaction
- MPC-TSS signing without exposing a full private key to RICE Pay
- Smart-account execution of the authorized instruction
After settlement
- On-chain transaction status
- Payment history, notification and receipt
- Transaction identifier for independent verification
Business safeguards
Simple controls that protect high-value supplier payments.
Technology protects the account structure; disciplined payment operations protect every instruction your team approves.
✓
Use a company-controlled email account and protect it with strong authentication.
✓
Verify a new or changed supplier wallet address through a separate trusted channel.
✓
Confirm the recipient, network and amount before signing—on-chain transfers generally cannot be reversed.
✓
Limit access to authorized staff and remove access promptly when responsibilities change.
✓
Never share passwords, one-time codes, key material or recovery credentials with RICE Pay support.
Security FAQ
The questions a finance team should ask before moving money.
Can RICE Pay withdraw or redirect customer funds?
No. RICE Pay is designed without a customer master key or unilateral signing authority. A supplier payment requires authorization from the customer-controlled account.
Does signing in automatically approve a payment?
No. Signing in provides access to the workspace. Each transaction is presented separately and requires the customer’s explicit approval.
Does RICE Pay hold the customer’s private key?
No. Particle Network documents an MPC-TSS design in which the full private key is not held in one place or exposed to RICE Pay.
How can a completed payment be verified?
The USDC transfer produces an on-chain transaction identifier. The customer and supplier can use it to check the status, destination and amount independently.
Can an incorrect blockchain payment be reversed?
Generally no. That is why RICE Pay places recipient, network, amount and fee review before authorization, and why supplier address changes should be verified outside the payment request.
Start with a payment route you can verify before you commit.
Share the sending country, supplier country, amount and frequency. RICE Pay will map the supported flow, expected cost and approval controls before any live payment.