Skip to content

Repayment & Extension Processing

Admin operations for verifying repayments, processing extensions, managing late payments, handling liquidation, and processing withdrawals.

Repayment Processing Flow


1. Verify Repayment Slip

When a user uploads a payment slip:

CheckDescription
Amount MatchPayment amount matches loan repayment + any late fees
Bank DetailsTransfer to correct bank account
DateTransfer date is current
Slip AuthenticityPayment reference, bank stamp, transaction ID

After verification:

  • Loan stage → loan_closed
  • Collateral released back to user's wallet
  • Confirmation email sent

2. Early Repayment Processing

For loans repaid before maturity:

  • Early payment fee calculated by .NET backend (CalculateEarlyRepayment endpoint)
  • Fee > 0 requires user to accept early repayment agreement
  • Admin verifies payment includes the early repayment fee
  • Available only after 14 days from loan start (14-day rule)

3. Loan Extension Processing

Extension fee components:

  • Processing fee for new term
  • Interest for new term
  • Late payment fee (if applicable)
  • Discount codes may apply

4. Late Payment Management

When a loan enters late_payment stage:

ActionDescription
Fee CalculationLate payment fee calculated based on overdue days
NotificationsAutomated email reminders to user
MonitoringAdmin dashboard highlights overdue loans
EscalationContinued non-payment may trigger liquidation

Late payment reminders appear on the user's dashboard as urgent notifications.


5. Liquidation Management

When loan health reaches 0% (collateral value drops below the liquidation threshold):

Two types of liquidation:

  1. Price-drop liquidation — crypto price falls, LTV threshold breached
  2. Late-payment liquidation — extended non-payment triggers forced liquidation

Top-up Protection

Loans with topup_active_time (not null) are temporarily protected from both price-drop and late-payment liquidation.


6. Withdrawal Processing

When a user requests a cryptocurrency withdrawal:

StepDescription
1. RequestUser submits withdrawal (asset, amount, destination address)
2. ValidationAddress format validated, sufficient balance checked
3. OTPUser completes OTP verification
4. ProcessingProcessed via custodian service (Kryptodian)
5. ConfirmationTransaction hash shared, status updated

Admin monitors withdrawal queue for:

  • Unusual amounts or patterns
  • Address change alerts
  • Failed transactions requiring manual intervention

Next: System & Configuration →

Confidential — For internal and authorized partner use only.