Connector Architecture

The Mambu-Marqeta integration is built around the Marqeta Just-in-Time (JIT) Funding concept, which can be described as a method of automatically funding an account in real time during the transaction process.

Through the gateway JIT Funding approach, the Marqeta platform applies spend controls to make authorization decisions and forwards funding requests to the bank’s core system through the gateway so that funding decisions can be made. The connector receives these funding requests and approves or denies them using the core system’s backend business rules.

The Marqeta platform exchanges the following types of messages with the connector:

• JIT Funding requests: Actionable messages for authorization requests sent by Marqeta to create a hold for the requested amount, check payment card account, or get the account balance.
• JIT Funding responses: Sent by the gateway to the Marqeta platform in response to an actionable message to approve or deny an authorization request.
• JIT Funding notifications: Transaction event messages sent by the Marqeta platform to the connector’s JIT Informative Notifications endpoint. These asynchronous messages contain the entire transaction and information about its final outcome.
• JIT Funding notification responses: Sent by the JIT Informative Notifications endpoint after a batch of transactions has been validated for the presence of all required parameters by the Mambu Process Orchestrator (MPO) process.

Communication is made using two endpoints.

Gateway endpoint

This endpoint is designed to receive and respond to actionable requests.

• To approve a request, a 200 OK HTTP status code is sent and the jit_funding object is included as the response body.
• To deny a request, a 402 Payment Required HTTP status code is sent and the jit_funding object as is included as the response body.

The gateway endpoint is the MPO JIT Actionable Receiver process, found in the root of the Marqeta connector folder.

Informative notifications endpoint

To handle Informative JIT Funding messages, the connector includes an endpoint for receiving event notifications. Within seconds of each transaction, the Marqeta platform sends webhook notifications to this endpoint to enable tracking of requests, maintain account balances, and resolve timeout issues.

The Marqeta connector validates for the presence of mandatory parameters for clearing messages and responds to each JIT Informative request through a dedicated API gateway with a 200 OK HTTP status code if the validation of the batch of transactions has passed. Otherwise, it sends back a 402 Payment Required HTTP status code, at which point Marqeta will resend the events.

The webhook endpoint is the MPO JIT Informative Notifications Receiver process, found in the root of the Marqeta connector folder.

Additional processes

The connector also features a series of supporting processes including business sub-processes, a notifications module, configuration settings, and API gateways for external applications.

The current version of the connector also provides an additional layer between Marqeta and MPO - two API Gateways, one for Actionable and one for Informative receivers, that handle HTTP status codes on behalf of the MPO system.