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
- Authorization with an SCA Exemption
  - Required Fields for Processing Basic Authorizations Using the REST API
  - REST Example: Authorization with an SCA Exemption for Low Value Transactions
- 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
- EMV Chip and Online PIN Authorization
  - Fallback
  - Required Fields for a Contact EMV Authorization with Online PIN Using the REST API
  - REST Example: EMV Chip and Online PIN Authorization
- EMV Chip (Contact) and Offline PIN Authorization
  - Fallback
  - Required Fields for a Contact EMV Authorization with Offline PIN Using the REST API
  - REST Example: EMV Chip (Contact) with an Offline PIN
- EMV Chip (Contact) and Signature
  - Fallback
  - Required Fields for a Contact EMV Authorization with a Signature Using the REST API
  - REST Example: EMV Chip (Contact) with a Signature
- EMV Chip (Contactless) and Online PIN
  - Fallback
  - Required Fields for an EMV Contactless Authorization with an Online PIN Using the REST API
  - REST Example: EMV Chip (Contactless) with an Online PIN
- EMV Chip (Contactless) and Offline PIN
  - Fallback
  - Required Fields for an EMV Contactless Authorization with an Offline PIN Using the REST API
  - REST Example: EMV Chip (Contactless) with an Offline PIN
- EMV Chip (Contactless with a Signature
  - EMV Fallback
  - Required Fields for an EMV Contactless Authorization with a Signature Using the REST API
  - REST Example: EMV Chip (Contactless) with a Signature

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
- Authorization with an SCA Exemption
  - Required Fields for Processing Basic Authorizations Using the REST API
  - REST Example: Authorization with an SCA Exemption for Low Value Transactions

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 | GPX

Capturing an Authorization Using
REST
APIs

To capture an authorization:

Pass the original authorization ID in the URL, and send the service request to:

ADDITIONAL INFORMATION

https://api.cybersource.com/v2/payments/{id}/captures

Where

id

is is the authorization ID. The authorization ID is passed in the authorization response as

id

.

{
  "id": "6481692924466004003001"
}

The URL with the

id

value is included in the authorization response:

{
  "_links": {
    "capture": {
      "method": "POST",
      "href": "/pts/v2/payments/6481692924466004003001/captures"
    }
  }

Check the response message to make sure that the request was successful. A 200-level HTTP response code indicates success. For information about response codes, see Transaction Response Codes.

Back to top