Recent Revisions to This Document

About This Guide

Basic Processing
- Basic Authorizations
  - Required Fields for Processing Basic Authorizations Using the REST API
  - Declined Authorizations
  - REST Interactive Example: Processing an Authorization
  - REST Example: Processing a Basic Authorization
- Authorization Reversals
  - Required Fields for Processing Authorization Reversals Using REST APIs
  - Capturing an Authorization Using REST APIs
  - Example: Processing an Authorization Reversal Using the REST API
- Authorization with Line Itemization
  - Required Fields
  - REST Example: Processing a Basic Authorization with Line Items
- Zero Amount Authorizations
  - Required Fields for Processing Zero Amount Authorizations Using the REST API
  - Authorizing a Payment Using REST APIs
  - REST Example: Processing a Zero Amount Authorization
- Captures
  - Required Fields for Processing Basic Captures Using the REST API
  - REST Interactive Example: Capturing a Payment
  - REST Example: Capturing an Authorization
- Sales
  - Required Fields for Processing Basic Sales Using REST APIs
  - REST Example: Requesting a Sale
- Refunds
  - Required Fields for Processing Refunds Using the REST API
  - REST Interactive Example: Processing a Refund
  - Example: Processing a Refund Using the REST API
- Stand Alone Credits
  - Required Fields for Processing RefundsFollow-On Credits Using REST APIs
  - REST Interactive Example: Processing a Credit
  - REST Example: Processing a Stand-Alone Credit
- Capture or Credit Voids
  - Required Fields for Processing Voids Using REST APIs
  - REST Example: Processing a Void

Card-Present Authorizations

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

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

On This Page

REST API | ValueLink

Enabling Debit and Prepaid Partial Authorizations

Partial authorizations and balance responses are special features that are available for debit cards and prepaid cards. This section provides the minimum set of information required to enable partial authorizations for a specific transaction.

Fields Specific to this Use Case

Include the following fields in addition to the fields required for a standard authorization request:

Indicate that this request is a partial authorization.

Set the

processingInformation.authorizationOptions.partialAuthIndicator

to

true

.

Back to top