Introducing Transaction Rules

Spade now offers the /transaction-rules endpoints for creating card-specific rules that get evaluated at enrichment time against enrichment outputs. For instance, you can set up rules to ensure a card is only used at a specific merchant, or to ensure a card is only used for certain spend categories, a combination of the two, and more. Transaction rules currently support counterparty_id, third_party_id, city, region, channel, amount, mcc, and category_code. Contact sales@spade.com for more information.