Information on the protection of personal data for QMORE Checkout Seamless

Information on the Protection of Personal Data for QMORE Checkout Seamless

This chapter provides information on all data that are processed by our solution QMORE Checkout Seamless.

When ordering QMORE Checkout Seamless, the merchant may acquire:

  • 1 basic solution, optionally extendable with

  • 1 to N payment methods, and/or

  • 0 to N optional and additional features

Go to section Payment method selection in chapter Basic Solution to simulate the processing of data (parameters) for a given payment transaction and the selected payment method. Furthermore, section Additional Features provides additional information on the processing of data (parameters) for each feature that was added to the basic solution.

For any further questions regarding data protection details and individual parameters, e.g. data subjects, categories of data, etc., consult privacy parameter for additional information.

Basic Solution

Data processing according to payment method

Go to section Payment method selection to simulate the processing of data (parameters) for a given payment transaction and the selected payment method. The displayed data refer to

  • data, which the merchant or consumer sends to the QENTA payment interface (so-called input data),

  • data, which QENTA returns to the merchant or consumer (so-called output data).

All indicated parameters need to be processed to ensure that the solution QMORE Checkout Seamless, basic version, meets our contractual obligations to the merchant (purpose of the processing of data):

The displayed parameters are subdivided into

  • parameters processed irrespectively of the payment method (standard)

  • parameters processed dependent on the respective payment method (payment method)

  • parameters entered by the consumer (consumer interaction)

Select Payment Method

Select a payment method:

Credit Card

Table 1. Input Data
Parameter Type Processed data

Required Request Parameters (payment method)

Optional Request Parameters (payment method)

Info

Additional Request Parameters (payment method)

Info

Additional Request Parameters B2B (payment method)

Required Request Parameters (Standard)

Info

Additional Required Request Parameter (Standard)

Info

Optional Request Parameters (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Plugin-Specific Data (Standard)

-

Table 2. Output Data
Parameter Type Processed data

Parameters regarding the status of a payment (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Table 3. Data entered by the consumer
Parameter Type Processed data

Entry of data in QENTA payment page

PAN, CVC, Name, Expiry Date, Issue Date, Cardholder Name

Forwarding of data to QENTA prior to payment initiation

Yes

eps-Überweisung

Table 4. Input Data
Parameter Type Processed data

Required Request Parameters (payment method)

Info

Optional Request Parameters (payment method)

Info

Additional Request Parameters (payment method)

Additional Request Parameters B2B (payment method)

Required Request Parameters (Standard)

Info

Additional Required Request Parameter (Standard)

Info

Optional Request Parameters (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Plugin-Specific Data (Standard)

-

Table 5. Output Data
Parameter Type Processed data

Parameters regarding the status of a payment (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Table 6. Data entered by the consumer
Parameter Type Processed data

Entry of data in QENTA payment page

Bank

Forwarding of data to QENTA prior to payment initiation

No

Giropay

Table 7. Input Data
Parameter Type Processed data

Required Request Parameters (payment method)

Info

Optional Request Parameters (payment method)

Info

Additional Request Parameters (payment method)

Additional Request Parameters B2B (payment method)

Required Request Parameters (Standard)

Info

Additional Required Request Parameter (Standard)

Info

Optional Request Parameters (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Plugin-Specific Data (Standard)

-

Table 8. Output Data
Parameter Type Proce ssed data

Parameters regarding the status of a payment (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Table 9. Data entered by the consumer
Parameter Type Processed data

Entry of data in QENTA payment page

Bank, Account number, Account owner

Forwarding of data to QENTA prior to payment initiation

Yes

Przelewy24

Table 10. Input Data
Parameter Type Processed data

Required Request Parameters (payment method)

Info

Optional Request Parameters (payment method)

Info

Additional Request Parameters (payment method)

Additional Request Parameters B2B (payment method)

Required Request Parameters (Standard)

Info

Additional Required Request Parameter (Standard)

Info

Optional Request Parameters (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Plugin-Specific Data (Standard)

-

Table 11. Output Data
Parameter Type Processed data

Parameters regarding the status of a payment (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Table 12. Data entered by the consumer
Parameter Type Processed data

Entry of data in QENTA payment page

-

Forwarding of data to QENTA prior to payment initiation

No

Sofort

Table 13. Input Data
Parameter Type Processed data

Required Request Parameters (payment method)

Optional Request Parameters (payment method)

Info

Additional Request Parameters (payment method)

Additional Request Parameters B2B (payment method)

Required Request Parameters (Standard)

Info

Additional Required Request Parameter (Standard)

Info

Optional Request Parameters (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Plugin-Specific Data (Standard)

-

Table 14. Output Data
Parameter Type Processed data

Parameters regarding the status of a payment (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Table 15. Data entered by the consumer
Parameter Type Processed data

Entry of data in QENTA payment page

-

Forwarding of data to QENTA prior to payment initiation

No

PayPal

Table 16. Input Data
Parameter Type Processed data

Required Request Parameters (payment method)

Info

Optional Request Parameters (payment method)

Info

Additional Request Parameters (payment method)

Additional Request Parameters B2B (payment method)

Required Request Parameters (Standard)

Info

Additional Required Request Parameter (Standard)

Info

Optional Request Parameters (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Plugin-Specific Data (Standard)

-

Table 17. Output Data
Parameter Type Processed data

Additonal Response Parameters

Info

Parameters regarding the status of a payment (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Table 18. Data entered by the consumer
Parameter Type Processed data

Entry of data in QENTA payment page

-

Forwarding of data to QENTA prior to payment initiation

No

Paysafecard

Table 19. Input Data
Parameter Type Processed data

Required Request Parameters (payment method)

Info

Optional Request Parameters (payment method)

Info

Additional Request Parameters (payment method)

Additional Request Parameters B2B (payment method)

Required Request Parameters (Standard)

Info

Additional Required Request Parameter (Standard)

Info

Optional Request Parameters (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Plugin-Specific Data (Standard)

-

Table 20. Output Data
Parameter Type Processed data

Parameters regarding the status of a payment (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Table 21. Data entered by the consumer
Parameter Type Processed data

Entry of data in QENTA payment page

-

Forwarding of data to QENTA prior to payment initiation

No

Invoice by Payolution

Table 22. Input Data
Parameter Type Processed data

Required Request Parameters (payment method)

Info

Optional Request Parameters (payment method)

Info

Additional Request Parameters (payment method)

Additional Request Parameters B2B (payment method)

Info

Required Request Parameters (Standard)

Info

Additional Required Request Parameter (Standard)

Info

Optional Request Parameters (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Plugin-Specific Data (Standard)

-

Table 23. Output Data
Parameter Type Processed data

Parameters regarding the status of a payment (Standard)

Info

Table 24. Data entered by the consumer
Parameter Type Processed data

Entry of data in QENTA payment page

-

Forwarding of data to QENTA prior to payment initiation

No

SEPA Direct Debit by Hobex

Table 25. Input Data
Parameter Type Processed data

Required Request Parameters (payment method)

Optional Request Parameters (payment method)

Info

Additional Request Parameters (payment method)

Info

Additional Request Parameters B2B (payment method)

Required Request Parameters (Standard)

Info

Additional Required Request Parameter (Standard)

Info

Optional Request Parameters (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Plugin-Specific Data (Standard)

-

Table 26. Output Data
Parameter Type Processed data

Additonal Response Parameters

Info

Parameters regarding the status of a payment (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Table 27. Data entered by the consumer
Parameter Type Processed data

Entry of data in QENTA payment page

Account owner, BIC, IBAN

Forwarding of data to QENTA prior to payment initiation

Yes

SEPA Direct Debit by b4Payment

Table 28. Input Data
Parameter Type Processed data

Required Request Parameters (payment method)

Optional Request Parameters (payment method)

Info

Additional Request Parameters (payment method)

Info

Additional Request Parameters B2B (payment method)

Required Request Parameters (Standard)

Info

Additional Required Request Parameter (Standard)

Info

Optional Request Parameters (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Plugin-Specific Data (Standard)

-

Table 29. Output Data
Parameter Type Processed data

Additonal Response Parameters

Info

Parameters regarding the status of a payment (Standard)

Info

1 to N Optional Custom Parameters (Standard)

Info

Table 30. Data entered by the consumer
Parameter Type Processed data

Entry of data in QENTA payment page

Account owner, BIC, IBAN

Forwarding of data to QENTA prior to payment initiation

Yes

Included Services

The basic version of QMORE already includes various functions that are described in detail below.

Table 31. Included Services
Feature Processing of data and information on the protection of personal data

1. Return of card holder

This feature involves the processing of personal data, i.e. cardholder as the card holder information is sent to the merchant.

2. Return of masked credit card number

This feature involves the processing of personal data, i.e. maskedPan as 10 of a total of 16 to 19 digits of the credit card number are sent to the merchant.

3. Return of transaction reference number

This feature allows the merchant to obtain a unique reference number of the transaction via parameter gatewayReferenceNumber. Thus, no additional processing of personal data takes place.

4. Return of iDEAL consumer data

This feature allows the merchant to obtain detailed information on the consumer, all of which are considered personal data: idealConsumerData.

5. Return of PayPal consumer data

This feature allows the merchant to obtain detailed information on the consumer, all of which are considered personal data: paypalConsumerData.

6. Return of contract number associated with transaction

This feature allows the merchant’s system to obtain the contract number of the processor/acquirer via parameter gatewayContractNumber. Thus, no additional processing of personal data takes place.

7. Return of Sofort. consumer data

This feature allows the merchant to obtain detailed information on the consumer, all of which are considered personal data: sofortConsumerData.

8. Return of SEPA consumer data

This feature allows the merchant to obtain detailed information on the consumer, all of which are considered personal data: SepaConsumerData.

9. Return of credit card expiration date

This feature allows the merchant to obtain the expiration date of the used credit card via parameter expiry. However, this mere date does not permit any conclusions to be drawn as to the person it relates.

10. Selective automatic deposit

Via parameter autodeposit the merchant may define the time of deposit for each individual transaction. This is a configuration setting relating to a decision which has to be made anyway during payment processing. The parameter only defines the time of deposit. Thus, no additional processing of personal data takes place.

11. Selection of credit card brand

This feature allows the merchant to define via the additional parameter financialInstitution which card brands are allowed for payment. Thus, no additional processing of personal data takes place.

12. Unique order number

The parameter orderNumber allows the merchant to unequivocally assign each transaction in order to fulfill organizational requirements. However, these data don’t permit any conclusions to be drawn as to the person they relate.

Additional Features

This chapter provides information on the data processed for each feature that has been added to the basic QMORE Checkout Seamless solution.

All parameters indicated for the respective feature need to be processed to ensure our solution meets the contractual obligations to the merchant (purpose of the processing of data).

Table 32. Optimization of Usability
Feature Processing of data and information on the protection of personal data

1. Customizable layout for QMORE Checkout Seamless

This feature allows the merchant to align QPAY Checkout Page with a given corporate design. The layout adaptation is carried out via a predefined CSS-Template, which is assigned to the merchant’s shopId. Thus, no additional processing of personal data takes place.

2. Additional languages

In order to display the payment window in the language preferred by the consumer, the merchant retrieves the consumer browser language settings, which are forwarded to QENTA via parameter language. Thus, processing of personal data involves the consumer’s language, although the consumer remains unknown because the personal data are not known.

3. Additional currencies

Depending on the merchant’s product portfolio, certain products may be paid in 1 to N currencies. Depending on the product and consumer’s choice, QENTA is informed on the currency via parameter currency. Thus, processing of personal data involves the currency of the merchant’s processed payment transaction.

Table 33. Optimization of Internal Processes
Feature Processing of data and information on the protection of personal data

4. Recurring payment

This feature allows the merchant to carry out recurring payments via parameter recurPayment. Thus, no additional processing of personal data takes place.

5. Additional access to the QPC Payment Center

For the web application of the Merchant Login a new access is set up which does not involve any personal data. A username and password are required for the access. Thus, no additional processing of personal data takes place.

6. Return of masked credit card number

This feature involves the processing of personal data, i.e. maskedPan as 10 of a total of 16 to 19 digits of the credit card number are sent to the merchant.

7. Extension of QMORE Checkout Seamless for back office use

This feature allows the merchant to trigger payment instead of the consumer. However, no further processing of data categories takes place.

Table 34. Security Features
Feature Processing of data and information on the protection of personal data

8. Confirmation notification by e-mail

This feature allows the merchant to obtain, via e-mail sent to the specified e-mail address, all response parameters that would otherwise be received via the confirmUrl. Thus, no additional processing of personal data takes place. To view the respective response information click confirmUrl.

9. Confirmation notification re-delivery attempts

If the merchant’s server is not accessible, this feature allows several re-delivery attempts in order to send the confirmation notification. However, this configuration setting does not imply any additional processing of personal data.