API Overview

Samsung Pay Developer Guide
- Recent Revisions to This Document

Introduction
- Requirements for Using Samsung Pay
- Supported Card Types and Optional Features
- Transaction Endpoints

Getting Started
- Registering with Samsung Pay
- Registering with Cybersource
- Creating a Project
- Integrating the Samsung Pay SDK
- Using the API Key
  - Example: Debug Mode
  - Example: Release Mode
- Verify That Your Application is Eligible for Samsung Pay
  - Example: Samsung Pay Class
- Initiating a Payment
  - Required Fields for Initiating a Payment
  - Example: Transaction Request Structure
- Requesting a Payment
  - Example: Request startSamsungPay() API Method

Services
- Authorization Service
  - Authorizing a Payment with JCB Using Cybersource Decryption Method
    - Required Fields for Authorizing a Payment Using JCB and the Cybersource Decryption Method
    - Authorizing a Payment
    - Example: Cybersource Decryption with JCB Using the Simple Order API
  - Authorizing a Payment with Mastercard Using Cybersource Decryption Method
    - Required Fields for Authorizing a Payment Using Mastercard and the Cybersource Decryption Method
    - Authorizing a Payment
    - Example: Cybersource Decryption with Mastercard Using the Simple Order API
  - Authorizing a Payment with Visa Using Cybersource Decryption Method
    - Required Fields for Authorizing a Payment Using Visa and the Cybersource Decryption Method
    - Authorizing a Payment
    - Example: Cybersource Decryption with Visa Using the Simple Order API
  - Authorizing a Payment with JCB Using Merchant Decryption Method
    - Required Fields for Authorizing a Payment Using JCB and the Merchant Decryption Method
    - Authorizing a Payment
    - Example: Merchant Decryption with JCB Using the Simple Order API
  - Authorizing a Payment with Mastercard Using Merchant Decryption Method
    - Required Fields for Authorizing a Payment Using Mastercard and the Merchant Decryption Method
    - Authorizing a Payment
    - Example: Merchant Decryption with Mastercard Using the Simple Order API
  - Authorizing a Payment with Visa Using Merchant Decryption Method
    - Required Fields for Authorizing a Payment Using Visa and the Merchant Decryption Method
    - Authorizing a Payment
    - Example: Merchant Decryption with Visa Using the Simple Order API
- Authorization Reversal Service
  - Required Fields for Reversing an Authorization
  - Reversing an Authorization
  - XML Example: Basic Credit Card Authorization Reversal Using the Simple Order API
- Capture Service
  - Required Fields for Capturing a Payment
  - Capturing a Payment
  - XML Example: Basic Credit Card Capture Using the Simple Order API
- Sale Service
  - Required Fields for Performing a Sale
  - Authorizing and Capturing a Payment
  - XML Example: Basic Credit Card Sale Using the Simple Order API

Authorization Reversal Service

The authorization reversal service is a follow-on service that uses the request ID returned from the previous authorization. An authorization reversal releases the hold that the authorization placed on the customer’s credit card funds. Use this service to reverse an unnecessary or undesired authorization.

Processor-Specific Information About Authorization Reversals
Payment Processor	Authorization Reversal Information
`FDC Nashville Global`	Card types supported for full authorization reversals: Visa, Mastercard, American Express, Discover, Diners Club, China UnionPay, and JCB (US Domestic). For JCB cards, US Domestic means that the currency is USD and your location is the U.S., Puerto Rico, Guam, U.S. Virgin Islands, or Northern Mariana Islands. For Discover, Diners Club, and JCB (US Domestic), the processor supports full authorization reversals for USD transactions only. The processor does not impose currency restrictions for full authorization reversals for Visa, Mastercard, and American Express.