Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adyen: Fail unexpected 3DS responses #3546

Commits on Feb 26, 2020

  1. Adyen: Fail unexpected 3DS responses

    There are certain situations where the initiator of a transaction is not
    expecting or prepared to complete a 3DS challenge flow, yet an authorize
    transaction triggers a 3DS auth response from Adyen.
    
    Previously, if a 3DS flow was not expected, a Purchase was initiated,
    and the auth step received a 3ds authentication response, the adapter
    would assume the auth step succeeded, and perform the capture, for which
    Adyen's response is not sufficient to indicate the money was actually
    moved. This means the Purchase would be assumed to succeed when in fact
    it was stalled at the 3DS auth step.
    
    This change recognizes these situations and fails the transaction with a
    meaningful message.
    
    Remote:
    82 tests, 276 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
    100% passed
    
    Unit:
    59 tests, 279 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
    100% passed
    chinhle23-zz authored and curiousepic committed Feb 26, 2020
    Configuration menu
    Copy the full SHA
    c1b645e View commit details
    Browse the repository at this point in the history