CBL Payment Gateway

# CENTRAL BANK OF LIBERIA — COLLATERAL PAYMENT GATEWAY

Build a secure, production-ready **Collateral Payment Gateway** to be embedded into the Central Bank of Liberia (CBL) website. Customers must be able to search their collateral obligation, verify their identity, view balances, make payments, receive receipts, and review payment history.

The system must include:

1. **Customer Payment Portal**
2. **Administrative & Operations Portal**
3. **Payment Provider Integrations**
4. **Reconciliation & Reporting System**
5. **Security, Audit & Troubleshooting Tools**

## 1. CUSTOMER PAYMENT PORTAL

Add a prominent **MAKE A PAYMENT** button to the CBL website.

When clicked, open:

**Central Bank of Liberia**
**Collateral Payment Portal**

Subtitle:

> Search your collateral account, review your balance, and make a secure payment.

The portal must work on desktop, tablet, Android and iPhone and perform well on low-bandwidth connections.

## 2. SEARCH FOR COLLATERAL

Allow customers to search using any ONE of:

* Collateral ID
* National ID
* Registered Phone Number

Provide:

**Search Using:**
Collateral ID | National ID | Phone Number

**SEARCH RECORD**

Do not expose financial information merely because someone knows a customer's ID or phone number.

## 3. IDENTITY VERIFICATION

After locating a record, require verification before displaying sensitive information.

Use:

* OTP to registered phone
* Email OTP where available
* Approved alternative verification process

Example:

> A 6-digit verification code was sent to the mobile number ending in **4721**.

OTP must expire, have retry limits and be protected by rate limiting.

## 4. COLLATERAL SUMMARY

After verification display:

* Customer Name
* Collateral ID
* Account Number
* Collateral Type
* Description
* Original Amount
* Previous Payments
* Fees/Interest if applicable
* Outstanding Balance
* Amount Due
* Due Date
* Last Payment
* Account Status

Statuses:

**Current | Payment Due | Partially Paid | Past Due | Paid | Under Review | Closed**

Mask sensitive information where appropriate.

## 5. PAYMENT AMOUNT

Allow:

**PAY FULL BALANCE**

or

**ENTER ANOTHER AMOUNT**

Support USD and LRD where applicable.

Before confirmation display:

* Payment Amount
* Processing Fee
* Total
* Current Balance
* Remaining Balance After Payment

Prevent unauthorized overpayments.

## 6. PAYMENT METHODS

Provide:

### Lonestar MTN Mobile Money

Customer enters registered/payment mobile number and approves a Request-to-Pay transaction.

### Orange Money Liberia

Customer enters Orange Money number and authorizes payment.

### Bank Transfer

Allow payment through approved participating banks.

Capture:

* Bank
* Amount
* Collateral ID
* Payment Reference
* Bank Transaction Reference

Design the architecture to support **CBL IIPS / Pay Na-Na** interoperability where approved, allowing integration with banks and mobile-money providers through the national payment infrastructure.

Never invent undocumented production APIs. Build provider adapters that can connect to official APIs once credentials/specifications are supplied.

## 7. PAYMENT PROCESSING

Transaction lifecycle:

**Initiated → Awaiting Authorization → Processing → Provider Confirmation → Reconciliation → Successful**

Alternative statuses:

* Failed
* Expired
* Reversed
* Pending
* Under Review

Never mark an obligation paid based solely on browser confirmation. Payment success must be confirmed server-side by the payment provider/bank/payment switch.

Every attempt receives a unique reference such as:

**CBL-PAY-20260822-482901**

Store:

* CBL Transaction ID
* Collateral ID
* Customer ID
* Amount
* Currency
* Provider
* Provider Transaction ID
* Date/Time
* Status
* Reconciliation Status

Use idempotency controls to prevent duplicate payments.

## 8. PAYMENT CONFIRMATION & RECEIPT

After confirmed payment display:

**PAYMENT SUCCESSFUL**

Include:

* Customer Name
* Collateral ID
* Amount Paid
* Payment Method
* CBL Transaction ID
* Provider Reference
* Date/Time
* Previous Balance
* Remaining Balance

Buttons:

**DOWNLOAD RECEIPT**
**EMAIL RECEIPT**
**SEND BY SMS**
**VIEW PAYMENT HISTORY**

Generate an official PDF receipt containing CBL branding and a unique QR verification code.

QR verification must validate the receipt through the server without embedding sensitive customer data.

## 9. PAYMENT HISTORY

Authenticated customers can view:

**Date | Transaction ID | Method | Amount | Status | Receipt**

Allow filtering and receipt downloads.

Send SMS/email notifications for successful, failed, pending or reversed payments.

## 10. ADMIN PORTAL

Build a separate secure administrative portal protected by MFA and Role-Based Access Control.

Dashboard should display:

* Collections Today
* Collections This Week
* Collections This Month
* Successful Payments
* Pending Payments
* Failed Payments
* Reversed Payments
* MTN Collections
* Orange Collections
* Bank Collections
* USD/LRD totals
* Reconciliation Exceptions

Show service health for:

**MTN | Orange | IIPS | Banks | SMS | Email | Database**

## 11. ADMIN SEARCH

Allow authorized administrators to search by:

* Customer Name
* Collateral ID
* National ID
* Phone
* Transaction ID
* MTN/Orange Reference
* Bank Reference
* Receipt Number

Permissions determine what information each administrator can see.

## 12. COLLATERAL MANAGEMENT

Authorized personnel can:

* View/add collateral records
* Update approved fields
* Review balances
* View payment schedules
* Adjust approved fees
* Change due dates
* Suspend/restore accounts
* Place accounts under review
* Close paid accounts
* View complete history

Sensitive changes require a reason, timestamp, administrator identity and audit record.

## 13. TRANSACTION TROUBLESHOOTING CENTER

Create a dedicated troubleshooting console.

Search using:

* CBL Transaction ID
* Collateral ID
* Phone
* MTN Transaction ID
* Orange Transaction ID
* IIPS Reference
* Bank Reference

Show payment lifecycle:

**Created → Request Sent → Provider Received → Customer Authorized → Provider Response → CBL Webhook → Ledger Updated → Reconciled → Receipt Generated**

Authorized administrators can:

* Query provider status
* Retry eligible callbacks
* Retry reconciliation
* Regenerate receipts
* Resend notifications
* View sanitized API responses
* Escalate transactions
* Place transactions under investigation

Administrators must NOT freely change failed transactions to successful.

Exceptional manual adjustments require elevated authorization and documented justification.

## 14. RECONCILIATION

Automatically compare CBL records against:

* MTN MoMo
* Orange Money
* IIPS
* Participating Banks

Detect:

* Missing payments
* Amount mismatches
* Duplicate payments
* Provider success/internal failure
* Internal success/provider mismatch
* Reversals
* Settlement discrepancies

Create a **Reconciliation Exceptions Queue** showing transaction, provider, amount, issue, assigned staff, status and resolution notes.

## 15. REFUNDS & REVERSALS

Create controlled workflows for:

* Duplicate payments
* Wrong collateral payment
* Excess payment
* Refunds
* Provider reversals

Workflow:

**Officer Request → Supervisor Review → Finance Approval → Processing → Reconciliation**

Never delete the original financial transaction. Generate linked reversal/refund ledger entries.

## 16. USERS & PERMISSIONS

Implement roles:

* Super Administrator
* Payment Operations
* Finance Officer
* Reconciliation Officer
* Customer Service
* Supervisor
* Auditor
* IT Support

Follow least-privilege principles.

Sensitive actions should support **Maker-Checker / Four-Eyes approval**, especially:

* Refunds
* Reversals
* Balance adjustments
* Write-offs
* Permission changes
* Provider configuration
* Large transaction overrides

## 17. AUDIT LOGS

Maintain immutable audit logs covering:

* Logins
* Failed logins
* Customer searches
* Record access
* Changes
* Payment investigations
* Refunds
* Approvals
* Reconciliation actions
* Permission changes
* Configuration changes
* Report exports

Record user, role, action, timestamp, IP/device, previous value, new value, reason and approval reference.

## 18. FRAUD & RISK

Flag:

* Excessive failed payments
* Repeated OTP failures
* Duplicate attempts
* Rapid transactions
* Unusual amounts
* Suspicious devices/IPs
* Excessive admin searches
* Repeated manual adjustments

Risk ratings:

**LOW | MEDIUM | HIGH | CRITICAL**

Provide an investigation queue.

## 19. REPORTING

Generate:

* Daily/Weekly/Monthly/Annual Collections
* Provider Collections
* Bank Collections
* USD/LRD Collections
* Outstanding Collateral
* Fully Paid Collateral
* Failed/Pending/Reversed Transactions
* Refunds
* Reconciliation Exceptions
* Settlement Reports
* Administrator Activity

Export to **PDF, Excel and CSV**.

Executive dashboard should show:

* Total Collateral Portfolio
* Outstanding Balance
* Collected Today
* Monthly/Annual Collections
* Collection Rate
* Payment Success Rate
* Provider Distribution
* Collection Trends

## 20. PAYMENT API ARCHITECTURE

Build modular adapters for:

* MTN Mobile Money
* Orange Money
* CBL IIPS / Pay Na-Na
* Participating Banks

Support:

* Secure authentication
* Request-to-Pay
* Transaction status
* Webhooks
* Idempotency
* Retries
* Timeout handling
* Reconciliation
* Settlement reporting

API credentials must remain server-side and encrypted.

Webhook endpoints must validate provider signatures/tokens and protect against replay attacks and duplicate callbacks.

## 21. FINANCIAL LEDGER

Use an auditable ledger instead of simply overwriting balances.

Ledger entry types:

* Charge
* Payment
* Fee
* Adjustment
* Refund
* Reversal
* Correction