Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-3105 Update criteria for assigning offsite payment accounts to an existing customer
  3. CORE-3299

Authorize.net: Ensure that a $client_reference_id is valid

        Details

        • Type: Sub-task
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: None
        • Fix Version/s: 4.8.0-b1
        • Component/s: Gateways
        • Labels:
          None

          Description

          The ::storeCc() and ::storeAch() methods uses a given $client_reference_id without first checking that it is in fact valid. Instead we should check if it is a valid client ID for the gateway, and only then use it.

            Activity

            Ascending order - Click to sort in descending order
            jonathan Jonathan Reissmueller created issue -
            jonathan Jonathan Reissmueller made changes -
            Field Original Value New Value
            Component/s Gateways [ 10005 ]
            Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
            Status Open [ 1 ] In Progress [ 3 ]
            Automated transition triggered when Jonathan Reissmueller created pull request #6 in Stash -
            Status In Progress [ 3 ] In Review [ 5 ]
            Resolution Fixed [ 1 ]
            jonathan Jonathan Reissmueller made changes -
            Remaining Estimate 0 minutes [ 0 ]
            Time Spent 44 minutes [ 2640 ]
            Worklog Id 12678 [ 12678 ]
            Automated transition triggered when Tyson Phillips (Inactive) merged pull request #6 in Stash -
            Status In Review [ 5 ] Closed [ 6 ]

              People

              • Assignee:
                jonathan Jonathan Reissmueller
                Reporter:
                jonathan Jonathan Reissmueller
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  23/Dec/19

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 44 minutes
                  44m

                    Agile