> ## Documentation Index > Fetch the complete documentation index at: https://docs.dintero.com/llms.txt > Use this file to discover all available pages before exploring further. # Glossary > Definitions of Dintero terms used across the documentation, including wallet, session, transaction, payment profile, payment product type, split payout, and account ID. ## Dintero Checkout | Term | Definition | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Account ID** | The identifier for your Dintero account, used in API paths as `{account_id}` or `{aid}`. The first character is the environment: `T` for sandbox, `P` for production. The same account has both, for example `T12345678` and `P12345678`. | | **Session** | The object you create to start a checkout. Holds the order amount, currency, line items, available payment methods, and the return and callback URLs. Creating one gives you a URL to open or embed. A session results in at most one transaction. See [Creating a session](/docs/checkout/create-session). | | **Transaction** | The record of an actual payment, created when the customer completes the checkout. Holds the payment method used, card details, and status, and is the object you capture, refund, or void. The session references it through `transaction_id`. See [Handling payment](/docs/checkout/after-payment). | | **Payment profile** | A named payment configuration stored on your account, referenced by `profile_id` when creating a session. Decides which payment methods the session offers, so you can change methods in Backoffice without changing integration code. Most accounts have a `default` profile. See [Payment profiles](/docs/checkout/payment-profiles). | | **`merchant_reference`** | Your own reference for the order, set on the session and carried through to the transaction and the callback. Use it to match Dintero's records against your order system. | | **Amount** | Every monetary amount in the API is given in the smallest unit of the currency, so `33890` is 338.90 NOK. This applies to order amounts, line items, shipping, captures, and refunds. | | **`line_id`** | The identifier of a line on the order, unique across all items. You reference it when capturing or refunding part of an order, and it is required for some payment methods. | | **Checkout Express** | A checkout flow where Dintero collects the customer's details and shipping choice inside the checkout, enabled with an `express` object on the session. Some features, such as shipping callbacks and [external payment methods](/docs/checkout/dintero-external), only work in Express sessions. See [Checkout Express](/docs/checkout/express). | | **`callback_url`** | The machine-to-machine notification Dintero sends when a payment completes, as an HTTPS `GET` with `transaction_id`, `session_id`, `merchant_reference`, and `time`. Retried up to 20 times. This is the reliable signal that a payment happened. See [Handling payment](/docs/checkout/after-payment#callback_url). | | **`return_url`** | The URL the customer's browser is redirected to after they complete or cancel the payment. Use it to show a confirmation page, not to record the payment: the customer may lose connectivity or close the browser first. Your integration must handle it arriving in parallel with `callback_url`. | | **Backoffice** | Dintero's merchant web application at [backoffice.dintero.com](https://backoffice.dintero.com/), where you manage account settings, transaction data and products associated with a Dintero account. | ## Payment lifecycle | Term | Definition | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Authorization** | The step where the provider reserves money on the customer's account without moving it. A successful payment leaves the transaction `AUTHORIZED`. The money is not yours until you capture it, and an authorization expires if it is not captured in time. | | **Capture** | Transferring the authorized money to your account, normally when you ship the order. Can be partial and repeated, up to the authorized amount. See [Transaction management](/docs/checkout/transaction-management). | | **Void** | Cancelling an authorized transaction so the reserved money is released back to the customer. Use it when the order will not be fulfilled and nothing has been captured. See [Void/cancel](/docs/checkout/transaction-management#void-cancel). | | **Refund** | Returning captured money to the customer, in full or in part. Cannot exceed the captured amount. To release an authorization that was never captured, void it instead. See [Refund](/docs/checkout/transaction-management#refund). | | **Transaction status** | The state a transaction is in after completion: `AUTHORIZED`, `ON_HOLD`, `CAPTURED`, `FAILED`, or `DECLINED`. See the [transaction state diagram](/docs/checkout/transaction-state-diagram). | | **Payout** | The transfer of captured funds from Dintero to your bank account. | | **Settlement report** | The report generated for each payout to your bank account, used for accounting and reconciliation. Found in Backoffice under **Reports** → **Payout reports**. See [Settlement reports](/docs/checkout/payout-reports-introduction). | ## Payment methods | Term | Definition | | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Payment method** | The way the customer pays: card, wallet, invoice, and so on. The docs also use "payment type" and "payment product" for this, so treat the three as the same concept. The precise machine-readable identifier is the payment product type. | | **Payment product type** | The identifier for a specific payment method, written as `provider.method`. The part before the dot is the provider handling the payment, the part after is the method. Examples: `dintero_psp.creditcard`, `dintero_psp.applepay`, `klarna.klarna`, `swish.swish`. Used to configure a session and to filter what the checkout displays with [`show_payment_type`](/docs/checkout/show-payment-type). | | **Wallet** | A payment method where the customer pays from an app or a device wallet instead of typing card details: [Apple Pay](/docs/checkout/apple-pay/apple-pay-overview), [Google Pay](/docs/checkout/google-pay/google-pay-overview), [Vipps](/docs/checkout/vipps) (Norway), MobilePay (Denmark), and Swish (Sweden). Configured like any other payment method and identified by payment product types such as `dintero_psp.applepay`. Not to be confused with the Wallet service. | | **Wallet service** | A separate product under Loyalty & Virtual Cards that issues and redeems gift cards with a stored balance. Lives under `/v1/accounts/{aid}/wallets/`, uses the `read:wallets` and `write:wallets` scopes, and emits `wallet_transaction` webhook events. Nothing to do with wallet payment methods. See [Create gift cards](/docs/loyalty/wallet-create-gift-card). | | **BNPL** | Buy now, pay later. Invoice and installment methods where a provider pays you up front and collects from the customer later, such as Klarna, Walley, Billie, Kravia, Two, and Instabank. See [test data](/docs/checkout/checkout-testdata). | | **EHF** | The Norwegian electronic invoicing format. Relevant for B2B invoice methods that support sending electronic invoices, such as [Two](/docs/checkout/two). | | **Gift card** | A card with a stored balance, issued and redeemed through the Wallet service and spendable in Dintero Checkout or your own payment flow. Unrelated to wallet payment methods. See [Gift cards](/docs/checkout/gift-cards). | | **External payment method** | A payment method you handle yourself, shown in the checkout under your own label and pay button. Express sessions only. See [External payment method](/docs/checkout/dintero-external). | | **EMD** | Extra merchant data, additional order detail sent to Klarna for travel, events, marketplaces, and digital goods to improve order acceptance. See [Klarna EMD attachments](/docs/checkout/klarna-emd). | | **POS** | Point of sale, the in-store checkout system. Dintero's in-person payments and the Loyalty services are commonly integrated from a POS. See [In-person payments](/docs/checkout/in-person/overview). | | **IPP** | In-person payments, accepting payments on physical Dintero terminals. See [In-person payments](/docs/checkout/in-person/overview). | **"Wallet" means two unrelated things at Dintero.** Enabling a wallet payment method does not require the Wallet service, and the `wallets` scopes are not needed for access to wallet payment methods. ## Cards and security | Term | Definition | | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **PSP** | Payment service provider, the party that processes the payment with the card networks or the payment method. Dintero Checkout routes to several PSPs, and the provider prefix in a payment product type tells you which one handles a given method. `dintero_psp` is Dintero's own. | | **Acquirer** | The institution that processes card payments on the merchant's behalf and moves the funds. Dintero is an acquirer. | | **Issuer** | The bank that issued the customer's card and that approves or declines the payment. | | **Cardholder** | The person the card belongs to. See [PCI DSS compliance](/docs/checkout/merchant-pci-dss-compliance) for what you may and may not store about them. | | **3-D Secure (3DS)** | The authentication step where the card issuer verifies the cardholder during a card payment, often with an app or a one-time code. See the [card test data](/docs/checkout/testdata/dintero-psp/checkout-dintero-cards-testdata) for how to trigger 3DS flows in sandbox. | | **SCA** | Strong Customer Authentication, the level of authentication that shifts fraud liability from you to the issuer. Achieved through 3-D Secure, and for wallets through the device authentication in the wallet app. | | **Liability shift** | Who carries the cost if a payment turns out to be fraudulent. With full SCA the issuer carries it, without it you do. Wallet payments differ by card scheme: see [Vipps](/docs/checkout/vipps) for a worked example. | | **ECI** | Electronic Commerce Indicator, the field on an authorized transaction (`card.eci`) that tells you what level of authentication was performed and therefore who carries the liability. Values differ per card scheme. See [Vipps](/docs/checkout/vipps). | | **Network token** | A card scheme issued stand-in for the real card number, passed to Dintero by wallets such as Vipps instead of the raw card data. | | **PCI DSS** | Payment Card Industry Data Security Standard, the security standard for handling card data. Dintero is a certified Level 1 Service Provider, which keeps your own scope small. See [PCI DSS compliance](/docs/checkout/merchant-pci-dss-compliance). | | **SAQ** | Self-Assessment Questionnaire, how merchants document PCI DSS compliance. Because Dintero handles all card data, most merchants qualify for **SAQ A**, the simplest one. | | **PAN** | Primary Account Number, the card number itself. A replacement card usually keeps the same PAN, which matters when handling stored tokens. | | **CVC** | The security code on the card, which the payer enters to complete a purchase. Still required when paying with a stored payment token in the checkout. | | **MIT** | Merchant initiated transaction, a payment you trigger without the payer being present, for example an unscheduled charge on a stored card. Requires approval from your account manager. See [Tokenization](/docs/checkout/tokenization). | | **Payment token** | A stored stand-in for a card that prefills the card in the checkout, where the payer still enters the CVC. With approval it can also be used for merchant initiated transactions. See [Tokenization](/docs/checkout/tokenization). | | **Recurrence token** | A stored stand-in for a card that charges it without payer interaction, for recurring billing. Only some providers issue these. Providers that do not, such as Dintero PSP and Bambora, use payment tokens for recurring payments instead. | | **OTP** | One-time password, a single-use code sent to the customer to confirm their identity during a payment. | | **SSN** | Social security number, the national identity number used to identify a customer for some invoice and financing methods in the Nordics. | ## Split payout | Term | Definition | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Split payout** | Splitting a single Checkout payment across multiple merchants, for marketplaces and platforms. See [Split payout overview](/docs/checkout/split-payment/split-overview). | | **Seller** | A merchant you onboard onto your platform so they can receive part of a split payment. | | **Payout destination** | The registered account a seller's share of a payment is paid out to, referenced by `payout_destination_id`. Requires completed KYC. See [Add payout destinations](/docs/checkout/split-payment/add-payout-destinations). | | **Merchant of record** | The party legally responsible for a transaction. Aggregators must specify it on each order with `store.payout_destination_id`. See [Creating a split session](/docs/checkout/split-payment/creating-split-session). | | **Marketplace / Aggregator** | The two split payout account types. Only aggregators have to specify the merchant of record on each transaction. Dintero tells you which one you are during onboarding. | | **KYC** | Know Your Customer, the verification of a business and its owners that Dintero's KYC department runs before a payout destination is approved. | | **Fund transfer** | Moving money from one seller's payout destination to another, processed asynchronously and shown in the settlement report. See [Fund transfer](/docs/checkout/split-payment/fund-transfer). |