Skip to main content

Transaction Held

1.# πŸ“˜ Compliance – Transactions Held

🧾 Overview​

The Transactions Held sub-module provides a dedicated space for managing transactions that have been suspended or flagged due to compliance-related issues. These transactions require manual review or clearance before they can proceed to payout.

Typical reasons for being held include:

  • Compliance rule violations
  • AML (Anti-Money Laundering) flags
  • Incomplete or failed validations
  • Policy breaches or operational triggers

This module enables compliance and operations teams to:

  • View all held transactions in one place
  • Investigate root causes
  • Take appropriate action (e.g., escalate, approve, or return to processing)

πŸ“Š Data Table View​

Once filters are applied, held transactions are displayed in a structured table. Each row represents a held transaction, including the following fields:

ColumnDescription
DateTimestamp of when the transaction was created
Reference #Unique ID to trace or reference the transaction
RemitterFull name, phone, and address of the sender
BeneficiaryReceiver’s name, bank details, account number, and phone
Delivery / Payment MethodCombined view of how money was paid and how it will be delivered
AmountTotal transaction value in both source and destination currencies
Payout CompanyThe payout partner or financial institution handling the delivery
Agent / BranchThe remitter’s agent and their specific location

πŸ–₯️ Monitoring Sidebar​

When a transaction is selected in the list, a sidebar panel opens on the right, offering detailed insight into the selected transaction. This includes:

SectionDescription
Transaction MetadataFull reference ID, date, status, and origin
Remitter DetailsName, phone number, ID, and location
Beneficiary DetailsName, account number, bank, contact info
Compliance FlagsAny triggered rules, risk scores, or document verification issues
Comments / NotesInternal remarks added by previous reviewers
DocumentsUploaded KYC, proof of funds, or ID images

This sidebar supports manual review by providing all relevant context in one view.

2.

πŸ” Manual Action – Add to Processing​

After compliance checks have been completed and a transaction is cleared:

  • The compliance officer or authorized team member can manually add the transaction back into the processing queue.
  • This removes the β€œHeld” status and resumes the payout workflow.

This action is available via:

  • β€œAdd to Processing” button within the sidebar, or
  • Bulk action tools in the transaction table (if enabled)

βœ… This ensures that only cleared transactions proceed to disbursement β€” preserving both compliance integrity and operational efficiency.

3. Click "Add To Processing"