Definitions of payment industry terms and Precium-specific concepts.
An authentication protocol that adds an extra layer of security to online card transactions. Cardholders verify their identity with their bank during checkout, typically via OTP or biometric authentication. Precium supports 3DS 2.0.
The financial institution that processes card payments on behalf of a merchant. The acquirer receives transaction requests and communicates with card networks to authorize and settle payments.
A unique identifier used to authenticate API requests. Precium provides separate API keys for sandbox and production environments.
The process of verifying that a cardholder has sufficient funds or credit for a transaction. An authorization does not transfer funds, it reserves them for later capture.
A code returned by the card issuer confirming that a transaction has been approved. Used as proof of authorization.
A fraud prevention measure that compares the billing address provided during checkout with the address on file with the card issuer.
A Precium resource that defines recurring billing configuration, including pricing, frequency, and payment method requirements. Used to automate subscription billing.
A merchant configuration in Precium that includes branding (logo, colours), payment method settings, and API credentials. Merchants can have multiple brands.
The unique identifier for a brand configuration. Required in most API requests to identify which merchant configuration to use.
To void a purchase before payment is completed or captured. Cancelled purchases cannot be paid.
The process of completing a previously authorized transaction and initiating a fund transfer. Used in two-step payment flows (authorize then capture).
Organisations that facilitate card payments between issuers and acquirers (e.g., Visa, Mastercard). They set rules, process transactions, and manage settlement.
A transaction where the physical card is not presented, such as online or phone payments. CNP transactions have different security requirements than in-person payments.
See Card Network.
The person whose name appears on a payment card and who is authorized to use it.
A URL provided by Precium that redirects customers to a hosted payment page. The safest integration method for PCI compliance.
A customer record in Precium contains contact information, billing address, and stored payment methods.
Card Verification Code/Value. The 3 or 4-digit security code on a payment card is used to verify card-not-present transactions.
A South African authenticated debit order system. Customers authorize mandates via their banking app, providing greater security than traditional debit orders.
A payment instruction that allows a merchant to collect funds directly from a customer's bank account. Traditional debit orders don't require real-time authentication.
An integration method where card data is submitted directly from the customer's browser to Precium, bypassing the merchant's servers. Requires PCI SAQ A-EP compliance.
A challenge to a payment initiated by a cardholder through their bank. Also known as a chargeback.
The electronic movement of money between bank accounts. Includes methods like Ozow, Stitch, and traditional bank transfers.
The URL where customers are redirected after a failed payment attempt.
A flag that ensures payment credentials are tokenized for future use, even if the customer doesn't opt in.
A service that transmits payment data between merchants and payment processors. Precium acts as a payment gateway.
A temporary reservation of funds on a card, typically used for pre-authorization. The hold reserves funds without completing the transaction.
A payment page hosted by Precium where customers enter payment details. Provides the highest level of PCI compliance simplification.
The property of an operation that, when performed multiple times, produces the same result. Important for retry logic to prevent duplicate charges.
Electronic funds transfer methods that provide immediate or near-immediate payment confirmation (e.g., Ozow, Capitec Pay).
The bank that issues payment cards to consumers and approves or declines transactions.
The real payment environment where actual funds are transferred. Contrasted with sandbox/test environments.
An authorization from a customer to collect payments from their account. Used in debit order and DebiCheck scenarios.
A business that accepts payments for goods or services.
A unique identifier assigned to a merchant by their acquirer or payment processor.
A transaction initiated by the merchant without the cardholder being present, such as recurring billing or scheduled payments.
The coordination of multiple payment providers, methods, and flows through a single platform. Precium provides payment orchestration.
A URL that directs customers to a payment page for a specific transaction. Can be shared via email, SMS, or messaging apps.
The specific instrument used for payment (e.g., Visa, Mastercard, Ozow, DebiCheck).
A list of payment methods that customers are allowed to use for a specific purchase.
Payment Card Industry Data Security Standard. A set of security requirements for organisations that handle card data.
The extent of PCI DSS requirements applicable to an organization based on how they handle card data.
An authorization that reserves funds without immediate capture. Used when the final amount may differ from the initial authorization (e.g., hotels, car rentals).
A payment request in Precium. Contains product information, pricing, and payment configuration.
The unique identifier for a purchase transaction.
A payment that occurs on a regular schedule using stored payment credentials.
A secure reference to stored payment credentials that can be used to process future payments without re-entering details.
The return of funds to a customer after a payment is completed. Can be full or partial.
The action of removing a hold on funds without capturing them.
A unique identifier assigned to a transaction that can be used to trace it through the payment system.
A test environment that simulates real payment processing without moving actual funds. Used for development and testing.
A PCI DSS compliance validation tool. Different SAQ types (A, A-EP, D) apply based on how card data is handled.
The process of transferring funds from the customer's bank to the merchant's bank after authorization.
A flag that creates an authorization without automatic capture, enabling two-step payment flows.
A recurring billing arrangement where customers are charged automatically on a schedule.
A URL that Precium calls via webhook when a payment succeeds.
The URL where customers are redirected after successful payment.
The process of replacing sensitive payment data with a non-sensitive reference (token) that can be used for future transactions.
A 36-character identifier in the format xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Used for all Precium resource IDs.
See Cancel.
An HTTP callback that delivers event notifications to your application in real-time. Used for payment confirmations, failures, and other events.
See Payment Method Whitelist.
An authorisation for R0.00 is used to verify a card and tokenise it without charging the customer.