---
title: "Create Rules Advanced"
method: POST
path: "/pws/v2/pws_other_rules/"
tags: ["Rules V2"]
---

# Create Rules Advanced

`POST /pws/v2/pws_other_rules/`

## Request

- Base URL: `https://api.uat.paymentology.com/ppws/api`
- URL: `https://api.uat.paymentology.com/ppws/api/pws/v2/pws_other_rules/`
- Auth: none declared

This web service allows to create different types of advanced rules.<p>Version 2 Advanced Rules api support idempotency</p>

## Request body

- CreateRulesModel: This web service allows to create different types of rules
  - `api_call_unique_identifier` string, required: Unique number that must be passed at each API request. Identifier to make each API request unique
  - `client_id` integer, required: Unique identifier for the client which Paymentology will provide at outset
  - `parameters` string, required: Parameters for rules.<ul><li class="docBullet">format of parameter is TAG:VALUE </li><li class="docBullet">parameter can be combination of multiple TAG:VALUE separated by semicolon(;) </li><li class="docBullet">VALUE can contain comma(,) separated multiple values </li><li class="docBullet">Accepted TAGS are MCC,TXN_CCY,CTRY</li><li class="docBullet">TXN_CCY=> transaction Currency DE49. (Three digit Numeric ISO-4217 standard currency code . i.e. : 048 → BHD, 060 → BMD, 036 → AUD)</li> <li class="docBullet">MCC=> Merchant category code DE18.</li><li class="docBullet">CTRY=> Country (DE43_5). <ul><li>For Master card (Alpha Three country ISO codes. i.e. : Afghanistan → AFG, Australia → AUS) </li><li>For VISA (Alpha Two country ISO codes . i.e. : Afghanistan → AF, Australia → AU) </li><li>For Both (MC & VISA) :(Comma separated Alpha Three country ISO codes & Alpha Two country ISO codes i.e Afghanistan-> AFG,AF , Australia → AUS,AU )</li> </ul> </li></ul>
  - `rule_desc` string, required: Rule description. Description should specific and should describe rule in a concise manner.
  - `rule_name` string, required: Rule name
  - `rule_type` string, required: Rule Type : <ul><li class="docBullet">Au = Authorisation</li><li class="docBullet">Se = Settlement</li><li class="docBullet">Sc = Scheduled</li><li class="docBullet">Lo = Load</li><li class="docBullet">Un = Unload</li><li class="docBullet">Ot = Others</li><li class="docBullet">Da = Deactivated</li></ul>
  - `scope` string, required: Rule applicable scope. Values of scope can be : <ul><li class="docBullet">C=Direct card rules (These rules are held at individual card level and therefore can be personalized per card holder.)</li><li class="docBullet">G=Group rules (These rules are more generic to card program and typically used to set upper limit controls.)</li><li class="docBullet">T=Token Group rules (These rules are more generic to card program which is set at token level and typically used to set upper limit controls.)</li><li class="docBullet">A=Parent Account rules (These rules cascade down to the cards linked to all children accounts of this parent.)</li><li class="docBullet">P=Product rules (These rules are set to the product.)</li></ul>
  - `severity` integer, required: Severity evel. It can be 0(lowest)-10(highest)
  - `user_id` string: User Id of the Customer who triggered the API request.
  - `remarks` string: Remarks for API request
  - `token` integer: Public token for card. Required in case of scope 'C'
  - `group_id` integer: Group Id. Required in case of scope 'G' or 'T'
  - `suitable_for_estimate` boolean: <ul><li class="docBullet">True = Rule is for limit check like (amount limit or transaction count limit)</li><li class="docBullet">False =Rule is not for limit check like (amount limit or transaction count limit)</li></ul>
  - `action_decline` string: Decline action,de39 response code <ul> <li class="docBullet">57 = Txn not permitted</li> <li class="docBullet">03 = Invalid merchant</li> <li class="docBullet">04 = Capture card</li> <li class="docBullet">05 = Do not honour</li> <li class="docBullet">12 = Invalid txn</li> <li class="docBullet">13 = Invalid amt</li> <li class="docBullet">14 = Invalid card no</li> <li class="docBullet">30 = Format Error</li> <li class="docBullet">41 = Lost card</li> <li class="docBullet">43 = Stolen card</li> <li class="docBullet">51 = Insufficient Funds</li> <li class="docBullet">54 = Expired card</li> <li class="docBullet">55 = Invalid pin</li> <li class="docBullet">57 = Txn not allowed</li> <li class="docBullet">58 = Invalid txn/terminal</li> <li class="docBullet">61 = Exceed Cash Limit</li> <li class="docBullet">62 = Restricted card</li> <li class="docBullet">63 = Security violation</li> <li class="docBullet">71 = pin not changed</li> <li class="docBullet">75 = Pin tries exceeded</li> <li class="docBullet">88 = crypto Fail</li> <li class="docBullet">96 = System error</li> <li class="docBullet">70 = Contact card issuer</li> </ul>
  - `account_id` integer: Account Id. Required in case of scope 'A'
  - `product_id` integer: Product Id. Required in case of scope 'P'

## Response `200`

Successful Response

- CreateRuleResponseModel
  - `header` ResponseHeader
    - `error_id` integer: Error Id
    - `error_desc` string: Error Message
  - `body` CreateRuleResponseModelBody
    - `rule_id` integer: Rule Id

## Other responses

- `404`: Webservices does not exist
- `500`: Internal Server error

## Changes

- **2026-11-03** `73c2771493b1`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/paymentology/apis/payapi-docs/changes/pws/v2/pws_other_rules/post.md)

---

[API](https://skmtc.dev/paymentology/apis/payapi-docs.md) - [All operations](https://skmtc.dev/paymentology/apis/payapi-docs/llms.txt) - [OpenAPI document](https://skmtc.dev/paymentology/apis/payapi-docs/revisions/73c2771493b1?raw)