Checkout, SCA & fraud — found from sitemap — Worldpay

Cited by

Facts read from this source

• 3ds liability shift Report an error

  “3DS Issuer performed risk and identity check, giving both liability shift and SCA compliance.”

• Payments API 3ds Report an error

  “Enable 3DS in our Payments API Add 3DS authentication as part of an orchestrated Payments API request.”

• Standalone 3ds API Report an error

  “Use our standalone 3DS API Send a separate 3DS authentication API request and receive a response with the authentication details. Apply this in our Card Payments API or other payment gateways/acquirers as part of external MPI.”

• Sca exemptions Report an error

  “SCA exemptions Worldpay performed risk checks and granting of TRA (Transaction Risk Analysis) exemptions. Reduce 3DS checkout friction.”

• Payments API sca exemptions Report an error

  “Enable SCA Exemptions in our Payments API Ask for an SCA Exemption to be applied automatically as part of our Payments API.”

• Standalone sca exemptions API Report an error

  “Use our standalone SCA Exemptions API Send a separate SCA Exemptions API request and receive a outcome containing a granted exemption. Apply this in the Card Payments API.”

• Sca lowvalue threshold Report an error

  “lowValue - the order is under €30”

• Sca lowrisk condition Report an error

  “lowRisk - the transactions through Worldpay (acquirer) are maintained below a set fraud threshold”

• Exemption liability Report an error

  “Liability is shifted to the Exemption provider (e.g. Worldpay) instead of the issuer for this case.”

• Mit no sca Report an error

  “MIT (Merchant Initiated Transactions) Recurring payments where the customer is not present, do not require SCA”

• Moto no sca Report an error

  “MOTO Payments For example: telephone, in-store”

• One leg out no sca Report an error

  “One Leg Out If the issuing bank or acquirer (e.g. Worldpay) is outside the EEA (European Economic Area)”

• Corporate payments no sca Report an error

  “Corporate Payments Virtual cards, used for things such as booking travel”

• Whitelist no sca Report an error

  “Whitelist (trusted Businesses) Cardholder can whitelist a merchant to avoid future 3DS checks”

• Sca factors Report an error

  “the user needs to authenticate with two or more factors: something the user knows - PIN, password, answer to a security question something the user possesses - mobile phone, physical card something the user is - fingerprint, facial recognition”

• Applepay googlepay sca Report an error

  “Payment methods such as Apple Pay or Google Pay, instead meet these SCA requirements by ensuring two of the factors above are met through their own authentication. There is an exception in the case of Google Pay when the payment is not stored as an android device token and must go through 3DS.”

• Challenge mandated setting Report an error

  “The challenge.preference in the 3DS authentication request must be set to challengeMandated”

• Account verification no payment Report an error

  “For this you can use an account verification to apply the 3DS authentication details, as there is no initial payment”

• Liability shift timing Report an error

  “Liability shift itself happens at the point of the payment, not the 3DS authentication. A successful 3DS authentication does however make this highly likely.”

• Exemptions cit only Report an error

  “You should only request exemptions for Customer Initiated Transaction (CIT) where no initial card storage is taking place.”

Scores citing this record

• The Compliance Officer Checkout, SCA & fraud
• The E-Commerce Lead Checkout, SCA & fraud
• The E-Commerce Lead Subscriptions & recurring payments
• The E-Commerce Lead Licence, risk & account terms
• The Payments Engineer Checkout, SCA & fraud
• The Payments Engineer European sovereignty
• The Finance Lead Checkout, SCA & fraud
• The Skeptic Checkout, SCA & fraud
• The SaaS Founder Checkout, SCA & fraud