Company

FAQ on Pecunia web app (PWA)

Last updated October 20, 2025

Chibugo Ohanyiri

In this post

The Lendsqr Admin Console also known as Pecunia web app (PWA) is the central hub for every lender operating on Lendsqr. It’s where you configure loan products, manage customers, monitor repayments, and oversee every aspect of your lending operations all in one secure, intuitive dashboard.

This FAQ is designed to help you understand how Pecunia works together to power your lending business. You’ll learn how to set up your account, configure decision models, manage disbursements, and customize workflows that fit your lending strategy.

Think of it as your complete guide to running a digital lending business with Lendsqr: how to get started, how the system works behind the scenes, and how to use each tool to make smarter, faster, and more compliant lending decisions.

What do I need to sign up on Lendsqr?

To create your loan web app and start operating on Lendsqr, you’ll need both personal and business verification details. This includes your legal full name, a valid phone number, an active email address, and your home or business address.

You’ll also need business registration documents such as your certificate of incorporation, company license, and logo, along with your bank account details for receiving repayments and disbursing loans.

How do I sign up on Lendsqr?

When you sign up on the website, you’ll be asked to select your role, fill out your details, upload relevant documents, and submit the form. Once completed, a verification link will be sent to your email. Click the link to activate your account and access the PWA dashboard.

Can I choose my role during sign-up?

Yes. Lendsqr’s onboarding process allows you to specify your role, whether you’re a fintech, microfinance institution (MFI), or independent lender. This selection helps tailor your dashboard features and tools to your lending model.

What is the primary purpose of the dashboard?

The PWA dashboard gives you an instant, high-level overview of your lending operations. You can track total users, loans disbursed, repayment performance, savings balances, and recent borrower logins. This makes it easy to spot trends, monitor credit performance, and make informed operational decisions.

How is the side navigation divided?

The PWA sidebar is divided into two major sections:

Customers: This section focuses on borrower management and individual account actions.
Back office: This area manages the products, services, and configurations that power your lending operations.

What actions can I perform in the Customers section?

In this section, you can handle all borrower-related activities. These include:

Accessing and editing user profiles
Approving or rejecting loan requests
Managing active and completed loans
Tracking borrower savings and repayments
Verifying customer identities (KYC)
Managing guarantors and beneficiaries
Creating and managing whitelists
Setting up and monitoring direct debit mandates

What can I manage in the Back Office?

The Back Office is where lenders manage the entire operational and financial structure of their lending business. Here’s what you can do:

Create and manage loan and savings products: Set up flexible loan or savings products customized for your customers’ needs. Define key terms, including interest rates, tenure, repayment frequency, and eligibility rules. You can also control product visibility, enabling or disabling specific products for certain customer groups.
Edit decision models: Adjust your credit decision models to determine how applications are evaluated and approved. This allows lenders to automate approval workflows based on data points like credit scores, repayment history, or income thresholds.
View and reconcile transactions: Track all financial activities, from disbursements to repayments and wallet top-ups. You can view transaction histories, check for discrepancies, and export reports for accounting or regulatory audits.
Manage prepaid and disbursement accounts: Control how loan funds are disbursed and received. You can link prepaid accounts for automated funding, manage liquidity levels, and ensure payouts reach borrowers without delay.
Review audit logs: Every action performed by a user, such as editing a product, approving a loan, or changing a workflow, is logged.

What settings can admins manage?

The Settings tab allows admins to configure how their organization and team operate on Lendsqr. This includes both technical and administrative controls, such as:

Team management: Invite new users, assign roles, activate or deactivate accounts, or remove team members.
Organization profile: Update your company details, such as name, address, logo, and branding elements.
Payment and fee configuration: Set or adjust transaction fees for card payments, transfers, and other operations to align with your revenue model or processing costs.
Notification preferences: Enable or disable automated email alerts for events to keep your team informed.
Loan and organization settings: Define lending rules, including loan limits, default penalties, repayment schedules, and interest configurations. You can also customize operational policies to fit your internal processes or regulatory requirements.

What are the main categories of metrics on the Pecunia Dashboard?

The Pecunia dashboard provides a live snapshot of your business health through key performance metrics. These metrics are grouped into three main categories:

Loan performance: Tracks every loan on your platform from new disbursements to active, paid-off, and overdue loans. This helps you assess portfolio quality, identify repayment trends, and monitor default risk.
Customer information: Shows your total customer base, active users, and those currently holding loans or savings. These insights help you track customer engagement and growth over time.
Savings performance: Monitors total savings balances, active saving goals, and participating customers. It’s useful for lenders offering hybrid products that combine credit and savings.

Can I customize the Pecunia dashboard?

Yes. Lenders can customize the dashboard by submitting a custom JSON configuration to Lendsqr. This allows you to rearrange widgets, highlight specific KPIs, or modify layouts to emphasize the data most relevant to your operations.

Whether you prefer a view focused on collections, disbursements, or customer acquisition, the dashboard adapts to your workflow.

What default roles exist on the Lendsqr admin console?

The PWA includes three core roles with predefined access levels:

Super Admin: Has unrestricted access to every part of the system, ideal for business owners or senior managers who oversee compliance and performance.
Admin: Handles daily activities like product setup, workflow management, and customer oversight. Admins can perform most actions, but may not change high-level configurations.
Team: Handles specific operational tasks such as reviewing loan requests, contacting customers, or managing savings based on permissions assigned by higher roles.

Can I create custom roles?

Yes, if your subscription plan supports it. With the “Create Roles” permission enabled, you can define new roles with custom permissions that reflect your internal structure, for example, creating separate roles for collections, marketing, or credit risk teams.

What is an approval workflow, and why is it important?

An approval workflow outlines the process by which loan or financial requests move through your organization before being finalized. It’s a safeguard that ensures the right people review sensitive actions. This supports compliance and risk management policies.

Can approval workflows be customized by loan amount?

Yes. Lenders can assign different approval layers based on loan amounts or risk levels. For example, smaller loans might go through a single-level approval, while larger ones could require multi-stage review involving multiple admins.

What is a loan product?

A loan product defines the type of loans you offer, including the loan amount ranges, interest rates, repayment tenors, and eligibility criteria. Each loan product determines the customer experience and ensures loans are issued under clear, predefined conditions. You must create at least one loan product before disbursing loans on your platform.

Can I create multiple loan products?

Yes. Lenders create multiple products to serve different borrower segments. For example, you might design one for salary earners with short tenors and low interest rates, and another for SMEs with higher loan limits and flexible repayment options.

Each product can also have its own credit scoring model and approval workflow.

How should I design a loan product?

Before creating a loan product, it’s best to document your design parameters with your team. Define your goals: are you optimizing for loan volume, profitability, or repayment reliability?

Discuss and set clear boundaries for loan amounts, tenors, and interest rates, and test different configurations to balance affordability with risk management. You can always update or refine these parameters based on borrower behavior and repayment performance.

What are the standard fees associated with loan products?

Loan fees on Lendsqr are grouped into two main categories:

Regular fees: Standard charges applied during loan processing, servicing, or subscription fees.
Penal fees: Applied when borrowers default or delay repayment, such as late payment or penalty charges.

Fees can be fixed, percentage-based, or hybrid, depending on your business model.

What happens when I deactivate a loan product?

When you deactivate a loan product, it becomes unavailable for new loan applications or disbursements. However, any loans that were already approved or disbursed under that product will continue running until they are fully repaid.

This ensures accurate performance tracking for historical products, even after they’re no longer offered to new borrowers.

What common mistakes should I avoid when creating loan products?

When setting up a loan product, accuracy and alignment are key. Avoid:

Incorrect or unrealistic interest rate configurations can lead to pricing errors or compliance issues.
Unclear or hidden fees can cause borrower disputes and reputational damage.
Mismatched minimum and maximum loan amounts or tenors may make the product ineligible for specific borrowers.
Poor documentation, where internal teams don’t have a shared understanding of how the product should function.

What key properties define a loan product?

Each loan product is defined by a set of core parameters that determine how it functions within your lending system. Key fields include:

Product ID and name: unique identifiers for internal tracking and reporting.
Description: a clear summary of the product’s purpose or target segment.
Customer type: defines who can access the product (e.g., salaried employees, SMEs, traders).
Repayment and disbursement methods: specify how funds are issued and how repayments are collected.
Interest rate and period: determines how much interest accrues over a given timeframe (daily, weekly, or monthly).
Loan amount and tenor limits: sets the minimum and maximum borrowing range and repayment duration.
Required documents and guarantors: outlines compliance requirements before approval.
Product status: indicates whether a product is active, inactive, or under review.

What repayment methods are available?

Lendsqr supports multiple repayment channels, depending on how your platform is set up. Borrowers can repay loans using:

Linked debit or credit cards
In-app wallets
Direct debit from bank accounts
External payment integrations (if configured)

Where is the loan disbursed to?

Loan disbursement destinations are defined at the product level. You can choose to:

Disburse to the borrower’s Lendsqr wallet
Send funds to their linked bank account

What is the loan savings multiplier?

The Loan Savings Multiplier is a ratio that links a borrower’s savings balance to their credit eligibility. It helps lenders ensure that borrowers’ loan limits are tied to their savings discipline. For instance, with a 2× multiplier, a borrower with ₦100,000 in savings can qualify for up to ₦200,000 in loans.

Why use the loan savings multiplier?

This feature offers three significant benefits:

Encourages savings: Borrowers are motivated to save more to increase their borrowing power.
Reduces default risk: By tying credit to liquidity, lenders can maintain healthier portfolios.
Improves customer profiling: Lenders gain insight into borrower behavior through savings patterns.

How does loan repayment work on Lendsqr?

Repayments follow a structured, transparent process that ensures funds are correctly accounted for.
All repayments are first credited to the borrower’s internal wallet, which serves as a settlement point.

From there, the system allocates payments across the correct components: principal, interest, fees, and penalties, according to your configured rules.

This two-step process enables lenders to maintain accurate records, facilitate reconciliation, and ensure that every repayment is correctly distributed to the correct ledger accounts.

What repayment methods are supported?

Lendsqr offers multiple repayment options to suit both lenders and borrowers:

Automated repayments: Scheduled through the system’s CRON jobs, which automatically trigger deductions on due dates.
Manual repayments: Borrowers can make payments through the mobile app, via USSD, or through unique payment links shared by the lender.
Direct Debit repayments: Borrowers authorize a direct debit mandate during the loan application. On repayment dates, their bank debits the approved amount and transfers it to Lendsqr’s settlement account.

What is the repayment application sequence?

When repayments are processed, funds are applied in a specific order to maintain consistency and operational accountability:

Penalties: Settles any outstanding penalty charges first.
Fees: Covers processing or management fees next.
Interest: Clears accrued interest on the loan.
Principal: Finally, it reduces the outstanding principal balance.

How does direct debit repayment work?

Direct debit repayments automate loan recovery through the borrower’s bank account. Here’s how it works step-by-step:

Authorization: Borrowers authorize repayment mandates during their loan application process.
Execution: On due dates, the bank automatically debits the borrower’s account for the repayment amount.
Settlement: The funds are settled into Lendsqr’s Providus Bank account, where they are credited to the lender’s system wallet.
Reconciliation: Transaction fees are charged to the lender, and settlements are reconciled against bank statements to ensure accuracy.
Reporting: For full transparency, Lendsqr provides monthly reports to external partners and weekly internal reports summarizing repayment performance and reconciliation data.

What must happen before users can start saving?

Before borrowers or customers can create savings plans, user onboarding must be completed and active savings products must be configured.

Lenders need to define savings products within the admin console, complete with interest rates, tenors, and Mifos settings (if applicable). Without these prerequisites, the savings module won’t function properly, as the app relies on preconfigured product data to display available options.

How does the savings process work for users?

Once setup is complete, users can begin saving directly through their web or mobile app:

They select a savings product that matches their goals or eligibility.
They enter the desired savings amount and tenor (duration).
The app generates a repayment or contribution schedule for review.
After submission, the plan is confirmed, and the savings account becomes active.

What happens if savings products aren’t defined?

If no savings products exist or they’re inactive, users won’t see any savings options on their app interface. The platform depends on these configurations to determine what plans and interest structures to display. Essentially, without a product setup, the savings feature is unavailable.

How can admins manage savings product status?

All new savings products are inactive by default to allow lenders to finalize configurations before going live. Admins can:

Activate a savings product to make it visible and accessible to users.
Deactivate it at any time if it needs updates, has reached capacity, or is temporarily unavailable.

These actions are managed via the “Savings Products” section of the admin console, giving full control over when and how savings options appear to borrowers.

What is a grace period in loan products?

A grace period is the time frame after a loan has been disbursed during which the borrower isn’t required to make any repayment, whether on the principal, interest, or both.

This feature provides borrowers with breathing room before their repayment cycle officially begins, which is particularly helpful for individuals or businesses with irregular income schedules.

How does it affect the repayment schedule?

When a grace period is applied, the borrower’s repayment schedule is shifted forward by the number of grace cycles set. For example, if a one-month grace period covers both principal and interest, the first payment won’t be due until the second month after disbursement.

All subsequent payments adjust accordingly, maintaining the same total tenor but with a delayed start.

What are tiers in?

Tiers in Lendsqr are customer classification levels that define what users can do on your lending platform based on their KYC (Know Your Customer) compliance, risk profile, and behavioral data.

They determine access to key services, including savings, loans, and transaction limits. Essentially, tiers help lenders balance accessibility with security and compliance.

What benefits do tiers provide?

Implementing a tiered structure helps lenders maintain both operational control and regulatory alignment. Some of the key benefits include:

Ensuring compliance: Meets KYC and AML (Anti-Money Laundering) standards by controlling who can access what.
Reducing fraud risk: Restricts high-value transactions for users with limited verification.
Managing credit exposure: Controls deposit, withdrawal, and loan limits according to verified data.
Improving scoring and decisioning: This process informs automated credit scoring by linking risk levels to customer profiles.
Enhancing security and oversight: Gives admins fine-grained control over customer permissions and progression.

What default and custom tiers exist?

There are three default tiers: Tier 1, Tier 2, and Tier 3.

Tier 1: Basic access for users with minimal KYC, capped at small transaction limits.
Tier 2: Intermediate level for partially verified customers with moderate transaction and loan access.
Tier 3: Fully verified customers with the highest transaction and loan privileges.

For lenders with specific regulatory or business needs, custom tiers can be created. These allow more flexibility, for example, adding a “VIP” tier for premium borrowers or a “Trial” tier for new users under review.

How do customers progress through tiers?

Tier progression can happen in two ways:

Automatic: The system upgrades or downgrades customers when they meet or fall short of defined criteria (e.g., submitting a valid ID or maintaining a positive repayment history).
Manual: An admin can manually adjust a customer’s tier after internal review or exception handling.

Where is tier data stored?

All tier-related data is stored securely within Pecunia’s database under the tiers table. Each record is linked by the organization ID, with full history logs that capture every change for transparency and audit tracking.

This ensures accurate monitoring of customer status and compliance over time.

Who is a guarantor?

A guarantor is an individual or organization that agrees to take financial responsibility for a borrower’s loan if the borrower fails to repay.

In other words, they serve as an additional layer of security for lenders, increasing confidence in the borrower’s ability to meet repayment obligations.

Guarantors are commonly used in riskier loan segments, such as high-value, unsecured, or first-time loans.

Why require a guarantor?

Requiring guarantors protects lenders from potential losses while reinforcing borrower accountability. Because a guarantor’s account can be charged if the borrower defaults, borrowers are less likely to delay or skip payments.

For lenders, this setting also improves portfolio quality, especially in environments where credit histories are thin or traditional collateral is unavailable.

How do I set a loan product to require a guarantor?

To configure this, navigate to Loan Product → Product Management → Product Settings in your admin console. Locate the “Guarantor required” attribute, enable it, and save your changes.

This ensures that borrowers applying for this loan type will be prompted to provide guarantor details during onboarding.

What additional guarantor settings can I configure?

Borrower & guarantor messages: Customize automated notifications or disclaimers explaining guarantor obligations.
Guarantor Oraculi scoring modules: Evaluate guarantors based on internal or third-party credit scoring models.
Number of guarantors required: Specify the number of guarantors a borrower must provide for approval.
Guarantor debit wait days: Set an organization-level delay before guarantor accounts are debited if borrowers default.

What are branches?

Branches represent your organization’s physical or operational locations. They mirror your real-world structure, enabling you to manage loans, staff, and customers more efficiently.

This setup is proper for lenders operating across multiple regions or distribution channels, allowing better oversight and localized decision-making.

What is a whitelist?

A whitelist is a feature that allows lenders to pre-approve or authorize specific customers for loan products even if they don’t meet the standard decision model criteria.

It works by identifying borrowers based on attributes such as BVN, email, or phone number and granting them access to loans that would otherwise be restricted or automatically declined.

What is manual loan booking?

Manual loan booking enables lenders to create and record loans for customers who cannot initiate requests digitally.

Using the Bank Verification Number (BVN) as the key identifier, lenders can profile, approve, and disburse loans even when borrowers face connectivity, device, or technical limitations.

What are the benefits of manual loan booking?

Improves accessibility: Customers who cannot use the app or online channels can still access credit.
Enables urgent processing: Loans can be booked and approved quickly for immediate financial needs.
Supports onboarding: New users can be profiled and added to the system via their BVN, facilitating future digital interactions.

How does manual booking work for new and existing users?

Existing customers: Enter the customer’s BVN, select the loan product and disbursement account, input the loan amount and tenor, then submit the request. The loan enters the approval workflow.
New customers: First, create a customer profile with BVN and bank details, then follow the same steps to book the loan.

What are the limitations?

Geolocation verification is not available.
Guarantors are supported for manually booked loans.
Specific loan form fields (e.g., API integrations, datetime, multimedia inputs) cannot be used.
Errors may occur if BVN or bank details are incorrect or if verification services are down.

What is a disbursement account?

A disbursement account is a dedicated central account created for every lender using Lendsqr. It manages all loan-related transactions, including fund outflows (loan disbursements) and inflows (repayments), providing complete transparency and control over financial operations.

What is third-party disbursement?

Third-party disbursement allows lenders to transfer loan funds directly to another party’s bank account on behalf of the borrower. This feature is ideal for use cases where funds need to reach specific beneficiaries rather than the borrower directly. Typical use cases are:

Rent payments: Loan funds sent directly to landlords.
School fees: Payments to educational institutions.
Invoice factoring: Supplier payments for purchased invoices.
Asset financing: Payments to vendors supplying financed assets.

Why send loan invites?

Loan invites are a strategic tool for lenders to reach prospective borrowers. Instead of requiring borrowers to first sign up or navigate the app, lenders can send a direct application link via SMS or email.

This approach reduces friction in the onboarding process, increases application completion rates, and allows lenders to target specific customer segments without modifying the core platform or decision models.

Why are Configurable Loan Forms (CLF) needed?

Standard loan application forms often limit the type and depth of borrower information that lenders can collect. CLFs allow lenders to capture richer, more granular data.

By customizing forms to specific loan products or borrower segments, lenders can reduce risk, improve underwriting accuracy, and better evaluate borrower capacity and intent.

Where do borrowers see CLFs?

Borrowers encounter CLFs in multiple channels:

On the web and mobile apps during the loan application.
Via loan invitations sent through SMS or email.

For a form to be visible, the loan product’s additional_form_data attribute must be activated in the admin console.

How are CLFs managed in Pecunia?

Admins can upload, edit, and preview JSON configurations under the Loan Attributes section in the product settings.

Pecunia provides real-time rendering so admins can see exactly how forms will appear to borrowers before saving.

What is Karma?

Karma is Lendsqr’s integrated blacklist engine designed to track individuals who have defaulted on loans or committed fraudulent activities across Lendsqr-powered lenders.

By maintaining records of high-risk borrowers, Karma helps lenders make informed decisions and mitigate lending risks.

How can lenders use Karma?

Admins can add new Karma entries with key details such as the borrower’s identity (phone, BVN, or email), type of activity (loan default or fraud), the amount owed or defrauded, and the date of the incident.

Karma records can also be searched by both entries added by your organization and external entries (the latter may require a paid search). This allows lenders to identify and track bad actors.

What are the possible reasons the system auto-declines loans

The possible reasons for a loan to be declined are:

Customer is in Karma blacklist: If a borrower’s phone number, BVN, or email matches entries in Karma, Nigeria’s primary blacklist system for fraud or unpaid loans, the request is automatically declined. Lenders can whitelist customers who were wrongly blacklisted to allow pre-qualification.
Too many failed loan requests: To prevent abuse, lenders can set caps on the number of loan requests a customer can make within a defined period. Requests exceeding this limit are declined, though whitelisting trusted customers can bypass this restriction.
Previously declined by the lender: Borrowers who were previously rejected for valid reasons may be temporarily blocked from reapplying. Admins can override this block via whitelisting for eligible customers.
Borrower has a running/active loan: To manage debt-to-income ratios and reduce default risk, new loan requests from borrowers with ongoing loans are often declined. Whitelisting can be used for select borrowers if policy permits.
Failed credit bureau check: Borrowers with a poor credit history, including past defaults, trigger automatic declines. Lenders can review the decision data for specific failure reasons and whitelist if justified.
Borrower is credit delinquent: Customers behind on repayments are flagged and declined to mitigate risk. In select cases, lenders may approve loans by whitelisting compliant delinquent borrowers.
Paid penalties before: Borrowers who have incurred late repayment penalties may be declined under default zero-tolerance settings. If penalties are settled, whitelisting can allow the borrower to proceed.
Failed selfie BVN verification: Mismatches between the borrower’s selfie and the BVN verification result in automatic declines due to fraud risk. Improved verification or cautious whitelisting may resolve this.
Excessive changes in employment category: More than two changes in employment category within a short period signal instability, causing declines. Thresholds are configurable, and whitelisting can be applied for trusted borrowers.
Frequent income category changes: If a borrower’s income category changes more than three times in 30 days, the request may be declined to reduce risk. Limits can be adjusted, and whitelisting allows flexibility for stable customers with unusual reporting patterns.

Smart Lending with Pecunia

The Pecunia web app does more than power digital lending. It simplifies complex operations and puts lenders in complete control of their ecosystem.

From automating decision models to customizing loan workflows, managing repayments, and tracking borrower performance, every feature is built to improve precision, transparency, and scalability.

Understanding how each component works ensures your lending business remains efficient, compliant, and customer-focused. Are you ready to optimize your lending decisions? Log in to your admin console to get started.