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.
Key capabilities
- 01Single and bulk issuance, replacement cards, renewals, primary cards and card sharing
- 02Physical card activation with a one-time password, plus PIN management
- 03Two-phase purchases: a provisional voucher at purchase, a final voucher on confirmation
- 04Automatic credit release for purchases not confirmed in time
- 05Customer profiles and request intake with dedicated forms and SLA timers
- 06Notifications on five channels from a single outbound point
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
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
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
Holds each company's chart of accounts, detail levels, vouchers and fiscal periods. Every account balance on the platform is read from here, and other modules record their financial effect only by posting vouchers to it.
Credit Card
Credit
A card credit line that links each card type to an account heading in the Financial Core. It takes the card from issuance and activation through two-phase purchases to merchant settlement.
Stakeholder Relations (CRM)
Customer Engagement
Each customer request is logged on a form specific to its type, and from that moment its handling time is measured against the service-level agreement (SLA).
Notifications & Messaging
Customer Engagement
Every message the platform sends to customers goes out through this module: SMS, email, push notifications, the in-app inbox and one-time passwords (OTP). Other modules send only the event type and its data.
More solutions
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.