Skip to content

Cards & Customers

In Dara, card credit lines sit directly on the Financial Core. Each card type is tied to an account heading in the core, and each card is issued to a specific counterparty. When the customer makes a purchase, their credit is reduced on the spot and a provisional voucher is posted. Once the merchant confirms, the voucher becomes final; if the confirmation does not arrive in time, the credit goes back to the customer. The customer's profile, their requests and the messages sent to them sit alongside this same cycle.

Book a demoAll solutions

Key capabilities

  1. 01Single and bulk issuance, replacement cards, renewals, primary cards and card sharing
  2. 02Physical card activation with a one-time password, plus PIN management
  3. 03Two-phase purchases: a provisional voucher at purchase, a final voucher on confirmation
  4. 04Automatic credit release for purchases not confirmed in time
  5. 05Customer profiles and request intake with dedicated forms and SLA timers
  6. 06Notifications on five channels from a single outbound point
01

Issuance and card lifecycle

Cards are issued individually or in bulk. Replacement cards, renewals, primary card setup and sharing a card with another mobile number are all handled here. Physical cards are activated with a one-time password, and PIN changes and verification run within the same lifecycle. Limits, repayment periods and fees are defined at the card-type level.

  • Single and bulk issuance
  • Replacement and renewal
  • Primary cards and card sharing
  • Activation with a one-time password
02

Two-phase purchases

In the first phase, the available credit is read from the Financial Core, the purchase amount is set aside as a pending hold, and a provisional voucher is posted. Each transaction has a set time window. If the merchant confirms the purchase within that window, the voucher becomes final and the transaction is marked as settled. If no confirmation arrives, the expiry service expires the transaction and the credit is released. Every purchase carries an idempotency key, so a repeated request never creates a second purchase.

  • Pending hold and provisional voucher at purchase
  • Final voucher on merchant confirmation
  • Automatic expiry and credit release
  • Purchase reversals with a reversing voucher
03

Customer profiles and requests

Each customer has a profile that shows their cards, accounts and requests. Every request type has its own form, and from the moment a request is logged, its handling time is measured against the service-level agreement. Messages are sent from the Notifications & Messaging module by SMS, email, push notification, in-app inbox and one-time password.

  • A dedicated form for each request type
  • SLA timers
  • Five notification channels

Fantap, Dara's sister company, offers white-label LendTech infrastructure built on this same core, from credit and financing cards to the acceptance network and merchant settlement. To learn more, visit the Fantap website.

Platform modules behind this solution

Financial Core

Financial Core

This module holds each company's chart of accounts, detail levels, vouchers and fiscal periods. The balance of every account is computed in real time from voucher lines, and every other module records its financial effect only by posting a balanced voucher to this core.

Credit Card

Credit

Issuing and use of credit, gift or corporate cards, and settlement with merchants. Each purchase first reserves the balance and then creates a final voucher in the Financial Core; the card balance is not stored in LendTech itself.

Customer Relations (CRM)

Customer Engagement

Every customer request is a trackable ticket, with a form specific to its type, a response deadline and correspondence history. The 360-degree view shows that customer's financing, payments and wallet side by side.

Notifications (Pulse)

Customer Engagement

SMS, email, push and an in-app inbox from one point. Each service submits a send request, and Pulse selects the right provider and template according to the company.

More solutions

01

Core Banking & Qard al-Hasan Fund

A multi-level chart of accounts, three-stage vouchers, fiscal periods and treasury in a single Financial Core. Deposits, financing, cards and wallets all read their balances from it.

  • Chart of accounts with up to six detail levels and conflict-free code allocation
  • Vouchers in three stages: draft, provisional and final
  • Consecutive, non-resettable voucher sequence numbers for each fiscal period
Solution details
02

Deposit Management

Each deposit category is defined by about thirty policy switches, from withdrawal permission and partial holds to daily limits. The balance lives in the Financial Core, and the account simply points to it.

  • About thirty policy switches for each deposit category
  • Account numbers generated from a pattern and a check digit
  • Joint ownership with ownership percentages, withdrawal rules and signatory groups
Solution details
03

Scoring & Eligibility Models

Daily deposit balances are converted into scores every night, and an eligibility policy turns each score into a financing limit. Eleven scoring methods and four eligibility models are available.

  • Eleven scoring methods, from average daily balance to progressive tiers
  • Four eligibility models with rounding rules and minimum and maximum amounts
  • Each method's parameters held in a versioned policy, outside the code
Solution details
Get in Touch

See this solution on demo data

In a demo session we walk through your organization's scenarios on Dara's demo environment and answer your technical and finance teams' questions.

Book a demoContact us