Glossary
| Term | Explanation |
|---|---|
| APM | Alternative Payment Method is any payment option other than traditional credit or debit cards, such as digital wallets, bank transfers, buy-now-pay-later services and others. |
| Attempts | Represents the fallbacks on different Partners. |
| Authorization | The process of verifying that the customer has sufficient funds or credit and reserving the required amount for a transaction, without actually transferring the money yet. |
| Authentication | The process of verifying the identity of a customer to ensure that the transaction is initiated by an authorized party. |
| Callback | A notification sent to your system when a transaction’s status changes. On what status changes it is sent depends on your notification setup. |
| Challenge | An authentication step that requires the customer to verify their identity or transaction, such as entering a one-time password (OTP) or completing two-factor authentication, to reduce fraud. |
| Chargeback | A reversal of a payment initiated by the cardholder’s bank, usually due to disputes such as fraud, unauthorized transactions, or dissatisfaction with goods or services. |
| Fallback | An alternative or the same Partner (re)used when the primary payment attempt fails, ensuring the transaction can still be completed. |
| Frictionless | Refers to a transaction flow where the customer can complete a payment without additional verification steps. |
| HPP | Hosted Payment Page is a payment page provided by us where customers enter their payment details. The page is hosted by us, keeping sensitive data off your servers while enabling seamless transaction processing. |
| Merchant Contract | Represents your connection with a Partner and is established on the required credentials that differ per Partner. Each Merchant Contract has its settings: settlement currency, payment channel, payment methods. In certain use cases, there could be more than one merchant contract for the same Partner. |
| Partner | An external provider to which you can establish a connection (Merchant Contract). |
| Payment Channel | Describes where the transaction takes place: e-commerce, recurring, moto (Mail Order Telephone Order), pos (Point of Sales). |
| Retries | Represent the repeated attempts (with the same Partner and other Partner in total) to process a payment after an initial transaction fails. |
| Routing Matrix | A feature that allows you creating routing rules that will apply for the selected merchant account. |
| SCA | Strong Customer Authentication is a security measure requiring at least two forms of verification to authenticate electronic payments and reduce fraud. |
| SCA Exemption | A provision that lets eligible transactions skip Strong Customer Authentication under specific conditions. It could be requested but does not guarantee being accepted by the issuer. |
| Tokenization | Tokenization replaces sensitive payment data with a secure, non-sensitive token for safe card data processing. |
Updated 21 days ago
