PIN Verification, PIN Selection, & PIN Change
Use the PIN as a component of a multi-factor authentication solution, to offer PIN selection while activating a new card, and to offer PIN change for existing cards. QwickPIN API works in branch, on-line, on mobile, and through a VRU that can be implemented in stages empowering your digital banking applications.
Seamless Voice Response Units
Enhance your over the phone transactions through Voice Response Units (VRUs) by integrating the QwickPIN API. Provide callers with the assurance that their account is protected by accepting a PIN over the phone as part of a strong multi-factor authentication solution used to identify the caller, to select, or even change a PIN. With QwickPIN, every VRU transaction remains secure, creating a seamless experience for your users.
Secure In-Branch Transactions
Transform in-branch transactions with the power of QwickPIN API. Whether cardholders are withdrawing funds, transferring money, checking account balances, or updating information, our PCI PTS certified PIN encrypting devices and secure card reader authenticator combined with the QwickPIN API guarantees the confidentiality of account and PIN data, enabling secure and efficient in-branch experience.
PIN Generation and Verification
QwickPIN API enables effortless generation and verification of PIN offsets without exposing cardholder sensitive data. Whether you’re dealing with PAN Tokens, PIN Block Tokens, MagTek ARQCs, MagTek Track 2 encrypted card data, or DUKPT PAN data, the QwickPIN API enables you to seamlessly handle PIN data in select ISO formats. Your transactions are resistant to threats while maintaining the utmost convenience.
PIN Offset Generation: Simple,“Qwick,” & Secure
- Developers can use standardized HTTPS methods to generate PIN offsets securely. By sending PANData, PANDataType, PINData, and PINDataType in a structured JSON format, developers seamlessly create PIN Offsets.
Made for a variety of Secure MagTek Devices
Magensa services are built to work with MagTek hardware. DynaPro Go PIN PED, iDynamo 6 mobile, tDynamo (Gen II) mobile and countertop, and DynaFlex II PED (shown here) are compatible.
A Unified Approach to PIN Security
QwickPIN takes a unified approach to PIN security. The API enables developers to interact with state-of-the-art PIN encrypting devices and tokenization services. No matter the size of your financial institution, QwickPIN API caters to your needs, allowing you to integrate advanced security measures without complexity, and where you need them most.
Industry Best Practice
QwickPIN Web API follows web development best practice using the principles of Representational State Transfer (REST) architecture. This emphasizes using standardized HTTPS methods secured by IP white-listing and digital certificates provided by Magensa. These methods secure interaction with resources and URLs to uniquely identify those resources. The request and response and the use of status codes align with RESTful design practices.
Expert Key Management
Magensa manages and secures encryption keys and performs PIN offset verification or calculations on behalf of the financial institution. Core processors and financial institutions can create an interface to the QwickPIN API. The data is provided by Magensa Tokens or from reading a card when a MagTek device is available in the branch. Once the transaction data is available, the core processor or financial institution sends the encrypted card data, the PIN block and if needed, the existing PIN offset to Magensa. QwickPIN performs the PIN calculation or PIN Offset verification and sends the response back to the client along with any necessary transaction results.
Hardware Requirement (in-branch only)
MagTek Secure card reader authenticator or PIN Pad
Compatible MagTek Hardware