> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.thepennyinc.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.thepennyinc.com/_mcp/server.

# Processing Rules

Use `processing` to allow or block card PAN entry methods. Penny compares the authorization's `processing_details.pan_entry_mode` with your list when a mode is present.

**`Processing rule config`**

```json title="Processing rule config"
{
  "rule_type": "processing",
  "applicable_transaction_authorizations": ["debit"],
  "applicable_card_issuance_modes": ["managed"],
  "configuration": {
    "pan_entry_mode_rules": {
      "denylist": ["magstripe", "manual"]
    }
  }
}
```

Supported modes are `manual`, `chip`, `magstripe`, `contactless`, `card_on_file`, `e_commerce`, and `tokenised` (a wallet or network token). `pan_entry_mode_rules` accepts an `allowlist` or a `denylist`: an allowlist permits only its entries, and a denylist blocks its entries. A mode can't appear in both lists. If you set both, the denylist governs; see [Allowlists and denylists](/spend-controls#allowlists-and-denylists).

This rule checks PAN entry mode. Other processing details, including processing type and card product, are included in the live decisioning payload and can be evaluated by a [Live Decisioning rule](/spend-controls/live-decisioning-rules). If the authorization has no PAN entry mode, this check is skipped.