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

BitPay: May fail to make payment when paying too many invoices at once

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: 3.6.0
        • Fix Version/s: 4.1.1, 4.2.0-b1
        • Component/s: Gateways
        • Labels:
          None

          Description

          See http://www.blesta.com/forums/index.php?/topic/5290-bitpay-multi-invoices-issue/

          It may be that attempting to pay multiple invoices. When serialized with their amounts and passed to the gateway, the max length is 100 characters. However, it may fail with fewer characters. We will need to test.

          We may need to update the gateway to limit the length of that field, and simply ignore paying specific invoices that exceed the length. Alternatively, we could display an error that too many invoices are being paid at once, and to select fewer invoices to pay before continuing.

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            tyson Tyson Phillips (Inactive) added a comment -

            We should investigate 2 approaches:

            1. If we can display an error from the BitPay gateway after selecting too many invoices, then we should do so
            2. If we attempt to pay for too many invoices, we should truncate the length to 1 fewer invoice than exceeds the total character length of the field (e.g., if 3 invoices will exceed the 100 character limit, only set 2 invoices). In this case, we can apply payments to as many invoices as we could, and the remaining one will be added as a credit, which could be applied automatically to open invoices if Blesta is configured to do so.
            Show
            tyson Tyson Phillips (Inactive) added a comment - We should investigate 2 approaches: If we can display an error from the BitPay gateway after selecting too many invoices, then we should do so If we attempt to pay for too many invoices, we should truncate the length to 1 fewer invoice than exceeds the total character length of the field (e.g., if 3 invoices will exceed the 100 character limit, only set 2 invoices). In this case, we can apply payments to as many invoices as we could, and the remaining one will be added as a credit, which could be applied automatically to open invoices if Blesta is configured to do so.
            Hide
            Permalink
            jonathan Jonathan Reissmueller added a comment - - edited

            1. Well an error can be displayed, but it might not be useful info. A generic error could be given, or maybe an error from BitPay about the posData field, but neither tell the customer that they are trying to pay too many invoices.

            2. This could be done. It is a bit strange to choose invoices, and get credit instead of paying for them. But it could be done.

            Show
            jonathan Jonathan Reissmueller added a comment - - edited 1. Well an error can be displayed, but it might not be useful info. A generic error could be given, or maybe an error from BitPay about the posData field, but neither tell the customer that they are trying to pay too many invoices. 2. This could be done. It is a bit strange to choose invoices, and get credit instead of paying for them. But it could be done.

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  27/Sep/17

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 5 hours, 42 minutes
                  5h 42m

                    Agile