MatchMove FAQs
Answers to the most common questions from partners building embedded finance — payments, accounts, and card issuance — with the MatchMove Banking Operating System.
If your question isn't covered here, contact your MatchMove Account Manager or the Matchmove Sales team.
A. Getting Started & Onboarding
(A) Questions and answers
(A) Questions and answers
[A1] What is the MatchMove Banking Operating System, and what can I embed into my product?
It is a Banking-as-a-Service (BaaS) platform for embedded finance — it lets you embed accounts, card issuance, collections, and payouts directly into your own product via APIs (Application Programming Interfaces), so financial services become a native part of your customer experience rather than a redirect to a bank. You operate the customer experience; MatchMove operates the regulated payment infrastructure underneath. Core building blocks include customer onboarding, wallets and accounts, prepaid cards, fund collection, and disbursement rails.
Reference: Platform overview
[A2] What sample use cases can I run as a program on MatchMove?
Common embedded finance programs include corporate expense and spend-management cards, payroll and benefits disbursement, gig-economy and marketplace payouts, consumer wallet and neobank-style propositions, loyalty and rewards wallets, and B2B (Business-to-Business) supplier payments. Each combines the same building blocks — onboarding, wallets, cards, collections, and payouts — configured to the use case. Your MatchMove Account Manager can walk you through reference programs closest to your business model.
Reference: Use cases
[A3] I don't have my own app — can MatchMove provide one?
MatchMove provides the backend financial infrastructure, accessible via API. The frontend — whether a mobile or web application — is the partner's responsibility to build and operate. This keeps you in full control of your brand and user experience, with the developer portal's guides and process documentation supporting your build.
Reference: MatchMove API overview
[A4] What does partner onboarding look like, and how long does it take?
Onboarding starts with commercial scoping and KYB (Know Your Business) due diligence, after which your integration requirements are gathered and used to configure your dedicated UAT (User Acceptance Testing) stack environment. Once the stack is created, your API access credentials are released, and integration, UAT, and production go-live follow. Timelines depend on use case complexity and compliance review, with your MatchMove Implementation Manager supporting you throughout.
[A5] Do I need my own payment or e-money licence to launch?
No — you operate under MatchMove's regulatory licenses and authorizations in each supported market. You remain responsible for your own business conduct and any sector-specific obligations. Licensing coverage is market-dependent, so confirm the scope for each country you plan to launch in.
[A6] Which markets and currencies are supported?
At the base, SGD and USD are supported alongside the local currencies of each operating market, with cross-border payout corridors extending currency reach further. Currency availability depends on region and program configuration. Product availability also differs by market — so validate your target market's feature and currency set with your MatchMove Account Manager during scoping.
[A7] What information and documents do I need to provide for onboarding as a partner?
KYB due diligence typically requires company registration documents, details of directors and UBOs (Ultimate Beneficial Owners), proof of registered address, and a description of your business model and intended use case. Additional documents may be requested depending on your industry, market, and risk profile. Having these prepared in advance is the single biggest factor in a fast onboarding.
[A8] Are there restricted industries or prohibited business categories?
Yes — certain business categories are restricted or prohibited under regulatory requirements, card network rules, and MatchMove's own risk policies, consistent with industry practice. Your use case is assessed during KYB, and approval is scoped to the business model you present. Discuss any higher-risk elements of your model openly during scoping to avoid surprises later.
Reference: Prohibited industries, High-risk industries
[A9] Does MatchMove's role and operating model differ between markets?
Yes — depending on the market, MatchMove may operate under its own license or in partnership with a locally licensed or regulated institution, which affects program structure, timelines, and responsibilities. The capabilities exposed to you through the platform remain consistent, but the underlying regulatory arrangement differs. Your MatchMove Account Manager will confirm the operating model for each target market during scoping.
[A10] Does our company need a business entity in the program's region to sign the contract and start a program?
MatchMove will request the Partner to have an entity in the jurisdiction designated for the partnership. However, this does not need to hold up signing: MatchMove can sign based on the Partner's existing entity and novate the agreement — transfer it to the designated entity — after it is established. Raise your corporate structure with your MatchMove Account Manager early so the contracting path can be planned alongside the prerequisites.
B. Products & Capabilities
(B) Questions and answers
(B) Questions and answers
[B1] What account and wallet capabilities are available?
You can create customer-level accounts (wallets) that hold balances, receive funds, and pay out, with full transaction history via API. Accounts support funding models including standard prefunding and mJIT™ (MatchMove Just-in-Time funding), where funds move at transaction time. Multi-purpose wallet structures let you separate balances by use case.
Reference: Accounts overview
[B2] What is a virtual account?
A virtual account is the banking interface of a user account — a bank-account-style number attached to a wallet so it can receive funds through the banking system. All deposits made to the virtual account land in the underlying wallet, credited automatically with no manual reconciliation needed. Availability of virtual account assignment depends on market and program configuration.
Reference: Virtual accounts overview
[B3] What are fund categories (multi-pocket wallets)?
A fund category — also called a pouch or pocket — is a compartment within a wallet that holds its own balance, enabling use cases such as separating meal, transport, and general-spend funds. Each pocket can be restricted to specific usage, for example, by MCC (Merchant Category Code), and funds can be transferred between categories. A default category automatically handles any transaction where none is specified.
[B4] What are closed-loop and open-loop transactions?
A closed-loop transaction is a direct debit or credit to a wallet that never touches the card network — for example, loading funds from your prefund balance to a user's wallet. An open-loop transaction originates from the card network — a purchase at a merchant — and is routed to MatchMove for authorization. Both types are retrievable via the transaction APIs and are reported separately.
Reference: Transactions overview
[B5] What card products can I issue?
The platform supports virtual and physical prepaid and debit cards on major card networks, issued instantly via API. Virtual cards are online-only cards used for e-commerce payments, while physical cards work at in-person terminals, POS (Point of Sale), and ATMs (Automated Teller Machines), and can be ordered as personalized or non-personalized. Multiple card types and card designs can be configured within a single program.
Reference: Cards overview
[B6] Do you issue credit cards?
No — MatchMove issues prepaid and debit cards, not credit cards. Credit-like experiences can sometimes be approximated through program design, for example employer-funded expense cards with controlled limits. If your use case requires true credit issuance, discuss alternatives with your MatchMove Account Manager.
[B7] How do collections (transfer-ins) work?
Collections let your customers or counterparties fund accounts through local and international bank transfers via the virtual accounts, depending on market. Incoming funds are credited to the target wallet and surfaced via API and webhooks. Reconciliation data is available per transaction.
Reference: Collections overview
[B8] What payout (transfer-out) and disbursement options exist?
Payouts feature two modes: direct transfers, where funds move from a wallet to an external bank account or beneficiary, and POBO (Payments On Behalf Of), where payouts are made to end beneficiaries on your behalf — initiated from your corporate float or from a user account. Both cover domestic transfers over local rails and cross-border payouts to bank accounts, cash pickup points, and mobile wallets, depending on the corridor. You initiate payouts via API with status tracking through to completion or return.
Reference: Payouts overview
[B9] Which sender-to-recipient combinations are supported for cross-border payouts?
All four combinations are supported: C2C (Consumer-to-Consumer), C2B (Consumer-to-Business), B2B (Business-to-Business), and B2C (Business-to-Consumer). The originating entity type follows your program setup — a corporate program originates as a business, a consumer program as an individual — and each program supports one entity type. Beneficiaries are risk-screened at creation, and rail-level limits maintained by providers also apply, so confirm corridors and limits during scoping.
Reference: Cross-border payouts
[B10] Can I run a spend-management or expense use case, such as corporate cards for staff?
Yes — issue cards tied to controlled wallets and set per-card limits, funded either through standard prefunding or just-in-time funding, where cards only draw funds at authorisation time. Transaction-level data — merchant, MCC (Merchant Category Code), and amount — supports expense categorisation. Real-time webhooks let you build approval logic or alerts into your own application.
Reference: Corporate Expense Management & Payroll
[B11] Does the platform support multiple currencies, and how are FX rates determined?
Cross-border payouts involve FX (Foreign Exchange) conversion, with rates quoted by the underlying payment rails and providers at transaction time and visible in the transaction record. Supported currencies and corridors depend on your markets and the rails in scope for your program. For card transactions, FX rates are set by the card network, while card payment fees and markup are set at the program level.
Reference: Card transaction fees, Get a quote for cross-border payment
[B12] How quickly do funds settle — for collections coming in and payouts going out?
Settlement timing depends on the rail: domestic real-time rails credit in near real time, while cross-border transfers and card-network settlements follow their respective cycles. Payout completion is tracked via API status and webhooks through to a terminal state. Expected timelines per rail and corridor are confirmed during scoping.
Reference: Transaction settlements
[B13] How does prefunding and float management work day to day?
You maintain a program prefund account — your pool account in the program — that transactions draw down from. A dedicated corporate virtual account can be tied to this program prefund and used to top up the prefund balance by bank transfer. Low-balance email alerts can be configured at thresholds you set in AdminNet, alongside balance visibility via API.
Reference: Program prefund, Program virtual account
[B14] Can I send bulk or batch payouts?
Yes — high-volume disbursement use cases such as payroll, marketplace seller payouts, or rewards are supported through the payout APIs, with each payout individually tracked. Design your integration for idempotent submission and webhook-driven status handling at scale. Flag expected batch sizes and frequency during scoping so limits and float are provisioned accordingly.
[B15] What happens if a payout fails or is returned?
Failed or returned payouts — for example, due to incorrect beneficiary details or a closed account — move to a failure or returned status visible via API and webhooks, with funds credited back to the source wallet. Where a transfer succeeds on the platform side but is rejected by the upstream bank, an associated reversal transaction returns the funds. Your integration should handle these states and surface them to your users or operations team.
C. Integration & APIs
(C) Questions and answers
(C) Questions and answers
[C1] What is the API architecture and how do I authenticate?
The platform exposes RESTful (Representational State Transfer) JSON APIs organized by domain: customers, accounts, cards, collections, payouts, and platform. Authentication uses HTTP Basic Authentication with your API Consumer Key and Secret, issued per environment and used against the endpoint carrying your program code — keep credentials server-side only. Endpoint requests are only accepted from your whitelisted IP (Internet Protocol) addresses, and OpenAPI specifications are published on the developer portal for every module.
Reference: Access the endpoints
[C2] Is there a sandbox I can test in?
MatchMove provides a dedicated UAT stack environment rather than a public self-serve sandbox. Since programs differ in configuration and enabled features, a UAT or staging stack environment programmed to your requirements can only be provisioned after signing, with test credentials released once stack provisioning is complete. The environments are functionally almost identical. Whatever you develop against UAT works unchanged in production, with only the endpoint base URLs and API credentials differing. However, due to network or payout rail partner rules, some transactions can only be tested in the real-world environment, in the live environment.
Reference: Staging and live environments
[C3] What are the limitations of the UAT environment — what can't I test there?
UAT provides simulators in place of live external parties — for example, an authorization simulator for open-loop card transactions and bank-transfer simulators in select markets — and physical cards are not actually produced there. No pre-loaded test data is provided: you create your own by registering users, wallets, and cards through the APIs; never use real customer data. Load or performance testing is not supported, and anything that can only be validated on live rails belongs in your production pilot.
Reference: Staging and live environments, Simulate card transactions
[C4] Can I start evaluating or integrating before contracts are signed?
The developer portal — API references, guides, and process documentation — is publicly accessible, so your technical team can evaluate the integration effort immediately. Hands-on access is provided post-signing: UAT environment credentials are issued once your stack has been created. Plan your pre-contract evaluation around the public documentation and scoping discussions with your MatchMove Account Manager.
[C5] Where do I get my API access credentials?
Your credentials will be provided to you by your MatchMove Implementation Manager when the stack setup is completed and include the API URL endpoint, the API Consumer Key and Secret, and your AdminNet portal URL. A separate set of credentials is issued for UAT and for production.
[C6] What is the basic integration sequence, and is there an entity hierarchy?
The foundational sequence is: create a user, put the user through KYC (Know Your Customer), and once KYC is approved, proceed to create accounts, virtual accounts, and cards — then the other financial features such as transfers, collections, and payouts become usable. The hierarchy is strict: a user holds a wallet, and a wallet holds zero or more virtual and/or physical cards, so a wallet or card cannot be created before its user exists.
Reference: Begin technical integration
[C7] Do you support webhooks for asynchronous events?
Yes — webhooks notify your system of events such as transaction authorizations, funding credits, payout status changes, and KYC (Know Your Customer) outcomes. You register endpoint URLs and should verify payload authenticity and implement idempotent processing. Webhooks are the recommended way to track event outcomes, so design your integration to be event-driven from the start.
Reference: Leverage webhooks
[C8] What API versioning and deprecation policy applies?
APIs are versioned per module — for example customer v1 and v2 — and versions may carry regional availability restrictions, so confirm which versions apply to your markets. Breaking changes can occur, including within a version, but partners are given ample time to adapt to breaking or required API upgrades before they take effect. Migration guides are published when versions change, and monthly release notes document all platform changes, including deprecations.
Reference: Releases and updates
[C9] Are there SDKs, or is integration purely via REST?
Integration is primarily direct REST using the published OpenAPI specifications, which you can also use to generate API client libraries in your preferred language. Outside of specific components such as the eKYC (electronic Know Your Customer) SDKs (Software Development Kits), integration is spec-driven REST rather than SDK-based. The developer portal's API reference is the source of truth for requests and schemas.
Reference: MatchMove API overview
[C10] What are the rate limits and expected API performance?
Rate limits and throughput expectations are environment- and contract-dependent and are shared during technical onboarding. Note that the UAT or staging environment is deliberately throttled down relative to production, so UAT response times and throughput are not indicative of production performance. Design for retries with exponential backoff and idempotency to handle transient errors gracefully, and flag high-volume use cases during scoping so capacity can be provisioned.
D. Security
(D) Questions and answers
(D) Questions and answers
[D1] How is the platform secured and what certifications does MatchMove hold?
The platform is operated to industry security standards, including PCI DSS (Payment Card Industry Data Security Standard) compliance for card data handling. Transport is encrypted via TLS (Transport Layer Security), credentials are scoped per partner and environment, and access to the platform and its endpoints is restricted to whitelisted partner system IP (Internet Protocol) addresses. Formal certification attestations can be shared under NDA (Non-Disclosure Agreement) during due diligence.
Reference: Secure endpoint integration
[D2] Do I ever touch raw card data such as the PAN or CVV?
No — sensitive card data such as the PAN (Primary Account Number) and CVV (Card Verification Value) is handled entirely within MatchMove's PCI-compliant boundary. Card details are exposed to cardholders through secure display mechanisms rather than through your servers, keeping card data out of your systems entirely.
Reference: Retrieve sensitive card information
[D3] Is my business required to be PCI DSS compliant before I can start a program?
No — PCI DSS (Payment Card Industry Data Security Standard) certification is not a prerequisite for launching a program, because sensitive card data is handled within MatchMove's PCI DSS-certified boundary, and you ride on that certification. You are, however, required to follow PCI DSS guidelines in how you build and operate your application and to keep sensitive card data out of your own systems, logs, and support tickets. If your product independently handles card data outside the platform, raise this during scoping, as it changes your compliance obligations.
[D4] How are API credentials managed and rotated?
Credentials are issued per environment (UAT and production) and must be stored server-side in a secrets manager — never in client-side applications or code repositories. Rotation can be requested through your support channel, and compromised credentials should be reported immediately for revocation. Credentials are scoped to the modules your program uses, following the principle of least privilege.
[D5] Is IP whitelisting required to access the platform?
Yes — your source IP (Internet Protocol) addresses must be whitelisted before you can access the MatchMove platform, and this applies both to API access from your servers and to AdminNet portal access by your operations team. Whitelisting applies to all environments, UAT and production alike, so submit your static IP addresses for each during technical onboarding and notify MatchMove ahead of any infrastructure changes that alter them. Requests from non-whitelisted IPs are rejected, so keep your registered list current to avoid disruption.
Reference: Access the endpoints
[D6] Can I whitelist MatchMove's IP addresses on my side?
MatchMove's outbound services run on a dynamic pool of cloud provider IP (Internet Protocol) addresses, so whitelisting individual MatchMove IPs on your firewall is not recommended. Where your security policy requires restriction, use domain-based whitelisting instead — the list of domains is available from technical support. Design your webhook receivers to authenticate payloads rather than rely on source IP alone.
[D7] Do I need to perform security testing (VAPT) on my own application?
Yes — if you operate your own application consuming the platform APIs, you are expected to perform VAPT (Vulnerability Assessment and Penetration Testing) on it and remediate any findings. The platform's certifications cover MatchMove's side of the boundary; your application, servers, and credential handling remain your responsibility. Regular VAPT is also commonly expected by regulators, auditors, and card networks.
[D8] Is my data mixed with other partners' data?
No — each partner runs on its own dedicated stack, and your program data is maintained separately from that of other partners. This segregation applies across users, wallets, cards, and transaction data. Stack-level isolation also means your configuration, limits, and card types are specific to your program.
[D9] What fraud and transaction-monitoring controls are in place?
Transaction monitoring, velocity limits, and card controls — limits, channel blocks, and geographic controls — operate at the platform level, complemented by controls you configure per card or wallet. Suspicious activity flows into MatchMove's compliance monitoring as the regulated entity. With shared authorization enabled on your program, you can layer your own risk logic using real-time webhooks, allowing you to decide on the transaction before it is approved.
[D10] How is customer data protected and where is it stored?
Personal data is processed in line with the applicable data protection laws of each operating market, with encryption at rest and in transit. Some markets require on-soil data storage or processing, and MatchMove operates local infrastructure where regulation requires it; residency specifics are covered in the data processing terms of your agreement. Access is role-restricted and audit-logged.
[D11] Where are customer funds held, and how are they safeguarded?
Customer funds are safeguarded in accordance with the regulatory requirements of each operating market, under the supervision of the relevant financial regulator. Funds held in wallets are segregated from MatchMove's own operating funds as required by regulation. Market-specific safeguarding arrangements can be detailed during due diligence.
E. Compliance & Regulatory
(E) Questions and Answers
(E) Questions and Answers
[E1] Who is responsible for KYC of end users — the partner or MatchMove?
End-user KYC is performed through the platform's native identity verification capabilities as part of customer onboarding, with MatchMove as the regulated party setting the requirements. You integrate the onboarding APIs and collect the required documents and data within your own user experience. Verification outcomes — approved, rejected, or pending — are returned via API and webhooks.
Reference: Identity & onboarding overview
[E2] What does the KYC flow look like for an end user?
The user submits identity data and documents through your app to the onboarding APIs, which run document verification, liveness and selfie checks, and screening. Results are returned asynchronously with a clear status you can act on in your user experience. The KYC journey may differ from user to user based on residence region and user and industry risk levels.
Reference: [v2] Onboard individual user
[E3] Do KYC requirements differ by market?
Yes — mandatory KYC fields, documents, and verification methods are driven by each market's local regulation, so requirements are not uniform across regions. The platform enforces the correct requirement set per program and market, and accepted field values can also differ by region. Factor these differences into your onboarding user experience for each market you launch in.
Reference: Region-specific onboarding
[E4] What eKYC options are available — and can I use my own provider?
MatchMove eKYC (electronic Know Your Customer) is the primary verification method, with verification performed by partner banks where required in some regions. As the regulated entity, MatchMove is mandated to conduct its own due diligence on its platform users; therefore, verification through a partner's own eKYC provider cannot be relied upon in its place. Contact your MatchMove Account Manager if you require further clarification on the verification setup for your target markets.
Reference: Perform individual eKYC
[E5] What AML obligations do I take on as a partner?
AML (Anti-Money Laundering) screening, sanctions checks, and transaction monitoring run at the platform level, but you must operate within your approved program scope and cooperate with information requests. Your use case is assessed during KYB and must remain within the approved scope. Notify MatchMove of any material changes to your business model.
[E6] Are there limits on wallet balances and transactions?
Yes — limits are driven by regulation, such as e-money limits in some markets, and by the KYC status of the end user. Per-transaction, daily, and balance caps are configurable within regulatory ceilings. Limit structures are agreed upon during program setup and can differ per market.
[E7] Who is the issuer of record for cards, and who holds cardholder funds?
MatchMove (or its locally licensed partner institution, depending on market) is the issuer of record with the card network and the regulated holder of cardholder funds. You are the program brand, while regulatory accountability for issuance and funds sits with the licensed entity. This split is documented in your program agreement and can be explained to your own auditors or regulators as needed.
[E8] What data privacy obligations do I have as a partner?
You act as a data controller (or the equivalent role under local law) for the personal data you collect from your customers, with your own obligations around consent, notices, and lawful processing. MatchMove processes that data for regulated service delivery under the data processing terms of your agreement, which define roles and responsibilities. Ensure your privacy policy accurately reflects the data shared with MatchMove for onboarding and transaction processing.
Reference: Understand account limits, Configure card transactional limits
[E9] Why might an end user's onboarding be rejected, and can it be reviewed?
Rejections typically result from failed identity verification, screening matches, incomplete or inconsistent documents, or risk evaluation hits. Rejection statuses are returned via API so you can guide the user — for example, prompting a document resubmission where permitted. Cases requiring manual review are handled through your operational support channel, though certain compliance outcomes are final and cannot be disclosed in detail.
[E10] Can I submit customer data and KYC documents in local languages such as Chinese, Vietnamese, Korean, or Arabic?
It depends on which layer the data is going to. API parameters must be in Latin script — names and addresses in local scripts should be transliterated before submission, because the card networks, banking rails, and screening systems the platform connects to all exchange data in Latin characters, and interoperability across them depends on it. KYC (Know Your Customer) documents are the exception: identity documents issued in a local language can be uploaded as they are, and the platform applies auto-translation during verification — so build your onboarding to transliterate the typed fields while accepting documents untouched.
F. Card Programs
(F) Questions and answers
(F) Questions and answers
[F1] How does physical card distribution work end to end?
Three models are supported: personalized cards delivered directly to cardholders; non-personalized stock handed over for you to distribute and link to customers, including QR code-based linking; and assign-and-deliver, where cards are assigned before delivery. Card ordering and delivery are managed through the Card Order and Delivery Service. Activation is a controlled final step before first use.
Reference: Card order and delivery
[F2] Can I customise the card design with my own branding?
Yes — cards carry your brand within card network and issuer design rules covering logo placement, the BIN (Bank Identification Number) area, orientation, and mandatory elements. Design guidelines specify what can and cannot be altered on the card front and back. Artwork goes through an approval cycle with the card network before production.
Reference: Create your card product, Launching a card program
[F3] What happens on a card authorisation in a just-in-time funding model?
With mJIT™, an authorization triggers a real-time funding check and transfer from the designated funding source at transaction time, rather than requiring the card wallet to be prefunded. The shared authorization model must be enabled to allow you, as the partner, to decide on the transaction — the authorisation request is passed to you in real time, and your approval determines the outcome. If funds are available and the transaction is approved, the amount is settled from the funding account, minimizing idle float while keeping approval latency low.
Reference: mJIT™ accounts, Transaction authorizations
[F4] How do refunds, reversals, and chargebacks work?
Refunds and reversals from merchants are credited back to the card wallet and are visible via transaction APIs and webhooks. Chargeback and dispute handling follows card network rules, with MatchMove managing the scheme process as the issuer. You surface dispute intake in your user experience and coordinate evidence through support channels.
Reference: Transaction settlements
[F5] Are online card transactions protected with 3DS or strong customer authentication?
Yes — e-commerce transactions are supported with 3DS (3-D Secure) authentication in line with card network requirements, with cardholder verification such as OTP (One-Time Password) challenges during checkout. 3DS authentication is merchant-initiated: whether a challenge is triggered depends on the merchant and their acquirer, alongside market regulation. 3DS behaviour for your program is confirmed during card program setup.
Reference: Platform-managed 3DS authentication
[F6] Can issued cards be added to mobile wallets such as Apple Pay or Google Pay?
Mobile wallet tokenization availability depends on the card program, network, and market and is scoped as part of your program setup rather than enabled by default. Where supported, cardholders can provision their card to the device wallet and transact via NFC (Near Field Communication). Confirm tokenization support for your target markets with your MatchMove Account Manager.
[F7] What is the difference between a shared BIN and a dedicated BIN, and when do I need my own?
On a shared BIN (Bank Identification Number), your cards are issued under a BIN range shared with other programs — the fastest and most cost-effective way to launch. A dedicated BIN gives you your own range, enabling deeper customization and program-level distinctiveness, but involves network setup lead time and higher cost. Most programs launch on a shared BIN and move to a dedicated one when scale or product requirements justify it.
Reference: Launching a card program
[F8] What is a BIN sponsor, and do I need one?
A BIN (Bank Identification Number) sponsor is a locally licensed bank or financial institution that sponsors the BIN and card network membership needed to issue open-loop cards in a given market. In markets where MatchMove holds the required license directly, no separate sponsor is involved; in others, MatchMove operates with a local sponsor institution. Either way, this is handled within your program setup rather than something you arrange yourself.
Reference: Launching a card program
[F9] Can cards be used internationally and for foreign-currency transactions?
International acceptance follows the card network, so cards can transact abroad and online with foreign merchants where the program configuration permits it. Foreign-currency transactions are converted at FX rates set by the card network, with any fees and markup defined at the program level. Cross-border usage can be enabled, restricted, or controlled per card depending on your use case and market rules.
Reference: Card transaction fees
[F10] What happens when a card is lost, stolen, or compromised?
The card can be blocked instantly via API — by the cardholder through your app or by your operations team through AdminNet — stopping further authorisations immediately. A new card with a fresh PAN (Primary Account Number) can then be issued to the same wallet, so the balance and history carry over. Suspected compromise events should also be reported through your support channel so network-level actions can be taken where needed.
Reference: Permanently block a card, Suspend an active card
G. Testing & Go-Live
(G) Questions and answers
(G) Questions and answers
[G1] What does UAT sign-off require before production access?
You demonstrate your critical flows end to end in UAT — onboarding, funding, spending or payout, and error and edge cases — against an agreed test plan. Compliance and operational readiness, including your support process and reconciliation approach, are reviewed alongside technical UAT. Production credentials are released after sign-off.
Reference: Demo and go-live checklist
[G2] Is there a recommended pilot approach at launch?
Yes — launch with a limited cohort, such as internal users or a friendly customer group, to validate live-rail behaviour before scaling volume. Monitor webhooks, reconciliation, and support tickets closely during the pilot window. Scale-up thresholds can be agreed with your MatchMove Customer Growth account manager.
Reference: Technical readiness
H. Operations & Support
(H) Questions and answers
(H) Questions and answers
[H1] What support is provided during integration and after go-live?
During integration you work with your MatchMove Implementation Manager alongside the developer portal documentation; after launch, support runs through MatchMove's support desk portal — your corporate email domain is registered during onboarding — with severity-based response. AdminNet, the operations portal, gives your operations team self-service visibility into customers, accounts, cards, and transactions. Escalation paths exist for production incidents.
Reference: Support & servicing readiness
[H2] How do I reconcile funds and transactions daily?
Transaction APIs and reports provide the data needed for daily reconciliation between your ledger, wallet balances, and settlement movements. Settlement reports in CSV (Comma-Separated Values) format can be downloaded from AdminNet at any time and are also delivered via settlement webhooks on a regular schedule after each settlement processing run. Automated reconciliation via API pull is the recommended pattern at scale.
Reference: AdminNet Reports dashboard
[H3] What monitoring and incident communication can I expect?
Platform incidents and maintenance windows are communicated through official partner channels, and release notes flag operationally relevant changes. You should implement your own health checks on API responsiveness and webhook delivery. Production-impacting issues follow a severity-based escalation and resolution process.
Reference: Subscribe to platform health alerts
[H4] Does MatchMove send notifications directly to end users?
Yes, for specific events: transaction OTPs (One-Time Passwords) for e-commerce authentication, mobile wallet tokenization lifecycle events, and card and account lifecycle actions taken via AdminNet. Delivery is via SMS and/or email depending on the event, with SMS coverage varying by country and messages sent under the MatchMove sender ID by default. All other end-user communications are yours to design and send from your own product.
Reference: Retrieve transaction history
[H5] How do my customers get payment status, proof of payment, or receipts?
Transaction status is available in real time via API and webhooks, so you can build self-serve status tracking into your own user experience rather than routing every query to support. Transaction records provide the detail needed to generate receipts or proof of payment for your product. For cases your own data can't resolve — for example, a beneficiary claiming non-receipt — raise the case through your support channel.
Reference: AdminNet overview
[H6] Can I provide account statements for end-user wallets?
Full transaction history per wallet is available via API, giving you the data to generate periodic statements within your own product. AdminNet's Transactions and Reports modules support operational exports for your back office. Statement formatting and delivery to end users is implemented on your side using this data.
[H7] What information should I include when raising a support ticket?
Include the environment (UAT or production), the affected API endpoints, the full request and response payloads with sensitive data redacted, relevant transaction or customer identifiers, timestamps, and the business impact. Never include full card numbers or CVV (Card Verification Value) data in tickets. Well-formed tickets are resolved significantly faster because they skip the information-gathering round trip.
Reference: Support and servicing readiness
I. Roadmap & Ecosystem
(I) Questions and answers
(I) Questions and answers
[I1] How do I stay informed about new platform capabilities?
Monthly release notes on the developer portal document new endpoints, behavior changes, and regional availability updates. After the implementation process, a dedicated MatchMove Customer Growth account manager will be assigned, responsible for growing your program.
Reference: Releases and updates
[I2] Can the platform grow with me into new markets or products?
Yes — the modular design means you can start with one capability in a single market, such as virtual cards, and add payouts, collections, or new markets using the same integration patterns. Each market addition involves its own regulatory and commercial scoping. Reusing the same API domains keeps incremental build cost low.
[I3] What differentiates MatchMove from other BaaS providers?
Deep local expertise in each operating market — local licences, local rails, and in-market compliance experience — combined with a full-stack offering spanning wallets, cards, collections, and payouts on one platform. Distinctive capabilities such as mJIT™ funding and flexible card distribution models suit embedded finance use cases. Market coverage is often the deciding factor, so evaluate against your target markets.
Regional availability varies by market. Commercial terms, including pricing and volume commitments, are agreed per program — contact your MatchMove Account Manager or the MatchMove Sales team for details.
Interested to learn more?
- Reach out to our MatchMove Sales team at [sales@matchmove.com].
On this page
- MatchMove FAQs