On This Page

Authorizing a Samsung Pay Digital Wallet Payment without 3-D Secure

The topics in this section show to how to authorize a Samsung Pay digital wallet payment without 3-D Secure authentication:

Basic steps

Required fields

Mastercard example

Common error responses and resolutions

When 3-D Secure is not used, the transaction ID is automatically populated with the cryptogram value

For general information about basic authorizations, see the "Standard Payments Processing" section of the

Payments Developer Guide

Basic Steps to Authorize a Samsung Pay Digital Wallet Payment without 3-D Secure

Follow these steps to request a Samsung Pay payment on a supported card without 3-D Secure authentication:

Create the request message with the required REST API fields.

Use the API fields listed in Required Fields to Authorize a Samsung Pay Digital Wallet Payment without 3-D Secure.

These REST API fields are specific to this request payload:

merchantInformation.merchantDomain

paymentInformation.tokenizedCard.cryptogram

paymentInformation.tokenizedCard.transactionType

processingInformation.commerceIndicator

processingInformation.paymentSolution

Refer to the example Mastercard Example: Authorize a Samsung Pay Digital Wallet Payment without 3-D Secure.

IMPORTANT

The example is based on a Mastercard transaction. For a Diners Club card or a Visa card transaction, set the card-specific value for the

paymentInformation.tokenizedCard.type

field.

Send the message to one of these endpoints:

Production:

POST https://api.cybersource.com/pts/v2/payments

Test:

POST https://apitest.cybersource.com/pts/v2/payments

Verify the response messages to make sure that the request was successful.

ADDITIONAL INFORMATION

A 200-level HTTP response code indicates success. See the

Transaction Response Codes

If the response message contain errors, see Common Error Responses for Transactions without 3-D Secure.

Required Fields to Authorize a Samsung Pay Digital Wallet Payment without 3-D Secure

These REST API fields are required to request authorization of a Samsung Pay Digital Wallet payment without 3-D Secure authentication.

clientReferenceInformation.code
merchantInformation.merchantId
orderInformation.amountDetails.currency
orderInformation.amountDetails.totalAmount
orderInformation.billTo.address1
orderInformation.billTo.administrativeArea
orderInformation.billTo.country
orderInformation.billTo.email
orderInformation.billTo.firstName
orderInformation.billTo.lastName
orderInformation.billTo.locality
orderInformation.billTo.phoneNumber
orderInformation.billTo.postalCode
paymentInformation.tokenizedCard.cryptogram: Set the value to the network token cryptogram from Samsung Pay.
paymentInformation.tokenizedCard.expirationMonth
paymentInformation.tokenizedCard.expirationYear
paymentInformation.tokenizedCard.transactionType: Set the value to
1
for network tokens.
paymentInformation.tokenizedCard.type: Set the value to the card type code. Possible values:
001
for Visa
002
for Mastercard
005
for Diners Club
processingInformation.commerceIndicator: Set the value to
internet
for a Diners Club, Discover, and Visa card for an authorization request without 3-D Secure authentication.
processingInformation.paymentSolution: Set the value to
008
for Samsung Pay digital wallet transactions.

Related Information

API Field Reference for the REST API

Mastercard Example: Authorize a Samsung Pay Digital Wallet Payment without 3-D Secure

Request

{
  "clientReferenceInformation": {
    "code": "MC-NO3DS-SAMSUNGPAY-004"
  },
  "orderInformation": {
    "amountDetails": {
      "totalAmount": "67.50",
      "currency": "EUR"
    },
    "billTo": {
      "firstName": "Hans",
      "lastName": "Mueller",
      "address1": "Alexanderplatz 1",
      "locality": "Berlin",
      "postalCode": "10178",
      "country": "DE",
      "email": "hans.mueller@example.de",
      "phoneNumber": "+49-30-12345678"
    }
  },
  "paymentInformation": {
    "tokenizedCard": {
      "cryptogram": "CwABBJQ0AgAAAAAgJDUCAAAAAAA=",
      "transactionType": "1",
      "expirationMonth": "04",
      "expirationYear": "2028",
      "type": "002"
    }
  },
  "processingInformation": {
    "paymentSolution": "008",
    "commerceIndicator": "internet"
  },
  "merchantInformation": {
    "merchantId": "demo_merchant_12345"
  }
}

Common Error Responses for Transactions without 3-D Secure

This topic lists common error responses to transaction requests without 3-D Secure authentication.

3DS ECI provided for non-3DS transaction: Cause: Invalid e-commerce indicator for a transaction that does not use 3-D Secure.; Resolution: Make sure the
processingInformation.commerceIndicator
field is set to
internet
to indicate a transaction without 3-D Secure authentication. You could also omit the field from your request and let the gateway assign the value.
Authentication data present in non-3DS transaction: Cause: Conflicting authentication data.; Resolution: Remove the cardholder authentication data, which is used for transactions with 3-D Secure:
Remove the
consumerAuthenticationInformation. cavv
field (for Diners Club or Visa cards).
Remove the
consumerAuthenticationInformation. ucafAuthenticationData
field (for Mastercard only).
Digital wallet transaction missing required cryptogram: Cause: Missing or invalid cryptogram.; Resolution: Make sure the
paymentInformation.tokenizedCard.cryptogram
field is populated with the correct value.