Problem/Motivation

The voiding mechanism in the Accept Hosted implementation is not properly re-introducing a balance to the order. While the void is created in Authorize and the pending settlement is voided the Drupal order balance is still 0 and the payment still shows that fully amount was captured even though the payment is in a voided state.

Steps to reproduce

  1. Create an order
  2. Add a shipment
  3. Add a payment method using the Accept Hosted gateway and Click Pay(Confirm that the payment is “captured”)
  4. Click Void
  5. Payment will be voided but will not show an order balance

Expected outcome

Voiding or Refunding a payment should create a balance on the order equal to the amount that had been captured. While we are correctly sending void to Authorize Drupal is not registering the fact that the payment is not actually captured.

Business Requirements

  1. You should be able to void an authorization
  2. You should be able to void a captured payment that is in “awaiting settlement” in authorize
  3. You should be able to “refund” a settled payment
  4. In all cases a balance should be present on the order and the transaction in Authorize should match what is in Drupal (and vice versa).
Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

vmarchuk created an issue. See original summary.

vmarchuk’s picture

Status: Active » Needs review

Failed tests are not related to changes.

vmarchuk’s picture

Status: Needs review » Reviewed & tested by the community

  • vmarchuk committed 19000ba9 on 2.x
    Issue #3566655: Update order balance when payment is voided.
    
vmarchuk’s picture

Assigned: vmarchuk » Unassigned
Status: Reviewed & tested by the community » Fixed

Committed!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.