Source
Checkout, SCA & fraud — found from sitemap — Saferpay
Checked for Saferpay on 13 Oct 2026
- Page
- https://docs.saferpay.com/home/integration-guide/general-information/3d-secure
- Checked
- 13 Oct 2026, 14:00 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:8765ccd8468e96901826da8e1856eb2244e9363bc8fb052e9666b7517a689112
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
3ds supported schemes Report an error
“3DS for short – is supported by Visa (Visa Secure), Mastercard (Mastercard ID check), American Express (SafeKey), Diners Club (ProtectBuy) and others and is intended as an anti-fraud measure.”
-
3ds supported flows Report an error
“3D Secure is only available through the Payment Page, Transaction Interface flows, or via the Standalone Secure Card Data registration, using the "ONLINE_STRONG" check function.”
-
3ds no extra integration cost Report an error
“This step is done automatically via the Transaction Interface and the Payment Page, meaning that no additional integration costs arise.”
-
3ds frictionless threshold Report an error
“This also applies to all orders smaller or equal to 30 Euro, or equivalent, though with a maximum of 5 concurrent transactions (Globally, not merchant/shop-based!).”
-
Force 3ds challenge parameter Report an error
“Via our API this can be triggered by submitting the parameter Authentication.ThreeDsChallenge=FORCE. Saferpay will then always request a Challenged Flow on issuer side.”
-
3ds API response fields Report an error
“The Saferpay JSON-API does return all necessary information inside the Liability-Container, when using Transaction Authorize or PaymentPage Assert. The important parameters are AuthenticationType and especially LiabilityShift.”
-
Liability shift only via 3ds Report an error
“Caution: Liability shift can only be granted through 3D Secure!”
-
Condition flag Report an error
“Only want to accept transactions with Liability Shift? Check out the Condition-flag that can be set within the Payment Page Initialize and Transaction Authorize requests, to control whether an authorization should be performed or not, in the first place.”
-
Force challenge payment page Report an error
“For the Payment Page, please set the parameter Condition to WITH_SUCCESSFUL_THREE_DS_CHALLENGE for the Payment Page Initialize.”
-
Force challenge transaction interface Report an error
“Set the parameter Authentication.ThreeDsChallenge to FORCE for the Transaction Initialize request. Set the parameter Condition to WITH_SUCCESSFUL_THREE_DS_CHALLENGE for the Transaction Authorize request.”
-
Force challenge standalone registration Report an error
“For the standalone card registration, please perform an "ONLINE_CHALLENGED" card check.”
-
Business card detection Report an error
“Saferpay does try to detect these cards, based on their BIN range. You will get this information with the rest of the transaction-data inside the PaymentMeans.Card.HolderSegment parameter.”
-
Block business cards Report an error
“Saferpay offers an option to block these cards, if so desired, by using the Risk Management from the Backoffice.”
-
Payer activation message Report an error
“If so, you will also get this message from Saferpay inside the PayerMessage parameter, so you may display it to your customer.”
-
Mandatory datapoints Report an error
“Datapoint Mandatory Payment Page Transaction Interface Complete Address Yes”
-
External 3ds providers Report an error
“While Saferpay does mainly use its own 3D Secure implementation, it is capable of accepting data from external 3D Secure providers, if necessary. You can use the Authorize Direct request for transactions and Insert Direct for registrations to pass this data towards Saferpay for an authorization, inside the Authentication.ExternalThreeDS container.”
-
3ds configuration datapoints Report an error
“MerchantId: The MerchantId is your contract number. You can find it inside the Saferpay Backoffice under Settings > Terminals for the given Payment Method. Acquirer BIN: The Acquirer BIN is the identification-number of your card processor, or acquirer.”
4 facts read from this page are not shown because they could not be confirmed on the page as captured.
Scores citing this record
- The Compliance Officer Checkout, SCA & fraud
- The E-Commerce Lead Checkout, SCA & fraud
- The Payments Engineer Checkout, SCA & fraud
- The Finance Lead Checkout, SCA & fraud
- The Skeptic Checkout, SCA & fraud
- The SaaS Founder Checkout, SCA & fraud