What if I want to allow a card to be used at multiple merchants?
To set up a transaction rule that allows a card to be used at multiple merchants, you can use the merchant search API multiple times to find the ID for each merchant. You can then provide each of these IDs when creating the relevant transaction rule.
What happens when merchant IDs change?
As is the case for any merchant database, a small percentage of Spade’s merchant IDs can change over time due to real-world changes (e.g. mergers and acquisitions) as well as general improvements. Spade’s transaction rules system handles migrations gracefully to ensure stability and robustness.
What entities can I apply transaction rules to?
Spade currently supports card-level transaction rules. Thus, when creating a transaction rule, you must specify the userId and cardId. Note that cards must be unique to users; two users are not allowed to share the same card.
What types of transaction rules can I create?
Spade currently supports two types of transaction rules:
allow- Allow transactions that meet the specified condition.block- Block transactions that meet the specified condition.
Do transaction rules impact enrichment latency?
Because low latency is core objective of our enrichment engine, we’ve built a custom parser and interpreter with the goal of minimizing latency. The result is that we are able to evaluate transaction rules during enrichment with effectively zero impact to latency (on the order of microseconds).