Create a card product with the appropriate funding model set to Gateway JIT Funding by referencing the Card Products endpoint in the Marqeta Core API; this links authorizations to your funding gateway.
Create a user account holder (individual cardholder) and associate it with an account holder group that has the desired authorization controls and velocity controls pre-configured.
Issue a virtual card by POSTing to the cards endpoint with the card_product_token and user_token; virtual cards are immediately available for card-not-present transactions.
Configure authorization controls to restrict permitted merchant categories and velocity controls to cap spending frequency or amounts via the Authorization Controls and Velocity Controls endpoints.
When a cardholder transacts, Marqeta sends a Gateway JIT Funding request to your registered funding gateway URL; respond with a funding decision (approve with amount or decline) within the required response window.
Subscribe to webhook events for transaction authorizations and clearings at your webhook endpoint to maintain a real-time ledger of card activity.
Known gotchas
Gateway JIT Funding requires your funding gateway to respond synchronously within the authorization window — if your gateway is unreachable, configure Commando Mode fallback rules in the Marqeta Dashboard to prevent blanket declines.
Virtual cards created via the Core API require a card product configured with virtual card support; physical card issuance requires additional onboarding steps including BIN validation and card art setup.
Authorization controls and velocity controls are applied per user or per account holder group; controls set on an account holder group affect all members — scope controls carefully to avoid unintended restrictions.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp