Core banking and source-system sync
Scheduled and manual sync, APIs and file exchange bring borrower, loan, overdue and upcoming notice context from your core banking and lending systems into portal records you own.
Integrations
Integrated with the systems your bank already runs.
Covenant Desk is custom and integrated: it connects to your core banking system, pulls from existing source systems, accepts structured imports, parses inbound communication, and exposes borrower and staff workflows through web and mobile surfaces.
How connections work
Core banking integration is what we do.
Covenant Desk includes its own core banking engine for lending, and it integrates with the core banking systems a bank already runs, through APIs or file exchange. Adopt it as the lending core, or run it beside your existing core. When it connects to your core, your loan system, a spreadsheet or a mailbox, it brings those records into a store you own. If you switch a source system off a year from now, your borrower records are still yours and still there.
That is why every connection begins with a source mapping rather than a credential. Before anything moves, the mapping records which system holds which field, which fields are authoritative, how borrowers are identified across companies, and what happens when two sources disagree. It is written down and agreed. Once live, each connection reports its own run history, so a sync that stopped three days ago is visible rather than silent.
Connection points
Source data, intake channels, payment instructions, and app surfaces.
Excel import
Spreadsheet import supports migration, one-off loading, and controlled intake where legacy workflows still depend on files.
Email intake
IMAP-connected inboxes can feed unread messages and attachments into AI extraction, confidence scoring, and staff review queues.
WhatsApp intake
WhatsApp screening captures borrower inquiries into structured lead records while preserving source channel metadata.
FPS repayment
Borrowers receive lender-specific FPS QR and reference details. Funds move through the lender's own account; Covenant Desk tracks intent and reconciliation context.
Mobile surfaces
Borrower and staff API surfaces expose loan detail, search, notices, messages, repayment, and profile context for web and native apps.
Available to connect
What we can connect for you now, market by market.
We connect each of these during your implementation, on your own account wherever money or borrower data is involved.
- 01
Stripe payments
Hong Kong, Singapore and Malaysia, on your own Stripe account: cards, Alipay and WeChat Pay in Hong Kong, PayNow in Singapore, FPX and GrabPay in Malaysia. Stripe does not allow loan repayments by credit card, so cards are used for fees and other payments.
Available to connect
- 02
Local payment gateways
The Philippines and Taiwan, where Stripe does not operate. Collections run on your own merchant account: PayMongo or Xendit for QR Ph, GCash, Maya and InstaPay payouts in the Philippines; ECPay or NewebPay for ATM virtual accounts and convenience-store codes in Taiwan.
Available to connect
- 03
E-signature
Every market. A self-hosted signing service, so documents and signatures stay in your deployment and there is no per-envelope fee. A document the law requires to be signed personally, such as the Hong Kong note under section 18 of Cap. 163, stays on paper until your solicitor confirms an electronic signature will do.
Available to connect
- 04
Messaging
WhatsApp Business in Hong Kong, Singapore, Malaysia and the Philippines, Viber in the Philippines and LINE in Taiwan, each on your own business account, for reminders and borrower messages.
Available to connect
- 05
Accounting
Xero and QuickBooks Online in every market, connected to your own subscription so repayments and disbursements post to your books.
Available to connect
- 06
Private AI with Minima AI
Every market. Covenant Desk distributes Minima AI, whose engine runs the AI features on a model inside your own infrastructure, on premises or in your private cloud, so no AI call leaves your network. Or use any hosted model provider you choose.
Available to connect
- 07
PhilSys Check
The Philippines. Verifies the signed QR code on a borrower's national ID card. The Philippine Statistics Authority offers it free to private companies.
Available to connect
Available
Government, bureau and bank connections, enabled for your institution on request.
These connections run through your own membership, scheme registration or bank. We build and connect each one during your implementation.
- 01
iAM Smart and CorpID
Hong Kong. Government sign-in, pre-filled borrower details and digital signing, for individuals through iAM Smart and for companies through CorpID. Available, enabled for your institution on request.
Enabled on request
- 02
Singpass Myinfo
Singapore. Myinfo pre-fills the application. Available, enabled for your institution on request, with the connection built during implementation.
Enabled on request
- 03
National digital IDs
Malaysia's MyDigital ID, the Philippine eVerify service and Taiwan's mobile citizen certificate. Each is connected through your institution's agreement with the issuing agency.
Enabled on request
- 04
Credit reference agencies
Through your own membership: the Credit Data Smart agencies in Hong Kong, the Moneylenders Credit Bureau in Singapore, CTOS and Experian in Malaysia, and CIC and its accredited bureaus in the Philippines. In Taiwan, JCIC reports are connected through your institution's membership.
Enabled on request
- 05
Direct debit
eDDA in Hong Kong, eGIRO in Singapore and DuitNow AutoDebit in Malaysia, each set up through your own bank, so instalments are collected without the borrower paying each time.
Enabled on request
- 06
Bank payment feeds
Automatic matching of incoming FPS, PayNow and DuitNow payments through your bank's API, with statement import matching as the file-exchange route.
Enabled on request
Discovery required
Every connection starts with source mapping.
The implementation demo confirms your entities, core banking and source systems, source fields, import files, receiving accounts, staff roles, borrower login method, and which intake channels go live first.
- 01
Data freshness
Sync health is visible through admin run history and dashboard status.
- 02
Field mapping
Lender-specific fields are reviewed before production import or sync.
- 03
Controls
Company scope, permissions, and audit are configured before staff rollout.
Before you connect
What banks ask about integrations.
Bring the systems you actually run and we will map them on the call, rather than guessing at them afterwards.
Not after migration. Records sync into the Covenant Desk database, which is your own. Keeping a source system connected during rollout is a convenience while you move across in phases. Covenant Desk is not affiliated with any legacy lending-system vendor, and nothing in the platform depends on one.
The mapping decides, and you write the mapping. Each field is assigned an authoritative source during discovery, and fields managed by a connected system are marked so staff do not overwrite them by accident. Where a conflict cannot be resolved automatically it surfaces for a named person rather than being silently resolved one way.
No. Borrowers receive a QR code and reference carrying your own FPS details, and funds move through your own bank account. The platform records the repayment intent and reconciles the credit against the right loan. It never holds, moves or takes custody of funds, and no software vendor can be an FPS participant — participation is limited to licensed banks and licensed stored value facility operators.
Extraction is scored, not assumed. High-confidence parses can route straight into the queue; low-confidence ones wait for a staff member to correct the fields before they become a borrower record. Duplicates are skipped by message ID, and every sync run reports how many items it processed, saved and failed on.
Borrower and staff API surfaces expose loan detail, search, notices, messages, repayment and profile context, and the same endpoints serve native iOS and Android clients. What a given integration can pull depends on the role it authenticates as, so company scope and permissions apply to an API caller exactly as they do to a person.
Each connection keeps a run history visible to administrators, and dashboard status reflects the freshness of the data behind it. A stale feed shows as stale rather than quietly serving old numbers, which matters when the queue you are working from is meant to tell you what to chase today.
Map your systems on a working session.
Bring the systems you actually run and we will map them on the call, rather than guessing at them afterwards.
Book a personalised demo