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 Simple Order 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 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 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 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

On This Page

Authorization Service

You can authorize a payment for Samsung Pay using two different types of decryption methods: Cybersource or Merchant. Each decryption method requires a different set of required API fields. In addition, depending on which card type is used, different fields are required for requesting the authorization service.

Processor-Specific Information About Authorizations and Captures
Payment Processor	Authorization and Capture Information
`Streamline`	`Streamline` limits authorization and capture amounts to 11 digits, which is 999999999.99. For Cartes Bancaires, the authorization and capture amount must be 0.99 EUR or more. `Streamline` supports enhanced response codes in authorization response messages. Enhanced response codes provide detailed information about declined transactions. Contact `Streamline` customer support to have this capability enabled for your account.

Back to top