Models
Here you can find some helpful models used in the SDK.
Envelope
The model Envelope can be found on TrustFactorSDK.V2.Util.Crypto namespace. Contains an encrypted message, the receiver and sender keys and the payload signature
Device Info
The model DeviceInfo can be found on TrustFactorSDK.V2.Models namespace.
| Attribute | Description |
|---|---|
Name | Device’s name (configured by the user on the Agent) |
Manufacturer | Device’s manufacturer |
OS | Device’s operating system (“Android”/“iOS”) |
OSVersion | Device’s operating system version |
Meta Data
The MetaData model for transactions v3 can be found on TrustFactorSDK.V2.Models.TransactionCreation.V3.Auxiliary namespace. Contains transaction’s metadata.
| Attribute | Description |
|---|---|
Timestamp | Should contain the application timestamp when the transaction was created |
UserAgent | Should contain the user’s UserAgent of the request that initiated the transaction creation flow |
Platform | User’s operating system |
Channel | Application channel used. Useful for applications that have Web/Mobile channels |
SourceIP | User’s IP either IPv4 or IPv6 |
Core
The Core model for transactions v3 can be found on TrustFactorSDK.V2.Models.TransactionCreation.V3 namespace.
| Attribute | Description |
|---|---|
MetaData | Transaction’s metadata |
Transaction’s core contains basic information needed to create any type of transaction.
Message Engine
The MessageEngine model for transactions v3 can be found on TrustFactorSDK.V2.Models.TransactionCreation.V3.Auxiliary namespace.
| Attribute | Description |
|---|---|
Language | Overrides the preferred language defined in the Operation |
Message | Specifies the message that should be displayed on user’s agent. It will override the message template engine or any operation defined message. MsgIdentifier should be null or empty if this field is filled. |
MsgIdentifier | Specifies the operation’s defined template message to use |
The MessageEngine object in the transactions is used to easily show messages to the user. There are two ways to do that, the simplest way is to fill the field Message with the intended message. The other way is to fill the MsgIdentifier with the identifier of a message created within the operation referenced on the Action field of the transaction. This message identifier is retrieved through the backoffice Operations menu. MessageEngine can only be used with NormalTransaction and ActionableTransaction types, since they are the only ones that take a predefined operation on the backoffice.
Confirmation Code Settings
The ConfirmationCodeSettings model for transactions v3 can be found on TrustFactorSDK.V2.Models.TransactionCreation.V3 namespace. Customizes the confirmation code generated for a transaction created with the RequireConfirmationCode flag active.
| Attribute | Description |
|---|---|
Options | Number of options presented on the user’s agent for the user to choose from |
Digits | Number of digits of the confirmation code and of each option |
Confirmation Code
The ConfirmationCode model can be found on TrustFactorSDK.V2.Requests namespace. It is returned on the Create Transaction response when the transaction was created with the RequireConfirmationCode flag active.
| Attribute | Description |
|---|---|
Code | The generated confirmation code. Should be displayed on the channel that initiated the transaction, so the user can pick the matching option on their agent |
Options | The full list of options presented on the user’s agent, which includes the generated code |