Cards
A card belongs to a customer and draws on that customer’s accounts. Open the customer and choose Cards to see every card they hold, or Issue card to give them one.
Issuing a card
Choose the card type, plastic or virtual, the name to emboss and the account the card draws on. The processor creates the card first; if it refuses, no card exists.
- A virtual card is active at once.
- A plastic card is Ordered until the cardholder has it. Then choose Activate.
The embossed name is up to 26 letters A–Z, spaces, hyphens, apostrophes and full stops.
Your organisation never sees the card number: the card shows its first six digits and last
four, for example Virtual · 400000 …… 0001 · 2029-10 (fixture CardsComponentFixture,
trading date 1 October 2026, a three-year credential).
What you can do, and when
| Status | Offered |
|---|---|
| Ordered | Activate, report lost or stolen, close, rename, controls, travel, valid until, funding, reveal |
| Active | Suspend, report lost or stolen, reissue, close, rename, controls, travel, valid until, funding, remove device, reveal |
| Suspended | Reinstate, report lost or stolen, reissue with a new number, close, rename, controls, travel, valid until, funding, remove device |
| Lost or stolen | Reissue with a new number, close |
| Closed | Nothing |
Suspend and report lost or stolen take effect at once, with no countersignature: delay is the risk. The processor is told every change after it is saved.
Each verb sits where its effect shows. Rename, controls, travel window and funding are the pencil on the row they change; the travel window shows on the Details tab beside controls. Activate, suspend, reinstate, report lost or stolen, reissue and close sit on the Lifecycle card of the Details tab. Reveal and remove device sit on the Credentials tab’s header.
Controls and travel
Controls only narrow what a card may do. Switch off online, in-store, in-store abroad, ATM or contactless use, set spending limits, and block or allow merchant categories and countries — see Card spend controls. A travel window lets a card work in store in the countries you choose, between two dates, even when in-store abroad is off. A card has one travel window: choose the countries from the ISO 3166 list, and clear every field to remove it.
Funding
The funding rule is the ordered list of accounts a purchase draws on. Each account must be held by the card’s owner and be in the card’s billing currency. A credit-style card type draws on exactly one account.
Available to spend
The card’s Details shows Available to spend under Limits and rules. It is the most one purchase can take now. The Funding panel shows the same figure for each account, with its Facility and Held amounts. A purchase is checked against exactly this figure.
| The account | Available to spend |
|---|---|
| Holds money | Its available balance, plus any overdraft facility, less holds |
| Is a credit card account | The credit facility, less what is owed, less holds |
Worked example: a credit card account has a 20,000.00 facility, owes 12,000.00 and has a 500.00 hold. Facility reads 20,000.00, Held reads 500.00 and Available to spend reads 7,500.00. A purchase over 7,500.00 is declined for insufficient funds. See Credit cards.
A card’s own limits only narrow this figure. They never let through more than the account has available.
How a purchase is answered
When a card is used, the processor asks your organisation whether to approve. The answer comes from the ledger in a moment, checked in this order. The first check that fails is the reason given.
| Check | Declined as |
|---|---|
| The card is known and active | Unknown card, or card not active |
| The card’s valid-until date has not passed | Card lapsed |
| The card has not expired | Credential expired |
| The way it was used is switched on | Channel not allowed |
| The merchant category is allowed by the card and its card type | Merchant category not allowed |
| Used in store abroad: in-store abroad is on, or a travel window covers the day | Country not allowed |
| The merchant country is allowed by the card | Country not allowed |
| The amount and the number of purchases are within every limit | Ceiling exceeded, or frequency exceeded |
| An account in the funding rule is open | No funding account |
| An account in the funding rule has the money available | Insufficient funds |
Limits count what was approved, less anything the merchant reversed. A declined purchase names the rule that declined it — see Card spend controls.
The whole amount goes on the first account in the funding rule that has it available. It is never split across two accounts. If no account has it, and the merchant allows a partial approval, the first account with money available approves what it has.
Holds
An approval holds the money on the account it chose. The account’s balance does not move, but its available balance falls by the hold.
| Balance | Held by cards | Available | |
|---|---|---|---|
| Before the purchase | 4,200.00 | 0.00 | 4,200.00 |
| After a 1,200.00 approval | 4,200.00 | 1,200.00 | 3,000.00 |
The account shows the held amount beside its available balance as Held by cards. The card’s Holds panel lists each hold, newest first, with its merchant, the date it was placed and the date it expires. It shows 50 holds at a time; select Load older for earlier ones.
A hold ends in one of four ways:
| How it ends | When |
|---|---|
| Reversed | The merchant cancels the purchase. A part reversal reduces the hold and the rest stays. |
| Cleared | The purchase arrives in the processor’s clearing file and is posted to the account. |
| Expired | Its expiry date closes and nothing has cleared it. See Card hold expiry. |
| Card closed | The card is closed. A later clearing line still posts to the account. |
If your organisation does not answer in time, the processor answers in its place. The hold stays, because the processor may have approved the purchase.
Purchases
The card’s Purchases panel lists everything its clearing posted, newest first. A purchase, a refund and a reversal each show as their own row.
| Column | What it tells you |
|---|---|
| Transaction date | The day the cardholder used the card. |
| Value date | The day the posting counts from on the account. |
| Merchant | Who the card paid, or who paid it back. |
| Kind | Purchase, refund or reversal. |
| Amount charged | The amount in the card’s currency. |
| Merchant’s amount | What the merchant charged in its own currency, when that differs. Its currency is an ISO 4217 code. |
| Account | The account the posting went to. |
| Transaction | The posting on that account. Select the row to open the account’s transactions. |
Worked example: a card’s purchase of 250.00 clears, and the next day the merchant’s refund of 80.00 clears. The panel shows the refund on top and the purchase below it. Both name the same account.
A refund is its own row. It never reduces the purchase it came from, because the card schemes send a refund as a separate credit. So the purchase can still be disputed in full.
A tap that has not cleared yet is a hold, not a purchase. See it on the Holds panel until end of day posts it.
Disputes
Where your organisation runs card disputes, the card’s Disputes panel lists every dispute raised on its purchases, open and closed, with its stage and next due date. See Card disputes.
Device wallets and reveal
A wallet asks the processor to put the card on a phone. The first request steps up; the same device asking again the same day is approved, and the card gains a device wallet. If the phone is lost, choose Remove device: that wallet stops at once and the card carries on.
Reveal opens the processor’s own page with the full number or the PIN, for a few minutes. Your organisation records who asked and when, never the address or the number. No role holds reveal by default.
Renewal
At end of day, a card whose credential is about to expire is renewed. The card keeps its number; the processor answers the new expiry date, and the card shows it. A plastic card gets a new plastic on the same number and stays active.
A card is due when its expiry month ends within its card type’s renewal lead. A card already past its expiry is renewed too.
| Status | Renewed at end of day |
|---|---|
| Active | Yes |
| Suspended | Yes, and it stays suspended |
| Ordered | No: it was never activated, so it expires |
| Lost or stolen | No: its replacement is a new number |
| Closed | No |
If the processor refuses a renewal, the card stays as it was. The end-of-day log names the card by its display name and last four, and the next end of day tries again. A device wallet keeps its own expiry: the wallet provider renews it.
Worked example, on a simulated processor whose cards live two months, with a 45-day lead:
| Date | What happens |
|---|---|
| 5 May 2027 | A virtual card is issued, expiring 2027-07 |
| 15 June 2027 | End of day renews nothing: July ends 46 days away |
| 16 June 2027 | End of day renews it, expiring 2027-08 |
| 17 June 2027 | End of day leaves it alone |
Renewal is never on the Cards menu. A clerk who needs a new expiry date chooses Reissue with the same number.
Card fees
Three fees come from your organisation’s price list, and each is charged to the card’s first funding account:
| Fee | Charged when |
|---|---|
| Card issuance fee | The card first becomes active: on issue for a virtual card, on activation for a plastic one |
| Card replacement fee | The card is reissued with a new number |
| Card renewal fee | The card is renewed, at end of day or by a clerk’s reissue with the same number |
A fee priced at nothing posts nothing. A fee names the card it is for, so two fees on one statement read apart. A replacement plastic’s activation is not a second issuance.
Worked example: a funding account holds 1,000.00 and funds an active card. The price list charges 150.00 to replace a card. The card is reported stolen and reissued with a new number. The funding account is charged 150.00 as a card fee and holds 850.00.
A fee can take a funding account below zero, as a purchase can. If the funding account is closed, the fee is not charged: the card records it as forgone, and the card act stands.
Purchase fees
A purchase can carry two more fees, priced from the same list. Each posts right after the purchase, on the same account and value date.
| Fee | Charged when |
|---|---|
| Card currency conversion fee | The purchase was in another currency and converted to the account’s |
| Card ATM fee | A debit card draws cash at an ATM — channel ATM, or merchant category 6011 |
A credit card’s ATM withdrawal is a cash advance. It pays the cash-advance fee, not the ATM fee.
The price list chooses the row by what the purchase was. If the merchant’s country is not your organisation’s home country, the purchase is cross-border. If the merchant billed in the account’s currency (dynamic currency conversion), nothing was converted. An original currency is named by its ISO 4217 code. Every posting records these facts beside it, so a statement line shows why it was charged.
Worked example (CardFeePricingTests, the retail Standard list): a conversion fee of 2.75%
where the currency was converted. A 100 USD purchase billed 1,850.00 posts a conversion fee
of 50.88 (1,850.00 × 0.0275 = 50.875, rounded half up). A 500.00 rand purchase posts none.
Worked example (same list): the ATM fee is 2% with a floor of 10.00 at home, and 3% with a floor of 60.00 abroad. A 200.00 withdrawal at home pays 10.00. A 3,000.00 withdrawal at home pays 60.00. A 90 GBP withdrawal in London billed 2,000.00 pays 60.00, and a conversion fee of 55.00.
The replacement fee can differ by card type. On the retail list a debit card’s replacement costs 150.00 and a credit card’s nothing.
A customer’s price override applies to whichever row is chosen, from the override’s own date. See Price matrix for reading a fee’s rows side by side.
What your organisation configures
- The card fees on each price list, and which price list each account uses.
- How many days before expiry each card type renews — see Card types.
- The card types your organisation offers, and what each may do — see Card types.
- Which processor runs your organisation’s cards — see Card processor.
- How long a hold lives, by merchant category — see Card hold expiry.
- The merchant category groups that limits and rules name — see Merchant category groups.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.