What this form does
Use this form to create one manual merchant-balance transaction. The transaction is stored as a journal row and then contributes to the current Merchant balance total according to its type.
How to use it
- Review the current
Merchant balanceshown above the form. This is the all-time current merchant-balance total, not a form-local preview, and the page renders it without a currency code or symbol. - Confirm
User IDis the current admin user ID. If it shows-1, do not submit; reload the page or contact an administrator because the admin details did not populate the disabled field correctly. - Choose
DEBITorCREDIT. With a non-negative amount,DEBITdecreases andCREDITincreases the merchant-balance formula. A negative amount reverses that direction, so do not submit one unless that signed adjustment is explicitly intended. - Enter the transaction
Amount. The form starts at0; replace it with the intended adjustment amount before submitting. - Click
Submitonce to create the journal entry. A success message is shown, the page requests its current merchant-balance data again, and then returns to the list after a short delay.
Important caveats
- This is a create-only screen. It does not edit an existing transaction.
- The
User IDfield is displayed but disabled. It snapshotssuperAdminUserIdduring local-state initialization and does not re-synchronize when admin details arrive later; the fallback is-1. - Save requires
type,amount, anduserIdto be present and restricts type toDEBITorCREDIT, but it has no explicit positive-amount or operator-friendly range rule. - The page does not show a separate confirmation step before submitting the adjustment.
- The
Submitbutton is not visibly locked while the request is in flight in the verified page code, so avoid repeated clicks. - After a successful create call, the page redirects back to the list page.
- The same current merchant-balance total is shown here, and it is not scoped by any date filter.
- The page has no idempotency key. Verify the journal before retrying after an uncertain response because repeated submissions can create repeated rows.
- The transaction payload contains no currency field. Do not infer a verified transaction currency from this form or its unlabelled amounts.