- 23 Oct 2024
- 1 Minute to read
- DarkLight
Local Transaction
- Updated on 23 Oct 2024
- 1 Minute to read
- DarkLight
With the local transaction feature of the OneSpan Orchestration SDK, the user can do a transaction to the Customer Website using a signature generated via the Customer Mobile Application. The signature can be transmitted manually by the user or remotely by the Customer Mobile Application. An authentication method must be defined to authenticate the user before the signature is generated. See Authentication methods for more information.
Local transaction workflow illustrates the local transaction workflow with a manual transmission of the signature.
Local transaction workflow
Local transaction workflow
New APIs are created for Swift users of the iOS SDK. For more information, refer to the Xcode API documentation on LocalTransactionDelegate for this workflow.
The user initializes a transaction request via the Customer Mobile Application (e.g. for login purposes), providing their user identifier and the transaction data.
The Customer Mobile Application calls the startLocalTransaction method of the Orchestration SDK to perform the local authentication with a given authentication method (see Authentication methods for more information).
The Orchestration SDK prompts the user to authenticate, using an authentication method defined by the Customer Mobile Application.
In case of successful user authentication, the Orchestration SDK generates a signature and transmits it to the Customer Mobile Application using the onLocalTransactionSuccess method.
The Customer Mobile Application displays the signature to the user.
The user initializes a transaction request via the Customer Website (e.g. for money transfer purposes) by providing their user identifier, the transaction data, and the generated signature. This request is transmitted to the Customer Application Server.
The Customer Application Server calls the transactions/validate method of the OneSpan Trusted Identity platform to verify the signature of the transaction request.
The Customer Application Server provides a response to the Customer Website, indicating the success of the transaction request.
The user is informed that the transaction has been validated on the Customer Website.
For more information about integrating this feature, see Local transaction.