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

Capture Service

The capture service is a follow-on service that uses the request ID returned from the previous authorization. The request ID links the capture to the authorization. This service transfers funds from the customer’s account to your bank and usually takes two to four days to complete.

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