Managed vs Gateway JIT Funding

The following table compares Managed JIT Funding with Gateway JIT Funding:

Managed JIT Funding Gateway JIT Funding
Supports Spend Controls Yes Yes
Automated Authorization Logic Configured within the Marqeta Platform by means of Spend Controls. First layer configured within the Marqeta Platform by means of Spend Controls.

Second layer custom built within the customer's system and accessed through a customer-hosted endpoint (the gateway).
Metadata Injection No Yes, gateway response can add transaction metadata, facilitating reconciliation.
Stand-in Processing Not applicable Commando Mode (a form of Managed JIT Funding) can be invoked as a fallback in case the Marqeta Platform and gateway cannot communicate with each other.
Exemplifying Solutions VIRTUAL DELIVERY

Procedure Overview

This page provides an overview of the tasks involved in implementing Just-in-Time (JIT) Funding of transactions.

Note: In a sandbox environment, customers normally perform these tasks themselves. In production, Marqeta performs the first two tasks on behalf of the customer ("Set up a Funding Source" and "Configure Card Product for JIT Funding").

  1. Set up a Funding Source.

    The funding source defines the source of the funds used to JIT-fund user accounts. In the case of Gateway JIT Funding, it also defines the JIT Funding gateway (the customer-hosted endpoint to which Marqeta sends JIT Funding requests). In task 2, you associate this funding source with a card product by including its token in the card product definition.

  2. Configure Card Product for JIT Funding.

    The card product defines the common characteristics of a group of cards, including those related to JIT Funding. The card product contains the token of the funding source you set up in task 1.

    Note: Tasks 3–6 pertain only to Gateway JIT Funding. If you are setting up Managed JIT Funding, stop here.

  3. Set up a JIT Funding gateway in the customer environment (see PGFS Methods and JIT Funding Message Models).

    This customer-hosted endpoint receives and responds to JIT Funding requests from Marqeta.

  4. Develop funding-decision algorithms (see PGFS Methods and JIT Funding Message Models).
    These algorithms take input from JIT Funding requests; decide whether to approve full funding, partial funding, or decline funding; and generate the appropriate response.

  5. Leverage Marqeta webhooks both to correlate JIT Funding requests with associated event notifications and to identify and resolve time-out issues (see Managing Timeouts).

    Webhooks are push-style event notifications that Marqeta sends to a customer-hosted endpoint (different than the JIT Funding gateway). These notifications are sent within seconds of each card-network transaction message received and responded to by Marqeta and contain the information needed to detect and resolve time-out issues.

  6. Complete Marqeta's Gateway JIT Funding certification.

    When customers utilize Gateway JIT Funding, they directly participate in the card network's authorization process. For this reason, it is essential for the customer's gateway to respond both promptly and correctly in every supported transaction scenario. Before enabling Gateway JIT Funding in a customer's production environment, the Marqeta team works with the customer in a sandbox environment, testing to ensure that the customer's gateway responds appropriately in each scenario. The sandbox environment provides real-time simulations of the transaction scenarios that will be encountered in a production environment and provides the feedback necessary for resolving issues of accuracy and responsiveness. Certification helps to ensure customer success with this powerful feature.