This article marks the final instalment of our Strong Customer Authentication overview series. Today, we’ll go over details related to APIs for payment service providers looking to meet SCA requirements.

Looking to swiftly move your bank towards European banking standards? Wultra is here to help.

To genuinely become mobile-first, it’s time for banks to rethink their mobile onboarding process. Here’s how Wultra can help.

Learn more about our new partner as well as the goals we’ve set for our future work together.

Authentication via SMS-OTP is considered outdated because of higher overall costs, low user convenience, and insufficient regulatory compliance in specific geographic regions, but primarily for practical security reasons.

Payment scenarios exempt from SCA requirements are generally determined by a transaction’s amount, recurrence, and the channel used to carry out the payment. Let’s take a more detailed look at each of these exemptions and their real-world applications.

mojeID has recently been certified for EU-wide use, which means that it’s now possible for users to access e-government services throughout Europe.

Authentication elements are either categorized as knowledge, possession, or inherence. How are these categories defined ⁠— and what does each of them require?

The latest installment of our series focused on Strong Customer Authentication (SCA) explores the aspect of dynamic linking. How is this component vital to providing secure online transactions?

In a continuation of our article series on Strong Customer Authentication (SCA), we’ll be examining the requirements for generating a core component of SCA requirements: authentication codes.