Understand how one official shared contract per chain provides direct, non-custodial settlement.
- Category
- Payments and settlement
- Updated
One official contract per chain
FRENT uses the same immutable Solidity implementation for one official deployment on Base and one on Polygon. Merchants configure which networks use their authenticated receiving wallet.
Every payment request is signed by FRENT and binds its unique payment ID, merchant, token, gross amount, platform fee, expiry, chain ID and verifying contract. Any silent change invalidates the authorization, and processed IDs cannot be replayed.
Payment behavior
The customer pays through the official contract. In that same transaction, the deterministic platform fee goes directly to the FRENT fee wallet and the net proceeds go directly to the merchant. The contract has no escrow, merchant balance or withdrawal process.
FRENT verifies the receipt against the configured official contract and checks the payment ID, token, payer, merchant, gross amount, fee and merchant net amount emitted by PaymentCompleted.
To use a different receiving wallet, sign in with that wallet and configure its payment networks. No contract migration is required.
Visual guide
Screens from the current flow.
Article FAQ
Common questions.
Which POS contract does a merchant use?
Every merchant uses the official shared FRENT POS deployment for the selected chain.
Can payment terms be modified?
No. Merchant, token, amount, fee, expiry, chain and contract are covered by the signed request.
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 official contract address, transaction hash and the displayed error. Never share a seed phrase or private key.