API Overview

Payments Developer Guide
- Recent Revisions to This Document

Introduction to Payments
- Financial Institutions and Payment Networks
- Card Types
- Transaction Types
- Payment Services
  - Authorization Reversal
  - Automatic Partial Authorization Reversal
  - Refund
    - Credit Workflow
  - Void
- Payment Features
  - Introduction to Credentialed Transactions
- Testing the Payment Services
  - Requirements for Testing
  - Test Card Numbers
  - Using Amounts to Simulate Errors
  - Test American Express Card Verification

Standard Payment Processing
- Authorization with a Card Verification Number
- Authorization with Strong Customer Authentication Exemption
- Account Verification with a Zero Amount Authorization
- Authorization Reversal
- Partial Authorization Reversal
- Time-Out Authorization Reversal
- Sale
- Capture
- Credit
- Time-Out Void for a Capture, Sale, Refund, or Credit

Split Shipments Processing
- Authorizing a Sale for a Product Not Yet Available
- Processing Two Authorizations and a Capture for Multiple Products
- Processing an Authorization and Two Captures for Multiple Products

Processing Payments Using Credentials
- Customer-Initiated Transactions with Credentials on File
  - Storing Customer Credentials with a CIT and PAN
  - Storing Customer Credentials with a CIT and Token Management
  - Using Stored Customer Credentials During a CIT
- Delayed Transaction
  - Merchant-Initiated Delayed Transaction with PAN
  - Merchant-Initiated Delayed Transaction with Token Management
- Incremental Transaction
  - Merchant-Initiated Incremental Transaction with PAN
  - Merchant-Initiated Incremental Transaction with Token Management
- No-Show Transactions
  - Merchant-Initiated No-Show Transactions with PAN
  - Merchant-Initiated No-Show Transaction with Token Management
- Installment Payments
  - Customer-Initiated Installment Payments with PAN
  - Customer-Initiated Installment Payment with Token Management
  - Customer-Initiated Installment Payment with Enrollable Network Tokens
  - Merchant-Initiated Installment Payments with PAN
  - Merchant-Initiated Installment Payment with Token Management
- Recurring Payments
  - Customer-Initiated Recurring Payment with PAN
  - Customer-Initiated Recurring Payment with Token Management
  - Customer-Initiated Recurring Payment with Enrollable Network Tokens
  - Merchant-Initiated Recurring Payments with PAN
  - Merchant-Initiated Recurring Payments with Token Management
- Mastercard Standing Order Payments
  - Mastercard Initial CIT Standing Order Payment
  - Mastercard Initial CIT Standing Order Payment with Token Management
- Mastercard Subscription Payments
  - Mastercard CIT Initial Subscription Payment
  - Mastercard CIT Initial Subscription Payment with Token Management
- Unscheduled COF Payments
  - Customer-Initiated Unscheduled COF Payment with PAN
  - Customer-Initiated Unscheduled COF Payments with Token Management
  - Customer-Initiated Unscheduled COF Payment with Enrollable Network Tokens
  - Merchant-Initiated Unscheduled COF Payment with PAN
  - Merchant-Initiated Unscheduled COF Payments with Token Management

On This Page

Authorization Reversal

The authorization reversal service releases the hold that an authorization placed on a customer’s payment card funds.

Each card-issuing financial institution has its own rules for deciding whether an authorization reversal succeeds or fails. When a reversal fails, contact the card-issuing financial institution to learn whether there is a different way to reverse the authorization.

GPX supports authorization reversal after void (ARAV), therefore you can reverse an authorization after you void the associated capture.

An authorization reversal is a follow-on transaction that uses the request ID returned from an authorization. The main purpose of a follow-on transaction is to link two transactions. The request ID links the follow-on transaction to the original transaction. The authorization request ID is used to look up the customer’s billing and account information in the Bank of America database. You are not required to include those fields in the full authorization reversal request. The original transaction and follow-on transaction are linked in the database and in BA360.

The full authorization reversal service works for debit cards and prepaid cards in addition to credit cards.

IMPORTANT

You cannot perform an authorization reversal if a transaction is in a review state, which can occur if you use a fraud management service. You must reject the transaction prior to authorization reversal. For more information, see the fraud management documentation in BA360.

Back to top