Transfer limits create conditional logic that automatically approves or declines a transfer based on its amount. You can configure transfer limits for your users, to regulate outgoing fund transfers from their balance accounts.<\/p>\n
When setting up a transfer limit, you configure the following settings:<\/p>\n
According to regulations in the EU, you must always provide your users with the option to configure transfer limits on their outgoing, instant transfers. Your users can choose whether to use this feature.<\/p>\n<\/div>\n
You can configure transfer limits on two levels:<\/p>\n
After a transfer limit is successfully created for your balance platform or your user's balance account, it works as follows:<\/p>\n
When you create a transfer limit, you can specify a start and end date. The transfer limit is only valid for the time period between its start and end date. Note that:<\/p>\n
Throughout its lifecycle, a transfer limit can have four statuses:<\/p>\n
Transfer limit conditions determine which transfers a transfer limit applies to. Conditions consist of:<\/p>\n
scope<\/code>: determines whether the transfer limit applies to each individual transfer, or to the total amount of all transfers made in a day.<\/li>\ntransferType<\/code>: determines whether the transfer limit only applies to transfers with an instant<\/strong><\/span> priority, or to all transfers.<\/li>\n<\/ul>\nYou can create multiple transfer limits with different combinations of scope<\/code> and transferType<\/code>.<\/p>\nAt any given moment, there can only be one scheduled<\/strong><\/span> or pendingSCA<\/strong><\/span> transfer limit with the same combination of scope<\/code> and transferType<\/code>. To create another scheduled<\/strong><\/span> or pending<\/strong><\/span> transfer limit with the same combination, you must first delete the existing one<\/a>.<\/p>\nAfter a transfer limit becomes active<\/strong><\/span>, you can create a new scheduled<\/strong><\/span> or pending<\/strong><\/span> transfer limit with the same combination of scope<\/code> and transferType<\/code>. The new transfer limit you create then overrides the previous one when it becomes active<\/strong><\/span>.<\/p>\nFor example:<\/h4>\n\n- \n
You create a transfer limit (TRLI_1) with the following details:<\/p>\n
\n- Amount: EUR 100.00<\/li>\n
- Scope: perDay<\/strong><\/span><\/li>\n
- Transfer type: instant<\/strong><\/span>
\nThe start date for the transfer limit is in the future, so it has a scheduled<\/strong><\/span> status.<\/li>\n<\/ul>\n<\/li>\n- \n
You want to schedule a new transfer limit (TRLI_2) with the following details<\/p>\n
\n- Amount: EUR 200.00<\/li>\n
- Scope: perDay<\/strong><\/span><\/li>\n
- Transfer type: instant<\/strong><\/span><\/li>\n<\/ul>\n<\/li>\n<\/ol>\n
Because TRLI_1 and TRLI_1 have the same scope and transfer type, you cannot schedule TRLI_2 while TRLI_1 has a scheduled<\/strong><\/span> status. To schedule TRLI_2, you must do either of the following:<\/p>\n\n- Delete TRLI_1<\/li>\n
- Wait until TRLI_1 becomes active<\/strong><\/span>. In this case, when TRLI_2 eventually becomes active, it will override TRLI_1.<\/li>\n<\/ul>\n
Get updates when a limit is triggered<\/h2>\n
To get updated about transfers that are declined because they triggered a transfer limit, you can use either webhook notifications or the Customer Area:<\/p>\n
\n- \n
Subscribe to the Transfer webhooks<\/a>. The webhook returns the following fields:<\/p>\n\n- transactionRulesResult<\/a>: Contains the details of the transfer limit that was triggered:<\/li>\n
- reason<\/a>: Returns declinedByTransactionRule<\/strong><\/span>.<\/li>\n
- reference<\/a>: Returns your reference for the transfer limit.<\/li>\n
- description<\/a>: Returns the description for the transfer limit in the format Enforce transfer limit with code: {transferLimitId}<\/strong><\/span><\/li>\n<\/ul>\n<\/li>\n
- \n