Glossary

A time span within which operations that have been processed are summed up.

This time span is equivalent to the period of 24 hours with the length variation due to daylight savings taken into account. The beginning and the end of the operation day in different cases varies depending on a number of factors (for example, the time zone in which the merchant operates). For more information about these factors, contact your account manager or the technical support.

A project which defines interaction between the merchant's web service and the payment platform.

Each project is characterised by a set of parameters which specify how payments are executed and how the interaction with the web service is organised (for example, the way callbacks are handled). The Rocketpay technical support specialists are in charge of registering and setting up the project's parameters, and merchants are provided with the IDs of their projects for working with the platform.

In addition, depending on the context, the term project can be used in this documentation to refer to other things, for example, when web service development projects of the merchant are mentioned.

A series of actions performed in order to execute the merchant's request for transferring funds between the merchant and the customer or the customer and the third party.

The funds can be transferred from the customer to the merchant (then it is a purchase) or from the merchant to the customer (then it is a payout). The funds can also be transferred from the customer to the third party (then the payment is classified as money transfer). Only processed purchases can be refunded, thus refunds do not constitute a separate payment type. At the same time, account verification is classified as a separate payment type which includes transferring a zero amount or placing a hold for a specified amount on the customer's card account and the subsequent cancellation of this hold.

At the moment, the following payment types are supported in the Rocketpay payment platform:

• purchase—one-time transfer of funds from the customer to the merchant, in one or two steps, by using one of the interfaces.
• invoice—payment link purchase in one or two steps.
• recurring—COF purchase on demand or with automatic debiting.
• payout—transfer of funds from the merchant to the customer.
• money transfer—card-to-card money transfer.
• account verification—payment instrument validity check.

More information about payments as well as requests and operations used for working with payments can be found at Payment types, operations and payments.

A sequence of actions which is logically complete and which is carried out as part of the payment execution.

To illustrate, three operations auth, capture, and refundare executed as part of a purchase.For more information about payments and operations, see Payment types, operations and payments.

A payment which can be processed only if the customer consents to have their payment credentials stored and used; the debiting of funds is performed on the basis of the provided consent and can be initiated by the customer or by the merchant.

These payments can require authentication, i.e. verifying the authenticity of the payment instrument (for example, by entering the card verification code), or they can be processed without it. COF payments with authentication include purchases with token or saved payment instrument data; COF payments without authentication include recurring purchases (one-click, auto- and regular purchases).

A COF purchase with each debiting of funds initiated by the customer.

For example, an online cinema customer can pay for renting one or more movies using saved card data without providing the card verification code.

A COF purchase with nonscheduled debiting of funds for a fixed or variable amount initiated by the merchant once or multiple times.

For example, an autopurchase is relevant when the available balance of the customer's account gets lower than the specified threshold; in this case, the customer's card can be debited automatically to add funds to the account.

A COF purchase with a series of scheduled debiting payments for a fixed amount and without a specified date for the last payment initiated by the merchant.

For example, the card of an online cinema customer is charged monthly for a fixed amount to pay for movie streaming subscription.

A system message which is an HTTP POST request with a specific structure sent to a URL provided by the merchant when the specified conditions are met.

Callbacks pass information to merchants: for example, that they need to redirect the customer to the provider's website, that an operation was executed with a certain result, or that a token was created. The structure, URLs, and events that trigger callbacks are configured according to the merchant's needs. More information can be found at Callbacks in Gate.

A string generated from a set of data to be signed with the use of a secret key. It is used for ensuring authenticity and integrity of data which is transferred in requests and callbacks between merchants and Rocketpay.

More information on generating signature can be found at Signature generation and verification.

An identifier that refers to the sensitive data to safeguard it.

In the Rocketpay payment platform, tokens are generated for payment card data and are used for ensuring secure communication of this data between Rocketpay and merchants during payment processing. In addition, specialized API tokens associated with specific user accounts are used for accessing Data API.

An organisation which acts as a global payment technology company that provides services such as authorization, processing, clearing and settlement of financial payments as well as managing and processing diverse payment data.

Global card organisations establish cooperation between acquirers (on behalf of merchants) and issuers (on behalf of customers).

A company which is a member of the card organisation (global or domestic) and which issues payment cards in accordance with the card organisation’s rules.

Payment cards offered by the issuer can be used by customers for making payments.

An identifier which characterises the primary business activity of the merchant and which is assigned by the acquirer in accordance with the rules of card organisations.

For example, code 7372 corresponds to computer programming, integrated systems design, and data processing services, while code 8299 corresponds to educational services. Depending on the code assigned to the merchant, different fees can apply to the processing of operations by the payment system, and certain operation types (for example, increasing the authorized amount) may not be allowed.

An identifier which provides information about the issuer of the payment card and the properties of this card.

PAN is generated according to the specific rules, is usually located on the front of the payment card, and is necessary for any operations with cards.

A standard for protecting cardholder data.

PCI DSS is developed by the Payment Card Industry Security Standards Council (PCI SSC) and defines specific requirements for companies which process, store, or transfer payment card data. Compliance with the up-to-date requirements set forth by this standard is mandatory for all participants involved in processing card payments.

A code used for card authentication.

Card Verification Code 2 (CVC2), Card Verification Value 2 (CVV2), and Card Identification Number (CID) can be used for card-not-present operations. In case of physical cards, these codes are located either on the front or the back of the card while in case of virtual cards, they can be absent and provided to customers in a different way.

Online payment security protocol which is used for cardholder authentication and is based on a three domain model: it includes the acquirer domain, the issuer domain, and the interoperability domain (of the card organisation).

A service provided by global card organisations which allows merchants and acquirers to reduce the risk of payment fraud by comparing the postal address specified by a cardholder when making a payment with the address which is kept on file as current for this cardholder by the issuer.

A category of payments when a cardholder provides the merchant with the payment card data via telephone, mail, fax, or email in order to make a payment.

In certain cases MO/TO payments can be processed without card verification code.