Transaction Policy FAQs
How do I create Transaction categories?
Use \transactionCategory endpoint to create a transaction category and provide values for the following parameters:
-
code
-
attrKey
-
attrVal
-
txnCategoryComparator
You can view the sample request payload for reference.
At what level are the transaction categories created?
How do I create transaction policies?
Use \transactionPolicies endpoint to create a transaction policy and provide values for following below parameters:
-
policyViolationAction
-
Action
-
allowedTransactionCategoryCodes
-
disallowedTransactionCategoryCodes
-
allowedTimeSlices
-
disallowedTimeSlices
-
errorCode
You can view the sample request payload for reference.
At what level are the transaction policies created?
What are the possible values for txnCategoryComparator in Transaction Category payload?
What is the maximum limit allowed per transaction?
Maximum transaction limit for,
-
Min KYC User: Rs. 10000 per transaction(debit/credit)
-
Aadhaar OTP KYC User: Rs. 1 lakh per transaction(debit/credit).
Can a disabled transaction be enabled in 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 2 categories of error codes to indicate when transaction limits are violated:
-
User defined error codes defined 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 codes