Information on the protection of personal data for QPAY Checkout Page

1. Customizable layout for QPAY Checkout Page

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. Payment method sort order

This feature allows the merchant to define the sort order of the payment methods offered in QPAY Checkout Page. This configuration setting is done via parameter paymenttypeSortOrder. Thus, no additional processing of personal data takes place.

3. 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.

4. 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.

5. Recurring payment

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

6. 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.

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

8. 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.

9. 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.

10. 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.

11. 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.

12. 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.

13. 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.

14. Return of instrument country

This feature allows the merchant to obtain personal data on the country in which the consumer’s payment method was issued via parameter instrumentCountry. However, the consumer remains unknown because the personal data are not known.

15. 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.

16. This feature allows to verify consumer-specific personal data (name, address, etc.), which were forwarded by the merchant, and to inform the merchant of the verification result avsResponseParameters.

17. Display of 3-D Secure transaction for credit card

This feature allows the merchant to display to the consumer information regarding 3-D Secure transaction for the relevant payment on the payment page. This configuration setting on part of QPAY does not imply any additional processing of personal data.

18. 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.

19. Return of hashed credit card number

This feature allows the merchant to obtain the random value hashedPAN, which provides information as to whether the same credit card number has been used for different payment transactions. However, these data don’t permit any conclusions to be drawn as to the person they relate, e.g. card holder.

20. 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.

21. 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.

22. Maximum number of unsuccessful payment attempts

This feature allows the merchant to define the permitted number of unsuccessful payment attempts. This configuration setting is done via parameter maxRetries. Thus, no additional processing of personal data takes place.

23. 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.

24. Extension of QPAY Checkout Page 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.

25. 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.

26. 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.