On This Page

Commit Tax Calculation Scenarios

You can commit tax calculation requests at different moments in a transaction.
Use these scenario examples to determine when it would be best for you to commit a tax calculation.
Possible scenarios:

Scenario 1: Pre-authorization

You can commit a tax calculation request before requesting an authorization. For example:
  1. Request the tax calculation service with the
    taxService_commitIndicator
     field set to
    true
    .
  2. Authorize and capture payment.
  3. If the authorization or capture fails, void the previously committed tax calculation request. See Void Tax Calculation.

Scenario 2: Post-capture

You can commit a tax request after a capture. If you implement the tax service in this way, you will have to request the tax calculation service at least twice per request. For example:
  1. Request the tax calculation service with the commit indicator field set to
    taxService_commitIndicator
     set to
    false
    .
  2. Authorize and capture the payment.
  3. If the authorization and capture are successful, request the tax calculation service with the
    taxService_commitIndicator
     set to
    true
    .

Scenario 3: Partial Captures

You can commit a tax request for partial captures. For example:
  1. Request the tax calculation service with the commit indicator field set to
    taxService_commitIndicator
     set to
    false
    .
  2. Authorize the payment for $0 or wait to authorize partial payments as items are transferred to the customer.
  3. Implement Scenario 1 or Scenario 2 as you make authorizations and captures.