Intro

By default, Connect prevents users from operating multiple concurrent SDK sessions. An SDK session is defined as an active JWT token. Connect enforces this restriction at the user level, identified by the reference_id field provided within the POST /sessions request:

{
  "account": {
    "reference_id": "USER01" 
  },
  "session": {
    "metadata": {  
	    }
  },
  "scopes": [
    "user:deposit:send"
  ]
}

Logic

Once an initial session has been established, if a subsequent session is initiated and the user attempts to perform an action in the original session (for example, by interacting with the SDK), the SDK will display the following error screen:

📘

Mobile vs. Web

This behavior applies across platforms. For example, if a user initiates a session on mobile and then starts another session on web, the original mobile session will be invalidated.