, but this code // executes before the first paint, when

ÃÛÌÒapp

is not yet present. The // classes are added to so styling immediately reflects the current // toolbar state. The classes are removed after the toolbar completes // initialization. const classesToAdd = ['toolbar-loading', 'toolbar-anti-flicker']; if (toolbarState) { const { orientation, hasActiveTab, isFixed, activeTray, activeTabId, isOriented, userButtonMinWidth } = toolbarState; classesToAdd.push( orientation ? `toolbar-` + orientation + `` : 'toolbar-horizontal', ); if (hasActiveTab !== false) { classesToAdd.push('toolbar-tray-open'); } if (isFixed) { classesToAdd.push('toolbar-fixed'); } if (isOriented) { classesToAdd.push('toolbar-oriented'); } if (activeTray) { // These styles are added so the active tab/tray styles are present // immediately instead of "flickering" on as the toolbar initializes. In // instances where a tray is lazy loaded, these styles facilitate the // lazy loaded tray appearing gracefully and without reflow. const styleContent = ` .toolbar-loading #` + activeTabId + ` { background-image: linear-gradient(rgba(255, 255, 255, 0.25) 20%, transparent 200%); } .toolbar-loading #` + activeTabId + `-tray { display: block; box-shadow: -1px 0 5px 2px rgb(0 0 0 / 33%); border-right: 1px solid #aaa; background-color: #f5f5f5; z-index: 0; } .toolbar-loading.toolbar-vertical.toolbar-tray-open #` + activeTabId + `-tray { width: 15rem; height: 100vh; } .toolbar-loading.toolbar-horizontal :not(#` + activeTray + `) > .toolbar-lining {opacity: 0}`; const style = document.createElement('style'); style.textContent = styleContent; style.setAttribute('data-toolbar-anti-flicker-loading', true); document.querySelector('head').appendChild(style); if (userButtonMinWidth) { const userButtonStyle = document.createElement('style'); userButtonStyle.textContent = `#toolbar-item-user {min-width: ` + userButtonMinWidth +`px;}` document.querySelector('head').appendChild(userButtonStyle); } } } document.querySelector('html').classList.add(...classesToAdd); })(); Payment Card Industry (PCI) Data Guidelines | ÃÛÌÒapp

ÃÛÌÒapp

Skip to main content

Payment Card Industry (PCI) Data Guidelines

Table of Contents


Why do I or my departments need to care about PCI?

PCI is important to you if you or your department takes credit cards on behalf of the University to conduct financial transactions. In order to collect credit card information our credit card systems and processes need to meet the requirements established in the PCI-DSS.

If we do not choose compliant payment card solutions or mishandle credit card information we are introducing serous risk to the University. Penalties for not being compliant with PCI-DSS can result in fees to the institution or losing the right to process credit cards altogether.

When choosing to take credit cards in your department you should do it in a way that minimizes risk to the University.

How can ÃÛÌÒapp reduce its risk exposure when collecting credit card information?

We can reduce risk to the University by making sure departments are aware of how to appropriately handle credit cards. At minimum the University needs to meet the standards and requirements found in the PCI-DSS.

Secondly, departments should collaborate with the best partners in our industry for payment card solutions that meet the appropriate PCI standards.

Finally, a significant portion of payment card risk can be reduced by establishing relationships with vendors that outsource the credit card processing operation from ÃÛÌÒapp's campus networks. The burden of meeting a large portion of the PCI-DSS requirements is borne by another entity who has expertise in this area.

Who Do I talk to about PCI and being compliant in my department?

Financial Services is responsible for overseeing the payment card process for the University. They should be consulted prior to establishing credit card services or for any merchant account questions. Information Technology is your partner in selecting and implementing secure and compliant credit card software systems for your department. IT should be engaged early in the vendor selection process to provide systems and security expertise.


Last updated
Audience
Staff