Marqeta Integration
  • 23 Feb 2023
  • 5 Minutes To Read
  • Dark
  • PDF

Marqeta Integration

  • Dark
  • PDF

Article Summary

Early Access Feature
If you would like to request early access to this feature, please get in touch with your Mambu Customer Success Manager to discuss your requirements. For more information, see Mambu Release Cycle - Feature Release Status.

We partner with Marqeta to provide card issuing and processing services. Marqeta is a card issuing platform providing an Open API.

The Marqueta connector is for Mambu customers who want to offer debit cards to their clients. Using the Marqeta connector means you don't need to build out your own gateways or deal with messaging standards such as ISO 8583.

Marqeta is live across North America, Australia, and Europe and integrated with the Visa, Mastercard, and Discover networks allowing you or your clients to make the best choice of a card product.

For more information about Marqeta see Mambu Marketplace or the Marqeta website.

The Mambu-Marqeta microservice is used to process payment card authorization requests and accept payment card clearing transactions and reversal instructions sent by Marqeta. The integration supports funding card transactions via Marqeta’s Just-in-Time (JIT) Funding™ solution. You manage card authorization via the Marqeta JIT Funding gateway. When a transaction is initiated, funds are moved from a funding account to the card account and the transaction is then settled, following a successful authorization via the JIT gateway. This setup supports use cases with multiple combinations of authorization and settlement business flows.


Before working with cards, make sure you have your Mambu environment set up. There may be additional setup to be done in Marqeta if you intend to use their simulation APIs for testing purposes.


The Mambu-Marqeta integration is built around the Marqeta 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. Mambu 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 Mambu:

  • 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. Mambu should respond in three seconds.
  • JIT Funding responses: Sent by Mambu 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 Mambu's JIT Informative Notifications endpoint. These asynchronous messages contain the entire transaction and information about its final outcome. Such batches are to be stored in five seconds and processed in an asynchronous way.
  • 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.

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 status code is sent and the jit_funding object is included as the response body.
To deny a request, a 402 Payment Required status code is sent and the jit_funding object is included as the response body with a decline reason.

Informative notifications endpoint

To handle Informative JIT Funding messages, Mambu uses 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, maintaining account balances and resolving timeout issues.

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

JIT actionable requests

The following JIT actionable requests are supported:

Transaction typeMethodPurpose
authorizationpgfs.authorizationTo create a new reservation for the requested amount, if it is available on the card account.
authorization.incrementalpgfs.authorization.incrementalTo increase a reservation with the requested amount, if it is available on the card account. Conventional FundsTo check a payment card and approve the credit authorization.
balanceinquirypgfs.balanceinquiryTo return account balances.
pindebitpgfs.auth_plus_captureTo debit card account with the requested amount, if it is available on the card account.
pindebit.cashback credit card account with the requested amount. Fast Funds

JIT informative notifications

The following JIT informative notifications are supported:

Transaction typeMethodStatePurpose
authorization.clearingpgfs.authorization.capture / pgfs.force_captureCOMPLETIONTo debit a card account and remove or reduce the debit hold if it is present.
account.funding.authorization.clearing Conventional FundsCOMPLETIONTo credit a card account and remove the credit hold if it is present.
pindebit.refundPENDING Fast FundsCOMPLETIONTo credit a card account.
authorization.advicepgfs.reversalPENDINGTo reduce or remove the debit hold.
authorization.standinpgfs.authorization.standinPENDINGTo create a hold without checking the available balance. Conventional FundsCLEAREDTo remove the credit hold.
refund.authorization.reversalpgfs.refund.authorization.reversal Fast FundsCLEAREDTo debit a payment card account, if a credit transaction has been executed.
authorizationpgfs.authorizationDECLINED / CLEAREDTo remove the debit hold.
authorization.incrementalpgfs.authorization.incrementalDECLINEDTo reduce the debit reservation. Conventional FundsDECLINED / CLEAREDTo remove the credit hold.
refund.authorizationpgfs.refund.authorization Fast FundsDECLINED/CLEAREDTo debit a payment card account, if a credit transaction has been executed.
pindebit.reversalpgfs.auth_plus_capture.reversalCOMPLETIONTo credit a payment card account, if a debit transaction has been executed. debit a payment card account, if a credit transaction has been executed.
authorization.clearing.chargebackpgfs.authorization.capture.chargebackCOMPLETIONTo credit a card account.
authorization.clearing.chargeback.reversalpgfs.authorization.capture.chargeback.reversalCLEAREDTo debit a payment card account, if a credit transaction has been executed.
authorization.clearing.representmentpgfs.authorization.capture.chargeback.reversal / pgfs.force_captureCOMPLETIONTo debit a payment card account.
authorizationpgfs.authorizationPENDING + COMMANDOTo create a new debit hold for the requested amount without checking the available balance.
authorization.incrementalpgfs.authorization.incrementalPENDING + COMMANDOTo increase a hold with the requested amount without checking the available balance. Conventional FundsPENDING + COMMANDOTo create a new credit hold.
pindebitpgfs.auth_plus_capturePENDING + COMMANDOTo debit card account with the requested amount without checking the available balance.
pindebit.cashback + COMMANDOTo credit card account with the requested amount. Fast Funds

Additional processes

Mambu also features a series of supporting processes including business subprocesses, a Notifications module, configuration settings and API gateways for external applications.

The current version also provides an additional layer between Marqeta and Mambu - two API Gateways, one for actionable and one for informative receivers - that handle HTTP response codes on behalf of Mambu.

Was this article helpful?