Introduction

Merchants who are integrated with the Cybersource API can submit refund and credit transactions programmatically instead of using Business Center. This option is typically used by merchants with an existing API integration who need to process credits through their own systems.

If a linked refund is no longer available, a Stand-Alone Credit (SAC) may be submitted through the API.

Important: If you need to issue a refund or credit directly in Business Center, refer to Support Article: Payments - How to Issue a Refund or Credit in Business Center.

Applicability

• Applies to: Merchants and support teams using the Cybersource API to process refunds or credits
• Use this article for: Determining when to issue a refund or credit through the API
• Does not apply to: Refunds processed directly in Business Center

When to Use the Cybersource API

Use the Cybersource API when the merchant is integrated with Cybersource and wants to submit refund or credit transactions programmatically.

This path may be appropriate when:

• The merchant uses the Cybersource API instead of the Business Center interface
• A refund or credit must be submitted through the merchant's own integrated workflow
• A Stand-Alone Credit (SAC) is needed

Stand-Alone Credits via the Cybersource API

A Stand-Alone Credit (SAC) is a credit transaction that is not linked to a prior sale. This option may be used when a linked refund is no longer available.

For SACs submitted through the Cybersource API:

• No account-level enablement is required.
• The request must include the actual card number (PAN) and expiration date.
• Network tokens and Token Management Service (TMS) tokens cannot be used for SAC submissions.

Required Information

Before submitting a refund or credit through the API, gather the necessary transaction and cardholder information.

For a Stand-Alone Credit, this typically includes:

• Card number
• Expiration date
• Cardholder name
• Billing address
• Email address
• Refund or credit amount
• Currency

Developer Resources

For request structure, required fields, implementation guidance, and sample code, refer to the appropriate developer documentation for your integration method:

• REST: Cybersource Payments Developer Guide (REST)
• SOAP: Standard Payments Processing (SOAP)

Use these resources for endpoint details, required request fields, processing flows, and integration-specific examples.

Additional Guidance

• If the merchant needs to process a refund or credit directly in Business Center, refer to Support Article: Payments - How to Issue a Refund or Credit in Business Center.
• If a linked refund is not available and the merchant is integrated with the Cybersource API, a Stand-Alone Credit may be submitted through the API instead.

Related Resources

• Cybersource Payments Developer Guide (REST)
• Standard Payments Processing (SOAP)
• Payments - How to Issue a Refund or Credit in Business Center