---
title: "Pass Back Feature"
slug: "pass-back-feature"
tags: ["encrypted signature", "url parameters", "passback", "pass back", "shared key", "AES"]
updated: 2023-09-30T01:14:26Z
published: 2023-09-30T01:14:26Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.lightspeedvt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pass Back Feature

The pass back feature is an easy way to create a seamless experience for your users between LSVT and your application or to collect basic data about a user without the need to use our full ADMIN API.

There are a fixed number of optional parameters, or data elements about a user (listed below) that LSVT can pass back to you via URL parameters. This could be used to allow a user to be passed back to your site and/or application – possibly already signed in, or to simply create a user in your system with the extra data provided.

We can quickly configure your system to pass these URL parameters of your choice, simply contact your project manager to get you in touch with System Config. Dept. to accomplish this.

To get started, you just need to let us know the URL, as noted below, and which of the available optional parameters you want to be added to the URL.

  

**URL SAMPLE**:

```
https://www.MyWebsite.com/my_listening_app/
```

### List of Optional URL Parameters

- **first_name**  
First name of the user  
EXAMPLE: John
- **last_name**  
Last name of the user  
EXAMPLE: Smith
- **email**  
Email address of the user  
EXAMPLE: JohnSmith@AcmeVT.com
- **global_user_id**  
The unique Global User ID that LSVT creates and stores. The user themselves never see this.  
EXAMPLE: 9999
- **location_id**  
The Location ID that the user is a member of.  
EXAMPLE: 123456
- **username**  
The unique user ID or name that the user themselves signs in as.  
EXAMPLE: johnsmith
- **vendor_id**  
An optional field relating to the “Location”  
EXAMPLE: Chevrolet
- **rep_id**  
An optional field relating to the “Location”  
EXAMPLE: Sales Dept

Once setup, a pass back URL could look like this:

```
https://www.MyWebsite.com/my_listening_app/?&first_name=JOHN&last_name=SMITH&email=ME%40EMAIL.COM&global_user_id=99999&username=JOHNSMITH&location_id=88888&vendor_id=CHEVROLET&rep_id=SALES%20DEPT
```

### Simple Shared Key AES Schema

Our system would generate a shared private key, which we would provide you with. Convert the values from HEX format and decrypt using the provided shared key.

URL would look something similar to this:

```
https://www.MyWebsite.com/my_listening_app/?first_name=9845192C74996476A33560387B66058D&last_name=E6EDE446FDB8ED9A85492BC0A62D31E5&email=19CDB1E79457464F205D4C1A0097C93065FA45352499A7694E57BB8A3AC4DAAD&global_user_id=09A8625144E0D41D965CD8E5BCAB5B58&username=26FD34D56ED7B713092F026EC3461F86&location_id=080FFA06FD82E25E3DE6F5FC10F6091D&vendor_id=&rep_id=54CDAD33EE9A4F020472CE77DF0A484F
```

### Shared Key + Signature

This adds another layer of security by providing you with an encrypted signature that would allow you to verify that the submission is valid. The signature uses Unix Time Stamp and the user’s global user id. The format is: unixtimestamp_GUserID.

URL would look something similar to this:

```

https://www.MyWebsite.com/my_listening_app/?first_name=9845192C74996476A33560387B66058D&last_name=E6EDE446FDB8ED9A85492BC0A62D31E5&email=19CDB1E79457464F205D4C1A0097C93065FA45352499A7694E57BB8A3AC4DAAD&global_user_id=09A8625144E0D41D965CD8E5BCAB5B58&username=26FD34D56ED7B713092F026EC3461F86&location_id=080FFA06FD82E25E3DE6F5FC10F6091D&vendor_id=&rep_id=54CDAD33EE9A4F020472CE77DF0A484F&signature=8A9CD11B414626EF4D3997CE2181FCF4FF8946372F8D4DE75CA93887EBCB52B
```