Transaction Policy FAQs
How do I create transaction categories?
Use the \transactionCategory endpoint to create a transaction category and provide values for the following parameters:
-
code
-
attrKey
-
attrVal
-
txnCategoryComparator
See the sample request payload for reference.
At what level are the transaction categories created?
How do I create transaction policies?
Use the \transactionPolicies endpoint to create a transaction policy and provide values for following parameters:
-
policyViolationAction
-
Action
-
allowedTransactionCategoryCodes
-
disallowedTransactionCategoryCodes
-
allowedTimeSlices
-
disallowedTimeSlices
-
errorCode
See the sample request payload for reference.
At what level are the transaction policies created?
If the transaction policy is disabled for an account holder, are credit/debit transactions permitted on their account?
What are the possible values for txnCategoryComparator in the Transaction Category payload?
Can a disabled transaction be enabled in transaction policy?
Are transaction limits enforced within the scope of form factors?
Can transactions to particular merchants/aggregators be blocked?
To what extent are aggregate limits applied?
Are there any error codes defined for violation of transaction limits?
Fusion provides the following categories of error codes to indicate transaction limit violations:
-
User-defined error codes during policy creation
-
System-defined legacy error codes
In the absence of any user-defined error codes, the system throws one of the relevant system-defined error code. See the System defined error codes documentation for more information.