Get Started 开始 Mulai Mulakan Bắt đầu

Migrate to SHOPLINE 迁移到SHOPLINE Pindah ke SHOPLINE Berpindah ke SHOPLINE Đồng bộ dữ liệu về SHOPLINE

Your SHOPLINE account SHOPLINE账户 Akun SHOPLINE Anda Akaun SHOPLINE anda Tài khoản SHOPLINE của bạn

Orders 订单 Pesanan Pesanan Đơn hàng

Products 商品 Produk Produk Sản phẩm

Customer 客户 Pelanggan Pelanggan Khách hàng

Marketing 营销 Marketing Marketing Marketing

Apps 相关应用 Aplikasi Apps Ứng dụng

One page shop 一页商店 One page shop One page shop Cửa hàng một trang

Setting 设置 Pengaturan Tetapan Cài đặt

Learn about Multipass

1. What is Multipass?

2. How to use Multipass

3. Example implementation





1. What is Multipass?

Multipass login is available for shop owners with separate websites and Shopline stores. It redirects users from the website to the Shopline store and seamlessly logs in using the same email address they used to sign up for the original website. If you don't already have an account with that email address, a new account will be created with that email address. No need to synchronize any customer databases.


2. How to use Multipass

2.1 Enable Sign in with Multipass in SHOPLINE Administrator

Log in to your store Administrator, go to "Setting up/sign in method",Scroll down and find "Log in with Multipass" and ensure that you have selected "Customer can sign up/sign in with email address".



Select Enable Multipass. Once enabled, a secret will be shared with you. You will need the secret in order to generate tokens to log your customers into your Shopline store. Make sure you keep your secret private.


2.2  Encode your customer information using JSON

The customer information is represented as a hash which must contain at least the email address of the customer and a current timestamp (in ISO8601 encoding). You can also include the customer's first name, last name or several shipping addresses. Optionally, you can include an IP address of the customer's current browser session, that makes the token valid only for requests originating from this IP address.

A minimal example, containing all required fields, might look like this:



"email": "",

"created_at": "2013-04-11T15:16:23-04:00",




 An example containing some optional fields might look like this:


"email": "",

"created_at": "2013-04-11T15:16:23-04:00",

"first_name": "Peter",

"last_name": "jason",

"tag_string": "canadian, premium",

"identifier": "peter123",

"remote_ip": "",

"return_to": "",

"addresses": [


"address1": "123 Oak St",

"city": "Ottawa",

"country": "Canada",

"first_name": "Peter",

"last_name": "Jason",

"phone": "555-1212",

"province": "Ontario",

"zip": "123 ABC",

"province_code": "ON",

"country_code": "CA",

"default": true





You can attribute tags to your customer by setting "tag_string" to a list of comma separated one-word values. These tags will override any tags that you may have already attributed to this customer.

If you want your users to see a specific page of your Shopline store, you can use the return_to field for that.


Shopline uses email addresses as unique identifiers for customers of a shop. When registering customers in Shopline, the merchant must set the unique identifier in the "identifier" field in the following cases:

  • The site uses other identifiers (such as usernames)
  • Two different users of the site might be registered with the same email address If the email address is always unique, setting the "identifier" field isn't required. Only one Shopify account can use a specific email address. Registering a second customer with the same email address (even with a different "identifier") will result in an error.


2.3 Encrypt the JSON data using AES

To generate a valid multipass login token, you need the secret given to you in your Shopline admin. The secret is used to derive two cryptographic keys — one for encryption and one for signing. This key derivation is done through the use of the SHA-256 hash function (the first 128 bit are used as encryption key and the last 128 bit are used as signature key).

The encryption provides confidentiality. It makes sure that no one can read the customer data. As encryption cipher, we use the AES algorithm (128 bit key length, CBC mode of operation, random initialization vector).


2.4 Sign the encrypted data using HMAC

The signature (also called message authentication code) provides authenticity. It makes sure that the multipass token is authentic and hasn't been tampered with. We use the HMAC algorithm with a SHA-256 hash function and we sign the encrypted JSON data from step 3 (not the plaintext JSON data from step 2).


2.5 Base64 encode the binary data

The multipass login token now consists of the 128 bit initialization vector, a variable length ciphertext, and a 256 bit signature (in this order). This data is encoded using base64 (URL-safe variant, RFC 4648).


2.6 Redirect your customer to your Shopline store

Once you have the token, you should trigger a HTTP GET request to your Shopline store.

HTTP GET request



When the request is successful (for example, the token is valid and not expired), the customer will be logged in to your Shopline store.

The multipass token is only valid within a very short timeframe and each token can only be used once. For those reasons, you should not generate tokens in advance for rendering them into your HTML sites. You should create a redirect URL which generates tokens on-the-fly when needed and then automatically redirects the browser.


3. Example implementation

The following shows a basic example implementation of the token generation in the java languages. 


public static void main(final String[] args) throws Exception {

final String createAt =;

final Map<String, String> dataMap = new HashMap<>();

dataMap.put("email", "");

dataMap.put("created_at", createAt);

final String dataJson = "..."; //json string from dataMap;

final String secret = "...";

final String token = generateToken(secret, dataJson);"plaintext={}, token={}", dataJson, token);

}public static String generateToken(final String secret, final String plaintext) throws Exception {

// SHA-256 hash

final MessageDigest messageDigest = MessageDigest.getInstance("SHA-256");

final byte[] encodedHash = messageDigest.digest(secret.getBytes(StandardCharsets.UTF_8));

final byte[] encryptedKey = new byte[16];

final byte[] signKey = new byte[16];

System.arraycopy(encodedHash, 0, encryptedKey, 0, 16);

System.arraycopy(encodedHash, 16, signKey, 0, 16);

// iv

final byte[] iv = new byte[16];

new SecureRandom().nextBytes(iv);

final SecretKeySpec encryptedKeySpec = new SecretKeySpec(encryptedKey, "AES");

final Cipher cipher = Cipher.getInstance("AES/CBC/PKCS5Padding");

cipher.init(Cipher.ENCRYPT_MODE, encryptedKeySpec, new IvParameterSpec(iv));

// encrypt byte array

final byte[] encrypted = cipher.doFinal(plaintext.getBytes(StandardCharsets.UTF_8));

final byte[] ivEncryptedByte = new byte[iv.length + encrypted.length];

System.arraycopy(iv, 0, ivEncryptedByte, 0, iv.length);

System.arraycopy(encrypted, 0, ivEncryptedByte, iv.length, encrypted.length);

final Mac hmac = Mac.getInstance("HmacSHA256");

final SecretKeySpec signKeySpec = new SecretKeySpec(signKey, "HmacSHA256");


// sign byte array, 256 bit

final byte[] signByte = hmac.doFinal(ivEncryptedByte);

final byte[] tokenBytes = new byte[ivEncryptedByte.length + signByte.length];

System.arraycopy(ivEncryptedByte, 0, tokenBytes, 0, ivEncryptedByte.length);

System.arraycopy(signByte, 0, tokenBytes, ivEncryptedByte.length, signByte.length);

String token = Base64.encodeBase64URLSafeString(tokenBytes);

token = token.replace('+', '-')

.replace('/', '_');

return token;




4. Security considerations

Shopline encourages you to always set the remote_ip field in the customer data hash, so that only the intended browser can use the token. We also encourage you to send tokens to the browser using secure HTTPS connections.

You should make sure that registering new accounts at your main website requires validation of the email address which is used. Otherwise, someone could sign up to your main site using somebody else's email address, thus getting access to his customer account in your Shopline store.


5. FAQ

Q:I have a huge customer database. How do I synchronize this with Shopify so that I can use multipass login?

A:You don't need to synchronize anything. As soon as you redirect a customer using multipass, we will automatically create a customer account for them in your Shopify store (if one doesn't exist yet).


Q:Some of my customers have already placed orders on Shopify. How do I update those customers so they can login through multipass?

A:You can use the Customer API to set the multipass_identifier for the customer. You will need to use the identifier with all your multipass requests for those customer accounts


Q:My secret was leaked. What do I do now?

A:If your secret ever leaks, it can be revoked in your shop admin and a new one can be generated. This will make all of the old URLs invalid. You should do this as quickly as possible since everybody who knows the secret can potentially access every customer account!


Q:Can I use Multipass login between multiple Shopify stores?

A:No, Multipass cannot be used to log in between multiple Shopline stores without redirection to an external site.


Q:Does Multipass login work with the wholesale channel?

A:No, Multipass cannot be used with the wholesale channel.


Q:Does the remote_ip field support IPv6 addresses?

A:No, only IPv4 addresses are supported. Multipass returns the error "You are not authorized to use Multipass login" if the remote_ip doesn't match the IP specified in the customer data hash.

Have more questions? Submit a request