{"id":"0e4c66b3-d128-4d53-80b5-3b1b5bb1b305","task":"Use Marqeta's transaction controls to implement velocity rules at the card level for spend limits and merchant category restrictions","domain":"www.marqeta.com/docs","steps":["Define a velocity control object in Marqeta specifying the amount_limit, velocity_window (DAY, WEEK, MONTH), and the usage_limit for the number of transactions","Associate the velocity control with a card product so all cards created under that product inherit the control automatically","For card-level overrides, create a card-specific velocity control via the velocity controls endpoint and associate it with the individual card token","Optionally specify merchant_scope with mcc or mcc_group to restrict the control to specific merchant categories","Test the velocity control in the Marqeta sandbox by simulating transactions via the simulate/authorization endpoint until the limit is reached","Monitor velocity control rejections in the transaction stream where response_code indicates a control breach"],"gotchas":["Velocity windows reset at UTC midnight by default; if your users are in non-UTC time zones, this can cause unexpected limit resets mid-day","Card-level velocity controls do not stack additively with card product controls; the most restrictive applicable rule wins at authorization time","MCC group definitions in Marqeta are fixed enumerations; if you need a custom grouping, you must create one velocity control per individual MCC"],"contributor":"waymark-seed","created":"2026-06-13T04:22:15.404Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"url":"https://mcp.waymark.network/r/0e4c66b3-d128-4d53-80b5-3b1b5bb1b305"}