Securing a card
The Paymentology Sprint Companion API allows you to secure your cards and ensure the safety of transactions.
You can use the following three main ways to secure your companion cards:
- Dynamic secure code on virtual cards
- PIN on physical cards
1. Securing a virtual card with a dynamic secure code
You can add an extra layer of security to your virtual card using a dynamic secure code. The secure code is what Mastercard refers to as 3D Secure, and Visa refers to it as Visa Secure (formerly Verified by Visa (VbV)). Mastercard and Visa created the technical standard to secure Cardholder Not Present (CNP) transactions.
This method provides additional authentication to secure a customer’s virtual card during an online transaction. It protects consumers against unauthorized use of cards and businesses from potential fraud liabilities.
3D Secure enables consumers to verify transactions using a One Time Pin (OTP), which is sent to their mobile device.
If your card program is enabled for Dynamic 3D Secure, the cardholder will be sent an OTP to conclude an online transaction. Through the Remote AdminMessage, Paymentology will send the OTP to your platform, which you can then send on to the cardholder.
2. Securing a physical card with a PIN
Your customers will require a PIN (personal identification number) for all ATM transactions. A secret PIN assists in verifying your users’ identity and allowing them to perform secure transactions.
There are two options for managing your PIN: Paymentology manages the PIN or you manage the PIN
In case the card PIN needs to be set for the first time or changed at a later time, or if the customer forgets it or requests it to be changed, you’ll need to make a call to the ChangePIN method to do this. Once the API request has been completed, Paymentology will issue a new PIN, which the cardholder can use for making transactions.
Was this page helpful?