A transaction hash is accepted only when the confirmed call and payment event match the request.
- Category
- Payments and settlement
- Updated
A hash is not enough
Submitting any transaction hash does not mark a request paid. FRENT fetches both the transaction and its receipt from the configured network RPC.
Required checks
FRENT verifies that:
- The receipt is confirmed and has a successful status.
- The transaction and receipt target the expected merchant terminal.
- The transaction sender is a valid payer address.
- The terminal call contains the exact payment identifier and USDC token amount.
- The terminal emitted the expected payment event for that payer and immutable merchant.
- The event's gross, fixed fee and merchant net amounts match the request.
Only then is the request marked paid. The transaction hash and block number are retained with the payment and its audit attempt.
If the transaction is still pending, wait for confirmation before resubmitting. If it failed, create or use a valid transaction rather than sending an unrelated hash.
Visual guide
Screens from the current flow.
Article FAQ
Common questions.
Can the same hash pay two requests?
No. The encoded payment identifier and exact amount must match the specific request.
Why can a wallet say sent while FRENT still says pending?
Wallet submission happens before the network returns a confirmed successful receipt that FRENT can verify.
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.