Developer
  • Getting started keyboard_arrow_down

    Discover

    • arrow_forward
      EV Charging

      Discover our unattended POS solution for the ev market

    Our solutions

    • arrow_forward
      CCV Terminal

      Integrate with a CCV Terminal

    • arrow_forward
      SoftPOS

      Turn your own device into a payment terminal

    • arrow_forward
      CCV Online Payments

      Accepting online payments in your platform without technical knowledge

    • arrow_forward

    • arrow_forward

    Connect to the CCV Platform

    Integrate our products into your software. Let's make payment happen together!

    Look at all the possibilities
  • Documentation
  • API Reference
menu
    • expand_less Payment API
      • expand_more General
        • Communication
        • Environments
        • Authentication
        • Idempotency
        • Transaction Types
        • Webhooks
        • Notifications
        • Error Handling
        • Security & Privacy
        • Return URL
      • expand_less Online Payments
        • expand_more Quick Start
          • Initial Setup
          • Create Payment
        • expand_more Basic Operations
          • Create A Payment
          • Refund A Payment
          • Authorise & Capture Payments
          • Query The Payment Status
        • expand_less Payment Features
          • expand_less 3D-Secure 2
            • SCA And 3D-Secure 2
            • Compliance Guide
            • Out Of Scope Transactions
            • Exemptions
          • Payment Links
          • Merchant Initiated Payments
          • Embedded Card Payments
          • Mandates
          • Customers & Loyalty
          • Partial Payment
        • expand_more Payment Methods
          • American Express
          • Apple Pay
          • Google Pay
          • expand_more Bancontact
            • Bancontact Walled Initiated Payments (WIP)
            • Bancontact Deferred Sales
          • Bancontact Mobile
          • Banktransfer
          • IDEAL
          • Klarna
          • Landingpage
          • Maestro
          • Mastercard
          • Payconiq
          • Paypal
          • Visa
        • expand_more Payouts
          • Split Payout
          • Test Payout
        • expand_more Developer Resources
          • Currencies
          • Languages
          • Payment Testing
          • Test Cards
      • expand_more In-person Payments
        • expand_more SoftPOS
          • expand_more General
            • Getting Started
            • Device Requirements
            • SoftPOS TerminalIds
            • SoftPOS Errors
            • Currencies
            • Languages
            • Network And Connectivity
            • Release Notes
          • expand_more Basic Operations
            • Install A Terminal
            • Make A Payment
            • Handling Receipts
          • expand_more API Reference
            • SoftPOS - API Reference
    • expand_more Board Your Merchants At CCV
      • expand_more General
        • Getting Started
        • Authentication
      • expand_more Boarding API
        • StartOrder
        • AddSalesPackage
        • AddProductPSPStandalone
        • AddProductPSPSubmerchant
        • AddTerminalPackage
        • SetShoppingCartPricingDetails
        • SubmitOrder
        • Boarding
      • API Reference
    • expand_more Android Rest Beta API
      • expand_more General
        • Getting Started
        • Brands
        • Supported Languages
      • expand_more Basic Operations
        • Make A Payment
        • Cancel A Payment
        • Handling Receipts
        • Show Display Messages
        • Recover A Payment
      • expand_more Payment Features
        • Authorise & Capture
        • Capture
      • expand_more Terminal Features
        • Transaction Overview
        • Brands
        • Period Closing
        • Terminal - Status
      • expand_more Tokenization
        • Tokenization - Get A Card Token
        • Read A Mifare Card
        • Custom Text On Terminal
      • expand_more API Reference
        • API Reference
    • expand_more Android SDK
      • expand_more General
        • Getting Started
        • Demo Application - Android SDK
        • Result States
        • Language Codes
        • Error Handling
        • Logging
        • EP2
        • Download SDK
        • Release Notes
      • expand_more Basic Operations
        • Make A Payment
        • Stop Ongoing Payment
        • Recover A Payment - Android SDK
      • expand_more Payment Features
        • Account Selection - Android SDK
        • Additional Receipt Text - Android SDK
        • Allow Or Deny Card Brands - Android SDK
        • Authorisation By Voice - Android SDK
        • Authorise - Android SDK
        • Capture - Android SDK
        • Card Detection - Android SDK
        • Card Detection Deprecated - Android SDK
        • Card Token - Android SDK
        • Card Validation - Android SDK
        • Customer Display - Android SDK
        • E-Receipt - Android SDK
        • Manual Card Information Entry - Android SDK
        • Payment Reversal - Android SDK
        • Refund - Android SDK
        • Request Transaction Information - Android SDK
        • Reservation - Android SDK
        • German Eichrecht - Android SDK
      • expand_more SDK Guides
        • Activate Terminal - Android SDK
        • Card Circuits - Android SDK
        • Card Reader Status - Android SDK
        • Card Reader Status - Android SDK
        • Check Password - Android SDK
        • Factory Reset - Android SDK
        • Get Config - Android SDK
        • Get Status - Android SDK
        • Mobile Phone Prepaid - Android SDK
        • Online Agent - Android SDK
        • Partial Period Closing - Android SDK
        • Period Closing - Android SDK
        • Possible Transaction Types - Android SDK
        • Retrieve Last Ticket - Android SDK
        • Retrieve Open Pre Authorisations - Android SDK
        • Startup - Android SDK
        • Taxfree - Android SDK
        • Terminal Administration - Android SDK
        • Terminal Discovery - Android SDK
        • Ticket Reprint Period Closing - Android SDK
        • Transaction Overview - Android SDK
        • Check Password - Android SDK
      • expand_more Hardware Access
        • Getting Started
        • NFC - Android SDK
        • Printing - Android SDK
        • QR And Barcode Scanner - Android SDK
      • expand_more API Reference
        • API Documentation
    • Android App Requirements
    • expand_more Certification
      • Introduction
      • expand_more Attended Certification Tests
        • expand_more Aborting
          • F1A - Regular Abort By Merchant
          • F1B - Failing Abort By Merchant
          • F1D - Hammering Abort By Merchant
        • expand_more Allowed Amounts
          • S1A - Transaction With Amount Of EUR 0,00
          • S1B - Transaction With Negative Amount
          • S1C - Transaction With Highest Possible Amount
          • S1D - Over-Amount Transaction
        • expand_more Connection Lost
          • Q1B - Manual Transaction Recovery
          • Q1C - Ethernet Connection With ITS Fails
          • Q1F - Device Unavailable
          • Q1G - Terminal Not Responding
          • T1A - Automatic Transaction Recovery
        • expand_more E Journal
          • M1A - Store E-Journal
          • M2A - ECR/POS Print Journal Receipts
          • M3A - ECR/POS Storing Journal Receipts
        • expand_more Reprint Ticket
          • L1A - Reprint Ticket
          • L1B - Reprint Ticket Declined Transaction
          • L2A - Reprint Ticket No Printer Available
          • L2B - Reprint Ticket Declined Transaction No Printer Available
        • expand_more Tickets
          • U1A - Request For Identification
          • U1B - Request For Signature
          • U1C - Request For Signature And Identification
          • U1D - Failing Transaction No Receipt
          • U1E - Split Payment
        • expand_more Time Out
          • R1A - Time Out On Presenting A Card
          • R1B - Time Out During Pin Entry
        • expand_more Transactions
          • C1A - Happy Flow
          • C1B - Happy Flow Contactless
          • C1D - Happy Flow Magnetic Stripe
          • C1E - Declined Transaction By Host
          • C1E - Transaction Aborted By Cardholder
          • C1F - Absence Of Thousand Separator
          • C1G - Cashier Display Messages
        • expand_more Validation
          • H1A - Too Many Fingers
          • H1B - Not Removing Card
          • H2A - Power Loss Or Closing Of ECR/POS During Transaction
      • expand_more Unattended Certification Tests
        • expand_more User Guidance
          • C1 - Successful Payment
          • C2 - Next Cardholder
          • C3 - Abort On PIN Entry
          • C4 - Time Out During PIN Entry
          • C5 - No Amount Entered
          • C6 - Language Selection
          • C7 - Amount To Authorise
          • C8 - Available Funds
        • expand_more Device Selection
          • D1 - Device Selection
          • D2 - Invalid Device
          • D3 - Charger Selection Abort
          • D4 - No Charger Selected
          • D5 - Authorisation With No Free Devices
        • expand_more Product Delivery
          • E1 - Product Selection
          • E2 - Enabled Products
          • E3 - Invalid Product Entered
          • E4 - Product Selection Aborted
          • E5 - No Product Selected
          • E6 - Max Delivery Time
          • E7 - Abort Session
          • E7 - Abort By POS
          • E9 - Not Started Charging In Time
          • E10 - Take More Fuel Than AVF
          • E10 - Multiple Sessions Mixed
          • E12 - Postpone Card Financial Advice On New Cardholder Card
          • E13 - Abort Session On Card Reinsert
        • expand_more Receipts
          • F1 - Cardholder Retrieve Receipt Info
          • F2 - Cardholder Receipt Retrieval
          • F3 - Reprint Ticket
          • F4 - F8 - Ticket Printing And Content
          • F9 - TrackingToken Deleted
          • F10 - Printer Paper Low
          • F11 - CardPayment Erased From Storage
          • F12 - E-Receipt Received By Cardholder
          • F13 - E-Receipt Failure
        • expand_more Transaction Limit Handeling Maestro
          • G1 - Maestro CardPayment 1 Euro
          • G2 - Maestro CardPayment 30 Euro
          • G3 - Maestro CardPayment 60 Euro
          • G4 - Maestro CardPayment 500 Euro
        • expand_more Transaction Limit Handeling Mastercard
          • H1 - Mastercard CardPayment 1 Euro
          • H2 - Mastercard CardPayment 30 Euro
          • H3 - Mastercard CardPayment 60 Euro
          • H4 - Mastercard CardPayment 500 Euro
        • expand_more Mifare Handling
          • I1 - Happy Flow Mifare
          • I2 - Unknown Mifare Card
          • I3 - No Mifare Card Presented
          • I4 - Mastercard Presented
        • expand_more Card Circuits
          • L1 - Available Card Circuits
        • expand_more Reconciliation
          • M1 - Reconciliation As Function
          • M2 - Reconciliation By New Shiftnumber
          • M3 - POS Auto Triggers Reconciliation With Closure
        • expand_more Journal
          • N1 - Journal Accessible By Authorized Employees
          • N2 - Journal Cannot Be Altered
        • expand_more Exception Flows
          • O1 - Unknown Card Session
          • O2 - Maximum Time Out
          • O3 - Device Unavailable
          • O4 - Time Out Card-Type Fallback
          • O5 - Time Out On Presenting Card
          • O6 - App Stability
          • O7 - Automatic Startup
          • O8 - Sleep Mode Not Supported
          • O8 - Sleep Mode Supported
        • expand_more Recovery
          • X1 - Recovery After Communication Failure
          • X2 - Recovery After CCV Component Update
          • X3 - Recovery After 24 Hour Reboot
          • X4 - Recovery After CCV-Fusion Client Restart
          • Y1 - Recovery After Power Failure With No Battery Backup
          • Y2 - Recovery After Power Failure With Battery Backup
      • expand_more SoftPOS Certification Tests
        • expand_more Success Scenarios
          • Installation Success - SoftPOS Certification Test
          • Payment Success - SoftPOS Certification Test
        • expand_more Failed Scenarios
          • Installation Failed - CCV SoftPOS App Not Installed - SoftPOS Certification Test
          • Payment Failed - Declined - SoftPOS Certification Test
          • Payment Failed - CCV SoftPOS App Is Closed During Payment - SoftPOS Certification Test
          • Payment Failed -CCV SoftPOS App Is Killed During Payment - SoftPOS Certification Test
          • Payment Failed - SoftPOS App Not Installed Anymore - SoftPOS Certification Test
        • expand_more Other Scenarios
          • Other Scenario - Data Cleared Of The CCV SoftPOS App - SoftPOS Certification Test
    • expand_more Development Kits
      • SoftPOS Dev Kit
      • IM30 Dev Kit
    • Glossary

Payment API

  • General
    • Communication
    • Environments
    • Authentication
    • Idempotency
    • Transaction Types
    • Webhooks
    • Notifications
    • Error Handling
    • Security & Privacy
    • Return URL
  • Online Payments
    • Quick Start expand_more
      • Initial Setup
      • Create Payment
    • Basic Operations expand_more
      • Create A Payment
      • Refund A Payment
      • Authorise & Capture Payments
      • Query The Payment Status
    • Payment Features
      • 3D-Secure 2
        • SCA And 3D-Secure 2
        • Compliance Guide
        • Out Of Scope Transactions
        • Exemptions
      • Payment Links
      • Merchant Initiated Payments
      • Embedded Card Payments
      • Mandates
      • Customers & Loyalty
      • Partial Payment
    • Payment Methods expand_more
      • American Express
      • Apple Pay
      • Google Pay
      • Bancontact expand_more
        • Bancontact Walled Initiated Payments (WIP)
        • Bancontact Deferred Sales
      • Bancontact Mobile
      • Banktransfer
      • IDEAL
      • Klarna
      • Landingpage
      • Maestro
      • Mastercard
      • Payconiq
      • Paypal
      • Visa
    • Payouts expand_more
      • Split Payout
      • Test Payout
    • Developer Resources expand_more
      • Currencies
      • Languages
      • Payment Testing
      • Test Cards
  • In-person Payments
    • SoftPOS expand_more
      • General expand_more
        • Getting Started
        • Device Requirements
        • SoftPOS TerminalIds
        • SoftPOS Errors
        • Currencies
        • Languages
        • Network And Connectivity
        • Release Notes
      • Basic Operations expand_more
        • Install A Terminal
        • Make A Payment
        • Handling Receipts
      • API Reference expand_more
        • SoftPOS - API Reference

What's on this page

  • Strong Customer Authentication and 3D Secure 2
  • What is Strong Customer Authentication?
  • What is 3D Secure?
    • 3D Secure 2: Authentication Process
      • Frictionless flow
    • 3D Secure 2: User Experience
  • What is 3D Secure chargeback liability shift?
    • Mastercard liability shift rules
    • Visa, American Express liability shift rules
  • How is CCV helping you with SCA compliance and the 3D Secure 2 transition?
Online Payments / Payment Features / 3D-Secure 2 / SCA And 3D-Secure 2

Strong Customer Authentication and 3D Secure 2

On September 14th, 2019, changes were introduced to the online payment environment in the European Union, which mandates Strong Customer Authentication (SCA) when a consumer starts an electronic payment transaction. These changes are described by the second Payment Services Directive (PSD2) and are aimed at reducing fraud and increasing protection for consumers. The requirements defined by SCA are part of PSD2, and are in effect from January 1st, 2021.

To meet the new SCA requirements, two-factor authentication is required for online card payments in Europe. Without authentication, merchants risk an increase in payment declines from the customer’s banks.

In this article, we provide more information on the new requirements known as Strong Customer Authentication (SCA). We’ll also cover 3D Secure and how it relates to SCA. Finally, we would like to inform you how CCV is preparing for these changes and how they might affect your business.

What is Strong Customer Authentication?

The Strong Customer Authentication specification or SCA brings a new set of requirements that will change how consumers and business customers confirm their identity when making purchases online. The goal of these requirements is to improve fraud protection for both parties.

The SCA regulation applies to all online (website or app) card-based payments, unless one of the limited exemptions allowed under the rules can be applied. For full details please refer to the Regulatory Technical Standards (RTS) .

SCA requires at least two of the following three elements for authentication:

Knowledge Possession Inherence
Something only the customer knows

e.g. password or PIN
Something only the customer has

e.g. phone or hardware token
Something the customer is

e.g., fingerprint or face recognition

To comply with SCA the payment industry has introduced the 3D Secure protocol. All transactions have to use EMV 3DS (3DS2).

Warning

Issuers may decline transactions that do not meet the new SCA criteria.

What is 3D Secure?

3D Secure is a security protocol used for authentication of online card-based payments and is recommended for SCA compliance. The protocol adds a verification step that identifies card owners during the transaction process (e.g. providing a fingerprint with their phone).

There are two 3D Secure protocol versions:

  • 3D Secure 2 (3DS 2): Also known as EMV 3DS which is the current standard method . In this version, the cardholder performs authentication within your website or mobile application for entering authentication data without redirections. The authentication data provided by the cardholder can be e.g., biometrics, token, etc.

  • 3D Secure 1 (3DS 1): Also known as Visa Secure which was introduced in 2001. This version is deprecated, replaced by 3DS 2.

The introduction of 3DS had a clear benefit for businesses as the request for additional information creates an extra layer of fraud protection that ensures payments only have legitimate customers. As a result, liability for fraud disputes could shift from merchants to issuers.

Features of 3D Secure 2:

  • Support for a frictionless authentication flow.
  • Collecting relevant data for each payment request, allowing better risk assessment by the issuing bank to enable a frictionless authentication flow.
  • Fraud protection due to the availability of more data.
  • Streamlined user experience by providing support for a native mobile authentication process without the need for a redirect.

3D Secure 2: Authentication Process

The authentication of a cardholder can either be frictionless or with a challenge, depending on the issuer’s requirements. This should result in high conversion rates due to a lower dropout of customers during the checkout process.

Frictionless flow

A frictionless authentication flow requires no interaction of the cardholder with the issuer during a transaction. This may be achieved by sending more data elements with each transaction. Based on the provided information the issuer can decide if the transaction qualifies for a frictionless flow. Transactions that follow a frictionless flow benefit from the same liability shift as transactions that pass through the challenge flow.

Note

The issuer always has the last say in whether or not a frictionless flow can be applied.

If the issuer decides further proof of authentication is required the customer will be sent through the Challenge flow.

Challenge flow

The Challenge flow is applied when the issuer requires more information to complete the authentication process. In this flow the issuer decides how the cardholder has to provide proof of authentication, it can be through the use of biometrics, two-factor authentication, or similar authentication methods based on the SCA criteria.

An issuer is not limited to one authentication method and can support multiple methods. It is up to the issuer to decide which methods are supported and how they should be implemented.

3D Secure 2: User Experience

3D Secure 1 was designed in a period before mobile applications. As a result, the customer was left with outdated browser-based user experience. 3D Secure 2 improves this experience by adding the following:

  • More Out-of-band authentication options. Instead of entering a password or SMS verification code, the cardholder can now authenticate using smartphone features like a fingerprint or facial recognition.
  • Support for embedded browser/app-based authentications and digital wallets, no more redirects. Allowing merchants the create a seamless look and feel for their interfaces across various devices.

What is 3D Secure chargeback liability shift?

When you implement 3D Secure 2 authentication, you can shift the liability for fraud-related chargebacks (such as when a customer denies making a purchase, or has their card stolen or lost) from you to the card issuer. This shift occurs when a payment is successfully authenticated. Typically, this happens when a customer completes a 3DS2 challenge authentication flow, which requires additional interaction from the customer. In some regions, a liability shift can also occur after a successful frictionless flow, where the transaction is approved through passive authentication without additional customer interaction.

Mastercard liability shift rules

Transaction type Liability shift
3DS authentication failed,
or could not be attempted
✗
3DS authentication processed
by a stand-in service,
and is classed as successful
✓
Successful 3DS authentication ✓
Frictionless authentication
via the Mastercard Identity
Check Data Only service
✗
SCA exemption used,
or transaction is out of scope
of SCA
✗
Successful 3DS authentication;
recurring transaction secured
by 3DS.
✓

Visa, American Express liability shift rules

Transaction type Liability shift
Successful 3DS authentication ✓
3DS authentication processed
by a stand-in service,
and is classed as successful
✓
SCA exemption used,
3DS authentication failed,
or could not be attempted
✗

How is CCV helping you with SCA compliance and the 3D Secure 2 transition?

The transition to mandatory SCA compliance in Europe is inevitable. As a result, more transactions will be declined for merchants not sending essential data.

CCV offers an integration guide that provides you with the necessary information to make your SCA transition a success.

Go to

Home
Documentation




Cookies Privacy Statement