Introduction

This article explains when a Stand-Alone Credit (SAC) permission request is required, when it is not required, and how to apply for permission to perform SAC in Business Center.

SAC is a higher-risk refund method because it is not linked to an original transaction. For that reason, merchants should use a follow-on credit (linked credit) when available and request SAC permissions only when SAC is truly required.

This article applies to merchants who think they may need SAC access and need to determine whether they should request permission through the Support Center.

Note: Cybersource Business Center is also referred to as EBC (Enterprise Business Center). Both terms refer to the same platform.

Important: This article does not provide steps for submitting a refund or credit. It explains when SAC permission is needed and how to request it for Business Center / EBC.

Before You Apply for SAC Permissions

Before submitting a request for Stand-Alone Credit (SAC) permissions, confirm that SAC is actually required.

• If the original transaction occurred within the past 365 days, a follow-on credit (linked credit) may be the preferred option. Because linked credits are tied to the original transaction, they present less risk than SAC.
• If you need access to the full 365-day linked refund window, contact Client Services by phone. Do not request SAC permissions if a linked credit will meet the business need.
• If you plan to issue the credit through the Cybersource API, do not submit an SAC permission request. API-based SAC does not require the same Business Center / EBC enablement process.
• If you use Business Center / EBC and need to issue a credit that is not tied to an original transaction, SAC permission may be required.

What Is Stand-Alone Credit?

Stand-Alone Credit (SAC) is a feature that allows you to issue a credit to a credit, debit, or prepaid card without linking the credit to an original transaction.

Because SAC is unlinked from a prior sale, it carries a higher risk of misuse and potential fraudulent activity than a follow-on credit. For that reason, SAC permissions are reviewed carefully and are not guaranteed for approval.

When SAC Permission Is Required

Whether SAC permission is required depends on how the merchant plans to issue the credit.

Business Center / EBC Users

If you plan to perform SAC in Business Center / EBC, SAC must be enabled on the merchant account before it can be used. Merchants using Business Center / EBC must submit a formal request through the Support Center. Requests are reviewed on a case-by-case basis and approval is not guaranteed.

Cybersource API Users

If you plan to issue the credit through the Cybersource API, do not submit an SAC permission request through the Support Center. API-based SAC does not require the same account-level permission process used for Business Center / EBC.

If you need to issue a refund or credit through the API, refer to Connectivity - How to Issue a Refund or Credit via the Cybersource API.

Using Follow-On Credits as an Alternative

Before requesting SAC permissions, determine whether a follow-on credit (linked credit) can be used instead.

A linked credit is the preferred refund method when it is available because it is tied directly to the original transaction and payment type. Linked credits:

• Can be issued up to 365 days after the settlement of the original transaction
• Reduce opportunities for misuse by maintaining a direct link to the original sale
• Support a more secure refund workflow than SAC

If the original transaction is still within the 365-day linked refund window, request assistance with the linked refund path rather than applying for SAC access.

How to Apply for SAC Permissions (Business Center / EBC Only)

Note: This process applies only to merchants using Business Center / EBC. Merchants using the Cybersource API do not need to complete this process.

Each Merchant Identification Number (MID) requires its own SAC request. Do not submit a single request for multiple MIDs, as these requests will be denied.

1. Sign in to the Support Center.
2. Select Apply for Standalone Credit from the Support Cases drop-down list.
3. Review the legal agreement and click Agree to proceed.
4. Complete the requested information and submit the form.
5. Provide a color copy of your government-issued photo ID after submission.
6. Allow 1–2 business days for the evaluation of your SAC application.

Common Questions

• Do I need to enable SAC on my account before I can use it?

  It depends on how you plan to issue the credit. If you are using Business Center / EBC, SAC must be enabled on the merchant account before use. If you are issuing the credit through the Cybersource API, do not submit an SAC permission request through the Support Center.

• Should I request SAC if the original transaction is less than 365 days old?

  Not necessarily. If the original transaction is still within the 365-day linked refund window, a follow-on credit (linked credit) may be the preferred and lower-risk option. Contact Client Services if you need assistance with the linked refund path.

• Why was my SAC request denied?

  SAC requests are reviewed on a case-by-case basis and are not guaranteed for approval. Common reasons for denial may include submitting a single request for multiple MIDs or not meeting the eligibility criteria during review.

• Can I request SAC for more than one MID at a time?

  No. Each MID requires its own individual SAC request. Requests that include multiple MIDs in a single submission will be denied.

• How long does it take to get a decision on my SAC request?

  Allow 1–2 business days for the evaluation of your SAC application after submission.

• Who is authorized to submit a SAC request?

  Only the Admin on the account may submit a Support Center case requesting SAC enablement.

Additional Resources

• Follow-On Credits (Linked Credits)
• Payments - How to Issue a Refund or Credit in Business Center
• Connectivity - How to Issue a Refund or Credit via the Cybersource API
• How to Open a Support Case