Source
Checkout, SCA & fraud — found from sitemap — Unzer
Checked for Unzer on 1 Oct 2026
- Page
- https://www.unzer.com/en/knowledge/articles/strong-customer-authentication-sca-/
- Checked
- 1 Oct 2026, 08:38 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:f4ea9ab4627d60cbe80fe81216bd7961d3976212fb9f2639974aa35db86215c4
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Sca feature Report an error
“Strong Customer Authentication (SCA) is an Unzer feature that allows merchants to decouple cardholder authentication from payment authorization.”
-
Sca protocol Report an error
“It uses the EMV 3DS 2.x authentication protocol to authenticate the cardholder without immediately authorizing or charging the card.”
-
Sca use cases Report an error
“This approach is PSD2-compliant and is designed for delayed-fulfillment use cases such as: Pre-orders and backorders Delayed shipment or custom manufacturing Services fulfilled at a later date”
-
Sca linkage window Report an error
“Ensuring the authorization occurs within the allowed 90-day linkage window”
-
Sca flow steps Report an error
“STEP 1: CARD REGISTRATION”
-
Sca registration typeid Report an error
“Before initiating SCA, the card must be registered. Purpose Registers the card Returns a typeId The typeId is mandatory for initiating SCA”
-
Sca authenticaton only Report an error
“Performs EMV 3DS authentication Does not create authorization or charge Persists 3DS artifacts (ECI, CAVV, protocol version, DS/ACS IDs, status, timestamp)”
-
Sca details endpoint Report an error
“(Optional) Retrieve SCA Details Purpose Retrieves SCA status and metadata Does not expose raw 3DS authentication data”
-
Sca card on file Report an error
“Yes. SCA can be performed during the initial card-on-file setup transaction. Subsequent merchant-initiated transactions may not require SCA if properly flagged and compliant with scheme rules.”
-
Sca recurring Report an error
“Yes. SCA can be used for recurring transactions, provided the initial transaction is properly authenticated.”
-
Sca partial capture Report an error
“Yes. If you perform an authorization linked to SCA, you may perform partial captures according to standard authorization rules.”
-
Sca merchant responsibilities Report an error
“Merchants are responsible for: Registering the card before initiating SCA Initiating authentication using the SCA API Securely storing the returned paymentId (SCA reference)”
8 facts read from this page are not shown because they could not be confirmed on the page as captured.