Skip to content

Digital Wallet

Dara's wallet is for organizations that want to give their customers or members a payment tool without building a parallel set of accounts. Each wallet has a unique 16-digit number, and its table has no balance column: the balance is always read from the Financial Core. Every operation is first posted as a voucher in the core, and only then is the wallet's status updated. That is why wallet balances and the organization's accounts never drift apart.

Book a demoAll solutions

Key capabilities

  1. 01Single and bulk opening that carries on even if some rows contain errors
  2. 02Wallets organized into groups
  3. 03Voucher posted before any change to wallet status
  4. 04Amount holds pending a process decision, without issuing a voucher
  5. 05Transfers with a one-time password and a request idempotency key
  6. 06Full transaction register
  7. 07Payment Collection Gateway with seven methods on a single payment order
01

Balance from the Financial Core

A wallet lives at the detail-account level of the Financial Core. Top-ups, withdrawals and transfers are each a voucher in the core, and the transaction register is built from those same vouchers. The order is fixed: voucher first, then wallet status. If the connection drops partway through, no money moves without a voucher.

  • No balance column in the wallet
  • Voucher first, then local status
  • Register built from vouchers
02

Amount holds

Sometimes an amount has to be set aside before any decision has been made about it, for example when a request is waiting for approval in a process. The wallet can hold that amount without issuing a voucher. If the process approves it, the main operation goes ahead; if it is rejected, the hold is lifted.

  • Holds without issuing a voucher
  • Release based on the process decision
03

Bulk opening and transfers

Organizations that want to open wallets for all of their employees or members can use bulk opening. If a few rows in the list contain errors, the rest are still opened and the errors come back in a separate report. Transfers between wallets are confirmed with a one-time password, and the request's idempotency key prevents duplicate transfers.

  • Fault-tolerant bulk opening
  • Wallet grouping
  • Transfers with a one-time password
04

Payment collection

For wallet top-ups and installment payments, the Payment Collection Gateway brings seven methods together on a single payment order, from online payment gateways and POS terminals to card-to-card transfers and submitted deposit slips. Whichever method the customer chooses, the result comes back to that same payment order.

  • Seven payment collection methods
  • One payment order for every method

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.

Wallet

Finance & Payments

The wallet balance is not a stored number. It is read from the Financial Core. Top-up, payment and transfer are each posted as a balanced voucher in the Financial Core.

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.

Payment Collection Gateway

Finance & Payments

Collects payments through online payment gateways, POS terminals, card-to-card transfers and other methods, all against a single payment order. The deposit slip is stored alongside the transaction.

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