This page describes Payment Gateway Solutions Pvt. Ltd.’s (“PAYMENTZ”, “we”, “our” or “us”) cookie policy, which applies when you use our websites, mobile sites, or mobile apps (collectively, Sites). Here you can find out more about cookies and how to control them.
By using our Sites, you accept the use of cookies in accordance with this Cookie Policy. This policy applies additional to any other Terms of Use or contract provision for the particular PAYMENTZ service being used. If you do not accept the use of cookies, please disable them as explained below, or please do not use this site.
Cookies are small data files that are placed on your computer or mobile device when you visit a website. Cookies are widely used by website and mobile application owners in order to make their websites and apps work or to work more efficiently, as well as to provide reporting information.
Cookies do a lot of different jobs which make your experience of the Internet much smoother and more interactive. For instance, they are used to remember your preferences on sites you visit often, to remember your user ID and the contents of your shopping baskets, and to help you navigate between pages more efficiently. They also help ensure that the advertisements that you see online are more relevant to you and your interests. Much, though not all, of the data that they collect is anonymous, though some of it is designed to detect browsing patterns and approximate geographical location to improve user experience.
If you visit our website, mobile site, or use our mobile apps, we will deploy cookies and similar technologies like JavaScript to provide an online service more suited to the device you connect from, as well as to prevent and detect fraud, to help keep you secure. When you visit our website from any device (e.g. mobile device or PC), we collect information about your use of this site, such as information about the device or browser you use to access the site (including device type, screen resolution, etc.), the way you interact with this site, and the IP address your device connects from. In many instances, these technologies are reliant on cookies to function properly, and so declining cookies will impair their functioning, e.g. you may not be able to initiate or complete some activities within our secure online services unless these cookies or similar technologies are installed.
Broadly speaking, there are four types of cookies: strictly necessary cookies, performance cookies, functionality cookies, and targeting or advertising cookies.
Additionally, these cookies are divided further into two sub-types.
The ability to disable or delete cookies can also be carried out by changing your browser’s settings. In order to do this, follow the instructions provided by your browser (usually found in the ‘Help’, ‘Edit’ or ‘Tools’ facility). If you disable all cookies, some pages may not work. If you switch off cookies at a browser level, your device won’t be able to accept cookies from any website.
Below is a list of the types of cookies and similar technologies used by the PAYMENTZ across our websites, mobile sites, and mobile applications. Not all of these cookies will appear on every site or application, and this list is not exhaustive.
| Cookie Name | Source | Cookie Description | Cookie Purpose | Duration |
|---|---|---|---|---|
| JSESSIONID | Internal | JSESSIONID is a cookie in J2EE web application which is used in session tracking. Since HTTP is a stateless protocol, we need to use any session to remember state. JSESSIONID cookie is created by web container and send along with response to client. | Session | Session |
| path | Internal | Indicates a URL path that must exist in the requested resource before sending the Cookie header. The %x2F ("/") character is interpreted as a directory separator and sub directories will be matched as well (e.g. path=/docs, "/docs", "/docs/Web/", or "/docs/Web/HTTP" will all be matched). | Directory Location | -- |
| Secure | Internal | A secure cookie will only be sent to the server when a request is made using SSL and the HTTPS protocol. However, confidential or sensitive information should never be stored or transmitted in HTTP Cookies as the entire mechanism is inherently insecure and this doesn't mean that any information is encrypted. | Data Security | -- |
| HttpOnly | Internal | HTTP-only cookies aren't accessible via JavaScript through the Document.cookie property, the XMLHttpRequest and Request APIs to mitigate attacks against cross-site scripting (XSS). | Security | -- |
| pzConsent | Internal | This cookie is used to remember your response to our consent box. | Essential Cookies | 30 Days |
| __cfduid | Cloudflare | This cookie is used to override any security restrictions based on the IP address the visitor is coming from and also this cookie is used to identify individual clients behind a shared I.P address and apply security settings on a per-client basis. This cookie does not store personally-identifying information. | Analytics | 1 Year |
| driftt_aid | Drift | These cookies are used to help remember you when you use the Drift messaging system on site. | Functional Cookies | 2 Years |
| driftt_sid | Drift | These cookies are used to help remember you when you use the Drift messaging system on site. | Functional Cookies | 30 Minutes |
| driftt_wmd | Drift | These cookies are used to help remember you when you use the Drift messaging system on site. | Functional Cookies | Browser Session |
| NID | google.com | Google uses cookies NID to contribute to the personalization of the ads in Google properties, like Google search. For example, we use them to store your most recent searches, your previous interactions with an advertiser's ads or search results and your visits to an advertiser's website. In this way we can show you personalized ads on Google. | Targeting Cookies | 45 Days |
| _ga | Internal | Used to distinguish users. | Analytics | 2 Years |
| _gid_UA-120911520-1 | Internal | Used to distinguish users. | Analytics | 24 Hours |
| _gat | Internal |
Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_ |
Analytics | 1 Minute |
| __asc | Internal | Used to distinguish users. | Analytics | 1 Day |
| __auc | Internal | Used to distinguish users. | Analytics | 1 Year |