\nSCA on initiation, for each transfer limit your user creates<\/strong>
\nWhen you send a request to create a transfer limit, you must include SCA details in the request header. Your user is immediately prompted to authenticate their identity using their registered SCA device.<\/p>\n<\/li>\n\nSCA on approval, for one or more pending transfer limits<\/strong>
\nYou send one or more requests to create transfer limits for your user without including SCA details in the request headers. These transfer limits end up in a pending state, because your user has not yet authenticated their identity. Then, you make a new request to approve all pending transfer limits, with SCA details in the request header. Your user is then prompted to authenticate their identity for all the pending transfer limit requests using their registered SCA device.<\/p>\n<\/li>\n<\/ol>\nExemptions to SCA<\/h3>\n
In some cases, your user's identity does not need to be authenticated when creating a transfer limit because of an SCA exemption. When you or your user has an SCA exemption, you must specify this in your request, along with the type of exemption that applies for that transfer limit.<\/p>\n
There are five types of SCA exemptions:<\/p>\n
\n- \n
lowerLimit<\/strong><\/span>: this exemption applies when the transfer limit created by your user is lower than the transfer limit that already exists for that balance account. Because the new transfer limit has a lower risk than the previous transfer limit, there is no need for SCA.<\/p>\n<\/li>\n- \n
notRegulated<\/strong><\/span>: this exemption applies when you want to use transfer limits in countries, regions, or industries where it is not mandated by law to use SCA.<\/p>\n<\/li>\n- \n
setByPlatform<\/strong><\/span>: this exemption applies when you<\/em> set a transfer limit for one of your user's balance accounts or for your entire balance platform. Because you<\/em> are configuring the transfer limit for your users, there is no need to verify their identity using SCA.<\/p>\n<\/li>\n- \n
initialLimit<\/strong><\/span>: this exemption applies when there is no transfer limit configured on the balance account, and no default transfer limit configured on the balance platform. Because having a transfer limit has a lower risk than having no transfer limit, there is no need for SCA.<\/p>\n<\/li>\n- \n
alreadyPerformed<\/strong><\/span>: this exemption applies when you are already confident about your user's identity and do not need to verify this using SCA. For example, if your user already performed SCA when logging into your app, they do not need to verify their identity again when setting a transfer limit.<\/p>\n<\/li>\n<\/ul>\nHow it works<\/h2>\n
The flow to create a transfer limit depends on whether you trigger SCA on initiation for each request, on approval for one or more requests, or if you are exempt from SCA.<\/p>\n\n
\n
\n
\n <\/tabs>\n <\/div>\n<\/div>\n\nCreate transfer limits<\/h2>\n
Before you create a transfer limit, you must determine:<\/p>\n
![\"-white_check_mark-\"](\"\/user\/data\/smileys\/emoji\/white_check_mark.png\" "\\"-white_check_mark-\\"")
<\/td>\n