---
title: "Replace rule model"
method: PUT
path: "/v1/models/{modelId}"
tags: ["Model"]
---

# Replace rule model

`PUT /v1/models/{modelId}`

Replace the rule model identified in the path.

## Path parameters

- `modelId` string, required

## Request body

- ModelPayload
  - `rules` Rule[], required — Processing code rules configuration array.
    - `cardId` integer, required — ID of card the rule applies to
    - `rulePriority` integer, required — Rule priority, `1` being the highest.
    - `scope` RuleScope2, required
      - `controlType` 'TCT_GLOBAL' | 'TCT_ATM_WITHDRAW' | 'TCT_AUTO_PAY' | 'TCT_BRICK_AND_MORTAR' | 'TCT_CROSS_BORDER' | 'TCT_E_COMMERCE' | 'TCT_CONTACTLESS' | 'MCT_ADULT_ENTERTAINMENT' | 'MCT_AIRFARE' | 'MCT_ALCOHOL' | 'MCT_APPAREL_AND_ACCESSORIES' | 'MCT_AUTOMOTIVE' | 'MCT_CAR_RENTAL' | 'MCT_ELECTRONICS' | 'MCT_SPORT_AND_RECREATION' | 'MCT_GAMBLING' | 'MCT_GAS_AND_PETROLEUM' | 'MCT_GROCERY' | 'MCT_HOTEL_AND_LODGING' | 'MCT_HOUSEHOLD' | 'MCT_PERSONAL_CARE' | 'MCT_SMOKE_AND_TOBACCO' | 'MCT_DINING', required — Transaction control type: * `TCT_GLOBAL`— Transaction control type (TCT) global * `TCT_ATM_WITHDRAW`— TCT ATM withdrawal * `TCT_AUTO_PAY`— TCT autopay * `TCT_BRICK_AND_MORTAR`— TCT brick and mortar * `TCT_CROSS_BORDER`— TCT cross border * `TCT_E_COMMERCE`— TCT e-commerce * `TCT_CONTACTLESS`— TCT contactless card * `MCT_ADULT_ENTERTAINMENT`— Merchant category type (MCT) adult entertainment * `MCT_AIRFARE`— MCT airfare * `MCT_ALCOHOL`— MCT alcohol * `MCT_APPAREL_AND_ACCESSORIES`— MCT apparel and accessories * `MCT_AUTOMOTIVE`— MCT automotive * `MCT_CAR_RENTAL`— MCT car rental * `MCT_ELECTRONICS`— MCT electronics * `MCT_SPORT_AND_RECREATION`— MCT sport and recreation * `MCT_GAMBLING`— MCT gambling * `MCT_GAS_AND_PETROLEUM`— MCT gas and petroleum * `MCT_GROCERY`— MCT grocery * `MCT_HOTEL_AND_LODGING`— MCT hotel and lodging * `MCT_HOUSEHOLD`— MCT household * `MCT_PERSONAL_CARE`— MCT personal car * `MCT_SMOKE_AND_TOBACCO`— MCT smoke and tobacco * `MCT_DINING`— MCT dining **Note:** Visa provides and validates these values. Consult your Visa representative to know which control types are available in your region. The values listed here are examples — if Visa provides a new `controlType` option not listed here, you can send it and Pismo will be accept it.
      - `cardHolderBillAmount` CardholderBillAmount, required
        - `maxAmount` number, float, required — Maximum transaction amount allowed
        - `minAmount` number, float — Minimum transaction amount allowed
      - `timeRange` RuleValidityTimeRange, required
        - `startTime` string, date-time, required — Start time for rule validity. RFC 3339 format.
        - `endTime` string, date-time, required — End time for rule validity. RFC 3339 format.
    - `definedBy` 'CARDHOLDER' | 'ISSUER', required — Entity that defined the rule
    - `ruleId` string, required — Rule ID
  - `name` string — Model name

## Response `200`

No content

## Other responses

- `400` — Bad request
- `404` — Not Found
- `500` — Internal server error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)