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
  • Payouts Developer Guide
    • Recent Revisions to This Document
  • Introduction to Payouts
    • Overview
      • AFT Types
      • Aggregator Support for Payouts
      • Single Message System Credit Card Processing
    • Supported Sender Card Types
    • Payment Networks
    • Requirement
    • AFT Limitations
  • AFT Transactions
  • Pull Services
    • Pull Funds Transfer Service
      • Pull Funds Transfer Required Fields
      • Pull Funds Transfer Optional Fields
      • REST Example: Pull Funds Transfer
      • REST Example: Pull Funds Transfer with TMS
    • Pull Transfer Reversal Service
      • Pull Funds Transfer Reversal Required Fields
      • Pull Funds Transfer Reversal Optional Fields
      • REST Example: Pull Funds Reversal Transfer
    • Pull Transfer Refund Service
      • Pull Funds Transfer Refund Required Fields
      • Pull Funds Transfer Refund Optional Fields
      • REST Example: Pull Funds Transfer Refund
  • Reference
    • Business Application Identifier
    • Sender Source
    • Visa Direct BAI to Mastercard TTI Mapping
    • Testing the Pull Funds Transfer Service
    • Test Card Numbers
  • Payouts Developer Guide
    • Recent Revisions to This Document
  • Introduction to Payouts
    • Overview
      • AFT Types
      • Aggregator Support for Payouts
      • Single Message System Credit Card Processing
    • Supported Sender Card Types
    • Payment Networks
    • Requirement
    • AFT Limitations
  • AFT Transactions
  • Pull Services
    • Pull Funds Transfer Service
      • Pull Funds Transfer Required Fields
      • Pull Funds Transfer Optional Fields
      • REST Example: Pull Funds Transfer
      • REST Example: Pull Funds Transfer with TMS
    • Pull Transfer Reversal Service
      • Pull Funds Transfer Reversal Required Fields
      • Pull Funds Transfer Reversal Optional Fields
      • REST Example: Pull Funds Reversal Transfer
    • Pull Transfer Refund Service
      • Pull Funds Transfer Refund Required Fields
      • Pull Funds Transfer Refund Optional Fields
      • REST Example: Pull Funds Transfer Refund
  • Reference
    • Business Application Identifier
    • Sender Source
    • Visa Direct BAI to Mastercard TTI Mapping
    • Testing the Pull Funds Transfer Service
    • Test Card Numbers
On This Page

Pull Funds Transfer Refund Optional Fields

These fields are optional in a request for a Pull Funds Transfer refund:
clientReferenceInformation.applicationName
clientReferenceInformation.applicationUser
clientReferenceInformation.applicationVersion
clientReferenceInformation.code
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.