Introducing Digi-Access™ for Online Banking

Choosing between One-Time-Passwords & Digi-Access™

Typical online banking services are well structured and 'secured' with access controlled and 'protected' by usernames and passwords. However, global initiatives such as 'Know Your Customer' [KYC [1]] and many others mean that usernames and passwords can no longer offer sufficient security or authentication of users. Increasing the security by introducing two factor authentication [2FA] is inevitable.

Online Banking Example

Understanding the Digi-Access™ Demonstration [2]

What You Will Learn from the Digi-Access™ Demonstration [3]

Digi-Access™ Demonstration Step-by-Step Instructions [4]

Important Things To Do Once You’ve Completed the Demonstration [5]

Read the instructions & take the demonstration now [6]

Username and password security is no longer sufficient and there are only two credible options available:

One-Time-Password [OTP] Tokens

Digi-Access™ Certificates

In Favour of OTP

Widely used & popular

End user needs no training

Against using OTP

Requires expensive infrastructure changes

Tokens have to be physically issued

Cannot stop 'man-in-the-middle [7]' attacks

In Favour of Digi-Access™

Requires no infrastructure changes

Simple issuing [8] to end users

End user needs no training

Protects against 'man-in-the-middle'

Implement in three simple steps [9]

Can be offered as a security add-on

Considerably less expensive

Against using Digi-Access™

Not as widely adopted as OTP

Concerns about CryptoAPI security [10]

You decide which makes more sense

Take the Digi-Access™ Online Banking Demonstration[6]

Read the three simple steps [9] to implementing Digi-Access™

Then there's the considerable cost savings [11] to take account of

And then let your users decide

Perhaps you don't have any plans to increase the security access to your online application. Budgetary restrictions may be another issue. So why not let your users decide if they want this security 'add-on'.

We have a simple programme for this too:

Implement a two-tiered [9] approach

And if your users want it, they pay for it (not you)

And we'll implement Digi-Access™ for you free-of-charge, on a shared revenue basis