Skip to main content

Parameter Definition

By using the config object with this input data in the SDK integration, an accurate and complete flow of information is ensured, allowing to efficiently interact with the functionalities and services provided by the SDK. It is important to follow the specific guidelines and recommendations provided by the SDK documentation to ensure correct use of this input data.

  1. Input data: The config object is composed of the following attributes:
config
Object
required

Object of Configuration, contain the other objects (order, token, billing, …)

  1. Output data:
code
String
required

Authorization response code

Length (min - max): 2 - 3
Example:00
message
String
required

Authorization response message, according to the language

Length (min - max): 5 - 30
Example:Ok
messageUser
String
required

Friendly message for the user, according to the language

Length (min - max): 5 - 50
Example:Ok
messageUserEng
String
required

Friendly message for the user in English

Length (min - max): 5 - 50
Example:Ok
response
Object
required

Response data object

payloadHttp
String
required

Original response message used for signature generation.

Example:{"code":"00","message":"OK"…..}
signature
String
required

It is the hash of the request payload expressed in a base64 value string.

Example:b166214e976c7e76390889
transactionId
String
required

Unique id for each transaction generated by the commerce, sent in the security api (Token Session) equivalent to the Correlation Id for the transaction flow.

Length (min - max): 5 - 40
Example:16881500822750