Skip to main content

Reject Deposit Lock Amount

Reject a pending lock amount transaction to deny the fund lock or seizure request.

Overview​

The RejectDepositLockAmountCommand rejects a pending lock amount transaction, preventing the funds from being locked or seized. This completes the authorization workflow for transactions that require supervisory review by denying the request and returning the account to normal status.

Key Capabilities​

  • Authorization Control: Deny inappropriate or unsupported lock requests
  • Supervisory Oversight: Management review and rejection authority
  • Automatic Cleanup: Removes pending transaction from queue
  • Audit Trail: Records rejection reason and decision maker
  • Customer Impact: Preserves full access to funds
  • Notification: Can trigger alerts to requestor
  • Compliance: Maintains documentation of denied requests

API Endpoint​

POST /api/bpm/cmd

Headers​

Content-Type: application/json
Authorization: Bearer {access_token}
X-Tenant-ID: {tenant_id}

Request Structure​

Command Payload​

{
  "commandName": "RejectDepositLockAmountCommand",
  "data": {
    "accountNumber": "string",
    "blockReference": "string",
    "notes": "string"
  }
}

Request Fields​

FieldTypeRequiredDescriptionValidation
accountNumberstringYesDeposit account number or encoded keyMust exist in system
blockReferencestringYesUnique reference of pending lock transactionMust be in pending state
notesstringYesRejection reason and explanationRequired for audit trail

Response Structure​

Success Response​

{
  "isSuccessful": true,
  "message": "The lock amount transaction has been rejected successfully.",
  "statusCode": "00"
}

Error Response​

{
  "isSuccessful": false,
  "message": "The lock transaction is not in pending state.",
  "statusCode": "INVALID_REQUEST"
}

Sample Requests​

1. Reject Insufficient Documentation​

{
  "commandName": "RejectDepositLockAmountCommand",
  "data": {
    "accountNumber": "ACC123456789",
    "blockReference": "LOCK-2024-12-001234",
    "notes": "Rejected - Insufficient supporting documentation. Court order copy not provided. Requestor should resubmit with complete documentation."
  }
}

2. Reject Improper Request​

{
  "commandName": "RejectDepositLockAmountCommand",
  "data": {
    "accountNumber": "SAV987654321",
    "blockReference": "HOLD-2024-445",
    "notes": "Rejected - Lock amount exceeds account balance by significant margin. Request appears to be based on incorrect account information. Please verify account details and resubmit if appropriate."
  }
}
{
  "commandName": "RejectDepositLockAmountCommand",
  "data": {
    "accountNumber": "8A3F2D1E9B5C4F7A6E8D2C1B3A9F5E7D",
    "blockReference": "SEIZE-COURT-20241219-001",
    "notes": "Rejected by Legal Department - Court order issued by jurisdiction with no authority over this account. Account domiciled in different jurisdiction. Legal counsel advises non-compliance."
  }
}

4. Reject Customer Request (Resolution)​

{
  "commandName": "RejectDepositLockAmountCommand",
  "data": {
    "accountNumber": "CHQ555444333",
    "blockReference": "CUST-LOCK-2024-987",
    "notes": "Rejected - Customer dispute resolved. Customer verified the disputed transaction was legitimate. Lock no longer necessary as issue has been clarified."
  }
}

Business Logic​

Rejection Workflow​

State Transitions​

Rejection Flow:

  • PENDING_APPROVAL → REJECTED → Transaction closed
  • Available Balance unchanged (remains accessible)
  • Lock request removed from approval queue

Use Cases​

1. Insufficient Documentation​

Scenario: Lock request lacks required supporting documents

Steps:

  1. Requestor submits lock with incomplete documentation
  2. Supervisor reviews request
  3. Supervisor rejects due to missing documents
  4. Requestor notified with specific requirements
  5. Can resubmit with complete documentation

2. Policy Violation​

Scenario: Request violates bank policies or procedures

Steps:

  1. Lock request created
  2. Compliance reviews against policies
  3. Policy violation identified
  4. Rejection with policy reference
  5. Requestor educated on proper procedures

3. Customer Issue Resolved​

Scenario: Reason for lock no longer exists

Steps:

  1. Lock requested for disputed transaction
  2. Customer and bank resolve dispute
  3. Lock no longer necessary
  4. Supervisor rejects pending lock
  5. Account remains fully accessible

4. Legal/Regulatory Issues​

Scenario: Legal basis for lock is insufficient

Steps:

  1. Court order submitted for seizure
  2. Legal department reviews
  3. Identifies jurisdictional or procedural issues
  4. Rejection with legal rationale
  5. Proper legal process must be followed

Validation Rules​

ValidationError MessageStatus Code
Account not found"The selected account number is not valid"INVALID_ACCOUNT
Lock transaction not found"Block reference not found"INVALID_REQUEST
Not in pending state"The lock transaction is not in pending state"INVALID_REQUEST
Already processed"This transaction has already been processed"DUPLICATE_TRANSACTION
Missing notes"Rejection notes are required"INVALID_REQUEST

Best Practices​

For Rejecting Authority​

  1. Clear Documentation: Provide specific, detailed rejection reasons
  2. Actionable Feedback: Explain what's needed for approval
  3. Timely Decisions: Don't leave requests pending unnecessarily
  4. Policy Reference: Cite specific policies or regulations
  5. Professional Tone: Maintain professional communication

Rejection Notes Guidelines​

Good Notes:

  • "Rejected - Court order lacks proper jurisdiction. Account domiciled in State A, order issued in State B. Legal counsel advises non-compliance."
  • "Rejected - Lock amount of $50,000 exceeds available balance of $12,345. Please verify intended account and amount."

Poor Notes:

  • "No" ❌
  • "Denied" ❌
  • "Not approved" ❌

For System Integration​

  1. Notification System: Alert requestor immediately upon rejection
  2. Resubmission Workflow: Allow easy resubmission with corrections
  3. Escalation Path: Provide appeal process for rejections
  4. Audit Retention: Maintain rejection records per policy
  5. Dashboard Metrics: Track rejection rates and reasons

Common Rejection Reasons​

Reason CategoryExample NotesFollow-up Action
Documentation"Missing court order copy"Provide complete documents
Policy Violation"Exceeds authorization limit"Escalate to higher authority
Account Status"Account closed"Verify account status
Balance Issues"Insufficient funds"Verify balance requirements
Legal Issues"Improper jurisdiction"Consult legal counsel
Resolved"Customer dispute resolved"No further action needed

Security Considerations​

Authorization Requirements​

  • Role-Based: Only authorized approvers can reject
  • Audit Trail: All rejections logged with user identity
  • Approval Limits: Respect hierarchical approval authority
  • Legal Protection: Document proper legal basis for rejection

Compliance Notes​

  1. Record Retention: Maintain rejection records per regulatory requirements
  2. Legal Review: Have legal counsel review high-value rejections
  3. Customer Rights: Ensure customer notification requirements met
  4. Reporting: Include rejections in compliance reports

Error Handling​

Common Errors​

Transaction Not Found:

{
  "isSuccessful": false,
  "message": "Block reference not found",
  "statusCode": "INVALID_REQUEST"
}

Already Processed:

{
  "isSuccessful": false,
  "message": "This transaction has already been approved",
  "statusCode": "DUPLICATE_TRANSACTION"
}

Missing Notes:

{
  "isSuccessful": false,
  "message": "Rejection notes are required",
  "statusCode": "INVALID_REQUEST"
}
APIRelationshipDescription
Approve Lock AmountAlternativeApprove instead of reject
Lock Deposit AmountPrerequisiteCreates the lock request
Delete Lock AmountRelatedRemove after approval

Next Steps​