Skip to content

Search

"card data security"

126 articles found

Diagram showing how card transaction data flows through the ISO 8583 messaging standard

Merchant & POS

What is ISO 8583?

Introduction: When a card (credit card/debit card/prepaid card) is used at an ATM or POS, data must be carried securely between systems. For example, in a store sale, the POS initiates the transaction, which must reach the cardholder's bank intact.

Diagram illustrating ISO 8583 field F23, the card sequence number

ISO 8583

ISO 8583 Field Descriptions (F23)

F23 - CARD SEQUENCE NUMBER: Information used to distinguish cards sharing the same card number. For example, the Card Sequence Number is incremented by 1 when a card is renewed. In an authorization transaction, if the F22 value is '05x'...

Illustration of ISO 8583 message format

ISO 8583

ISO 8583 Field Descriptions (F44)

DE 44 - ADDITIONAL RESPONSE DATA is used to provide other supplementary data that may be needed in authorization, as a response to the authorization message. The Card Authentication Results Code is sent in position 9, and the CAVV Result Code is sent in position 15.

Illustration explaining how a card's CVV value is generated

Credit Card

How is CVV generated?

CVV is a very critical 3-digit value used during a card's authorization process. The CVV value is encoded in the card's magnetic stripe data (Track 1 and Track 2). Is it generated by an algorithm or chosen at random?

Diagram illustrating the tokenization and detokenization process for card payments

HCE

What Are Tokenization and Detokenization?

Tokenization generates secure data from a credit card number, using specific algorithms, for use during authorization. In CNP transactions, it removes the risk of storing or compromising the original card number.

Diagram of the chargeback process between cardholder, issuer and acquirer

Chargeback

How to Reduce Chargebacks (For Cardholders)

A chargeback is when a cardholder asks the issuing bank to refund a transaction made without their knowledge. It cannot be prevented entirely, but simple precautions can minimize the risk. Here is how the process works and what cardholders should do.

Diagram illustrating account-to-account (A2A) payment flow between banks

Online & Authorization

What are A2A (Account-to-Account) Payments?

Account-to-account (A2A) payments can be described as making a payment by transferring money from one bank account to another. Though similar to wire transfer/EFT, combining the transfer with the payment creates a seamless experience.

Diagram explaining PVKI and PVV calculation in card PIN verification

Credit Card

What Is PVKI (PIN Verification Key Index)?

PVKI is the abbreviation for PIN Verification Key Index. It is located within the card's Track 1 and Track 2 data and is used in PVV calculation. It can take values from 1 to 6, usually defaulting to 1.

Cover of the EMVCo Software-based Mobile Payment Security Requirements document

Security

What is Software-based Mobile Payment Security Requirements?

“Software-based Mobile Payment Security Requirements” is a document published by EMVCo in April 2020 to guide payment application developers in building secure payment applications. This post summarizes its purpose and who it concerns.

Diagram illustrating the structure of Track3 data on a payment card

Credit Card

What Is Track3?

Track3 is a field that doesn't need to be written to the card's magnetic stripe. It's used only in very specific cases and isn't required for authorization transactions. Issuers generally don't encode Track3 data onto the card's magnetic stripe. It consists of 104 numeric characters.

Diagram comparing the three levels of payment-card tokenization: static, semi-dynamic and dynamic

HCE

What Are the Levels of Tokenization?

Generating a token from the card number is essential to the security of payments made with mobile devices. The level of tokenization used depends on the need and on how critical the token is. Static tokenization: the token is generated once and stored in a database.