FPS pay-now and autopay readiness
Borrowers repay instalments by scanning an FPS QR or opening their bank app. Autopay setup explains the future bank-app authorization model without collecting or storing bank account numbers.
Platform package 04
Coming soon August 24th
Client Repayment App
Borrower dashboards, loan detail, FPS repay-now, autopay readiness, alerts, request tracking, statements, account controls, and messages — web and mobile.
Overview
The borrower-facing layer for repayment, requests, and lender communication.
The Client Repayment App gives borrowers a clear, self-service view of their loans, repayment schedules, and selected-lender requests. Instead of relying on phone calls and manual messages for every instalment update, borrowers sign in to see what they owe, pay via FPS, review bank-app autopay readiness, and track the status of loan applications they submitted through the marketplace.
Covenant Desk is instruct-only for payments: the platform generates FPS QR codes and reference codes, reconciles incoming bank credits, and surfaces truthful payment status — but never holds or moves funds. Staff receive worklist entries to post confirmed receipts into the source loan system. The same client experience is available on web (/client) and through the mobile API seam.
Requests and loan detail
Selected-lender loan requests, approval status, and per-loan repayment breakdowns — repayment amount, overdue interest, penalty, and total — in one client-facing view.
Messages and statements
Borrower messages and statement context stay linked to lender operations in the Management Portal. Staff responses appear in the client app.
Capabilities
What borrowers see and do in the client app.
Repayment, request tracking, marketplace tools, and lender communication — connected back to staff operations.
Borrower dashboard
Sign in with reference number and access code. Dashboard shows outstanding instalments across all active loans, sourced from synced repayment notices and loan records.
Loan detail and schedules
Per-loan view with instalment breakdown, repayment amount, overdue interest, penalty, and total due. Status chips show awaiting, received, and confirmed payment states.
FPS repay now
Dynamic FPS QR encoding the lender's proxy, amount, and reference code. Bank-app deep link and copyable manual details as fallbacks. Irrevocable — no chargeback.
Autopay readiness
Bank-app authorization guidance for future recurring debit. Covenant Desk does not see or store the borrower's bank account number; fallback remains FPS pay-now.
Marketplace and calculator
Browse the lender directory, compare options, and use the loan calculator before submitting a multi-lender request with explicit per-lender consent.
Messages and request tracking
Track selected-lender loan request status, receive lender messages, and view statements — all connected to the same records staff see in the Management Portal.
Workflows
How borrowers repay and stay informed.
From instalment due to confirmed receipt
The primary client-pay path uses FPS-push — no bank details collected from the borrower.
- Borrower signs in and sees outstanding instalments per loan with amount breakdown.
- Taps Repay → Covenant Desk creates a RepaymentIntent and generates an FPS QR with reference code.
- Borrower approves payment in their own bank app; funds land in the lender's corporate account.
- Bank notifies Covenant Desk of the incoming credit; reference code matches to the intent.
- Status updates to reconciled; borrower sees receipt with bank reference. Staff get a worklist row to post into the loan system.
From marketplace submission to status update
Borrowers follow their application without calling the branch for every update.
- Browse lender directory and submit a multi-lender request with selected-lender consent.
- Request appears in /loan-requests with status: pending review, approved, or additional info needed.
- Staff review in the intake queue; approved requests create or update borrower records.
- Borrower receives in-app messages and status changes as staff act on the request.
- Returning clients can request top-up facilities linked to their existing identity.
Key screens and payment objects
Client surfaces across web and mobile.
The Client Repayment App spans the borrower login, dashboard, repayment flows, and marketplace entry points. These are the primary routes and data objects involved.
- 01/client — borrower dashboard with outstanding instalments, loan list, and quick actions for repay and autopay readiness.
- 02/login (Client tab) — sign in with reference number and access code provisioned during staff intake or profile setup.
- 03/loan-requests — selected-lender request list with status tracking and message thread per application.
- 04RepaymentIntent — idempotent payment intent with FPS QR, reference code, amount breakdown, and reconciliation status.
- 05/client/account — editable account details, data-sharing consents, notification preferences, data export, and deletion request controls.
- 06/client/alerts — payment alerts and lender notifications with read state and links back into loan message threads.
- 07Autopay setup — bank-app authorization readiness without collecting or storing borrower bank account numbers.
- 08Mobile API seam — same repayment, request, and message endpoints exposed for native iOS and Android client apps.
Scope
Borrower self-service connected to staff operations.
Who uses it
Borrowers, customer service staff, operations teams, and managers rolling out repayment, messaging, statement, and request tracking journeys.
Included
Borrower dashboard, loan detail, repayment schedules, FPS QR, repayment intent, autopay readiness, messages, request tracking, statements, and account controls.
Controls
Borrower reference/access code login, lender branding, entitlements, data export, account preferences, no bank account storage for FPS pay-now, and staff reconciliation path.
Not included
The app does not issue lending offers, guarantee approval, or move funds through Covenant Desk. Funds go to the lender's configured account.
- DemoBring: borrower login method, FPS receiving details, statement expectations, messaging rules, and whether native mobile apps are required.