5.11. Glossary

Payment Gateway	GitPay system that provides accepting, processing, storage and transmitting of payment data between members of payment process (Payer, Connecting Party, payment institutions).
Connecting Party	A third-party organization which implements integration to Payment Gateway following API Use-cases using API commands.
Merchant	User account in Payment Gateway provided to the merchant’s representatives.
Manager	User account in Payment Gateway provided to the representatives of PSP or payment institutions.
Reseller	User account in Payment Gateway provided to the agent, which engage merchants for PSP and payment institutions.
Payer	A person who pays for goods or services provided by Connecting Party. Also referred to as Customer.
Sender	A person who initiates the sending of funds from his side to another.
Receiver	A person who requests/receives funds from Sender or Connecting Party.
Acquirer	Member of payment system, which is licensed to accept payment cards.
Issuer	Member of payment system, which is licensed to issue payment cards.
Endpoint	Uniquely identified terminal in Payment Gateway, which is assigned to the Merchant and has to be provided in the commands within Payment Gateway API.
Endpoint Group	A set of endpoints with different currencies consolidated and available as one logical uniquely identified unit, which has to be provided in the commands within Payment Gateway API instead of endpoint.
Master Endpoint	Special endpoints that combine auxiliary endpoints. When making a payment, the Payer can choose the payment method he needs on the payment form. When choosing a payment method, auxiliary transactions on the corresponding endpoints are called on the side of the Payment Gateway, which leads to different payment methods being initiated. Relevant for Payment Cashier integration. See Payment Cashier.
Auxiliary Endpoint	Regular endpoints united by master endpoint with their own settings and forms. Each auxiliary endpoint has its own payment method such as Credit card, Bank Transfer, Cryptocurrency, etc. Relevant for Payment Cashier integration. See Payment Cashier.
Project	Payment Gateway entity which determines the conditions for receiving a payment message and its further routing to the connected Processor.
Gate	A set of parameters, which identify account registered in a third-party processing system. These parameters can be used to process payment data in an external system using the messaging protocol implemented in the Processor.
Processor	Payment Gateway internal entity, which encapsulates interconnection with third-party processing system (e.g. Acquirer).
PAN	Payment card number or Primary account number.
RPI	Recurring Payment Identification number. Identifier of tokenized cardholder data, gathered in initial transaction, or registered without a transaction, that can be used multiple times for recurring transactions. Some Payment Gateway APIs are designed to accept RPI, others are designed to accept Card reference ID. See respective Use-Case for details.
Card reference ID	Identifier of tokenized cardholder data, gathered in initial transaction that can be used multiple times for recurring transactions. Some Payment Gateway APIs are designed to accept RPI, others are designed to accept Card reference ID. See respective Use-Case for details.
Form	Form in which payment data is indicated. In Form APIs, the payment form is hosted on Payment Gateway side. In Direct APIs, the payment form is hosted on Connecting Party side.
ACS	3DS Access Control Server.
3DS Method	A scripting call provided by the 3DS Integrator that is placed on the 3DS Requestor website (the Connecting Party payment form or Payment Gateway payment form). Optionally used to obtain additional browser information to facilitate risk-based decisioning.
PaReq	Payment authentication request message. See PaReq in 3DS Decision Making Schema of the respective Use-Case.
PaRes	Payment authentication response message. See PaRes in 3DS Decision Making Schema of the respective Use-Case.
CReq	Challenge Request Message. See CReq in 3DS Decision Making Schema of the respective Use-Case.
CRes	Challenge Response Message. See CRes in 3DS Decision Making Schema of the respective Use-Case.