SCA Optimization
2 min
\<font color="#78b5c7">\</font> topic type constraint purpose explain how sca optimization is supported through api risk signals audience api integrators and client developers applies to apis that support fraud risk evaluation for sca‑regulated transactions does not apply to data privacy apis, internal batch processing, or non‑request‑based integrations strong customer authentication (sca) optimization rules allow the apis to support regulatory compliance requirements while minimizing unnecessary customer friction these rules apply when transactions are subject to sca regulations and the client is enrolled in ’s sca optimization capabilities evaluation is performed using a combination of event data, historical intelligence, and real‑time risk signals purpose of sca optimization sca optimization does not determine regulatory compliance on its own and does not guarantee exemption eligibility sca optimization is designed to identify transactions that may qualify for sca exemptions support risk‑based authentication decisions reduce unnecessary authentication challenges where permitted the apis do not perform authentication or enforcement instead, they provide risk signals that can be used by downstream systems to determine appropriate handling data dependency sca optimization relies on accurate and complete context if you have signed up for our sca solution, you must send the following fields eventsource paymentamount currencycode cardnumber purchasetype paymenttype emailaddress phone ipaddress address1 city region postcode country nameoncreditcard transactionid missing or inconsistent data may limit the ability to assess exemption eligibility client responsibilities clients remain responsible for understanding applicable regulatory requirements applying authentication or exemption logic in their own systems interpreting api responses appropriately api responses should be treated as decision support , not regulatory determinations