API Overview

Samsung Pay Developer Guide
- Recent Revisions to This Document
- VISA Platform Connect: Specifications and Conditions for Resellers/Partners

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

Getting Started
- Registering with Samsung Pay
- Registering with National Australia Bank
- 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 National Australia Bank Decryption Method
    - Required Fields for Authorizing a Payment Using JCB and the National Australia Bank Decryption Method
    - Authorizing a Payment
    - Example: National Australia Bank Decryption with JCB Using the REST API
  - Authorizing a Payment with Mastercard Using National Australia Bank Decryption Method
    - Required Fields for Authorizing a Payment Using Mastercard and the National Australia Bank Decryption Method
    - Authorizing a Payment
    - Example: National Australia Bank Decryption with Mastercard Using the REST API
  - Authorizing a Payment with Visa Using National Australia Bank Decryption Method
    - Required Fields for Authorizing a Payment Using Visa and the National Australia Bank Decryption Method
    - Authorizing a Payment
    - Example: National Australia Bank Decryption with Visa 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

Recent Revisions to This Document

24.02

This revision contains only editorial changes and no technical updates.

24.01

This revision contains only editorial changes and no technical updates.

23.01

Removed American Express and Discover as supported card types.

22.03

Removed

deviceInformation

fields from REST API sales request code examples.

Removed

paymentInformation.tokenizedCard.requestorId

field from list of required fields and code examples for authorizations.

22.02

Deprecated PNT assurance fields replaced with new fields: For VDC National Australia Bank Ltd only, the deprecated API request and response fields
paymentInformation.tokenizedCard.assuranceLevel
are replaced with the new fields named
paymentInformation.tokenizedCard.assuranceMethod
.

Back to top