A security protocol that provides an additional layer of authentication for online card transactions. 3DS 2.0 supports risk-based authentication, allowing frictionless flows for low-risk transactions while challenging high-risk ones.
The authentication step where the cardholder must verify their identity, typically through an OTP, biometric, or password sent by the issuing bank.
A financial institution that processes card payments on behalf of merchants. The acquirer maintains the merchant relationship and routes transactions to the appropriate card networks.
The issuing bank's server that handles 3DS authentication. It generates and validates authentication requests during the 3DS flow.
A formal declaration confirming that a merchant or service provider meets PCI DSS requirements. Required annually for S2S integrations.
A unique identifier used to authenticate API requests. Precium uses two types: Standard API Key (for general operations) and S2S API Key (for card data submission).
The process of verifying that a cardholder has sufficient funds or credit and obtaining approval from the issuing bank to proceed with a transaction.
The first 6-8 digits of a card number that identify the issuing bank and card type. Used for routing decisions and fraud detection.
A unique identifier assigned to each merchant brand within the Precium platform. Used in API calls to route transactions correctly.
A collection of browser and device attributes (screen size, timezone, language, etc.) used for 3DS risk assessment and fraud detection.
A URL Precium sends to the customer after 3DS authentication. The URL receives authentication results for further processing.
The process of finalising a pre-authorized transaction to transfer funds. Can be full (entire authorized amount) or partial (less than authorized).
Organisations such as Visa, Mastercard, and American Express that operate the payment infrastructure connecting issuers and acquirers.
A transaction where the physical card is not presented, such as online or phone payments. Requires additional fraud prevention measures.
A secure substitute for a card number that can be stored and reused for future transactions without exposing the actual card data.
A cryptographic value generated during 3DS authentication that proves the cardholder was authenticated. Included in authorization requests for liability shift.
A transaction reversal initiated by the cardholder through their issuing bank, typically due to fraud, non-receipt of goods, or disputes.
A transaction where the cardholder is actively participating at the time of payment, requiring their authentication.
The actual card number (Primary Account Number) as opposed to a tokenized representation.
A dynamic security value generated by a network token service (MDES/VTS) that provides transaction-specific authentication.
The 3 or 4-digit security code printed on a card, used to verify card-not-present transactions.
A dynamically generated, single-use URL where card data is securely submitted in the S2S flow. Unique to each purchase.
A network token that represents the actual card number. Used in network tokenization (MDES/VTS).
A card network component that routes 3DS messages between the merchant and the issuer's ACS.
A unique identifier assigned by the Directory Server in 3DS 2.x authentication, used to link authentication to the transaction.
A code returned during 3DS authentication that indicates the level of authentication achieved:
A flag in purchase creation that signals intent to store card credentials for future recurring transactions. Generates a token when enabled.
A numerical value representing the risk level of a transaction based on various factors including velocity, geography, device fingerprint, etc.
A 3DS authentication that completes without cardholder interaction because the risk assessment deemed the transaction low-risk.
A service that securely transmits transaction data between merchants and payment processors.
A permanent decline that should not be retried. Indicates issues like invalid card, stolen card, or closed account.
A property where repeating the same request produces the same result, preventing duplicate transactions or charges.
The financial institution that issued the card to the cardholder and is responsible for authorizing transactions and managing the cardholder's account.
Transfer of fraud liability from the merchant to the issuing bank upon successful 3DS authentication.
A checksum algorithm used to validate card numbers. The last digit of a card number is a check digit calculated using this algorithm.
A four-digit code classifying the type of business a merchant operates. Affects interchange rates and transaction permissions.
An opaque value passed through the 3DS flow to maintain state between the redirect to the issuer and the callback.
Mastercard's network tokenization service that provisions and manages network tokens for secure digital payments.
A transaction initiated by the merchant when the cardholder is not present, such as a subscription renewal or scheduled payment.
A software component that handles 3DS authentication on behalf of a merchant. Can be provided by Precium (internal) or a third-party provider (external).
A card token provisioned by the card network (Visa, Mastercard) that updates automatically when a card is reissued, providing higher authorization rates.
A unique identifier assigned by the card network to link related transactions (e.g., original CIT and subsequent MITs).
A temporary code sent to the cardholder during 3DS authentication, typically via SMS or an authenticator app.
A message sent to the issuer's ACS containing transaction details for 3DS authentication.
Capturing less than the pre-authorized amount. Used when the final transaction amount is lower than the original authorisation.
Returning only a portion of the original transaction amount to the customer.
A set of security standards designed to ensure all companies that accept, process, store, or transmit credit card information maintain a secure environment.
An authorization request that reserves funds on a cardholder's account without immediate capture. Also called "auth-only" or "authorize-only."
In Precium's API, a purchase object represents a transaction intent including amount, currency, products, and redirect URLs.
An organisation certified by the PCI Security Standards Council to assess and validate compliance with PCI DSS.
A detailed document created by a QSA documenting an organisation's compliance status with PCI DSS requirements.
A series of transactions charged to a customer's card at regular intervals based on prior authorization.
The return of funds to a cardholder, either full or partial, that reverses a previous successful charge.
An integration pattern where card data is transmitted directly from the merchant's server to Precium's API, requiring PCI DSS SAQ-D compliance.
A PCI DSS compliance validation tool. Different types exist based on how card data is handled:
The process of transferring funds from the cardholder's issuing bank to the merchant's acquiring bank after transaction authorization.
A temporary decline that may succeed if retried later. Often due to insufficient funds, velocity limits, or temporary system issues.
The process of replacing sensitive card data with a non-sensitive substitute (token) that can be safely stored and used for future transactions.
A unique identifier assigned to each payment transaction for tracking and reference purposes.
Fraud prevention rules that limit the number or value of transactions within a time period to detect suspicious patterns.
Cancellation of an authorized transaction before settlement occurs. Also used to cancel refunds before settlement.
Visa's network tokenization service that provisions and manages network tokens for secure digital payments.
An HTTP callback that Precium sends to your server when specific events occur (payment completed, refund processed, etc.).
A cryptographic key provided by Precium used to sign webhook payloads. Used to verify webhook authenticity and prevent spoofing.
An HMAC-SHA256 hash of the webhook payload, computed using the webhook secret. Included in the X-Webhook-Signature header for verification.
A unique identifier used in 3DS 1.x authentication to link the authentication to the transaction.
A card authorization for zero amount used to validate card details without placing a hold on funds. Often used during card registration or verification flows.