Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-2072

AuthorizeNet: Save last 4 of card in reference ID for CIM

        Details

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

          Description

          Authorize.net gateway should store the last 4 of the card number as the reference_id for the transaction for CIM as it does for AIM.

          This will mean passing along the $account from GatewayPayments::[process|authorize|capture|refund|void]Payment, via MerchantGateway::[set|get]Account()

          This would then allow AuthorizeNet::processStoredCc() to fetch the account info (via MerchantGateway::getAccount(), and set the appropriate value as the reference_id.

            Issue Links

            relates to

            New Feature - A new feature of the product, which has yet to be developed. CORE-1962 Show reference ID in transactions listings

            • Major - Major loss of function.
            • Closed

              Activity

              Hide
              Permalink
              tyson Tyson Phillips (Inactive) added a comment -

              This task only updates Authorize.net to pass the last 4 that is retrieved from the API response as the transaction reference ID. It does not perform the generic changes to GatewayPayments or the MerchantGateway.

              Show
              tyson Tyson Phillips (Inactive) added a comment - This task only updates Authorize.net to pass the last 4 that is retrieved from the API response as the transaction reference ID. It does not perform the generic changes to GatewayPayments or the MerchantGateway.

                People

                • Assignee:
                  tyson Tyson Phillips (Inactive)
                  Reporter:
                  cody Cody Phillips (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    15/Sep/16

                    Agile