Documentação

English

Português
Español

English

Português
Español

Appearance

Manage Manual Payments ​

Access prerequisites

  • Permission (module): viewPayments (to view the listing). The approve/reject actions also require the approveWithdrawal and cancelWithdrawal modules respectively.
  • License/Feature: None.
  • Menu container: GENERAL → Operations group

What it is / when to use ​

Review screen for manual deposits/contributions made by users — payments where the receipt is manually attached (PIX, TED, Neteller) and the system does not receive automatic confirmation from the bank/provider. The operator checks the receipt (receipt), approves — crediting the user's balance — or rejects the deposit. This is the manual reconciliation point between money that has entered the house account and the credit in the client's wallet.

Prerequisites ​

  • Permission: viewPayments to view; approveWithdrawal / cancelWithdrawal to act (dual permission — CPM enum on the backend + dynamic module in the DB).
  • License/Feature: None.
  • Dependencies on other screens: the target user must be APPROVED (KYC) to receive a financial credit. Actions can only be taken on deposits with status Waiting (WAITING).

Step by step ​

  1. Go to Operations → Manage manual payments.
  2. Use the search (numbers only — CPF/CNPJ/identifier) and the two filters: deposit type (All, PIX, TED, Neteller) and status (All, Approved, Cancelled, Waiting).
  3. Click the receipt icon to open the proof of payment in full screen and verify the amount and the sender's identity.
  4. Approve (the check icon) to credit the balance or reject (the clear icon) to deny. Confirm in the footer (bottom-sheet).

Filters and columns ​

Filter/ColumnWhat it showsData source
SearchFilters by document/identifier (numbers only)Sent as searchInput to the backend (getDeposits)
Deposit typePIX / TED / Neteller / AlldepositType in the request
StatusWaiting / Approved / Cancelled / Allstatus in the request
DateDate and time of the depositwhen
Name / IdentifierUser's name and CPF/CNPJ/passportuser (formatted by cpfCnpjFormater)
TypePayment methoddepositType
Amount / CurrencyAmount and unit (token or fiat)amount / unitOfMoney (BigNumber, 2 decimals)
StatusRequest state (green=approved, red=cancelled)status
External IDTransaction identifier in the provider/ledgerexternal_id

Actions and modals ​

  • Approve (check): opens a confirmation bottom-sheet; upon confirmation, calls updateDeposits(id, 'APPROVED'). The backend (FMS – PaymentController) credits the amount to the user's wallet and marks the deposit as APPROVED. The page reloads.
  • Reject (clear): confirmation bottom-sheet; calls updateDeposits(id, 'CANCELLED'). No credit is generated.
  • Receipt: opens the proof of payment (transferProofFile) in full screen. Does not change state.
  • Export CSV: downloads the current page as .csv.

Business rules / considerations ​

Attention

  • The approve/reject icons only appear when the status is Waiting (WAITING). Already approved or cancelled deposits are read-only.
  • Always check the receipt and the External ID before approving — this is the manual reconciliation; there is no automatic bank verification on this screen.

Irreversible

  • Approving credits the user's balance immediately. There is no automatic rollback: to reverse the action, a separate financial reversal entry is required. Treat each approval as a release of real money.
  • Financial values: handled as BigNumber — no rounding; check the decimal places of the token/currency.
  • Idempotency: the credit in FinLib is idempotent by externalId. If the backend returns E00021 "already processed", the deposit has already been credited — treat it as success, do not reprocess.
  • Status APPROVED: the target user must have KYC status APPROVED to receive the credit.