Authorizations: Cybersource Decryption

You can authorize a payment for Samsung Pay using two different types of decryption methods: 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.

Supported processors (14)

American Express Direct, Barclays, Chase Paymentech Solutions, Elavon, Elavon Americas, FDC Compass, FDC Nashville Global, GPN, HSBC, JCN Gateway, OmniPay Direct, Streamline, TSYS Acquiring Solutions, Visa Platform Connect

Supported processors: Chase Paymentech Solutions, Elavon Americas, FDC Nashville Global, Streamline, Visa Platform Connect

Supported processors: TSYS Acquiring Solutions, Visa Platform Connect

Supported processors: Barclays

Supported processors: GPX

Supported processors: Visa Platform Connect

Endpoints

POST /pts/v2/payments

Processor-Specific Authorization and Capture Information

This table describes processor-specific authorization and capture behavior:

Processor	Description
American Express Direct	For USD, American Express Direct limits authorization and capture amounts to 9,999,999.00. For other currencies, the maximum amount depends on the currency. Contact American Express for the maximum amounts for the currencies that you are using. Regardless of exponent or currency, the maximum number of digits for the amount value is 12 digits.
Barclays	The amount is rounded to the correct number of decimal places for the currency. Barclays does not support amounts of 0.01. Barclays supports zero amount authorizations and amounts greater than 0.01. Barclays supports enhanced response codes in authorization response messages. Enhanced response codes provide detailed information about declined transactions. Contact Barclays customer support to have this capability enabled for your account.
Elavon	Elavon limits authorization and capture amounts to 999999999999 (twelve 9s).
FDC Nashville Global	Merchant descriptor information is always provided to the processor for all capture and credit transactions.
GPN	Amounts for authorizations, captures, and credits are limited to 10 digits.
HSBC	The amount is rounded to the correct number of decimal places for the currency. HSBC supports enhanced response codes in authorization response messages. Enhanced response codes provide detailed information about declined transactions. Contact HSBC customer support to have this capability enabled for your account.
JCN Gateway	Amounts for authorizations and captures are limited to 8 digits.
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.
TSYS Acquiring Solutions	TSYS Acquiring Solutions limits authorization and capture amounts to the equivalent of 99,999.99 USD. To process an amount greater than this, contact TSYS Acquiring Solutions.
Visa Platform Connect	Visa Platform Connect limits authorization and capture amounts to 999999999999 (twelve 9s).

Processor-Specific Authorization and Capture Information

This table describes processor-specific authorization and capture behavior:

Processor	Description
FDC Nashville Global	Merchant descriptor information is always provided to the processor for all capture and credit transactions.
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.
Visa Platform Connect	Visa Platform Connect limits authorization and capture amounts to 999999999999 (twelve 9s).

Processor-Specific Authorization and Capture Information

This table describes processor-specific authorization and capture behavior:

Processor	Description
TSYS Acquiring Solutions	TSYS Acquiring Solutions limits authorization and capture amounts to the equivalent of 99,999.99 USD. To process an amount greater than this, contact TSYS Acquiring Solutions.
Visa Platform Connect	Visa Platform Connect limits authorization and capture amounts to 999999999999 (twelve 9s).

Processor-Specific Authorization and Capture Information

This table describes processor-specific authorization and capture behavior:

Processor	Description
Barclays	The amount is rounded to the correct number of decimal places for the currency. Barclays does not support amounts of 0.01. Barclays supports zero amount authorizations and amounts greater than 0.01. Barclays supports enhanced response codes in authorization response messages. Enhanced response codes provide detailed information about declined transactions. Contact Barclays customer support to have this capability enabled for your account.

Processor

Description

Barclays

The amount is rounded to the correct number of decimal places for the currency. Barclays does not support amounts of 0.01. Barclays supports zero amount authorizations and amounts greater than 0.01. Barclays supports enhanced response codes in authorization response messages. Enhanced response codes provide detailed information about declined transactions. Contact Barclays customer support to have this capability enabled for your account.

Processor-Specific Authorization and Capture Information

This table describes processor-specific authorization and capture behavior:

Processor	Description
Visa Platform Connect	Visa Platform Connect limits authorization and capture amounts to 999999999999 (twelve 9s).

American Express

Example

{    "clientReferenceInformation": {        "code": "demorefnum"    },    "processingInformation": {        "paymentSolution": "008",        "commerceIndicator": "aesk"    },    "paymentInformation": {        "tokenizedCard": {            "transactionType": "1",            "type": "003"        }    },    "fluidData": {      "descriptor": "ABCDEFabcdefABCDEFabcdef0987654321234567",      "value": "RklEPUNPTU1PTi5TQU1TVU5HLklOQVBQLlBBWU1FTlQ="    },    "billTo": {        "firstName": "James",        "lastName": "Smith",        "address1": "111 S. Division St.",        "address2": "Suite 123",        "locality": "Ann Arbor",        "administrativeArea": "MI",        "postalCode": "48104-2201",        "country": "US",        "email": "[email protected]",        "phoneNumber": "9999999999"    },    "orderInformation": {        "amountDetails": {            "currency": "USD",            "totalAmount": "100.00"        }    }}

{    "clientReferenceInformation": {        "code": "demorefnum"    },    "orderInformation": {        "amountDetails": {            "currency": "USD",            "authorizedAmount": "100.00"        }    },    "paymentInformation": {        "tokenizedCard": {            "prefix": "593056",            "suffix": "0842",            "expirationMonth": "08",            "expirationYear": "2021"        }    },    "processingInformation": {        "reconciliationID": "13209256CGJSMQCZ"    },    "processorInformation": {        "approvalCode": "888888",        "responseCode": "100",        "avs": {            "code": "I1"        }    },    "submitTimeUtc": "2015-11-03T205202Z"}

These fields are required when submitting an authorization request using the decryption method and an American Express card:

Field	Type	Description
`descriptor`		Set this field under the `fluidData` object to `RklEPUNPTU1PTi5TQU1TVU5HLklOQVBQLlBBWU1FTlQ=`.
`processingInformation.commerceIndicator`		Set this field to `aesk`.
`paymentInformation.fluidData.value`		Set this field to the value that was returned from Samsung Pay in the 3ds.data block: retrieve the payment data from Samsung Pay in `JSON` Web Encryption (JWE) format, encode it in Base64, and add the value to the `paymentInformation.fluidData.value` field.
`paymentInformation.tokenizedCard.transactionType`		Set this field to `1`.
`processingInformation.paymentSolution`		Set this field to `008`.

JCB

Example

{    "processingInformation": {        "paymentSolution": "008"    },    "consumerAuthenticationInformation": {        "cavv": "EHuWW9PiBkWvqE5juRwDzAUFBAk=",        "eciRaw": "05"    },    "paymentInformation": {        "tokenizedCard": {            "number": "xxxx55555555xxxx",            "expirationMonth": "12",            "expirationYear": "2031",            "transactionType": "1",            "type": "007"        }    },    "billTo": {        "firstName": "Jane",        "lastName": "Smith",        "address1": "123 Main Street",        "address2": "Suite 12345",        "locality": "Small Town",        "administrativeArea": "CA",        "postalCode": "98765",        "country": "US",        "email": "[email protected]",        "phoneNumber": "9999999999"    },    "orderInformation": {        "amountDetails": {            "currency": "USD",            "totalAmount": "100.00"        }    }}

{    "clientReferenceInformation": {        "code": "ref123"    },    "orderInformation": {        "amountDetails": {            "currency": "USD",            "authorizedAmount": "100.00"        }    },    "processingInformation": {        "reconciliationID": "15356268CR2XF23X"    },    "processorInformation": {        "approvalCode": "888888",        "responseCode": "100",        "paymentSolution": "008",        "avs": {            "codeRaw": "I1"        }    }}

These fields are required when submitting an authorization request using the decryption method and a JCB card:

Field	Type	Description
`descriptor`		Set this field under the `fluidData` object to `RklEPUNPTU1PTi5TQU1TVU5HLklOQVBQLlBBWU1FTlQ=`.
`paymentInformation.fluidData.value`		Set this field to the Base64-encoded value obtained from the `paymentData` property of the `PKPaymentToken` object.
`processingInformation.paymentSolution`		Set this field to `008`.

Mastercard

Example

{    "clientReferenceInformation": {        "code": "demorefnum"    },    "processingInformation": {        "paymentSolution": "008",        "commerceIndicator": "spa"    },    "paymentInformation": {        "tokenizedCard": {            "transactionType": "1"        }    },    "fluidData": {      "descriptor": "ABCDEFabcdefABCDEFabcdef0987654321234567",      "value": "RklEPUNPTU1PTi5TQU1TVU5HLklOQVBQLlBBWU1FTlQ="    },    "billTo": {        "firstName": "James",        "lastName": "Smith",        "address1": "111 S. Division St.",        "address2": "Suite 123",        "locality": "Ann Arbor",        "administrativeArea": "MI",        "postalCode": "48104-2201",        "country": "US",        "email": "[email protected]",        "phoneNumber": "9999999999"    },    "orderInformation": {        "amountDetails": {            "currency": "USD",            "totalAmount": "100.00"        }    }}

{    "clientReferenceInformation": {        "code": "demorefnum"    },    "orderInformation": {        "amountDetails": {            "currency": "USD",            "authorizedAmount": "100.00"        }    },    "processingInformation": {        "reconciliationID": "13209255CGJSMQCR"    },    "processorInformation": {        "approvalCode": "888888",        "responseCode": "100",        "avs": {            "code": "I1"        }    },    "submitTimeUtc": "2015-11-03T205035Z"}

These fields are required when submitting an authorization request using the decryption method and a Mastercard card:

Field	Type	Description
`descriptor`		Set this field under the `fluidData` object to `RklEPUNPTU1PTi5TQU1TVU5HLklOQVBQLlBBWU1FTlQ=`.
`processingInformation.commerceIndicator`		Set this field to `spa`.
`paymentInformation.tokenizedCard.transactionType`		Set this field to `1`.
`processingInformation.paymentSolution`		Set this field to `008`.

Visa

Example

{    "clientReferenceInformation": {        "code": "demorefnum"    },    "processingInformation": {        "paymentSolution": "008",        "commerceIndicator": "internet"    },    "paymentInformation": {        "tokenizedCard": {            "transactionType": "1"        }    },    "fluidData": {      "descriptor": "ABCDEFabcdefABCDEFabcdef0987654321234567",      "value": "RklEPUNPTU1PTi5TQU1TVU5HLklOQVBQLlBBWU1FTlQ="    },    "billTo": {        "firstName": "James",        "lastName": "Smith",        "address1": "111 S. Division St.",        "address2": "Suite 123",        "locality": "Ann Arbor",        "administrativeArea": "MI",        "postalCode": "48104-2201",        "country": "US",        "email": "[email protected]",        "phoneNumber": "9999999999"    },    "orderInformation": {        "amountDetails": {            "currency": "USD",            "totalAmount": "100.00"        }    }}

{    "clientReferenceInformation": {        "code": "demorefnum"    },    "orderInformation": {        "amountDetails": {            "currency": "USD",            "authorizedAmount": "100.00"        }    },    "paymentInformation": {        "tokenizedCard": {            "prefix": "294672",            "suffix": "4397",            "expirationMonth": "08"        }    },    "processingInformation": {        "reconciliationID": "13209254CGJSMQCQ"    },    "processorInformation": {        "approvalCode": "888888",        "responseCode": "100",        "avs": {            "code": "I1"        }    }}

These fields are required when submitting an authorization request using the decryption method and a Visa card:

Field	Type	Description
`descriptor`		Set this field under the `fluidData` object to `RklEPUNPTU1PTi5TQU1TVU5HLklOQVBQLlBBWU1FTlQ=`.
`processingInformation.commerceIndicator`		Set this field to `internet`.
`paymentInformation.tokenizedCard.transactionType`		Set this field to `1`.
`processingInformation.paymentSolution`		Set this field to `008`.

Was this page helpful?

Last published: September 29, 2026