Source
Checkout, SCA & fraud — found from sitemap — Unzer
Checked for Unzer on 16 Nov 2026
- Page
- https://www.unzer.com/en/knowledge/articles/strong-customer-authentication-sca-/
- Checked
- 16 Nov 2026, 19:47 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:cd7d13b63891558336215130e3e7229e006785298a3cf06aad5d5073816c5623
- 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 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) Using the same paymentId for exactly one subsequent authorization or charge Ensuring the authorization occurs within the allowed 90-day linkage window”
-
Sca single use Report an error
“Each SCA reference (paymentId) can be linked to only one authorization or charge Reuse of an SCA reference will result in a decline (single-use CAVV)”
-
Sca linkage window days Report an error
“Authorization must be completed within 90 days of successful authentication”
-
Sca does not reserve funds Report an error
“SCA authentication does not reserve funds”
-
Sca flow card registration Report an error
“STEP 1: CARD REGISTRATION Before initiating SCA, the card must be registered. Purpose Registers the card Returns a typeId The typeId is mandatory for initiating SCA”
-
Sca flow authenticate only Report an error
“Step 2: Initiate SCA (Authentication-Only) Purpose Performs EMV 3DS authentication Does not create authorization or charge Persists 3DS artifacts (ECI, CAVV, protocol version, DS/ACS IDs, status, timestamp) Returns a unique SCA reference (paymentId)”
-
Sca flow retrieve details Report an error
“Step 3: (Optional) Retrieve SCA Details Purpose Retrieves SCA status and metadata Does not expose raw 3DS authentication data”
-
Sca flow linked authorization Report an error
“Step 4: Authorization Linked to Prior SCA Performed when goods or services are ready. Rules Uses stored SCA authentication data Consumes the SCA reference Only one authorization or charge is allowed per SCA”
-
Sca flow linked charge Report an error
“Step 5: Charge Linked to Prior SCA (Alternative) Purpose Performs authorization and capture in one step Uses stored SCA data No new SCA is triggered”
-
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 recurring requirements Report an error
“The initial transaction must clearly indicate that it is setting up a recurring payment. Subsequent transactions must be flagged correctly as recurring / MIT. If the amount or agreement changes significantly, re-authentication may be required. Issuers retain the right to request SCA again in certain cases.”
-
Sca amount change Report an error
“Changes in the amount may require a new SCA authentication and could result in a decline. Merchants should authenticate the expected final amount whenever possible.”
-
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. However, the SCA reference itself can only be used once for authorization.”
-
Sca split not allowed Report an error
“No. Each SCA reference (paymentId) is strictly single-use and can be linked to only one authorization or charge. Attempting reuse will result in a decline.”
-
Sca failed authorization Report an error
“If authorization is declined: The SCA reference is considered consumed. A new SCA authentication must be performed before retrying. Authentication success does not guarantee authorization approval.”
-
Sca issuer rights Report an error
“Yes. Although prior SCA has been performed, issuers always retain the right to require additional authentication under risk-based decisioning.”
-
Sca cancellation Report an error
“No. Once authentication is completed, it cannot be cancelled. If unused within the 90-day window, it expires automatically.”
-
Sca benefits Report an error
“REGULATORY COMPLIANCE Meets PSD2 SCA requirements without forcing immediate authorization REDUCED CHECKOUT FRICTION Customers authenticate only once No need to re-authenticate later when goods ship HIGHER CONVERSION & FLEXIBILITY Ideal for delayed fulfillment use cases Enables authorization only when goods or services are ready”
-
Address Report an error
From the vendor’s structured data (JSON-LD) on https://www.unzer.com/en/knowledge/articles/strong-customer-authentication-sca-/, captured 16 Nov 2026
{ "address": { "@type": "PostalAddress", "postalCode": "10963", "streetAddress": "Schöneberger Str. 21 a", "addressCountry": "DE", "addressLocality": "Berlin" } }
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The Compliance Officer Checkout, SCA & fraud
- The Compliance Officer Subscriptions & recurring payments
- The E-Commerce Lead Checkout, SCA & fraud
- The E-Commerce Lead Subscriptions & recurring payments
- The Payments Engineer Checkout, SCA & fraud
- The Finance Lead Checkout, SCA & fraud
- The Finance Lead Subscriptions & recurring payments
- The Skeptic Checkout, SCA & fraud
- The Skeptic Subscriptions & recurring payments
- The SaaS Founder Checkout, SCA & fraud