mJIT™ accounts

Understanding the mJIT™ Account Type

The mJIT™ (MatchMove Just-In-Time) Account is an advanced account type designed for partners who want to manage customer balances on their own systems. Instead of storing funds directly in the wallet, this model maintains the wallet balance at zero and employs a mechanism that pulls funds from the main prefund just-in-time to approve a transaction. This provides greater control and flexibility over fund management.

Wallet Limits

Even though an mJIT account maintains a zero balance, it is still governed by the overall wallet limits approved for the program. These restrictions, which may include daily transaction counts, spending caps, and other velocity checks, apply to the account to ensure all activity remains within the program's defined operational and compliance boundaries.

Wallet Balance

The defining feature of an mJIT account is that it does not hold a balance. The account is always "zeroized," meaning its balance on the platform is maintained at zero.

Since the balance is not kept in the MatchMove ledger, the partner is responsible for maintaining their own "partner ledger." This external ledger is where the partner records all customer debits and credits, effectively tracking transactions made against their “customer assigned balance“ on their own systems. This assigned balance is dependent on the partner's relationship with the customer. MatchMove will have no visibility on this ”assigned balance,” and the platform will refer to the prefund balance for card transactions.

Wallet Transactions

Since the mJIT account does not hold a balance on the platform, certain transactions are unavailable. Specifically, direct API-based transfers between wallets or from a program pre-fund account are not supported for this account type.

Card Transactions

Card transactions on an mJIT account require a Shared Authorization model. This is a mandatory process where both the partner and MatchMove participate in approving a transaction.

Here’s how it works:

1. A cardholder initiates a purchase.
2. The transaction request is sent to the MatchMove platform by the card network.
3. The platform will send a pre-authorization webhook (containing details of the payment request) to the partner.
4. The partner will receive the pre-authorization webhook and run their own business logic.
5. The partner checks their external ledger to confirm if the customer has sufficient funds and proceeds to debit their ledger.
6. The partner responds with an approval or denial to the platform.
7. If approved, funds are pulled "just-in-time" from the partner prefund to settle the transaction.

This collaborative process ensures that transactions are only approved when the partner confirms the availability of funds in their own system. This also assumes that the partner has subscribed to the pre-authorization webhook, which enables the Shared Authorization model.

Record Keeping

With the mJIT model, the official record of credits and debits is maintained exclusively on the partner's ledger. Since the platform wallet remains at zero, it will not provide a transactional history of balance changes. The partner assumes full responsibility for accurately tracking all customer funds and transaction histories on their end.

Related Links

• Account overview
• Account types
• Standard accounts
• Provision user accounts
• Access account information
• Understand account limits
• Virtual accounts overview
• Issue a virtual account