An importer should not need to become a crypto trader just to pay an overseas supplier. RICE Pay is designed to connect a familiar business payment interface with a customer-controlled smart account, a conversion partner and an onchain USDC transfer.
The easiest way to understand the service is to follow one payment from the business's funding source to the supplier's designated wallet—and to identify who is responsible at each stage.
1. Confirm that the business and payment route are supported
Before the first live payment, the importer completes the required business verification. The conversion partner may review the company, beneficial owners, payment purpose, expected volume, source of funds and destination countries.
Approval of a business does not mean every transaction is supported. Currency, country, industry, payment size and supplier location can affect availability and limits.
- Business verification status
- Funding currency and country
- Supplier country and intended use
- Typical amount and payment frequency
2. Add the supplier and enter the payment details
The importer selects or adds the supplier's designated wallet, enters the invoice amount and records the information needed to identify the payment internally.
An address book can reduce repeated entry for recurring suppliers, but the business must still verify a new or changed wallet address through a trusted channel. A blockchain transfer generally cannot be reversed simply because the wrong address was approved.
- Supplier name or internal reference
- Designated wallet address and supported network
- Invoice or payment reference
- Amount to be delivered in USDC
3. Review the fiat-to-USDC conversion quote
The conversion partner provides the supported funding method and the cost of converting the customer's fiat currency into USDC. RICE Pay presents the partner charge together with its own applicable service fee before authorization.
A quote can depend on the funding currency, payment amount, market conditions, banking route and partner policy. The customer should compare the total cost—not only a blockchain network fee—with its existing bank payment.
- Funding amount and currency
- Conversion partner fee and exchange rate
- RICE Pay fee
- Expected USDC amount and quote validity
4. Check the recipient, amount and fees before approving
Before any outgoing USDC payment is authorized, the customer reviews the supplier wallet, network, payment amount and disclosed fees. This review screen is the point at which a business should stop if any detail is unfamiliar or does not match the invoice.
Logging in and approving a payment are different actions. Access to the RICE Pay interface does not, by itself, create a valid outgoing transfer.
- Correct supplier and wallet address
- Correct network
- USDC payment amount
- Conversion and RICE Pay fees
Particle Network — Security (MPC-TSS) ↗Particle Network — Account Abstraction ↗
5. The customer authorizes the payment
The customer approves the payment using the authority recognized by its smart account. RICE Pay may prepare the transaction request, relay an approved operation and sponsor the network fee, but it is not intended to manufacture the customer's signature or approve a different payment.
The production integration may coordinate conversion and transfer in one user experience, but an outgoing payment from the customer smart account must remain tied to customer authorization.
Particle Network — Security (MPC-TSS) ↗Particle Network — Account Abstraction ↗Ethereum Improvement Proposals — ERC-4337 Account Abstraction ↗
6. The conversion partner converts fiat into USDC
The conversion partner—not RICE Pay—receives the supported fiat funding and performs the fiat-to-USDC conversion under its own terms, compliance controls and processing times.
The converted USDC is delivered into the payment flow associated with the customer's smart account. A bank debit or transfer being initiated does not mean the conversion has already completed; the status must distinguish funding, conversion and onchain transfer.
7. USDC is transferred to the supplier's designated wallet
Once the required funding and authorization conditions are satisfied, the customer-authorized USDC payment is submitted on the supported blockchain and sent to the wallet specified for the supplier.
The blockchain records the destination, token amount and transaction status. This makes the transfer traceable, but it does not prove that the supplier has converted the funds into a bank-account currency.
Ethereum.org — Transactions ↗Ethereum Improvement Proposals — ERC-4337 Account Abstraction ↗
8. Track the payment and keep the record
RICE Pay is designed to bring the payment status, transaction history, notifications and payment receipt into one business workflow. The onchain transaction identifier provides an additional reference for checking whether the USDC transfer was recorded.
A blockchain record does not replace an invoice, contract, accounting entry or tax document. The business remains responsible for keeping the records required in its jurisdiction.
- Payment status and onchain transaction identifier
- Supplier and payment reference
- Notifications and transaction history
- Receipt for the completed RICE Pay payment
9. The supplier chooses whether to hold, reuse or convert USDC
After USDC reaches the designated wallet, the supplier may keep it, use it for another supported payment or convert it into USD or local currency through a service available to the supplier.
That later conversion is not part of RICE Pay's initial service boundary. The supplier may face separate off-ramp fees, exchange rates, verification requirements, limits and processing times.
Who is responsible at each stage?
Separating the roles prevents a payment interface from being mistaken for the company performing every financial service.
| Participant | Primary role | What the role does not automatically mean |
|---|---|---|
| Importer | Verifies details and authorizes the payment | RICE Pay may approve a payment instead |
| RICE Pay | Organizes the interface, fee review, submission and records | Holds or freely moves customer funds |
| Particle Network infrastructure | Supports the smart account and signing experience | Performs fiat conversion |
| Conversion partner | Handles supported fiat-to-USDC conversion and compliance | Controls the supplier's later use of USDC |
| Supplier | Provides the designated wallet and receives USDC | Automatically receives fiat in a bank account |
A live transaction should disclose the actual providers and terms that apply to that payment route.
Where RICE Pay's initial service boundary ends
RICE Pay's initial service objective is the delivery of the customer-authorized USDC amount to the supplier's designated wallet. It does not promise that the supplier will receive the same numerical amount in USD or local currency after conversion.
The supplier's final bank-account proceeds can change because of off-ramp fees, exchange rates and local banking charges. Those costs should be considered before the importer and supplier agree to use USDC.
- No guarantee of supplier-side fiat conversion
- No guarantee of a fixed off-ramp fee or exchange rate
- No guarantee that every country, currency or business is supported
- No replacement for trade contracts, tax advice or accounting treatment
The payment is complete for RICE Pay when the authorized USDC reaches the designated supplier wallet—not when the supplier later converts it into fiat.
What to confirm before the first supplier payment
A short operational check is more useful than assuming that every USDC payment follows the same route.
- The importer and payment route passed the required verification
- The supplier agrees to receive USDC on the stated network
- The wallet address was confirmed through a trusted channel
- All conversion and RICE Pay fees are visible
- The supplier understands any later off-ramp cost
- The invoice or contract states how payment completion will be determined
Conclusion: one workflow, with clear responsibilities
RICE Pay is intended to make a USDC supplier payment understandable to a finance team that does not live inside a crypto exchange. The importer sees the payment details and fees, authorizes the outgoing transfer and can track its completion.
The model remains transparent only when the conversion partner's role, customer authorization, RICE Pay's service fee and the supplier's separate off-ramp decision are clearly distinguished.
RICE Pay does not ask a business to hand over control of its funds. It gives the business a clearer way to review, authorize and record its own supplier payment.
See what RICE Pay can improve in your supplier payments.
Share the amount, frequency, funding currency and supplier country. We will compare your current route with a clear, trackable RICE Pay workflow—no bank account numbers required for the first review.
Review my supplier-payment routeThis article describes RICE Pay's intended initial workflow. The exact conversion partner, supported countries, currencies, limits, fees, network and technical sequence must be confirmed before a live payment. Availability remains subject to business verification and partner coverage.
Partner coverage, fees, limits, networks and technical sequencing can change. Review the live quote, transaction screen and applicable terms before authorizing a payment.