Skip to login Skip to content
Developer Cybersource Logo

Our API

Learn about Cybersource REST APIs, SDKs and sample codes.

API reference

View sample code and API field descriptions. Send requests to the sandbox and see the responses.

Developer guides

View feature-level guides with prerequisite and use-case information for implementing our API

Sample code on [GitHub]

Sample codes published on GitHub for each REST API in 6 popular languages

SDKs on [GitHub]

Client SDKs source code published on GitHub in 6 popular languages

Getting started

Use these developer resources to make your first API call.

 

Hello world

Step by step guide to make first Cybersource REST API call.

 

Common setup questions

Commonly-encountered problems and solutions. 

Testing

Guide with sandbox testing instructions and processor specific testing trigger data.

 

Support

Reach out to our award-winning customer support team, or contact sales directly.

FAQ

Frequently asked questions relating to Cybersource REST APIs and developer center.

Customer service

Payzli is here to support your business with all of your payment processing needs, 24 hours per day, 7 days per week.

Call: 813–565–9999

GitHub

Response (error) codes

Understand all different error codes that Cybersource REST API responds with.

StackOverflow

Sign up

Menu
API Overview
  • Recent Revisions to This Document
  • About This Guide
  • VISA Platform Connect: Specifications and Conditions for Resellers/Partners
  • Introduction to Level II and Level III Processing
    • Level II Data
      • Supported Processors and Card Types: Level II
    • Level III Data
      • Supported Processors and Card Types: Level III
    • Cybersource Level II and Level III Data Processing
    • Relaxed Requirements for Address Data and Expiration Date
    • Using Decimals and Strings
  • Visa Platform Connect
    • Captures with Level II Data
      • Required Fields for Capturing a Payment with Level II Data
      • Optional Fields for Capturing a Payment with Level II Data
      • REST Example: Capturing a Payment with Level II Data
    • Credits with Level II Data
      • Required Fields for Processing a Credit with Level II Data
      • Optional Fields for Processing a Credit with Level II Data
      • REST Example: Processing a Credit with Level II Data
    • Sales with Level II Data
      • Required Fields for Processing a Sale with Level II Data
      • Optional Fields for Processing a Sale with Level II Data
      • REST Example: Processing a Sale with Level II Data
    • Captures with Level III Data
      • Required Fields for Capturing a Payment with Level III Data
      • Optional Fields for Capturing a Payment with Level III Data
      • REST Example: Capturing a Payment with Level III Data
    • Credits with Level III Data
      • Required Fields for Processing a Credit with Level III Data
      • Optional Fields for Processing a Credit with Level III Data
      • REST Example: Processing a Credit with Level III Data
    • Sales with Level III Data
      • Required Fields for Processing a Sale with Level III Data
      • Optional Fields for Processing a Sale with Level III Data
      • REST Example: Processing a Sale with Level III Data
  • Reference Information
    • Product Codes
    • Units of Measure Codes
    • Relaxed Requirements for Address Data and Expiration Date in Payment Transactions
  • Recent Revisions to This Document
  • About This Guide
  • VISA Platform Connect: Specifications and Conditions for Resellers/Partners
  • Introduction to Level II and Level III Processing
    • Level II Data
      • Supported Processors and Card Types: Level II
    • Level III Data
      • Supported Processors and Card Types: Level III
    • Cybersource Level II and Level III Data Processing
    • Relaxed Requirements for Address Data and Expiration Date
    • Using Decimals and Strings
  • Visa Platform Connect
    • Captures with Level II Data
      • Required Fields for Capturing a Payment with Level II Data
      • Optional Fields for Capturing a Payment with Level II Data
      • REST Example: Capturing a Payment with Level II Data
    • Credits with Level II Data
      • Required Fields for Processing a Credit with Level II Data
      • Optional Fields for Processing a Credit with Level II Data
      • REST Example: Processing a Credit with Level II Data
    • Sales with Level II Data
      • Required Fields for Processing a Sale with Level II Data
      • Optional Fields for Processing a Sale with Level II Data
      • REST Example: Processing a Sale with Level II Data
    • Captures with Level III Data
      • Required Fields for Capturing a Payment with Level III Data
      • Optional Fields for Capturing a Payment with Level III Data
      • REST Example: Capturing a Payment with Level III Data
    • Credits with Level III Data
      • Required Fields for Processing a Credit with Level III Data
      • Optional Fields for Processing a Credit with Level III Data
      • REST Example: Processing a Credit with Level III Data
    • Sales with Level III Data
      • Required Fields for Processing a Sale with Level III Data
      • Optional Fields for Processing a Sale with Level III Data
      • REST Example: Processing a Sale with Level III Data
  • Reference Information
    • Product Codes
    • Units of Measure Codes
    • Relaxed Requirements for Address Data and Expiration Date in Payment Transactions
On This Page

Required Fields for Processing a Credit with Level III Data

Use these required fields to process a credit that includes Level III data.
orderInformation.amountDetails.currency
orderInformation.amountDetails.nationalTaxIncluded
Set to
1
if the sum of all
orderInformation.lineItems[].taxDetails[].amount
values >
0
.
orderInformation.amountDetails.totalAmount
orderInformation.billTo.address1
orderInformation.billTo.administrativeArea
orderInformation.billTo.country
orderInformation.billTo.email
orderInformation.billTo.firstName
orderInformation.billTo.lastName
orderInformation.billTo.locality
orderInformation.billTo.postalCode
orderInformation.invoiceDetails.purchaseOrderNumber
Required for purchase/procurement cards only.
orderInformation.invoiceDetails.taxable
Required if the sum of all
orderInformation.lineItems[].taxAmount
values >
0
.
orderInformation.lineItems[].taxAmount
paymentInformation.card.expirationMonth
paymentInformation.card.expirationYear
paymentInformation.card.number
processingInformation.purchaseLevel
Set field to
3
.

Related Information

  • API field reference guide for the REST API
Previous topic
Next topic
Back to top

Privacy

Terms + conditions

© 2021 Cybersource. All rights reserved. All brand names and logos are the property of their respective owners, are used for identification purposes only, and do not imply product endorsement or affiliation with Cybersource.