Payments Developer Guide

This section describes how to use this guide and where to find further information.
Audience and Purpose
This guide is written for application developers who want to use the
REST API
to integrate payment card processing into an order management system.
Implementing the
Cybersource
payment services requires software development skills. You must write code that uses the API request and response fields to integrate the credit card services into your existing order management system.
Conventions
These statements appear in this document:
IMPORTANT
An
Important
statement contains information essential to successfully completing a task or learning a concept.
WARNING
A
Warning
contains information or instructions, which, if not heeded, can result in a security risk, irreversible loss of data, or significant cost in time or revenue or both.
Related Documentation
Visit the
Cybersource
documentation hub
to find additional processor-specific versions of this guide and additional technical documentation.
Customer Support
For support information about any service, visit the Support Center:

Recent Revisions to This Document

24.08

This revision contains only editorial changes and no technical updates.

24.07

Pre-Authorizations
Added pre-authorization processing. See Pre-Authorizations.
Meeza Cards
Added Meeza as a supported card type for
Visa Platform Connect
.
Multiple Partial Captures
Updated the multiple partial capture required fields to include the
processingInformation.captureOptions.captureSequenceNumber
and
processingInformation.captureOptions.totalCaptureCount
fields for all countries.

24.06

Credit Authorizations on
Refunds
Added credit authorization information to Refunds.
Credit Authorizations on
Credits
Added credit authorization information to Credits.
Multiple Partial Captures
Updated how to set the
processingInformation.captureOptions.totalCaptureCount
field. See Multiple Partial Captures.

24.05

Incremental Authorizations
Credentials
Added support for Mastercard Standing Order Transactions and Subscription Transactions using the
Token Management Service
(
TMS
). See:

24.04

Relaxed Requirements for Address Data and Expiration Date

24.03

Timeout Authorization Reversals
Added an important note about the wait time before requesting a timeout authorization reversal. See Timeout Authorization Reversals.
Added an important note about the wait time before requesting a timeout authorization reversal. See Timeout Authorization Reversals.
Token-Based Processing
Added support for authorizing a payment ignoring a network token. See Authorize a Payment While Ignoring Network Token.

24.02

Refunds
The time limit for
refunds
has been updated. See these topics:

24.01

Processing Payments Using Credentials
Updated the Mastercard Standing Order Payments and the Mastercard Subscription Payments to include
TMS
information. See Mastercard Standing Order Payments and Mastercard Subscription Payments.
Timeout Reversals
Added timeout authorization reversals. See Timeout Authorization Reversals.
Timeout Voids

23.10

This revision contains only editorial changes and no technical updates.

23.09

Authorizations with Strong Customer Authentication Exemption

23.07

Added notes about merchants in India not being permitted to store PANs. For details, see Authorizations with Payment Network Tokens.

VISA Platform Connect: Specifications and Conditions for Resellers/Partners

The following are specifications and conditions that apply to a Reseller/Partner enabling its merchants through
Cybersource for Visa Platform Connect (“VPC”) processing
. Failure to meet any of the specifications and conditions below is subject to the liability provisions and indemnification obligations under Reseller/Partner’s contract with Visa/Cybersource.
  1. Before boarding merchants for payment processing on a VPC acquirer’s connection, Reseller/Partner and the VPC acquirer must have a contract or other legal agreement that permits Reseller/Partner to enable its merchants to process payments with the acquirer through the dedicated VPC connection and/or traditional connection with such VPC acquirer.
  2. Reseller/Partner is responsible for boarding and enabling its merchants in accordance with the terms of the contract or other legal agreement with the relevant VPC acquirer.
  3. Reseller/Partner acknowledges and agrees that all considerations and fees associated with chargebacks, interchange downgrades, settlement issues, funding delays, and other processing related activities are strictly between Reseller and the relevant VPC acquirer.
  4. Reseller/Partner acknowledges and agrees that the relevant VPC acquirer is responsible for payment processing issues, including but not limited to, transaction declines by network/issuer, decline rates, and interchange qualification, as may be agreed to or outlined in the contract or other legal agreement between Reseller/Partner and such VPC acquirer.
DISCLAIMER: NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE OR LIABLE FOR ANY ERRORS OR OMISSIONS BY THE VISA PLATFORM CONNECT ACQUIRER IN PROCESSING TRANSACTIONS. NEITHER VISA NOR CYBERSOURCE WILL BE RESPONSIBLE OR LIABLE FOR RESELLER/PARTNER BOARDING MERCHANTS OR ENABLING MERCHANT PROCESSING IN VIOLATION OF THE TERMS AND CONDITIONS IMPOSED BY THE RELEVANT VISA PLATFORM CONNECT ACQUIRER.