developer.smartpayfuse.barclaycard Open in urlscan Pro
198.241.207.250  Public Scan

Form analysis
2 forms found in the DOM

GET /search.html

<form class="search-form" role="search" method="get" action="/search.html">
  <input class="search-bar" minlength="3" type="text" name="q" autocomplete="off" placeholder="Search Cybersource Developer" aria-label="Search through site content">
  <button type="submit" id="submit-search" class="submit-search">Search</button>
</form>

GET /search.html

<form role="search" class="search-form-mobile" method="get" action="/search.html">
  <input class="search-bar" minlength="3" type="text" name="q" autocomplete="off" placeholder="Search Cybersource Developer" aria-label="Search through site content">
  <button type="submit" id="submit-search-mobile" class="submit-search">Search</button>
</form>

Text Content

Skip to login Skip to content
Developer Cybersource Logo
MENU
Search

 * API
   
   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

 * Hello world
   
   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
   
   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.
   
   Sales help
   
   Learn more about how our services can help your business.
   
    
   
   GitHub
   
   Response (error) codes
   
   Understand all different error codes that Cybersource REST API responds with.
   
   StackOverflow

 * Contact us
   
   

Search

Sign up



Search
Search
Menu
 * Recent Revisions to This Document

 * About This Guide

 * Introduction to Payments
   * Financial Institutions and Payment Networks
   * Card Types
   * Transaction Types
   * Payment Services
   * Payment Features

 * Standard Payments Processing
   * Basic Authorizations
   * Authorizations with Line Items
   * Authorizations with Payment Network Tokens
   * Authorizations with a Card Verification Number
   * Authorizations with the Service
   * Authorizations with Strong Customer Authentication Exemption
   * Zero Amount Authorizations
   * payments-processing-basic-auth-reversal-intro
   * Captures
   * Multiple Captures
   * Refunds
   * Credits
   * Sales
   * Voids

 * Debit and Prepaid Card Processing
   * Processing Debit and Prepaid Authorizations
   * Enabling Debit and Prepaid Partial Authorizations
   * Disabling Debit and Prepaid Partial Authorizations

 * Level II Processing
   * Captures with Level II Data
   * Credits with Level II Data
   * Sales with Level II Data

 * Level III Processing
   * Captures with Level III Data
   * Credits with Level III Data
   * Sales with Level III Data

 * Mastercard Payment of Winnings Processing
   * Required Fields for Processing a Mastercard Payment of Winnings
   * REST Example: Processing a Mastercard Payment of Winnings

 * Payer Authentication Processing
   * Providing Payer Authentication Information for Authorization
   * Discover/Diner ProtectBuy
   * Mastercard Identity Check
   * Visa Secure

 * Processing Payments Using Credentials
   * Customer-Initiated Transactions with Credentials on File
   * Merchant-Initiated Delayed Transaction
   * Merchant-Initiated Incremental Transaction
   * Merchant-Initiated No-Show Transactions
   * Merchant-Initiated Reauthorization Transactions
   * Merchant-Initiated Resubmission Transaction
   * Recurring Payments
   * Mastercard Standing Order Payments
   * Mastercard Subscription Payments
   * Unscheduled COF Payments

 * Token Management Service Processing
   * Authorize a Payment with a Customer Token
   * Authorize a Payment with a Non-Default Shipping Address
   * Authorize a Payment with Non-Default Payment Instrument
   * Authorize a Payment with a Payment Instrument
   * Authorize a Payment with an Instrument Identifier
   * Authorize a Payment with Legacy Token
   * Make a Credit with a Customer Token
   * Make a Credit with Non-Default Payment Instrument
   * Make a Credit with a Payment Instrument
   * Make a Credit with an Instrument Identifier
   * Make a Credit with Legacy Token

ABOUT THIS GUIDE

 * Recent Revisions to This Document

 * About This Guide

 * Introduction to Payments
   * Financial Institutions and Payment Networks
     * Merchant Financial Institutions (Acquirers)
     * Issuing (Customer) Financial Institutions
     * Payment Networks
     * Payment Processors
   * Card Types
     * Co-Branded Cards
     * Credit Cards
     * Debit Cards
     * Prepaid Cards
     * Private Label Cards
   * Transaction Types
     * Card-Not-Present Transactions
     * Card-Present Transactions
     * Authorizations with Card Verification Numbers
       * CVN Locations and Terminology
     * Token Management Service
   * Payment Services
     * Authorizations
       * Micropayment Authorizations
       * Online Authorizations
       * Offline Authorizations
       * Incremental Authorizations
         * Example: Incremental Authorization
       * Payment Network Token Authorizations
       * Authorization Workflow
     * payments-intro-processing-reversal
     * Captures
       * Capture Workflow
     * Credits
       * Credit Workflow
     * Capture or Credit Voids
     * Sales
       * Dual Message Processing
         * Partial Authorizations
       * Single Message Processing
   * Payment Features
     * cp-services-auth-intro
     * Debit and Prepaid Card Payments
     * Level II and Level III Data
     * Mastercard Payment of Winnings Stand-Alone Credits
     * Payer Authentication
     * Stored Credentials
     * Token Management Service

 * Standard Payments Processing
   * Basic Authorizations
     * Declined Authorizations
     * Required Fields for Processing a Basic Authorization
     * REST Interactive Example: Processing a Basic Authorization
     * REST Example: Processing a Basic Authorization
   * Authorizations with Line Items
     * Required Fields for Processing an Authorization with Line Items
     * REST Example: Processing an Authorization with Line Items
   * Authorizations with Payment Network Tokens
     * Supported Processors and Card Types
     * Required Fields for Authorizations with Payment Network Tokens
     * Optional Fields for Authorizations with Payment Network Tokens
     * REST Example: Authorizations with Payment Network Tokens
   * Authorizations with a Card Verification Number
     * Required Fields for Processing an Authorization with a Card Verification
       Number
     * Optional Fields for Processing an Authorization with a Card Verification
       Number
     * REST Example: Processing an Authorization with a Card Verification Number
   * Authorizations with the Service
     * Required Fields for Processing Authorizations Using the REST API
     * REST Example: Processing a Authorization
   * Authorizations with Strong Customer Authentication Exemption
     * Required Fields for Processing an Authorization with an SCA Exemption
     * REST Example: Processing an Authorization with an SCA Exemption for
       Low-Value Transactions
   * Zero Amount Authorizations
     * Required Fields for Processing a Zero Amount Authorization
     * REST Example: Processing a Zero Amount Authorization
   * payments-processing-basic-auth-reversal-intro
     * Required Fields for Processing an Authorization Reversal
     * REST Example: Processing an Authorization Reversal
   * Captures
     * Required Fields for Capturing an Authorization
     * REST Example: Capturing an Authorization
   * Multiple Captures
     * Required Fields for Processing Multiple Captures
     * REST Example: Processing Multiple Partial Captures
   * Refunds
     * Required Fields for Processing a Refund
     * REST Interactive Example: Processing a Refund
     * REST Example: Processing a Refund
   * Credits
     * Required Fields for Processing a Credit
     * REST Interactive Example: Processing a Credit
     * REST Example: Processing a Credit
   * Sales
     * Required Fields for Processing a Sale
     * REST Example: Processing a Sale
   * Voids
     * Required Fields for Processing a Void
     * REST Example: Processing a Void

 * Debit and Prepaid Card Processing
   * Processing Debit and Prepaid Authorizations
     * Required Fields for Processing Debit and Prepaid Authorizations
       * payments-debit-prepaid-auth-required-country
     * Optional Field for Processing Debit and Prepaid Authorizations
     * REST Example: Processing Debit and Prepaid Authorizations
   * Enabling Debit and Prepaid Partial Authorizations
     * Required Fields for Enabling Debit and Prepaid Partial Authorizations
     * Optional Field for Enabling Debit and Prepaid Partial Authorizations
     * REST Example: Enabling Debit and Prepaid Partial Authorizations
   * Disabling Debit and Prepaid Partial Authorizations
     * Required Field for Disabling Debit and Prepaid Partial Authorizations
     * Optional Field for Disabling Debit and Prepaid Partial Authorizations
     * REST Example: Disabling Debit and Prepaid Partial Authorizations

 * Level II Processing
   * 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

 * Level III Processing
   * 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

 * Mastercard Payment of Winnings Processing
   * Required Fields for Processing a Mastercard Payment of Winnings
   * REST Example: Processing a Mastercard Payment of Winnings

 * Payer Authentication Processing
   * Providing Payer Authentication Information for Authorization
   * Discover/Diner ProtectBuy
     * Required Fields for Processing an Authorization Using Discover ProtectBuy
       Authentication
     * REST Example: Processing an Authorization Using Discover ProtectBuy
       Authentication
   * Mastercard Identity Check
     * Required Fields for Processing an Authorization Using Mastercard Identity
       Check
     * REST Example: Processing an Authorization Using Mastercard Identity Check
   * Visa Secure
     * Required Fields for Processing an Authorization Using Visa Secure
     * REST Example: Processing an Authorization Using Visa Secure

 * Processing Payments Using Credentials
   * Customer-Initiated Transactions with Credentials on File
     * Storing Customer Credentials with a Customer-Initiated Transaction
       * Required Fields for Storing Customer Credentials During a
         Customer-Initiated Transaction
       * REST Example: Storing Customer Credentials During a Customer-Initiated
         Transaction
     * Using Stored Customer Credentials During a Customer-Initiated Transaction
       * Required Fields for Retrieving Customer Credentials During a
         Customer-Initiated Transaction
         * Card-Specific Required Field for Retrieving Customer Credentials
           During a Customer-Initiated Transaction
       * REST Example: Retrieving Customer Credentials During a
         Customer-Initiated Transaction
   * Merchant-Initiated Delayed Transaction
     * Required Fields for Processing a Merchant-Initiated Delayed Transaction
       * Card-Specific Required Field for Processing a Merchant-Initiated
         Transactions
     * REST Example: Processing a Merchant-Initiated Delayed Authorization
       Transaction
   * Merchant-Initiated Incremental Transaction
     * Required Fields for Processing Merchant-Initiated Incremental
       Transactions
       * Card-Specific Required Field for Processing a Merchant-Initiated
         Transactions
     * REST Example: Processing Merchant-Initiated Incremental Transactions
   * Merchant-Initiated No-Show Transactions
     * Required Fields for Processing Merchant-Initiated No-Show Charges
       * Card-Specific Required Field for Processing a Merchant-Initiated
         Transactions
     * Optional Field for Processing Merchant-Initiated No-Show Charges
     * REST Example: Processing Merchant-Initiated No-Show Transactions
   * Merchant-Initiated Reauthorization Transactions
     * Required Fields for Processing Merchant-Initiated Reauthorized
       Transactions
       * Card-Specific Required Field for Processing a Merchant-Initiated
         Transactions
     * REST Example: Processing a Merchant-Initiated Reauthorized Transaction
   * Merchant-Initiated Resubmission Transaction
     * Required Fields for Processing a Merchant-Initiated Resubmitted
       Transaction
       * Card-Specific Required Field for Processing a Merchant-Initiated
         Transactions
     * REST Example: Processing a Merchant-Initiated Resubmitted Transaction
   * Recurring Payments
     * Recurring Billing for Recurring Payments
     * Initial CIT Recurring Payment with a PAN
       * Required Fields for Authorizing Initial Recurring Payments Using REST
         API
       * REST Example: Authorizing an Initial CIT Recurring Payment with a PAN
     * Initial CIT Recurring Payment with an Instrument Identifier
       * Required Fields for Authorizing Initial Recurring Payments with an
         Instrument Identifier
       * REST Example: Authorizing an Initial Recurring Payment with an
         Instrument Identifier
     * Initial CIT Recurring Payment with a Customer ID
       * Required Fields for Authorizing Initial Recurring Payments with a
         Customer ID
       * REST Example: Authorizing an Initial Recurring Payments with a Customer
         ID
     * Subsequent MIT Recurring Payments
       * Required Fields for Authorizing Subsequent Recurring Payments
         * Card-Specific Required Fields for Authorizing Subsequent Recurring
           Payments
         * credentials-mit-common-intro-country
       * REST Example: Authorizing Subsequent Recurring Payments
     * Subsequent MIT Recurring Payments with an Instrument Identifier
       * Required Fields for Authorizing Subsequent Recurring Payments with
         Instrument Identifier
         * Card-Specific Required Fields for Authorizing Subsequent Recurring
           Payments
       * REST Example: Authorizing Subsequent Recurring Payments with an
         Instrument Identifier
     * Subsequent MIT Recurring Payments with a Customer ID
       * Required Fields for Authorizing Subsequent Recurring Payments with a
         Customer ID
         * Card-Specific Required Fields for Authorizing Subsequent Recurring
           Payments
       * REST Example: Authorizing Subsequent Recurring Payments with a Customer
         ID
   * Mastercard Standing Order Payments
     * Mastercard Initial CIT Standing Order Payment
       * Required Fields for Authorizing Initial CIT Standing Order Payments
       * REST Example: Authorizing Initial CIT Standing Order Payments
   * Mastercard Subscription Payments
     * Mastercard CIT Initial Subscription Payment
       * Required Fields for Authorizing CIT Initial Subscription Payments
       * REST Example: Authorizing Initial CIT Subscription Payments
   * Unscheduled COF Payments
     * Initial CIT Unscheduled COF Payment
       * Required Fields for Authorizing Initial CIT Unscheduled COF Payments
       * REST Example: Authorizing Initial CIT Unscheduled COF Payments
     * Subsequent MIT Unscheduled COF Payments
       * Required Fields for Authorizing Subsequent MIT Unscheduled COF Payments
         * Card-Specific Required Field for Processing a Merchant-Initiated
           Transactions
         * credentials-mit-common-intro-country
       * credentials-mit-unsched-optfields
       * REST Example: Authorizing Subsequent MIT Unscheduled COF Payments

 * Token Management Service Processing
   * Authorize a Payment with a Customer Token
     * Required Fields for Authorizing a Payment with a Customer Token
     * REST Example: Authorizing a Payment with a Customer Token
     * REST Example: Authorizing a Payment Using a Customer Token Linked to a
       Network Token
   * Authorize a Payment with a Non-Default Shipping Address
     * Required Fields for Authorizing a Payment with a Non-Default Shipping
       Address
     * REST Example: Authorizing a Payment with a Non-Default Shipping Address
   * Authorize a Payment with Non-Default Payment Instrument
     * Required Fields for Authorizing a Payment with Non-Default Payment
       Instrument
     * Optional Fields for Authorizing a Payment with Non-Default Payment
       Instrument
     * REST Example: Authorizing a Payment with Non-Default Payment Instrument
   * Authorize a Payment with a Payment Instrument
     * Required Fields for Authorizing a Payment with a Payment Instrument
     * Optional Fields for Authorizing a Payment with a Payment Instrument
     * REST Example: Authorizing a Payment with a Payment Instrument
   * Authorize a Payment with an Instrument Identifier
     * Required Fields for Authorizing a Payment with an Instrument Identifier
     * REST Example: Authorizing a Payment with an Instrument Identifier
   * Authorize a Payment with Legacy Token
     * Required Fields for Authorizing a Payment with Legacy Token
     * REST Example: Authorizing a Payment with Legacy Token
   * Make a Credit with a Customer Token
     * Required Fields for Making a Credit with a Customer Token
     * REST Example: Making a Credit with a Customer Token
   * Make a Credit with Non-Default Payment Instrument
     * Required Fields for Making a Credit with Non-Default Payment Instrument
     * Optional Fields for Making a Credit with Non-Default Payment Instrument
     * REST Example: Making a Credit with Non-Default Payment Instrument
   * Make a Credit with a Payment Instrument
     * Required Fields for Making a Credit with a Payment Instrument
     * REST Example: Making a Credit with a Payment Instrument
   * Make a Credit with an Instrument Identifier
     * Required Fields for Making a Credit with an Instrument Identifier
     * REST Example: Making a Credit with an Instrument Identifier
   * Make a Credit with Legacy Token
     * Required Fields for Making a Credit with Legacy Token
     * REST Example: Making a Credit with Legacy Token

On This Page
 * Audience and Purpose

 * Conventions

 * Customer Support

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
Barclays
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 special statements are used 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.
CUSTOMER SUPPORT

For support information about any service, visit the Support Center:
https://www.barclaycard.co.uk/business/forms/bps-sme?Area=BOC

Back to top

Privacy



© 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.