Cards
A card is a payment device that lets a user transact at merchants. Cards can be physical or virtual, and can be tokenised for use in digital wallets. The platform lets you customise a card's attributes, behaviours and lifecycle — including spending limits, the number of card uses, and the number of active cards. These controls align with KYC:
- Spending limits — customers set limits based on their financial profile, helping them manage finances responsibly.
- Number of card uses — some customers prefer a single-use virtual card for specific online transactions.
- Number of active cards — helps verify the legitimacy of card requests and prevents unauthorised issuance.
Regional feature availability
Not all AdminNet features are available in every region, and what you can see depends on your program's configuration and your AdminNet role provisions. Some items described here may not be enabled for your program — contact MatchMove support via Freshdesk to confirm.
Sub-tabs
The Cards tab contains two sub-menus:
- Cards (the card list)
- Card Transactions
Type of Cards
The card list is the central place to view every virtual and physical card issued for a chosen period, each showing its current status. The list distinguishes between Virtual and Physical tabs — a virtual card has a different number, design and even limits versus a physical card.
Card type | Statuses |
|---|---|
Virtual — exists in digitised form, presented on screen and active immediately. | Active · Locked · Blocked |
Physical — a tangible instrument for in-store and online purchases. | Active · Pending Activation · Locked · Blocked |
Card ID | A card ID derived from the card number, used for tracking card details. |
User ID | The user's ID, used for tracking user details. |
Wallet ID | The user's wallet ID, returned at wallet creation. |
Proxy Number | A unique number used as an alternative to the card number. |
Card Transactions
Only cards with an Active status can be used to make purchases; attempts on inactive or cancelled cards are automatically declined. Card transactions fall into three types:
- Authorization
- Settlement
- Account Verification
Authorization
Online messages received as the platform processes transactions for cardholder accounts. There are two kinds:
- Non-financial — originates from the card network, payment institutions or merchants as part of the processing lifecycle; no impact on customer balances. Includes account verification.
- Financial — initiated when a cardholder executes and confirms a payment; impacts customer balances. Includes ATM, card-present, mobile wallet, card-not-present and contactless (wearable) transactions.
Authorization transactions appear under two sub-menus:
- Purchase History — authorised and approved open-loop transactions. From the list you can open the transaction, the card used, and the user who transacted. Quick filter pills for Success and Failed are available.
- Purchase Reversal — open-loop transactions that were reversed. Because they were not settled with the network, the funds are returned to the customer; the report supports reconciliation.
Both open a transaction detail page with these sections: Transaction Details, Amount Details, Merchant Details, Card Details, Account Details, User Details. Representative fields:
Transaction Details | Transaction ID, Transaction Type, Response Code, Channel (POS/ECOM/ATM), Network (e.g. VISA, Mastercard, RuPay), Retrieval Reference Number, Trace, Local Transaction Time/Date, Created At, Settlement Date, Transmission Date & Time. |
Amount Details | Card Amount, Card Currency, Transaction Amount & Currency, Fee Amount & Currency, Total Amount & Currency. |
Merchant Details | Merchant Name, Merchant ID, Merchant Category Code, Terminal ID, Acquiring Institution & code. |
Card Details | Card Number, Card ID, Proxy Number, Card Status, Preferred Name, Card Type, Date Expiry/Created/Closed, Closure Reason. |
Account Details | Wallet ID, Wallet Number, Wallet Balance, Net Balance, Date Created, Status. |
User Details | Personal details, biographical information, contact details, address information. |
Settlement
The settlement process reconciles transactions: receiving and validating clearing files (Clearing), comparing them with the authorised transactions on record (Reconciliation), and posting reconciled values to cardholder and program balances (Posting). Settlement transactions are categorised into buckets:
Exact Match | Authorisation and settlement amounts match exactly, with no discrepancies. |
Mismatch | The authorised and settled amounts differ — e.g. currency conversion variations, final hotel charges, or unavailable e-commerce goods. |
No Auth | A settlement with no corresponding authorisation (e.g. subscription charges). |
Auth Release | Authorised but not settled within the network's expected timeframe; the transaction is unsuccessful and funds are returned. |
Credit Voucher | Already settled with the network but requires a credit to the customer — merchant-originated credits (e.g. inability to deliver goods or services). |
Each bucket opens the same detail sections (Transaction Details, Amount, Merchant, Card, Account, User), with settlement-specific fields such as Settlement Date, Reversal Response Code, Reversal Date, Reversal Settlement Date and Response Balance.
Account Verification
Non-financial transactions that let merchants validate a cardholder's account status before submitting a full authorisation or recurring payment. Categorised by status: Success, Failed, Reversed.
Card Detail Information
Opening a specific card gives a complete view of that card:
Card Information | Card status (active, suspended, blocked), issuance and expiration dates. |
User Information | User details associated with the card, including biographical information and billing address. |
Account Details | The account linked to the card — account type and number, account holder information, balance. For non-shared-balance programs, Card Balance Details (with card number) appear here. |
Transaction History | A record of all transactions on the card. A Settlement Date Range filter is available to filter by settlement date. |
Card Management Actions
The platform provides controls for security and lifecycle management. These controls depend on region and role access.
Lock | Temporarily disable a card — when misplaced (not confirmed lost/stolen) or to prevent unauthorised use if suspicious activity is suspected. Locked cards cannot be used for new transactions, though existing pre-authorised transactions may still process. Only Active cards can be locked. |
Unlock | Reactivate a locked card. |
Block | When a card is confirmed lost, stolen or damaged, or to prevent further use in case of suspected fraud. |
For lost or stolen cards, terminate the card completely and issue a new one with a fresh PAN (Primary Account Number) for enhanced security.
On this page
- Cards