Skip to main content
This page visualizes the end-to-end card-issuing ecosystem so that you can better understand the role of your business within the wider payments landscape. It also describes the connections between key parties and their respective roles. Additionally, this page provides information that you should consider when onboarding third parties.
Note
In the following diagram, each entity can perform one or more of the featured functions. For example, your business might decide to be self-issuing and therefore will act as the issuer and the JIT (Just-in-Time) gateway client.
Marqeta card-issuing ecosystem

Roles and responsibilities

This section details the roles and responsibilities of all parties in the card-issuing ecosystem.

Issuer or BIN sponsor

The issuer or bank identification number (BIN) sponsor is a legal entity that holds the issuing license with the scheme, and is therefore ultimately liable. Normally, the issuer owns the bank accounts that debit settlement funds and charge fees. The issuer typically has specific reconciliation requirements.

Card network

The card network sets the rules and technical standards for processing transactions and connects all underlying payment agents. Visa and Mastercard are examples of card networks.

Marqeta

Marqeta is a certified issuer processor that allows you to create physical cards and authenticate card transactions by requiring a PIN or signature verification when the card is present. If the card is not present (CNP), Marqeta provides services such as address verification, card verification value (CVV2), and 3D Secure (3DS) to authenticate cardholder identity. Marqeta offers JIT Funding so that you can take control of the funds approval process. As your issuer processor, Marqeta performs the following actions on your behalf:
  • Assists with issuing physical cards, using integrated providers, and establishing card activation procedures.
  • Converts the ISO message received from the card network into a JSON object that has a user-friendly naming convention to simplify the content of the ISO message.
  • Validates authorization requests for card status, CVV2, country restrictions, and spend controls.
  • Ensures the correctness and validity of the authorization request and response before requesting approval from the JIT gateway.
  • Sends notifications to your webhook endpoint for any subscribed events or changes on the Marqeta platform, including financial transactions, card status changes, and PIN set or view operations.
  • Provides an additional verification step via 3DS, Marqeta’s hosted Access Control System (ACS).
  • Sets PINs and handles any updates to the PIN by using the set PIN widget or by calling the relevant endpoint on the Marqeta platform.

Your organization or a third-party JIT gateway

Either your organization or a third party that you have selected can build your JIT gateway. The JIT gateway allows you to participate in authorization decisioning, meaning that you can approve or decline authorizations based on your own criteria. The majority of Marqeta’s customers have criteria for approvals based on their ledger and internal risk policies. The ledger is held by you, not Marqeta.
Warning
Marqeta allows three seconds for you to approve or decline an authorization at your JIT gateway. Keeping your ledger separate from the JIT gateway can cause latency in the authorization flow.

Core banking platform

Your organization will develop or contract with a third-party core banking platform. This platform—known as the ledger—acts as your main system of record and carries all cardholder balances. You can also choose to have your core banking platform calculate interest and add relevant cardholder fees. Your core banking platform should mirror the cardholder accounts created using the Marqeta platform. You can opt to use Marqeta’s services with your platform to create cardholder accounts and their associated cards, and then mirror these assets in the banking platform. Users and cards that exist in your banking platform are also mirrored in the Marqeta platform. You can create this mirroring using either your banking platform or the Marqeta platform. If your JIT gateway and banking platform are separate, it may add latency to the flow. Integration with Marqeta is not required from the banking platform provider. However, due to potential latency, you might want your core banking provider to host the JIT gateway.

Card manufacturer

The card manufacturer must be integrated with Marqeta.
Important
The project timeline will be longer for new integrations.
To set up a new card, use the following process:
1
Set up the chip profile with the card manufacturer.
2
Design your card art and obtain card network approval for it.
3
Marqeta creates white plastic for validation testing with the card network.
4
Marqeta queues any cards that have been created, and then sends one batch order to the card manufacturer per day.
5
With Marqeta support, perform initial authorization tests using the first printed cards.
6
Perform end-to-end testing with the physical cards.

Standard authorization and funding flows

Standard authorization flow

The standard authorization flow confirms the cardholder identity and performs a typical transaction according to the following process:
1
The merchant processes cardholder transactions with the card network via the acquirer.
2
The card network passes the ISO authorization to Marqeta.
3
Marqeta determines the transaction’s correctness and validity, as provided by the merchant. All transactions require a valid personal account number (PAN), CVV, and expiration date.
4
Marqeta checks the transaction against the spend controls that you have configured on the Marqeta platform.
5
Marqeta determines transaction funding and reaches out to your JIT gateway for authorization approval.
6
Marqeta returns an approval, decline, or error response back to the card network.
7
The card network sends the information from Marqeta to the merchant regarding the transaction status (approved, declined, or error response).
8
Merchants gather approved authorizations, and then submit them to the acquirer.
9
The card network generates clearing messages in batches, and then sends them to your processor.
10
Marqeta processes the card network files and sends you the settlement files via Secure File Transfer Protocol (SFTP) or Simple Storage Service (S3).
11
Marqeta parses the data and sends clearing webhooks to your specified webhook endpoints.
12
You perform daily reconciliation of network data with the sum and count of Marqeta webhooks. For more information, see About webhooks.
13
The card network collects funds from issuers and transfers funds to the acquirers.

Standard funding flow

1
As required by your issuer, you must first deposit funds into a reserve account to cover the daily card network settlement position. This amount is driven by your projected volumes and any agreements that you have established with your issuer.
2
You will be advised of the amount you owe the card network to cover the merchant position. The card network typically delivers these notifications on a daily basis.
3
The issuer moves the funds from your reserve account to their nominated settlement account to pay the card network.
4
Subsequently, the issuer will inform you if your reserve account needs to be replenished. The frequency of the replenishment is also an agreement between you and your issuer.