Glossary of terms
This glossary defines terms used across the MatchMove developer portal. Terms are grouped by category and listed alphabetically within each group, with acronyms spelled out on first use.
Card Operations & Payment Ecosystem
Acquirer / Acquiring Bank | The financial institution that processes a payment on behalf of the merchant. |
BIN (Bank Identification Number) | The first 6 to 8 digits of a payment card that identify the issuing bank, payment network, and card tier. |
BIN Sponsor / BIN Sponsorship | Allows non-bank businesses to issue payment cards by leveraging a licensed bank's access to networks like Visa or Mastercard. In a two-party model, the bank provides both regulatory compliance and backend technology directly to the card program. In a three-party model, a separate Technology Provider acts as middleware to handle software APIs and processing, allowing the program owner to launch much faster. |
Card Lifecycle | The sequence of states a card moves through — typically Issued, Activated, Suspended, Blocked, Expired, and Terminated. |
Card Network / Scheme | The central infrastructure (such as Mastercard or Visa) that connects the Acquirer and the Issuer to securely route transactions. |
Cardholder | The individual to whom a card is issued and who is authorized to use it. |
Chargeback | A forced reversal of a transaction, initiated by the cardholder's Issuer, that returns disputed funds from the merchant back to the cardholder. |
Closed Loop | A payment system restricted to within the platform, typically between accounts in the same ecosystem. |
CVC / CVV (Card Verification Code / Value) | The 3-digit security code used to validate online or Card-Not-Present purchases. |
DFCP (Digital First Card Program) | A form submitted to and approved by the network when a card design is numberless — one that omits or masks the PAN or other card details — required before card art can be submitted for approval. |
Dispute | A cardholder's formal challenge to a transaction (e.g., as fraudulent or incorrect), which may lead to a chargeback if upheld. |
Embossing / Personalization | Printing or engraving cardholder-specific details (name, PAN, expiry) onto a physical card during production. |
Form Factor | The physical or digital medium of the card (e.g., virtual, physical, or tokenized). |
Instant Issuance | Making a card (typically virtual) usable immediately upon approval, without waiting for physical production or delivery. |
Interchange Fee | A fee paid by the Acquirer to the Issuer for each card transaction, set by the Card Network. |
Issuer / Issuing Bank | The financial institution that provides the card to the consumer and holds the funds. |
MCC (Merchant Category Code) | A 4-digit code classifying a business type (e.g., airlines, retail), used to set spending rules or block certain purchases. |
MID (Merchant ID) | A unique identifier assigned to a merchant's business to process payments. |
Non-Personalized Physical Card | A physical card produced with generic (non-cardholder-specific) data, allowing it to be issued instantly from stock rather than manufactured to order. |
Open Loop | A payment system where a card can be used anywhere its network (such as Mastercard) is accepted. |
PAN (Primary Account Number) | The 16-digit card number printed on the card or generated virtually. |
Personalized Physical Card | A physical card manufactured to order with the cardholder's specific name, PAN, and other embossed or printed details. |
Platform-Managed Authorization | An authorization flow where MatchMove's platform evaluates and approves or declines a transaction directly, without the partner's own system in the loop. |
POS (Point of Sale) | The physical terminal or digital checkout page where a customer makes a payment. |
PPM (Prepaid Program Management) | The formal registration process a prepaid card program must complete with the network before it can be launched; not required for debit-only programs or those already covered under an existing approved PPM. |
Program Manager | The entity responsible for designing and operating a card program on top of an Issuer's licensed infrastructure — managing product rules, partner relationships, and day-to-day operations. |
Push Provisioning | Adding a tokenized card directly into a mobile wallet (e.g., Apple Pay, Google Pay) from within a partner's own app, without the cardholder manually entering card details. |
Shared Authorization | An authorization flow where MatchMove and the partner jointly evaluate a transaction, with the partner able to weigh in before it is approved or declined. |
TID (Terminal ID) | A unique number assigned to the specific POS machine processing a transaction. |
Virtual Card / Physical Card | The two form factors a card can take — a virtual card exists only as digital data for online or in-app use, while a physical card is a tangible card that can be used at a POS terminal. |
White-labeling | Issuing cards under your own company's branding while leveraging a partner's (like MatchMove's) banking license and infrastructure. |
Security, Compliance & Authentication
2FA (Two-Factor Authentication) | Requiring a secondary verification factor, such as a One-Time Password (OTP) or biometrics, to approve a transaction. |
3DS (3-D Secure) | An additional security layer for online transactions. Platform-Managed 3DS: MatchMove hosts the authentication screen. Assisted 3DS: Partners embed the OTP or biometric flow into their own app. |
AML / CFT (Anti-Money Laundering / Combating the Financing of Terrorism) | The regulatory frameworks requiring financial platforms to monitor and prevent illicit financial activities. |
Cooling-Off Period | Regulatory controls (like delay windows for adding new payment recipients) designed to protect users from fraud. |
Biometric Authentication | Verifying a user's identity using a physical characteristic, such as a fingerprint or facial scan, in place of or alongside a password or OTP. |
eKYC / KYC (Know Your Customer) | The mandatory digital process of verifying an individual user's identity using official IDs and biometrics. |
Fuzzy Name Matching | A screening technique that flags likely matches against watchlists or sanctions lists even when a name is misspelled, abbreviated, or formatted differently. |
KYB (Know Your Business) | The process of verifying a legal entity, its ownership structure, and directors. |
Maker-Checker (Four-Eyes Principle) | A security control where one administrator initiates a sensitive action and a second, independent administrator must approve it. |
MDES (Mastercard Digital Enablement Service) | Mastercard's service that facilitates the secure provisioning of tokens into mobile wallets (like Apple Pay). |
OTP (One-Time Password) | A single-use, time-limited code sent to a user (via SMS, app, or email) to verify their identity or authorize a transaction. |
PCI DSS (Payment Card Industry Data Security Standard) | A set of security standards that organizations handling card data must comply with to protect cardholder information. |
PEP (Politically Exposed Person) | An individual holding a prominent public position, subject to enhanced due diligence under AML regulations because of a higher risk of involvement in bribery or corruption. |
Risk Scoring | Assigning a numeric or categorical risk level to a user or transaction based on behavioral, identity, and transactional signals. |
Sanctions Screening | Checking a user or transaction against government and international sanctions lists to prevent dealings with restricted individuals or entities. |
SAR (Suspicious Activity Report) | A report filed with a regulator when a financial institution identifies a transaction or pattern of activity that may indicate money laundering or other financial crime. |
Tokenization | Replacing a card's real PAN with a unique, randomized digital placeholder (token) for secure payments. |
Velocity Limits / Spend Controls | Rules that cap the frequency, amount, or type of transactions a user can make within a given time period. |
Accounts, Money Movement & Accounting
Authorization | The instant approval and holding of funds when a card is swiped. |
Beneficiary / Recipient | The end party designated to receive funds in a payout or transfer. |
Clearing | The back-end process where the Acquirer and Issuer exchange final transaction data to confirm exact amounts owed. |
Collections | Funds received into the platform from an external source (e.g., a bank transfer or card payment) on a user's or program's behalf. |
Credit Prefund Balance | A prefund model where a program draws down against a pre-approved credit facility to cover real-time transactions, replenishing the facility periodically rather than depositing cash upfront. |
Cross-border Payouts | Moving money internationally, which incorporates real-time Foreign Exchange (FX) rates. |
Debit Prefund Balance | A prefund model where a business deposits actual cash in advance — a pool of collateral held to cover real-time user transactions and platform fees. |
Domestic Payouts | Transferring funds via local bank clearing rails (like ACH). |
Float | The total physical money held in a master bank account corresponding to the digital balances in users' wallets. |
Fund Category | A configurable sub-account or spending bucket within a wallet, used to partition funds and enforce granular limits — each with a name, a maximum amount (fixed or percentage-based), and an optional MCC filter restricting which merchant types it can spend at. Balances can be transferred between a user's categories via a |
FX Rate (Foreign Exchange Rate) | The rate at which one currency is converted into another, applied in real time to cross-border transactions and payouts. |
Ledger | The core database that records every single financial transaction (credits and debits) within the system. |
mJIT™ (Just-In-Time) Accounts | MatchMove's proprietary model where an account sits at a zero balance until a transaction occurs, instantly pulling the exact amount from a master funding pool. |
P2P (Peer-to-Peer) Transfer | Internal ledger transfers of funds directly between two accounts on the same platform. |
Partner Ledger | The subset of the platform ledger scoped to a single partner, recording every transaction across that partner's programs and accounts. |
Program Prefund Account | The account into which a program's prefund balance (credit or debit) is held before being drawn down for user transactions and fees. |
Program Virtual Account | A Virtual Account issued at the program level, used to route incoming funds for that program as a whole rather than for an individual user. |
Quote | A time-limited FX rate offered for a specific transfer amount and currency pair, locked in for the user to accept before the transfer is executed. |
Refund | Returning funds to a cardholder for a previously completed transaction, typically initiated by the merchant. |
Remittance | The transfer of money, often cross-border, from one party to another — commonly used to describe person-to-person international transfers. |
Reversal | Canceling an authorization or transaction before it settles, releasing the held funds back to the cardholder. |
Settlement | The actual, physical movement of money between banks to fulfill obligations established during clearing (usually 1–3 days later). |
Shared Balance | An account's balance is pooled and accessible across multiple cards (shared) owned by the user. |
Standard Accounts | Accounts that hold a persistent stored-value balance for an end user. |
Virtual Accounts | Proxy or "dummy" bank numbers assigned to users to automatically route incoming external bank transfers into a master corporate account. |
Wallet / Multi-currency Wallet | A digital store of value tied to a user, which may hold one or more currencies and funds cards, transfers, and payments. |
Technical Integrations & Administration
AdminNet | MatchMove's administrative back-office management console for inspecting ledgers, generating reports, and overseeing accounts. |
API (Application Programming Interface) | The set of rules allowing your software to communicate with MatchMove's servers. |
Callback URL | The partner-hosted endpoint that MatchMove sends webhook notifications or redirect responses to. |
Enumerations (Enums) | Predefined lists of strictly allowed API values (e.g., status fields accepting only ACTIVE or SUSPENDED). |
Idempotency / Idempotent Request | A safeguard ensuring that if an API request (like charging a card) is accidentally sent twice, the system recognizes the unique key and only processes it once. |
OAuth 2.0 / Bearer Token | An authorization framework where API requests carry a token in the request header to prove the caller's identity and permissions. |
Pagination | Splitting a large API response into smaller, sequential pages of results to reduce payload size per request. |
Payload | The actual data package (usually JSON) sent to the API to request an action (e.g., user details for onboarding). |
Program Code (program_code) | A unique identifier for a partner's program, used in API paths and payloads to scope requests to that program. |
Rate Limiting | Restricting the number of API requests a client can make within a given time window, to protect platform stability. |
Request ID / Correlation ID | A unique identifier attached to an API request, used to trace and troubleshoot that specific call across logs and systems. |
Sandbox / UAT / Production | The environment tiers a partner integrates against: Sandbox and UAT (User Acceptance Testing) for development and testing, Production for live transactions. |
SDK (Software Development Kit) | A packaged set of tools, libraries, and code samples that simplify integrating with an API in a specific programming language. |
Webhooks | Automated server-to-server push notifications triggered by platform events (e.g., an instant alert when a payment succeeds). |
Platform Architecture & System Entities
Account ID | The unique identifier assigned to a specific account or wallet within a user's profile, used to reference it in API calls. |
BaaS (Banking as a Service) | A model where a licensed institution like MatchMove exposes its banking infrastructure through APIs, letting a partner build and brand its own financial products on top of it. |
Card ID | The unique identifier assigned to a specific card record, used to reference it in API calls. |
Client Reference ID (client_ref_id) | A partner-supplied identifier attached to a request so the partner can trace and reconcile it against their own system of record. |
Partner | The business entity that has a commercial and technical relationship with MatchMove to build and operate one or more programs on its platform. |
Program | An instance of a specific card or wallet offering that a Partner operates on the platform, scoped and identified in the API by a program_code (see Program Code). |
User ID | The unique identifier assigned to a User / Customer Profile, used to reference that end user in API calls. |
Virtual Account ID | The unique identifier assigned to a Virtual Account, used to reference it in API calls. |
On this page
- Glossary of terms