Skip to main content

Parameters definition

By using the config object with this input data in the SDK integration, ensures an accurate and complete flow of information, allowing to interact efficiently with the functionalities and services provided by the SDK. 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 a correct use of this input data. The config object stores information related to the transaction, as well as data related to the form appearance.

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

Configuration object, contains the other objects (order, token, billing, ...).

  • Output data: The output data responded by the SDK expresses the mandatory in general. to review which fields are mandatory according to the use case, refer to chapter use-cases.

The response object is composed of the following attributes:

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:Operación exitosa
messageUserEng
String
required

Friendly message for the user in English

Length (min - max): 5 - 50
Example:Successful
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:QBY3s3RRMwHqFmF93lhRTTqrjcuolsVBCUnDFXniKY8=
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:172356538519500