subnetwork field of the transaction record.
- A
subnetworkvalue ofGATEWAY_JITindicates that the transaction was funded through normal Gateway JIT Funding and that Commando Mode was not in effect at the time. - A value of
MANAGED_JITindicates that the transaction was funded while Commando Mode was in effect. In addition, thestandin_approved_byfield has a value ofCOMMANDO_AUTOorCOMMANDO_MANUALwhen Commando Mode is enabled for a transaction.
COMMANDO_MANUAL is configured, all transactions are processed via Commando Mode. When COMMANDO_AUTO is configured, Commando Mode is enabled only when a transaction times out or encounters an error.
While Commando Mode is a form of Stand-in Processing (STIP), it is different than network STIP. Network STIP occurs when the card network cannot communicate with the Marqeta platform. Transactions handled by network STIP include the standin_approved_by field with a value of NETWORK.
Commando Mode and Managed JIT Funding are functionally equivalent. See About Just-in-Time Funding for more information.
Note
Commando Mode requires additional configuration. To configure Commando Mode control sets, contact your Marqeta representative.
Commando Mode requires additional configuration. To configure Commando Mode control sets, contact your Marqeta representative.
Transaction payload for Commando Mode transactions
The transaction payload differs depending on which type of Commando Mode handled the transaction:- Auto Commando Mode (a JIT Funding request was attempted and then timed out or errored): the transaction payload includes
gpa_order.funding.gateway_logwith the details of the failed gateway call. Thegpa_order.jit_fundingobject is also present. - Manual Commando Mode (no JIT Funding request is made): the transaction payload doesn’t include
gpa_order.funding.gateway_log, since no gateway call was made. Thegpa_order.jit_fundingobject is still present, with the same required and optional fields as any other JIT Funding transaction.
gateway_log and jit_funding fields, see Transactions.