--- title: "Secure Channel Transaction" slug: "csl-ig-secure-channel-transaction-4-38-1" updated: 2025-10-30T11:15:18Z published: 2025-10-30T11:15:18Z canonical: "docs.onespan.com/csl-ig-secure-channel-transaction-4-38-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Secure Channel Transaction ![CrontoSign Libraries Overview of Secure Channel Transaction Integration](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/CrontoSignLibraries_Secure_Channel_Transaction_Integration.png?sv=2026-02-06&spr=https&st=2026-11-16T16%3A19%3A29Z&se=2026-11-16T17%3A19%3A29Z&sr=b&sp=r&sig=flejQm6m9FEkfFfhexSKYVYHMe4NOnfbqnQ7%2BXLWWjk%3D) ## Secure Channel Transaction process 1. All input is converted into FormattedText and transformed into a transaction message body with the `generateSignatureTransactionMessageBodyV2` function of the Secure Messaging SDK. 2. This transaction message body is encrypted and transformed in a transaction message request with the Authentication Suite Server SDK function `AAL2GenMessageRequest`. 3. This transaction message request is converted into a Cronto image with the Image Generator SDK function `generateCrontoSign`. 4. The client reads this image and generates a one-time password (the signature of the transaction message request). 5. This signature is verified by the Authentication Suite Server SDK with the `AAL2VerifyMessageSignature` function. For more information, refer to the Authentication Suite Server SDK Product Guide, section Digipass Secure Channel Service.