Recent Revisions to This Document

About This Guide

Basic Processing
- Basic Authorizations
  - Required Fields for Processing Basic Authorizations Using the Simple Order API
  - Declined Authorizations
  - SO Example: Processing a Basic Authorization
- Authorization Reversals
  - Required Fields for Processing Authorization Reversals Using Simple Order APIs
  - Capturing an Authorization Using Simple Order APIs
  - Example: Processing an Authorization Reversal Using the SO API
- Authorization with Line Itemization
  - Optional Line Item Fields
  - Required Fields
  - Processing a Basic Authorization with Line Items and DCC
- Zero Amount Authorizations
  - Required Fields for Processing Zero Amount Authorizations Using the Simple Order API
  - Authorizing a Payment Using Simple Order APIs
  - SO Example: Processing a Zero Amount Authorization
- Captures
  - Required Fields for Processing Basic Captures Using the Simple Order API
  - SO Example: Capturing an Authorization
- Sales
  - Required Fields for Processing Basic Sales Using Simple Order APIs
  - SO Example: Requesting a Sale
- Follow-On Credits
  - Required Fields for Processing Follow-On Credits Using the Simple Order API
  - Example: Processing a Follow-On Credit Using the SO API
- Stand Alone Credits
  - Required Fields for Processing RefundsFollow-On Credits Using Simple Order APIs
  - SO Example: Processing a Stand-Alone Credit
- Capture or Credit Voids
  - Required Fields for Processing Voids Using Simple Order APIs

Card-Present Authorizations

Payer Authentication Processing
- Visa Secure
  - Required Fields for an Authorization with Visa Secure Using SO APIs
  - Example: Authorizing Visa Secure Using the SO API

Debit and Prepaid Card Processing
- Processing Debit and Prepaid Authorizations
  - Required Fields for Debit and Prepaid Authorizations Using Simple Order APIs
    - payments-debit-prepaid-auth-required-country
  - Optional Field for Debit and Prepaid Authorizations Using Simple Order APIs
  - SO Example: Debit and Prepaid Authorizations
- Enabling Debit and Prepaid Partial Authorizations
  - Required Field for Enabling Debit and Prepaid Partial Authorizations Using Simple Order APIs
  - Optional Field for Enabling Debit and Prepaid Partial Authorizations Using Simple Order APIs
  - Enabling Partial Authorizations
  - Example: Enabling Debit and Prepaid Partial Authorizations Using the Simple Order API
- Disabling Debit and Prepaid Partial Authorizations
  - Required Field for Disabling Debit and Prepaid Partial Authorizations Using Simple Order APIs
  - Optional Field for Disabling Debit and Prepaid Partial Authorizations Using Simple Order APIs
  - Disabling Partial Authorizations
  - Example: Disabling Debit and Prepaid Partial Authorizations Using the Simple Order API

On This Page

Simple Order API | First Data Merchant Solutions

Partial Authorizations

All debit and prepaid card processors as well as a limited number of credit card processors support partial authorizations when using dual message processing.

When partial authorization is enabled, the issuing financial institution can approve a partial amount when the balance on the card is less than the requested amount. When a partial amount is authorized, the capture is not processed. This enables the merchant to use a second card to cover the balance, adjust the total cost, or void the transaction.

Back to top