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 American Express Using Cybersource Decryption Method
    - Required Fields for Authorizing a Payment Using American Express and the Cybersource Decryption Method
    - Authorizing a Payment
    - Example: Cybersource Decryption with American Express Using the REST API
  - 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 REST 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 REST 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 REST API
  - Authorizing a Payment with American Express Using Merchant Decryption Method
    - Required Fields for Authorizing a Payment Using American Express and the Merchant Decryption Method
    - Authorizing a Payment
    - Example: Merchant Decryption with American Express Using the REST 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 REST 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 REST 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 REST API
- Authorization Reversal Service
  - Required Fields for Reversing an Authorization
  - Reversing an Authorization
  - Example: Basic Credit Card Authorization Reversal Using the REST API
- Capture Service
  - Required Fields for Capturing a Payment
  - Capturing a Payment
  - Example: Basic Credit Card Capture Using the REST API
- Sale Service
  - Required Fields for Performing a Sale
  - Authorizing and Capturing a Payment
  - Example: Basic Credit Card Sale Using the REST API

On This Page

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
`OmniPay Direct`	You are responsible for complying with the processor’s specific requirements for full authorization reversals. Contact the processor for more information. Card types supported for full authorization reversals: Bank of America Merchant Services: Visa, Mastercard, Maestro (UK Domestic), and Maestro (International). Cardnet International: Visa, Mastercard, Maestro (UK Domestic), and Maestro (International). First Data Merchant Solutions (Europe): Visa, Mastercard, Discover, Diners Club, Maestro (UK Domestic), and Maestro (International). Global Payments International Acquiring: Visa, Mastercard, Maestro (UK Domestic), and Maestro (International). On Cardnet International, enhanced authorization reversals are supported; therefore, extra data is included in the authorization reversal request. It is not necessary to process or monitor the extra data.

Back to top