Understand the per-network contract that verifies payment IDs and splits successful USDC payments.
- Category
- Payments and settlement
- Updated
One terminal per merchant and network
Each merchant deploys a separate terminal for Base and Polygon. The contract records immutable values including the merchant wallet, supported USDC contract, FRENT fee wallet and fixed fee settings.
Deployment verification
FRENT does not activate an arbitrary address pasted into the interface. It reads the deployment transaction, checks that the configured factory created the terminal and verifies the immutable settings against the merchant record and current network configuration.
Payment behavior
The customer calls the terminal with a unique payment identifier and exact USDC amount. In one successful transaction, the contract sends the fixed protocol fee to the FRENT fee wallet and the remainder directly to the merchant wallet. FRENT does not hold a merchant balance for later payout.
The merchant address in an existing terminal cannot be changed. A different receiving wallet requires a new deployment.
Visual guide
Screens from the current flow.
Article FAQ
Common questions.
Can FRENT redirect the merchant share later?
No. The merchant wallet is an immutable terminal setting.
Does the contract hold a balance for payout?
The payment flow splits the successful transfer directly between the fee wallet and merchant wallet.
Need product support?
Bring the public details, never your keys.
Share the network, public wallet or terminal address, transaction hash and the displayed error. Never share a seed phrase or private key.