The page you’re looking for does not exist. It may have been moved. You can return to the start page, or follow one of the links in the navigation to the left.
+If you arrived on this page by clicking on a link, please notify the owner of the site that the link is broken. +If you typed the URL of this page manually, please double check that you entered the address correctly.
+The link can be controlled based on the request field and what customer see in the checkout can be adjusted.
+There are two types of links that provide different checkout options:
+Create a simple link - the link is used when the merchant doesn’t have a basket and doesn’t need customer-specific shipping and billing data (except consumer e-mail) e.g. donations or membership fees for already existing customers.
+Create a complex link - the link is used if the merchant wants to provide and receive basket, shipping, and billing data from their customers.
+| Name | +Description | +
|---|---|
Basic-Auth (Test) |
+Credentials that integration specialist team provides. |
+
Secret Key (Test) |
+Provided by the integration specialist team. |
+
Base-URL |
+
|
+
| Name | +Description | +
|---|---|
Content-Type |
+
|
+
Authorization |
+
|
+
X-Signature |
+HMAC-SHA512 hashed request body with the cryptographic secret key. |
+
To receive a payment link or a QR code for the link send a POST request to the /links endpoint:
+https://api.qenta.com/link/links
{
+ "amount": "55.00",
+ "basket": {
+ "basketItems": []
+ },
+ "currency": "EUR",
+ "customer": {
+ "billingFirstName": "",
+ "billingLastName": "",
+ "billingPhone": "",
+ "email": "test@qenta.com"
+ },
+ "description": "Test:0000",
+ "displayBasketData": false,
+ "displayBillingData": false,
+ "displayShippingData": false,
+ "enabled": true,
+ "expirationStatus": "Valid",
+ "expired": false,
+ "linkCallLimit": 0,
+ "linkValidFrom": "2023-04-01T12:00",
+ "linkValidTo": "2028-04-01T23:59",
+ "orderReference": "1234512345",
+ "paymentType": "SELECT",
+ "cancelUrl": "https://payments.qenta.com/cancel/",
+ "confirmUrl": "https://yourconfirm.com",
+ "serviceUrl": "https://yourimprint.com",
+ "merchantLogoUrl": "",
+ "successUrl": "https://payments.qenta.com/success/",
+ "failureUrl": "https://payments.qenta.com/failure/",
+ "paymenttypeSortOrder": "CCARD, PayPal, SOFORTUEBERWEISUNG, EPS",
+ "title": "Link_Title"
+}| + + | ++Detailed description of parameters can be checked here. + | +
The payment link and QR code will be received in the response.
+{
+ "id": "{linkId}",
+ "title": "Link_Title",
+ "description": "Test:0000",
+ "expirationStatus": "Valid",
+ "lastPaymentStatus": "No payments",
+ "amount": 55.00,
+ "sales": 0,
+ "orderStats": {
+ "total": 0,
+ "successful": 0,
+ "pending": 0,
+ "inProgress": 0,
+ "canceled": 0,
+ "failed": 0
+ },
+ "clicks": 0,
+ "createdAt": "2023-04-27T06:00:00.000+00:00",
+ "orderReference": "1234512345",
+ "linkValidFrom": "2023-04-01T12:00:00.000+00:00",
+ "linkValidTo": "2028-04-01T23:59:00.000+00:00",
+ "linkCallLimit": 1,
+ "maxRetries": 0,
+ "displayBasketData": false,
+ "displayShippingData": false,
+ "displayBillingData": false,
+ "paymentType": "SELECT",
+ "paymentTypes": "No payments",
+ "paymenttypeSortOrder": "CCARD, PayPal, SOFORTUEBERWEISUNG, EPS",
+ "language": "en",
+ "currency": "EUR",
+ "customer": {
+ "billingFirstName": "",
+ "billingLastName": "",
+ "email": "test@qenta.com",
+ "billingPhone": ""
+ },
+ "basket": {
+ "basketItems": []
+ },
+ "cancelUrl": "https://payments.qenta.com/cancel/",
+ "confirmUrl": "https://yourconfirm.com",
+ "serviceUrl": "https://yourimprint.com",
+ "merchantLogoUrl": "",
+ "successUrl": "https://payments.qenta.com/success/",
+ "failureUrl": "https://payments.qenta.com/failure/",
+ "merchantConfigId": "{merchantConfigId}",
+ "enabled": true,
+ "expired": false,
+ "qrCode": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAPoAAAD6AQAAAACgl2eQAAABtklEQVR4Xu2ZUW7DIBBEkTiAj8TVOZIPYInOm7WjJK3S34zkVUJgefkY7TI4bVufY7b3zFvcQMUNVNxAhYHZFNvq+9D8YDE81l4MoPexaZx9Fzk7yzMfBEiUMl2ZXRNhQ2PjK3EA6lQy5WuZCSxp1GLto1tsHLDccmbGtTzzQYCP/zRzvf7why8HruC8kOtVNUcOgEx04caMmncab2QB3dJ8Xnx89lFYFGDjshXrQiSHG6M0CziUV5k8Hr5QtOP2iwI2TOws2eJy9CQMsMCh0Z3GHI02gSxApUIXybNM67knE4BVDvDoPQpHBcOAHSsGo9kGc1tZFIDG5ZKVUhhfLlEAJnz4iZFdEtNX5MgCCKQVxq7I155MAGi5USbAFYkVzF89+eXAdI3ILxqPI/PWkxmACiSNFrjsZss+kAYwVp4Jj4s0Xhagd+MHLMkSS8mczwEqUMdnPWu5glHARNVGBoG0X6smzAJWPZAgU94Fw85ry30/cFhXp16cemtsry6XA1y/ZI01e0IesB6VklL+Ij2ygEXLncCy2HplAWowH38u9Pb4v8DTtZgAfIobqLiBihuo+B/4ATVh6kzRA/0OAAAAAElFTkSuQmCC",
+ "linkUrl": "https://api.qenta.com/link/pbl/checkout/5e5b54ef-3c57-4142-ba69-dd80fd9ef70b"
+}| + + | ++Detailed description of parameters can be checked here. + | +
{
+ "amount": "55.00",
+ "basket": {
+ "basketItems": [
+ {
+ "articleNumber": "123",
+ "description": "Product Description",
+ "name": "Product",
+ "quantity": "1",
+ "unitGrossAmount": 55.0,
+ "unitNetAmount": 50.0,
+ "unitTaxAmount": 5.0,
+ "unitTaxRate": 10.0
+ }
+ ]
+ },
+ "currency": "EUR",
+ "customer": {
+ "billingAddress": {
+ "city": "Graz",
+ "country": "AT",
+ "countryState": "Steiermark",
+ "street": "Street 1",
+ "zipCode": "8020"
+ },
+ "billingAddress2": {
+ "street": ""
+ },
+ "billingAddress3": {
+ "street": ""
+ },
+ "billingFirstName": "Max",
+ "billingLastName": "Mustermann",
+ "billingPhone": "+4312345678",
+ "email": "test@test.com",
+ "shippingAddress": {
+ "city": "Graz",
+ "country": "AT",
+ "countryState": "Steiermark",
+ "street": "Street 1",
+ "zipCode": "8020"
+ },
+ "shippingAddress2": {
+ "street": ""
+ },
+ "shippingFirstName": "Max",
+ "shippingLastName": "Mustermann",
+ "shippingPhone": "+4312345678"
+ },
+ "description": "Test:0000",
+ "displayBasketData": true,
+ "displayBillingData": true,
+ "displayShippingData": true,
+ "enabled": true,
+ "expirationStatus": "Valid",
+ "expired": false,
+ "linkCallLimit": 0,
+ "linkValidFrom": "2023-04-01T12:00",
+ "linkValidTo": "2028-04-01T23:59",
+ "maxRetries": 0,
+ "orderReference": "1234512345",
+ "paymentType": "SELECT",
+ "cancelUrl": "https://payments.qenta.com/cancel/",
+ "confirmUrl": "https://yourconfirm.com",
+ "serviceUrl": "https://yourimprint.com",
+ "merchantLogoUrl": "",
+ "successUrl": "https://payments.qenta.com/success/",
+ "failureUrl": "https://payments.qenta.com/failure/",
+ "paymenttypeSortOrder": "CCARD, PayPal, SOFORTUEBERWEISUNG, EPS",
+ "title": "Link_Title"
+}| + + | ++Detailed description of parameters can be checked here. + | +
The payment link and QR code will be received in the response.
+{
+ "id": "{linkId}",
+ "title": "Link_Title",
+ "description": "Test:0000",
+ "expirationStatus": "Valid",
+ "lastPaymentStatus": "No payments",
+ "amount": 55.00,
+ "sales": 0,
+ "orderStats": {
+ "total": 0,
+ "successful": 0,
+ "pending": 0,
+ "inProgress": 0,
+ "canceled": 0,
+ "failed": 0
+ },
+ "clicks": 0,
+ "createdAt": "2023-04-27T06:00:00.000+00:00",
+ "orderReference": "1234512345",
+ "linkValidFrom": "2023-04-01T12:00:00.000+00:00",
+ "linkValidTo": "2028-04-01T23:59:00.000+00:00",
+ "linkCallLimit": 0,
+ "maxRetries": 0,
+ "displayBasketData": true,
+ "displayShippingData": true,
+ "displayBillingData": true,
+ "paymentType": "SELECT",
+ "paymentTypes": "No payments",
+ "paymenttypeSortOrder": "CCARD, PayPal, SOFORTUEBERWEISUNG, EPS",
+ "language": "en",
+ "currency": "EUR",
+ "customer": {
+ "billingFirstName": "Max",
+ "billingLastName": "Mustermann",
+ "shippingFirstName": "Max",
+ "shippingLastName": "Mustermann",
+ "billingAddress": {
+ "street": "Street 1",
+ "city": "Graz",
+ "zipCode": "8020",
+ "country": "AT",
+ "countryState": "Steiermark"
+ },
+ "billingAddress2": {
+ "street": ""
+ },
+ "billingAddress3": {
+ "street": ""
+ },
+ "shippingAddress": {
+ "street": "Street 1",
+ "city": "Graz",
+ "zipCode": "8020",
+ "country": "AT",
+ "countryState": "Steiermark"
+ },
+ "shippingAddress2": {
+ "street": ""
+ },
+ "email": "test@test.com",
+ "billingPhone": "+4312345678",
+ "shippingPhone": "+4312345678"
+ },
+ "basket": {
+ "basketItems": [
+ {
+ "name": "Product",
+ "articleNumber": "123",
+ "description": "Product Description",
+ "quantity": 1,
+ "unitGrossAmount": 55.00,
+ "unitTaxAmount": 5.00,
+ "unitTaxRate": 10.0,
+ "unitNetAmount": 50.0
+ }
+ ]
+ },
+ "cancelUrl": "https://payments.qenta.com/cancel/",
+ "confirmUrl": "https://yourconfirm.com",
+ "serviceUrl": "https://yourimprint.com",
+ "merchantLogoUrl": "",
+ "successUrl": "https://payments.qenta.com/success/",
+ "failureUrl": "https://payments.qenta.com/failure/",
+ "merchantConfigId": "{merchantConfigId}",
+ "enabled": true,
+ "expired": false,
+ "qrCode": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAPoAAAD6AQAAAACgl2eQAAABvklEQVR4Xu2YUY6DMAxEI3GAHilXz5E4AJJ33phuUVfq/nYkrIDAeXyMxk6AUZ9jjffMW9xAxw103ECHgTUUjzUeXG+MOkj1XAyg43iUpoQdY/Zt54MAiVJmjKlRO+cD1ZGAktsui6bOuUC1ZfuQa4nA75QulLdZZz4IoNUfSHsNUj2XAnSo3rrYqqz3zMYA9AtmUXsw1djFrAhgUG9Ts3QQLlmv1+QgwLdjYxFW75fLDbFRgHofpuwOeqm66b0+CZCic+2yWW7/eZWZACys8dliUarhJ5OADZnd/gSMjYsC6nC/IK2HJR+vzT0DcIa3xLPqvC22cUGA8nKH4WJT+wu4dlYEcC5ZO9KwSbOU3IoClgBrHO4dZPb3YBigPNsHs5LZNnUEAVQauuiabh8bN7MAT3kTwS9WM5x6NU4GoKOcdLFh3HDhZQHcomsCPzeUq1kJQIcsG091y7dZAKKGf5LglzfEg98LfiwH0HEAwJyWaebPT5IvB1DnV3cJLH9SKUzmAWr86s2d67qalQNUS2Md1lLGy/ybWd8OFCW38MtnAeWP9CwAh/g2n+SZHb2CRQGf4gY6bqDjBjr+B34AyJOJDtJVUa0AAAAASUVORK5CYII=",
+ "linkUrl": "https://api.qenta.com/link/pbl/checkout/c7910e30-ad50-4fe7-9ab7-eff841b63ffb"
+}| + + | ++Detailed description of parameters can be checked here. + | +
There are two ways for gathering information about created links and orders/payments:
+Data transfer object from link by ID - general information from link
+Orders for link - information about every order and/or payment
+| Name | +Description | +
|---|---|
Basic-Auth (Test) |
+Credentials that integration specialist team provides. |
+
Base-URL |
+
|
+
| Name | +Description | +
|---|---|
Content-Type |
+
|
+
Authorization |
+
|
+
For more information about a link send a GET request to the base URL and include the link ID. ID was provided in the initial response for creating a link and the path for orders (/links/{id}):
+https://api.qenta.com/link/links/{id}
{
+ "id": "{linkId}",
+ "title": "Link_Title",
+ "description": "Test:0000",
+ "expirationStatus": "Valid",
+ "lastPaymentStatus": "No payments",
+ "amount": 55.00,
+ "sales": 0,
+ "orderStats": {
+ "total": 0,
+ "successful": 0,
+ "pending": 0,
+ "inProgress": 0,
+ "canceled": 0,
+ "failed": 0
+ },
+ "clicks": 0,
+ "createdAt": "2023-04-27T06:00:00.000+00:00",
+ "orderReference": "1234512345",
+ "linkValidFrom": "2023-04-01T12:00:00.000+00:00",
+ "linkValidTo": "2028-04-01T23:59:00.000+00:00",
+ "linkCallLimit": 0,
+ "maxRetries": 0,
+ "displayBasketData": true,
+ "displayShippingData": true,
+ "displayBillingData": true,
+ "paymentType": "SELECT",
+ "paymentTypes": "No payments",
+ "paymenttypeSortOrder": "CCARD, PayPal, SOFORTUEBERWEISUNG, EPS",
+ "language": "en",
+ "currency": "EUR",
+ "customer": {
+ "billingFirstName": "Max",
+ "billingLastName": "Mustermann",
+ "shippingFirstName": "Max",
+ "shippingLastName": "Mustermann",
+ "billingAddress": {
+ "street": "Street 1",
+ "city": "Graz",
+ "zipCode": "8020",
+ "country": "AT",
+ "countryState": "Steiermark"
+ },
+ "billingAddress2": {
+ "street": ""
+ },
+ "billingAddress3": {
+ "street": ""
+ },
+ "shippingAddress": {
+ "street": "Street 1",
+ "city": "Graz",
+ "zipCode": "8020",
+ "country": "AT",
+ "countryState": "Steiermark"
+ },
+ "shippingAddress2": {
+ "street": ""
+ },
+ "email": "test@test.com",
+ "billingPhone": "+4312345678",
+ "shippingPhone": "+4312345678"
+ },
+ "basket": {
+ "basketItems": [
+ {
+ "name": "Product",
+ "articleNumber": "123",
+ "description": "Product Description",
+ "quantity": 1,
+ "unitGrossAmount": 55.00,
+ "unitTaxAmount": 5.00,
+ "unitTaxRate": 10.000,
+ "unitNetAmount": 50.00
+ }
+ ]
+ },
+ "cancelUrl": "https://payments.qenta.com/cancel/",
+ "confirmUrl": "https://yourconfirm.com",
+ "serviceUrl": "https://yourimprint.com",
+ "merchantLogoUrl": "",
+ "successUrl": "https://payments.qenta.com/success/",
+ "failureUrl": "https://payments.qenta.com/failure/",
+ "merchantConfigId": "{merchantConfigId}",
+ "enabled": true,
+ "expired": false,
+ "qrCode": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAPoAAAD6AQAAAACgl2eQAAABuklEQVR4Xu2Yy43jMBBECTAAhaTUGZICINDbr0qD0fowc50C1KANqfh4aPSP9qifbY1P5cNewPYCthewCVij7VjjKK9ZtZG8FwP0Zx+9Fpj0frUeBLRTrczrHOPs9/42nAj0IkLHmtfIBUrRqeucrQQCpRybbKl2CNatBwGO0X4uJO+lALZF4agJ1PVQYwBXCh243AH0Wo9gJQA9PiR2dK7hVsYRNbQgAO/oXWz1g9INOAqgX7VfUhaT/fARjuYAem07HLVT5U/4ogC6VjHTybetqPXSySAA75RsMPZuqvajgGXRu4SpZcY9TA5AE+aW0qoybWssUkpJAG46x6b62KaC7qglAdyvbtc0SoZE9BzAycYopF7oAHf4sgBa8fcV5Q6TLQegFTtG/U03U/k4CYOAYhcdRuVDpP6vrAiAfLuTrb0u4McdJgJAxMeTIUKM1iBwZxRgu0V5t0pHogC2uJ98zRGKiL8XfCwG6I+SjSbmYLHzvMMkANvXqq8+vHF7iAwE9DD0PBn3FQiUZ0q5lfVk+QzWXweKlFsWN4vca3+zACKk/zy3fkwp686S5QA/2QvYXsD2ArbfgX+HOoq+BMD9uwAAAABJRU5ErkJggg==",
+ "linkUrl": "https://api.qenta.com/link/pbl/checkout/0bbc89de-ef46-4b01-a225-972b552c976e"
+}For more information about every order/payment processed with a link send a GET request to the base URL and include the link ID. ID was provided in the initial response for creating a link and the path for orders (/links/{id}/orders):
+https://api.qenta.com/link/links/{id}/orders
{
+ "items": [
+ {
+ "id": "{orderId}",
+ "linkConfigId": "{linkId}",
+ "amount": 55.00,
+ "currency": "EUR",
+ "paymentType": {
+ "id": 3,
+ "name": "CCARD",
+ "description": "Credit Card, Maestro SecureCode"
+ },
+ "financialInstitution": "Visa",
+ "language": "de",
+ "orderNumber": "13425114",
+ "paymentState": {
+ "id": 1,
+ "state": "SUCCESS"
+ },
+ "orderDescription": "Test:0000",
+ "purchaseInformation": {
+ "additionalParameters": [],
+ "orderDescription": "Test:0000",
+ "orderReference": "123451234557226",
+ "consumerIpAddress": "10.137.4.3",
+ "consumerUserAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0",
+ "customerStatement": "123451234557226",
+ "consumerBillingFirstName": "Max",
+ "consumerShippingFirstName": "Max",
+ "consumerBillingLastName": "Mustermann",
+ "consumerShippingLastName": "Mustermann",
+ "consumerEmail": "test@test.com",
+ "consumerBillingAddress1": "Street 1",
+ "consumerShippingAddress1": "Street 1",
+ "consumerBillingCity": "Graz",
+ "consumerShippingCity": "Graz",
+ "consumerBillingCountry": "AT",
+ "consumerShippingCountry": "AT",
+ "consumerBillingZipCode": "8020",
+ "consumerShippingZipCode": "8020",
+ "basketItem": [
+ {
+ "name": "Product",
+ "articleNumber": "123",
+ "description": "Product Description",
+ "quantity": 1,
+ "unitGrossAmount": 55.00,
+ "unitTaxAmount": 5.00,
+ "unitTaxRate": 10.000,
+ "unitNetAmount": 50.00
+ }
+ ],
+ "basketItems": "1",
+ "consumerBillingAddress2": "",
+ "consumerBillingState": "Steiermark",
+ "consumerShippingAddress2": "",
+ "consumerShippingState": "Steiermark",
+ "consumerShippingPhone": "+4312345678",
+ "consumerBirthDate": "2002-04-27"
+ },
+ "timestamp": "2023-04-27T13:11:00.000+00:00",
+ "createdAt": "2023-04-27T13:10:00.000+00:00"
+ },
+ {
+ "id": "{orderId}",
+ "linkConfigId": "{linkId}",
+ "amount": 55.00,
+ "currency": "EUR",
+ "paymentType": {
+ "id": 3,
+ "name": "CCARD",
+ "description": "Credit Card, Maestro SecureCode"
+ },
+ "financialInstitution": "MC",
+ "language": "de",
+ "orderNumber": "7430895",
+ "paymentState": {
+ "id": 1,
+ "state": "SUCCESS"
+ },
+ "orderDescription": "Test:0000",
+ "purchaseInformation": {
+ "additionalParameters": [],
+ "orderDescription": "Test:0000",
+ "orderReference": "123451234519526",
+ "consumerIpAddress": "10.137.4.18",
+ "consumerUserAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/112.0",
+ "customerStatement": "123451234519526",
+ "consumerBillingFirstName": "Max",
+ "consumerShippingFirstName": "Max",
+ "consumerBillingLastName": "Mustermann",
+ "consumerShippingLastName": "Mustermann",
+ "consumerEmail": "test@test.com",
+ "consumerBillingAddress1": "Street 1",
+ "consumerShippingAddress1": "Street 1",
+ "consumerBillingCity": "Graz",
+ "consumerShippingCity": "Graz",
+ "consumerBillingCountry": "AT",
+ "consumerShippingCountry": "AT",
+ "consumerBillingZipCode": "8020",
+ "consumerShippingZipCode": "8020",
+ "basketItem": [
+ {
+ "name": "Product",
+ "articleNumber": "123",
+ "description": "Product Description",
+ "quantity": 1,
+ "unitGrossAmount": 55.00,
+ "unitTaxAmount": 5.00,
+ "unitTaxRate": 10.000,
+ "unitNetAmount": 50.00
+ }
+ ],
+ "basketItems": "1",
+ "consumerBillingAddress2": "",
+ "consumerBillingState": "Steiermark",
+ "consumerShippingAddress2": "",
+ "consumerShippingState": "Steiermark",
+ "consumerShippingPhone": "+4312345678",
+ "consumerBirthDate": "2002-04-27"
+ },
+ "timestamp": "2023-04-27T13:18:00.000+00:00",
+ "createdAt": "2023-04-27T13:17:00.000+00:00"
+ }
+ ],
+ "currentPage": 0,
+ "totalItems": 2,
+ "totalPages": 1
+}| + + | ++Detailed descriptions for parameters from the example are here. + | +
With the following commands, the merchant is able to alter the accessibility of their links, which are already created:
+Disable link by ID - PUT call for deactivation of an existing link.
+Reactivate link by ID - PUT call for reactivation an existing link.
+Delete link by ID - DELETE call for completely deleting an existing link.
+| Name | +Description | +
|---|---|
Basic-Auth (Test) |
+Credentials that integration specialist team provides. |
+
Base-URL |
+
|
+
| Name | +Description | +
|---|---|
Content-Type |
+
|
+
Authorization |
+
|
+
PUT request with whom the active link can be disabled, so the consumer is not able to call the link again. To check if a link is enabled or not the data transfer object from the link by ID command should be executed. In the response, the merchant will receive the parameter enabled with the value true or false.
Send a PUT request to the base URL and include the link ID, which was provided in the initial response for creating a link and the correct path (/links/disable/”id”).
+https://api.qenta.com/link/links/disable/{id}
PUT request with whom the active link can be reactivated using the link ID.
+| + + | +
+To check, if a link is disabled or not, send a data transfer object from link by ID request first and check the response field expirationStatus. If the value "Deactivated" is returned, the link is disabled and can be reactivated. If the returned value is "Expired", the link can’t be reactivated anymore.
+ |
+
If a link has already expired (expiry date for linkValidTo has passed), the link is not reachable either, even if the state "enabled" with the value "false" is set.
Send a PUT request to the base URL and include the link ID, which was provided in the initial response for creating a link and the correct path (/links/reactivate/”id”).
+https://api.qenta.com/link/links/reactivate/{id}
DELETE call with whom the link is completely deleted.
+| + + | ++If this command is executed, the information from the link can’t be gathered anymore. + | +
Send a DELETE request to the base URL and include the link ID, which was provided in the initial response for creating a link and the correct path (/links/”id”).
+https://api.qenta.com/link/links/{id}
With these commands, more than one link at once can be disabled or deleted.
+Disable batch - PUT call for deactivation of a batch of existing links.
+Delete batch - DELETE call for completely deleting a batch of existing links.
+| Name | +Description | +
|---|---|
Basic-Auth (Test) |
+Credentials that integration specialist team provides. |
+
Base-URL |
+
|
+
| Name | +Description | +
|---|---|
Content-Type |
+
|
+
Authorization |
+
|
+
PUT request with whom more than one link can be disabled at once using link IDs.
+Provide the link IDs in the request body and send a PUT request to the base URL and the correct path (/links/disable).
+https://api.qenta.com/link/links/disable
[
+ "{id}",
+ "{id}",
+ "{id}"
+]DELETE call with whom more than one link can be deleted at once using link IDs.
+| + + | ++If this command is executed, the information from the link can’t be gathered anymore. + | +
Send a HTTP DELETE request to the base URL and include the link ID, which was provided in the initial response for creating a link and the correct path (/links/delete).
+https://api.qenta.com/link/links/delete
[
+ "{id}",
+ "{id}",
+ "{id}"
+]| Name | +Description | +
|---|---|
|
+Title of the link that will be shown in the portal description. |
+
|
+Request parameter |
+
|
+Currency of the requested amount. Request parameter |
+
|
+Request parameter |
+
|
+Determines date and time from when the link is valid. |
+
|
+Determines date and time until the link is valid. |
+
|
+Determines how many times a link can be called. |
+
|
+Determines if basket data are shown in the checkout or not. If the consumer data are not needed, set to "false" for a simple link. |
+
|
+Determines if customer shipping data are shown in the checkout or not (will be shown anyway if it is sent within customer parameters). |
+
|
+Determines if customer shipping data are shown in the checkout or not (will be shown anyway if it is sent within customer parameters). |
+
|
+Shows if a link is enabled/accessible or not. |
+
|
+Request parameter |
+
|
+Determines the sort order of payment types, shown on the checkout page. |
+
|
+Amount to pay - needs to be sent, if the merchant doesn’t provide basket fields. Request parameter |
+
|
+Customer specific parameters - either provided in the request or entered by customers.
+Request parameters for consumerShipping and consumerBilling:
Request Parameters basketItems: |
+
|
+URL of online shop where the consumer is forwarded when the payment process has been completed. Request parameter |
+
|
+URL of the page where consumer is forwarded when the payment process has been canceled. Request parameter |
+
|
+URL of online shop where consumer is forwarded when the payment process has failed for some reason. Request parameter |
+
|
+URL of a web page in an online shop that informs the consumer about the different possibilities to get in contact with the merchant. Request parameter |
+
|
+URL to an image on the web server, that will be displayed during the payment process. Request parameter |
+
| Name | +Description | +
|---|---|
|
+Link ID created by QENTA. |
+
|
+Status that are showing if the link is still available to call or not. |
+
|
+Date and time of the last time the link has been called. |
+
|
+Date and time of the last successful payment of the link. |
+
|
+
+
+The last payment status can be: +
+
|
+
|
+Amount to pay within the link. |
+
|
+Sum of all successful payment amounts made with the link. |
+
|
+
+
+Shows the sums of transactions, depending on their states: +
+
|
+
|
+Number of how many times a link has been clicked/called. |
+
|
+Date and time the link has been created. |
+
|
+Payment type used by the customer. |
+
Parameters that will be received for gathering order specific commands (Orders for Link).
+| Parameter | +Description | +
|---|---|
| + | The financial institution, chosen by the customer. |
+
|
+The language on the checkout page, chosen by the customer. |
+
|
+Payment related orderNumber, created by the QENTA. |
+
|
+Fields that are indicating whether the payment was successful or not
|
+
|
+|
| + | Description of the order. |
+
|
+Consumer related parameter fields: |
+
basketItem |
+Contains more details about the basket fields: |
+
| + + | ++Detailed description of the consumer data parameters are here. + | +
Backend operations both for QMORE Checkout Seamless and QPAY Checkout Page are called by a server-to-server request from thr web server to the QENTA Checkout Server. These operations are possible to call automatically from the backend or manually from the user interface. They’re subdivided into two categories:
+To start an operation a request needs to be sent from the web server to the following URL at the QENTA Checkout Server: https://api.qenta.com/page/toolkit.php
| + + | ++Here is the example. + | +
Enable server-to-server requests within the configuration of the web server.
+| + + | ++Parameters should be specified depending on the operation that will be used. With getOrderDetails list of all possible transaction-based backend operations can be obtained. + | +
For a proper request set the correct HTTP header elements within request:
+| HTTP header parameter | +Description and value | +
|---|---|
|
+Domain name of the server, value: |
+
|
+User agent string of client |
+
|
+MIME type of the body, value: |
+
|
+Length of the body in bytes |
+
|
+Type of connection, value: |
+
| + + | ++Incorrect setting of the header parameters results in an HTTP 403 error message of the QENTA Checkout Server. + | +
To start an operation set all required parameters to their corresponding values.
+Optional request parameters for backend operations.
+| Payment Method | +Acquirer | +approve Reversal | +deposit | +deposit Reversal | +getOrder Details | +recur Payment | +refund | +refund Reversal | +
|---|---|---|---|---|---|---|---|---|
| + | Riverty |
+✔ |
++ | + | ✔ |
++ | ✔ |
++ |
Riverty (Installment) |
+✔ |
++ | + | ✔ |
++ | ✔ |
++ | |
| + | Paysafe Group |
++ | + | + | ✔ |
++ | + | + |
| + | Paysafe Group |
++ | + | + | ✔ |
++ | + | + |
| + | card complete |
+✔ |
+✔[1] |
+✔ |
+✔ |
+✔[3] |
+✔ |
++ |
Emerchantpay |
+✔ |
+✔ |
++ | ✔ |
+✔ |
+✔ |
++ | |
Hobex |
+✔ |
+✔[1] |
+✔[4] |
+✔ |
+✔ |
+✔ |
++ | |
Payone (SIX AT/Paylife) |
+✔ |
+✔ |
+✔[4] |
+✔ |
+✔ |
+✔ |
+✔[5] |
+|
Payone (B+S) |
+✔ |
+✔[1] |
+✔ |
+✔ |
+✔ |
+✔ |
+✔[5] |
+|
Worldline (SIX EU) |
+✔ |
+✔[1] |
+✔[4] |
+✔ |
+✔ |
+✔ |
+✔[5] |
+|
Wordline |
+✔ |
+✔[1] |
+✔[4] |
+✔ |
+✔ |
+✔ |
+✔[5] |
+|
SIX CH |
+✔ |
+✔[1] |
+✔[4] |
+✔ |
+✔ |
+✔ |
+✔[5] |
+|
Concardis |
+✔ |
+✔[1] |
+✔ |
+✔ |
+✔ |
+✔ |
+✔[5] |
+|
Diners |
+✔ |
+✔[1] |
+✔ |
+✔ |
+✔ |
+✔ |
+✔[5] |
+|
Amex |
+✔ |
+✔[1] |
+✔ |
+✔ |
+✔ |
+✔ |
+✔[5] |
+|
First Cash Solution |
+✔ |
+✔[1] |
+✔[4] |
+✔ |
+✔ |
+✔ |
+✔[5] |
+|
| + | Paysafe Group |
++ | + | + | ✔ |
++ | + | + |
| + | Local bank |
++ | + | + | ✔ |
++ | ✔[3] |
++ |
Invoice (by Payolution) |
+Payolution (by Unzer) |
+✔ |
+✔[1] |
++ | ✔ |
++ | ✔ |
++ |
| + | Paysafe Group |
++ | + | + | ✔ |
++ | + | + |
| + | Paypal |
+✔[6] |
++ | + | ✔ |
+✔[3] |
+✔ |
++ |
| + | Paysafe Group |
++ | + | + | ✔ |
++ | + | + |
| + | Paysafe Group |
++ | + | + | ✔ |
++ | + | + |
| + | Local bank |
++ | + | + | ✔ |
++ | + | + |
| + | Paysafe Group |
++ | + | + | ✔ |
++ | + | + |
| + | Hobex |
++ | + | ✔[4] |
+✔ |
+✔ |
++ | + |
b4payment/ |
++ | + | + | ✔ |
+✔ |
++ | + | |
| + | Klarna |
++ | + | + | ✔ |
+✔[7] |
++ | + |
| Acquirer | +card complete | +|
|---|---|---|
Transaction-Based Operations |
++ | ✔ |
+
| + | ✔[1] |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔[3] |
+|
| + | ✔ |
+|
| + | + | |
Acquirer |
+Emerchantpay |
+|
Transaction-Based Operations |
++ | ✔ |
+
| + | ✔ |
+|
| + | + | |
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | + | |
Acquirer |
+Hobex |
+|
Transaction-Based Operations |
++ | ✔ |
+
| + | ✔[1] |
+|
| + | ✔[4] |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | + | |
Acquirer |
+Payone (SIX AT/Paylife) |
+|
Transaction-Based Operations |
++ | ✔ |
+
| + | ✔ |
+|
| + | ✔[4] |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔[5] |
+|
Acquirer |
+Payone (B+S) |
+|
Transaction-Based Operations |
++ | ✔ |
+
| + | ✔[1] |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔[5] |
+|
Acquirer |
+Worldline (SIX EU) |
+|
Transaction-Based Operations |
++ | ✔ |
+
| + | ✔[1] |
+|
| + | ✔[4] |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔[5] |
+|
Acquirer |
+Wordline |
+|
Transaction-Based Operations |
++ | ✔ |
+
| + | ✔[1] |
+|
| + | ✔[4] |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔[5] |
+|
Acquirer |
+SIX CH |
+|
Transaction-Based Operations |
++ | ✔ |
+
| + | ✔[1] |
+|
| + | ✔[4] |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔[5] |
+|
Acquirer |
+Concardis |
+|
Transaction-Based Operations |
++ | ✔ |
+
| + | ✔[1] |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔[5] |
+|
Acquirer |
+Diners |
+|
Transaction-Based Operations |
++ | ✔ |
+
| + | ✔[1] |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔[5] |
+|
Acquirer |
+Amex |
+|
Transaction-Based Operations |
++ | ✔ |
+
| + | ✔[1] |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔[5] |
+|
Acquirer |
+First Cash Solution |
+|
Transaction-Based Operations |
++ | ✔ |
+
| + | ✔[1] |
+|
| + | ✔[4] |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | ✔[5] |
+|
| Acquirer | +Local bank | +|
|---|---|---|
Transaction-Based Operations |
++ | + |
| + | + | |
| + | + | |
| + | ✔ |
+|
| + | + | |
| + | ✔[3] |
+|
| + | + | |
| Acquirer | +Payolution (by Unzer) | +|
|---|---|---|
Transaction-Based Operations |
++ | ✔ |
+
| + | ✔[1] |
+|
| + | + | |
| + | ✔ |
+|
| + | + | |
| + | ✔ |
+|
| + | + | |
| Acquirer | +Paypal | +|
|---|---|---|
Transaction-Based Operations |
++ | ✔[6] |
+
| + | + | |
| + | + | |
| + | ✔ |
+|
| + | ✔[3] |
+|
| + | ✔ |
+|
| + | + | |
Payment Method |
++ | |
Acquirer |
+Paysafe Group |
+|
Transaction-Based Operations |
++ | + |
| + | + | |
| + | + | |
| + | ✔ |
+|
| + | + | |
| + | + | |
| + | + | |
Payment Method |
++ | |
Acquirer |
+Paysafe Group |
+|
Transaction-Based Operations |
++ | + |
| + | + | |
| + | + | |
| + | ✔ |
+|
| + | + | |
| + | + | |
| + | + | |
Payment Method |
++ | |
Acquirer |
+Paysafe Group |
+|
Transaction-Based Operations |
++ | + |
| + | + | |
| + | + | |
| + | ✔ |
+|
| + | + | |
| + | + | |
| + | + | |
Payment Method |
++ | |
Acquirer |
+Paysafe Group |
+|
Transaction-Based Operations |
++ | + |
| + | + | |
| + | + | |
| + | ✔ |
+|
| + | + | |
| + | + | |
| + | + | |
Payment Method |
++ | |
Acquirer |
+Paysafe Group |
+|
Transaction-Based Operations |
++ | + |
| + | + | |
| + | + | |
| + | ✔ |
+|
| + | + | |
| + | + | |
| + | + | |
Payment Method |
++ | |
Acquirer |
+Paysafe Group |
+|
Transaction-Based Operations |
++ | + |
| + | + | |
| + | + | |
| + | ✔ |
+|
| + | + | |
| + | + | |
| + | + | |
Payment Method |
++ | |
Acquirer |
+Paysafe Group |
+|
Transaction-Based Operations |
++ | + |
| + | + | |
| + | + | |
| + | ✔ |
+|
| + | + | |
| + | + | |
| + | + | |
| Acquirer | +Local bank | +|
|---|---|---|
Transaction-Based Operations |
++ | + |
| + | + | |
| + | + | |
| + | ✔ |
+|
| + | + | |
| + | + | |
| + | + | |
Acquirer |
+Riverty(Invoice) |
+|
Transaction-Based Operations |
++ | ✔ |
+
| + | + | |
| + | + | |
| + | ✔ |
+|
| + | + | |
| + | ✔ |
+|
| + | + | |
Acquirer |
+Riverty(Installment) |
+|
Transaction-Based Operations |
++ | ✔ |
+
| + | + | |
| + | + | |
| + | ✔ |
+|
| + | + | |
| + | ✔ |
+|
| + | + | |
| Acquirer | +Hobex | +|
|---|---|---|
Transaction-Based Operations |
++ | + |
| + | + | |
| + | ✔[4] |
+|
| + | ✔ |
+|
| + | ✔ |
+|
| + | + | |
| + | + | |
Acquirer |
+b4payment/SEPA Express |
+|
Transaction-Based Operations |
++ | + |
| + | + | |
| + | + | |
| + | ✔ |
+|
| + | ✔ |
+|
| + | + | |
| + | + | |
Transaction-based operations depend on existing orders, which have been completed by the online shop consumer.
+| Operations | +Description | +
|---|---|
| + | Cancel an approval, typically done by the consumer in the online shop. |
+
| + | Convert an approval into a deposit. |
+
| + | Cancel a deposit. |
+
| + | Return all order details including corresponding payments and credit notes. |
+
| + | Create a new order based on an existing order, typically used for subscriptions. |
+
| + | Create a credit note for an order, typically done by the merchant after the consumer returned an ordered product. |
+
| + | Cancel a credit note. |
+
| + | Create a credit note without dependency on a pre-existing payment. |
+
The availability of a transaction-based operation depends on:
+Financial institution
+Current state of the payment/order
+| + + | ++With getOrderDetails list of all possible transaction-based backend operations can be obtained. + | +
All supported payment methods and their corresponding transaction-based operations can be found in transaction-based operations by payment method.
+Non-transaction-based operations don’t depend on existing orders and are carried out independently of any existing orders.
+The availability of a non-transaction-based operation depends on:
+Financial institution
+approveReversal is the operation that cancels an approval and can be done only when the approval has not yet been debited.
customerId,shopId,toolkitPassword,secret,command,language,orderNumber
Additional required request parameters for approveReversal.
| + + | ++No additional response parameters are returned. + | +
deposit is executed by the merchant if an order of a consumer has been accepted. This operation causes an approval to be converted into a deposit and a daily closing is automatically opened when there is no one already open for this payment method and currency.
deposit can be reversed with the depositReversal when the corresponding daily closing has not yet been done and the financial services provider and the payment method support it.
customerId,shopId,toolkitPassword,secret,command,language,orderNumber,amount,currency
Shopping basket parameters must be sent for a split capture for Riverty and Payolution.
+depositReversal either cancels a deposited payment or converts a deposited payment into an approved payment. This operation can only be done before the day-end closing has been executed.
customerId,shopId,toolkitPassword,secret,command,language,orderNumber,paymentNumber
Additional required request parameters for depositReversal.
| + + | ++No additional response parameters are returned. + | +
getOrderDetails returns all details for a given order including all possible operations, corresponding payments and credit notes.
customerId,shopId,toolkitPassword,secret,command,language,orderNumber
Additional required request parameters for getOrderDetails.
Within the additional response parameters, some parameters will occur more than once, so we use the letters n and m as placeholders for digits. Currently, n is always 1 because getOrderDetails returns only one order and m indicates that there may be more than one payment or credit object returned.
The response parameter enhances the result data of the payment process regarding specific features and functions.
+| Parameter | +Data type | +Description | +
|---|---|---|
| + | Alphabetic, fixed 2. |
+Country of the consumer which has been detected and returned by the financial service provider. |
+
payment.{n}.{m}.instrumentCountry |
+|
|---|---|
Data |
+Value |
+
Data type |
+Alphabetic, fixed 2. |
+
Description |
+Country of the consumer which has been detected and returned by the financial service provider. |
+
The parameter paymentType returns the technical property used for the transaction.
| Value | +Description | +
|---|---|
|
+Credit Card, Maestro SecureCode |
+
|
+Credit Card MOTO |
+
|
+Circle K |
+
|
+CVC |
+
|
+Dollar General |
+
|
+EPS-Überweisung |
+
|
+Hobex SEPA |
+
|
+Invoice by Payolution |
+
|
+Mastercard Maestro |
+
|
+oBucks |
+
|
+PayPal |
+
|
+PagoEfectivo |
+
|
+Paysafecard |
+
|
+Przelewy24 |
+
|
+Riverty |
+
|
+Klarna Sofort |
+
|
+Direct Debit |
+
|
+Safetypay |
+
If the getOrderDetails is carried out for order numbers that are still in progress no statement on the actual or final order state may be retrieved and the message PENDING is returned:
| Message | +errorCode | +paySysMessage | +Status | +
|---|---|---|---|
The final state of the transaction could not yet be determined. |
+
|
+(15/30761)-No payer assigned to EC token. |
+
|
+
Currently, error code 30014 is supported by those payment methods for which the pendingUrl is required or recommended.
If the operation getOrderDetails is carried out, payments in status REJECTED return the following result:
| Message | +errorCode | +paySysMessage | +Status | +
|---|---|---|---|
The financial institution has declined the transaction. Check the data that have entered. |
+
|
+WCP: Auth: Verification failed. |
+
|
+
| + + | +
+paySysMessage depends on the relevant financial service provider’s response.
+ |
+
recurPayment uses the payment information available from a previous order to create a new order and a new payment attempt.
customerId,shopId,toolkitPassword,secret,command,language,orderNumber,sourceOrderNumber,autoDeposit,orderDescription,amount,currency,orderReference,customerStatement,mandateId,mandateSignatureDate,creditorId,dueDate,transactionIdentifier,useIbanBic,merchantTokenizationFlag,periodicType
According to credit card company requirements for risk minimization, there are two parameters for recurring payments.
+For recurring transactions based on SEPA Direct Debit, a given authorization by the consumer is used for regular direct debits initiated by the creditor, e.g payment for monthly rent. The initial mandateId signed by the consumer is used as a basis for all recurring transactions.
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Alphanumeric, up to 35 characters. |
+Identifier of mandate. |
+
| + | Date as |
+Date when mandate was signed by the consumer. |
+
| + | Enumeration |
+
|
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Alphanumeric |
+Identifier of Merchant CRM. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Enumeration |
+
|
+
Recurring transactions for b4payment don’t require the parameter useIbanBic.
To process a SEPA recurring payment with b4payment integration the mandatory parameter consumerMerchantCrmId needs to be added.
Recurring transactions for Hobex don’t require the parameters useIbanBic and the parameter transactionIdentifier.
Response backend operations parameters and source orders based on SEPA Direct Debit for recurPayment.
Response backend operations parameters and source orders based on SEPA Direct Debit for recurPayment.
| + + | +
+Extending an authorization is not possible, so recurring payment returns a new order Id and the original authorization should be canceled as soon as possible. Anyhow if the transaction(s) exceeds the limit, it will be declined by the issuing bank.
+ |
+
A recurring payment can be made for an existing order which is not older than 400 days and use expired or reversed orders as source orders within a time frame of 400 days.
+refund creates a credit note for the specified order and it can only be done after the order has been debited and the corresponding day-end closing has been done.
customerId,shopId,toolkitPassword,secret,command,language,orderNumber,amount,currency
If supported by the financial service provider it’s possible to refund only a part of the deposited amount. Send additional optional request parameters for the shopping basket e.g. additional information about the item for a refund or the items which remain with the consumer should be sent.
+Additional required request parameters and response request parameters for refund.
For refunds, there are additional optional request parameters available. An additional reference for each operation can therefore be set with the parameter merchantReference. For some payment methods information about the basket items on each refund is required, especially if only a part of the order is refunded. For this purpose the following shopping basket and merchantReference are available.
| + + | +
+Although the following parameters are in general optional, either all parameters need to be set or none, except for basketItem(n)Description and basketItem(n)ImageUrl which remain optional.
+ |
+
A refund can only be done for an order for which the deposit has already been done and it’s not possible to do one refund for several orders, so a refund should be done for each order.
+refundReversal cancels a credit note and can only be done before the corresponding day-end closing has been executed.
customerId,shopId,toolkitPassword,secret,command,language,orderNumber,creditNumber
Additional required request parameters for refundReversal.
transferFund creates a credit note without dependency on a specific order. Depending on the relevant payment method, QENTA currently supports:
customerId,shopId,toolkitPassword,secret,command,language,orderNumber,creditNumber,orderDescription,amount,currency,orderReference,customerStatement,fundTransferType,sourceOrderNumber
The parameters sourceOrderNumber and fundTransferType EXISTINGORDER are relevant to be used for this transfer type. The data of an existing order that are stored on QENTA Checkout Server are used.
The fund transfer type is used for the SEPA Direct Debit and Sofort.
+customerId,shopId,toolkitPassword,secret,command,language,orderNumber,creditNumber,orderDescription,amount,currency,orderReference,customerStatement,fundTransferType,bankAccountOwner,bankBic,bankAccountIban
SEPA-CT is used to pay out money to any bank account using SEPA standard. Thus, the parameters bankBic, bankAccountIban, bankAccountOwner and fundTransferType are relevant to be used.
| + + | ++SEPA-CT is used for all payment methods provided that the BIC, IBAN and account owner are known. + | +
Additional required request parameters and response parameters for refundReversal.
| + + | ++The certificates will be exchanged by QENTA on 2 Nov 2022 11 a.m. CET, therefore the certificate must be in place by this date. Contact our integration specialists for any further questions. + | +
The current api.qenta.com certificate expires on Fri Nov 04 2022 00:59:59 CET and a certificate is available here for downloading.
| + + | ++Only in the case of certificate pinning it is necessary to import the new certificate. Otherwise, the new certificate can be ignored. For more information ask the webmaster/integrator. + | +
The current Truststore certificate will expire on Fri Nov 04 2022 00:59:59 CET and a new certificate is available here for downloading.
+| + + | ++If the QTILL Truststore certificate expired, the connection to QENTA can’t be established anymore. For more information ask the webmaster/integrator. + | +
For any questions or further assistance contact our integration specialists.
+Phone: +43 316 813681-1800
+Fax: +43 316 813681-1203
+integration@qenta.com
+
For any questions about the QENTA solutions contact our sales team.
+Phone: +43 316 813681-1400
+sales@qenta.com
+
The integration of products in the online shop can be checked with a demo mode. There is no communication with the financial service provider but only between the online shop and QENTA. A connection to the Internet is required to gain access to QPAY Checkout Page and the payment process is only simulated displaying the financial service provider pages as images and the possibility to select a successful or failed payment process result. The executed payments are not displayed in the QPC Payment Center.
+| + | QPAY Checkout Page | +QMORE Checkout Seamless | +
|---|---|---|
| + |
|
+|
|
+
|
+|
| + | not used |
+
|
+
QPAY Checkout Page |
+|
Data |
+Value |
+
| + |
|
+
secret |
+
|
+
| + | not used |
+
QMORE Checkout Seamless |
+|
Data |
+Value |
+
| + |
|
+
secret |
+
|
+
| + |
|
+
| Payment Method | +Credentials Available | +
|---|---|
| + | ✔ |
+
| + | + |
| + | + |
| + | + |
| + | ✔ |
+
| + | + |
| + | ✔ |
+
| + | ✔ |
+
| + | ✔ |
+
| + | + |
Invoice (by Payolution) |
+✔ |
+
| + | + |
| + | ✔ |
+
| + | ✔ |
+
| + | + |
QFILE URL |
++ |
QCALL URL |
++ |
QPC URL |
++ |
Username |
+
|
+
Password |
+
|
+
Different financial data such as credit card numbers, usernames and passwords are needed for different payment methods. Since these data are not real financial data an error message from QENTA will be received if used in production mode.
+| Credit Card | +Credit card number | +
|---|---|
Mastercard without Mastercard ID Check (SSL only) |
+
|
+
Mastercard with Mastercard ID Check |
+
|
+
Visa without Visa Secure (SSL only) |
+
|
+
Visa with Visa Secure |
+
|
+
Maestro with Maestro SecureCode |
+
|
+
American Express (SSL only) |
+
|
+
American Express with American Express SafeKey |
+
|
+
Diners Club (SSL only) |
+
|
+
Discover (SSL only) |
+
|
+
| + + | ++Use any card holder name, any day in the future for expiration date and any number with 3 digits for CVC. + | +
Bank sorting code |
+Numeric value with at least 5 digits. |
+
Bank |
+Any alphanumeric text. |
+
Account number |
+Numeric value with at least 4 digits. |
+
Account owner |
+Any alphanumeric text. |
+
An acquirer is a special form of financial service provider for credit cards. Merchants are screened and accepted into the acquirer’s credit card program for which merchants need to conclude corresponding acceptance contracts. To process credit card data, Payment Card Industry Data Security Standard (PCI DSS) needs to be fulfilled which can be handled by a payment service provider.
+Address Verification System is a system primarily used to combat fraud that verifies whether the billing address of the credit card matches the address that was given by the consumer in the online shop, i.e. the system checks the billing address of the credit card provided by the consumer with the address on file at the credit card company.
+Alphanumeric is a combination of alphabetic and numeric characters and is used to describe the collection of Latin letters and Arabic digits or a text constructed from this collection.
+The back-end offers the possibility to execute back-end operations for successful payments like deposit, refund or recurring payments.
+Backend operations both for QMORE Checkout Seamless and QPAY Checkout Page are called by a server-to-server request from the web server to the QENTA Checkout Server. These operations are possible to call automatically from the backend or manually from the user interface. They’re subdivided into two categories:
+The checkout process is an umbrella term containing the following subordinate steps a consumer has to go through when checking out the items in the shopping basket:
+Registration and entry of personal data
+Entry of shipping information
+Selection of shipping method
+Selection of payment method, entry of payment method specific data, a commitment of payment, receipt of payment result
+Return to the online shop to proceed
+CSS (Cascading Style Sheets) is used to format the design and layout of an HTML page that is displayed in a web browser.
+A customer is a person who bought and uses QENTA Payment CEE solutions and services. In the context of QENTA, a merchant is a customer.
+Data storage stores sensitive payment data entered by the consumer during the payment process in the online shop when QMORE Checkout Seamless is used. +The merchant doesn’t need a PCI-compliant online shop and web server since sensitive payment data such as credit card numbers, expiration date, etc. are directly sent from a web form in the online shop to the QENTA data storage, thus bypassing the web server. The data storage is unique to each and valid for 30 minutes after the latest access.
+Typical financial service providers (FSP) are credit card companies, banks and banking systems. Their field of activities includes accepting money transfer requests, approval or denial of transactions and processing of payments. Since every payment request needs to be processed, the payment service provider, i.e. QENTA, transmits the payment information to the respective financial service provider. The payment is approved or denied and corresponding information is sent back to the payment service provider. Merchants need to close appropriate contract(s) with a financial service provider(s) depending on the payment methods they want to offer. The processed amount is transferred to the corresponding merchant’s account by the FSP.
+HTML (HyperText Markup Language) is a markup language for layout web pages.
+JavaScript is a programming language that is typically used in web browsers to add dynamic and interactive elements and functionality to an HTML page.
+A merchant is the owner or operator of an online shop. This is typically a customer of QENTA Payment CEE using our solutions.
+MOTO stands for accepting credit and debit cards by phone or via e-mail to settle a purchase, i.e. the consumer enters the website from any computer, selects an item or service, and calls or e-mails the merchant in order to place an order.
+More about the possibilities QENTA offers to handle MOTO transactions is on the following link → Credit Card - Mail Order and Telephone Orders.
+A non-transaction-based operation is a backend-operation that does not depend on existing orders i.e. such operations are carried out independently of any existing orders.
+An online shop is a virtual shop accessible from a browser on the desktop computer, tablet or smartphone. In some cases also native apps for iOS or Android devices are called online shops, although this is not always appropriate from a technical point of view.
+With the transaction a deposit is done immediately. This also means there is no payment in the approved state.
+Most alternative payment methods have this as a default configuration, but some can be changed to two steps. The specific details for payment methods can be checked here.
+When the payment of a certain amount is authorized, some financial service providers offer a one-off deposit of less than the authorized amount, e.g. if the price of the item the consumer ordered is reduced.
+Not to be confused with a split capture.
Payment method is a specific way the consumer selects for purchasing a product in the online shop. Typical payment methods are credit cards, direct debits, invoices or installments.
+The payment process is part of the checkout process and includes the following steps:
+Selection of payment method
+Entry of payment method specific data
+Commitment of payment
+Receipt of payment result
+A payment service provider (PSP), i.e. QENTA, offers a technical interface allowing the online shop to interact with financial service providers. Payment service providers also assist merchants with supplementary services such as integration of payment methods, fraud and risk management, compliance with PCI DSS, etc.
+The Payment Card Industry Data Security Standard (PCI DSS) is a binding set of rules and procedures established by four major credit card companies (Visa, Mastercard, Discover and American Express) in 2004 and is aimed at companies that accept credit cards as a payment method. The primary objective of PCI DSS is the prevention of fraud and theft of credit card data on the Internet.
+The PCI DSS Self-Assessment Questionnaire (SAQ) is a tool that merchant may use to determine whether the online shop meets established PCI DSS requirements. Different versions of the PCI DSS SAQ are available to cover all possible merchant scenarios.
+A secret is a (pre-shared key) that is only known to the merchant, the integrator of the online shop and QENTA Payment CEE. This secret is used to secure the transfer of all sensitive parameters and their values between the online shop and the QENTA Checkout Server.
+A shop plugin is an additional module that is installed in the merchant’s online shop. Our free-of-charge shop plugins which we offer for many popular shop systems, serve as a technical connection between the shop system and QPAY Checkout Page or QMORE Checkout Seamless, or both for some plugins.
+For the installation of a shop plugin, typically no programming work is required. Shop plugins are constantly updated and improved in order to be compatible with the current version of the shop systems and to offer merchants all available payment methods.
+When the payment of a certain amount is authorized, some financial service providers offer to deposit the total amount not in one single deposit but in multiple smaller deposits. E.g. when shipping only some items from the consumer’s shopping basket,the merchant can make deposits for each separate shipping up to the total authorized amount (e.g. 100 authorized, 2×50 deposited).
+Not to be confused with partial capture.
A (financial) transaction is a communication carried out between the consumer of the online shop, the merchant and the financial institution to exchange an asset for payment.
+A transaction-based operation is a backend operation that depends on existing orders, i.e. orders which have been completed by the consumers in the online shop and which are at the disposal for further actions.
+As an independent service provider for secure settlement of online payment transactions, QENTA offers solutions for any checkout process with more than 20 tailor-made payment methods available to consumers. Same as the profound technical, commercial, and consultant knowledge of experienced staff who has been working in this sector for many years.
+QENTA Payment CEE has been operating on the market since 2000.
+QENTA Payment CEE: http://payments.qenta.com
QENTA Checkout Server is our technology platform where our payment solutions are running as PaaS (Platform as a Service).
+QPC Payment Center is our online portal and allows merchants to search and view payments and start additional operations and transactions, e.g. approve or refund. The merchant can access the QPC Payment Center in demo mode by using test as username and jcv45z as password.
If a merchant uses the QPC Payment Center in demo mode then displayed demo data is immutable.
+Security approach originally developed by Visa for online credit card payments with the main objective being the reduction of fraud and credit card abuse. By offering 3-D Secure, merchants benefit from payment guarantees and will receive the outstanding amounts even in case of a consumer payment default (a liability shift from the merchant to the card issuer occurs).
+During the payment process, the consumer first enters the credit card number. A connection is established to the card issuer and the consumer is prompted to enter the 3-D Secure code which is only known to him in order to prove that he is the authorized card holder. After successful authentication, the transaction is carried out.
+The 3-D Secure code is defined by the cardholder during the registration process and must not be confused with the 3 or 4 digit CVC code which is printed on the back of a credit card. The most common services using 3-D Secure are American Express SafeKey, Visa Secure, and Mastercard ID Check.
+If the default design and layout of QPAY Checkout Page do not fit the design and layout of the online shop, there are different possibilities to modify the design.
+The responsive design of QPAY Checkout Page can be adjusted using a valid CSS file. The URL to this CSS file is stored on the server and must be accessible from the Internet. The CSS file is received via the given URL in the request parameter cssUrl from the server.
+| + + | ++Neither url() functions nor @import directives are allowed in the CSS file. The recommendation is to customize the fonts using CSS templates; otherwise, security checks may last several minutes and lead to payment cancellation. + | +
QPAY Checkout Page is a flexible payment page for the online shop. It allows the consumers to select their preferred payment method and affect their payments in real time while respecting all security standards.
+| + + | ++For PHP we provide an example code on GitHub. + | +
+The consumer opens a shopping card that contains the previously selected items.
+Enters personal data and the shipping address into the provided input fields of a form.
+Selects one of the available payment methods enters the required payment method-specific data and commits the payment.
+Receives relevant information on the result of the payment and returns to the online shop to proceed.
+The payment process includes three parts:
+Consumer
+Online shop
+QPAY Checkout Page
+
+The online shop displays a list of available payment methods which are enabled for the online shop.
+Then the consumer selects one of these payment methods.
+| + + | ++Alternatively (to points 1 and 2), the payment method SELECT can be displayed in the online store, in which case the payment method is selected directly on the checkout page. + | +
The online shop redirects the consumer to QPAY Checkout Page hosted on the QENTA Checkout Server.
+QPAY Checkout Page displays an input form for entering payment data such as credit card number, expiration date, etc. to the consumer, and/or redirects the consumer to the financial service provider.
+The consumer enters the required sensitive payment data into an input form and commits the payment by clicking a relevant button.
+QPAY Checkout Page processes the payment and interacts directly with the consumer and the financial service provider.
+QPAY Checkout Page informs the online shop about the result of the payment.
+Then the online shop stores the result of the payment and triggers a manual or automated shipping process to send the purchased items to the consumer.
+The online shop verifies the received payment result and displays to the consumer an appropriate page containing information on the result of the payment process.
+After returning to the online shop the consumer proceeds with browsing or shopping for additional items in the shop.
+Backend operations for QPAY Checkout Page are subdivided into two categories:
+Transaction-based operations depend on existing orders and non-transaction-based operations don’t.
+| + + | ++Backend operations are an optional feature and to enable it, contact our sales team. + | +
During test mode, there is communication between the online shop and a test area provided by the relevant financial service provider. The payment process is only simulated and no money is transferred.
+To start integrating the payment process in the online shop add an HTML form with some specific field names and values to the web page displaying the order details of the consumer.
+
+On QPAY Checkout Page a web page from our QENTA Checkout Server is shown to the consumer containing an HTML form. After the consumer commit, the payment QPAY Checkout Page handles the entire communication with the financial service provider. After the payment process is completed, QPAY Checkout Page informs the online shop about the result of the payment and forwards the consumer to a specific URL in the online shop which depends on the result of the payment process.
+| State | +Description | +
|---|---|
|
+The payment process has been successfully completed by the consumer. |
+
|
+The payment process has been canceled by the consumer. |
+
|
+The payment process has not been finished successfully by the consumer. |
+
|
+The result of the payment process has yet to be determined and typically occurs on payment methods requiring additional checks. The state pending is only used if the request parameter pendingUrl is used. |
+
| + + | ++For each possible result state a corresponding URL on the web server is called by the QENTA Checkout Server and the consumer is redirected depending on the result of the payment process. + | +
+| + + | ++See the example available on GitHub that can run on the server. + | +
confirmUrl
+If the optional request parameter confirmUrl is set, QPAY Checkout Page calls the given URL with a 30-second timeout using the same return values as for all 4 states. If for any reason the server is not reachable at the moment, the confirmation can be sent again at a later time.
If the optional request parameter confirmUrl is not set, but instead optional parameter confirmMail, an e-mail regarding the result of the payment will be received.
If neither the confirmUrl nor confirmMail is set, the merchant may not be notified of the payment process outcome (if the consumer closes the browser window prematurely!).
If the consumer does not finish the payment process within a time frame of 30 minutes, we check the status of the payment process and sent a notification to the URL set in the request parameter confirmUrl.
An e-mail for each transaction irrespective of the parameters confirmUrl or confirmMail is possible to get.
| + + | ++Contact our sales team to enable the features above. + | +
To check the authenticity of the return values sent from the QENTA Checkout Server to the online shop, compare the responseFingerprint with a hash of the return values.
Create a string by concatenating all returned parameters and the secret based on the order in the return parameter responseFingerprintOrder. Then hash the string with an HMAC-SHA-512 algorithm using the secret as a cryptographic key and compare the result with the value of the return parameter responseFingerprint. If both values are identical, the response is authentic, and if they’re not, re-check the calculation.
| + + | +
+Save all return values after the payment process, or at least the returned order number received from QPAY Checkout Page via successUrl, cancelUrl, failureUrl, pendingUrl, or the confirmUrl, to be able to identify each payment of consumers at a later time and to correlate them to the corresponding session and order.
+ |
+
To check the integration of QPAY Checkout Page use QENTA Checkout Journal as a debugging tool that gives an overview of transaction details when doing a checkout.
+| + + | ++Due to data protection regulations access to the Journal for test transactions can’t be provided. + | +
To integrate QPAY Checkout Page into the online shop choose between the following display options:
+Iframe
+In the online shop, consumers first select the desired items or services and start the checkout process usually by clicking the checkout button. An iframe embeds another website or a web page within the current HTML document. Iframes can be configured by their size and with or without scrollbars independently of the surrounding page’s scrollbars. QPAY Checkout Page can be integrated within an iframe in the HTML page of the online shop so that the whole checkout process is surrounded by the online shop and the consumer does not leave the shop.
+After completing the payment process, consumers are redirected to the online shop and receive relevant information on the result or state of the payment which is sent to the respective successUrl, cancelUrl, failureUrl or pendingUrl.
Pop-up window
+In the online shop, consumers first select the desired items or services and start the checkout process usually by clicking the checkout button. QPAY Checkout Page opens as a new browser window in front of the main window overlaying the online shop.
+After completing the payment process, the pop-up window is closed by QENTA, consumers are redirected to the online shop and receive relevant information on the result or state of the payment which is sent to the respective successUrl, cancelUrl, failureUrl or pendingUrl.
| + + | ++Many web browsers usually offer an option to block pop-up windows which are typically enabled by default. + | +
QPAY Checkout Page redirects the consumer by default with a pop-up to all alternative payment methods. This might result in two pop-ups consecutively opening during the checkout process. The exception is cards with 3-D Secure which will be displayed as an iframe within QPAY Checkout Page or optionally as a page redirect.
+When integrating QPAY Checkout Page in a pop-up window, the external pages of financial institutions can be displayed as an additional pop-up or as a page redirect in the pop-up window.
+Page redirect
+In the online shop, consumers first select the desired items or services and start the checkout process usually by clicking the checkout button. QPAY Checkout Page opens by redirecting the consumers automatically from the online shop to QPAY Checkout Page which replaces the online shop entirely in the browser window. The QENTA-URL is displayed in the address bar.
+After completing the payment process, consumers are redirected to the online shop and receive relevant information on the result or state of the payment which is sent to the respective successUrl, cancelUrl, failureUrl, or pendingUrl.
Use the user interface customization possibilities, so the consumer still has the feeling to be in the online shop.
+When integrating QPAY Checkout Page as a page redirect, the external pages of financial institutions can be displayed as a pop-up or as another redirect to the financial service provider.
+| + + | +
+To use various display options for additional pages, from the financial service provider a different shopId can be requested and a different configuration can be set. Contact our integration specialists.
+ |
+
For PHP we provide an example code on GitHub.
+Browser initiation (default usage)
+To initiate the payment process with QENTA Checkout Page send a POST request to: https://api.qenta.com/page/init.php
The browser receives an HTTP response with the header Location and redirects to the Checkout Page.
Server-to-server initiation
+Alternatively, the same request can be sent to https://api.qenta.com/page/init-server.php
The response is in the following format:
+redirectUrl=https%3A%2F%2Fapi.qenta.com%2Fpage%2F[CustomerID] +[ShopID]_DESKTOP%2Fselect.php%3FSID%3[randomSessionID]+
| + + | +
+If server-to-server initiation is used then parameters consumerIpAddress and consumerUserAgent are mandatory.
+ |
+
Both requests need to contain the required request parameters and should at least have the highly recommended optional parameters.
+| + + | ++In case an error is returned, refer to the error codes listing. + | +
When defining the request parameters, the URLs leading the consumer back to the shop need to be set.
+| URL | +Description | +
|---|---|
| + | Payment was successful |
+
| + | Payment process was canceled by the consumer |
+
| + | Payment failed, e.g. due to a wrong 3-D Secure Code |
+
| + | Payment is pending |
+
| + + | ++Define the confirmURL parameter to get a server-to-server communication of the outcome, regardless of whether the customer is being redirected back to the shop. + | +
To prevent fraud, check the authenticity of returned data for pending and successful payments by calculating the fingerprint. That is done by concatenating all response parameter values plus the secret in the order defined in the responseFingerprintOrder parameter without any dividers in between and using the secret as a cryptographic key for the hashing function. The resulting fingerprint has to be identical to the value of the response responseFingerprint parameter.
+| + + | ++For a PHP example on how to calculate a fingerprint take a look at our reference implementation at the link QENTA Checkout Client Library. + | +
Submit the same URL for all four parameters and provide the appropriate content after interpreting the payment process results.
+Refer to technical implementation for integrating backend operations in general and to each available transaction-based operation.
+During the payment process based on QMORE Checkout Seamless there are some pages that are managed by the QENTA Checkout Server, so merchant can customize these pages according to personal design requirements.
+The responsive design of QMORE Checkout Seamless can be adjusted using a valid CSS file. The URL to this CSS file is stored on the server and must be accessible from the Internet. The CSS file is received via the given URL in the request parameter cssUrl from the server. The rule set contained in the CSS is then used by our responsive design.
+| + + | ++Neither url() functions nor @import directives are allowed in the CSS file. The recommendation is to customize the fonts using CSS templates; otherwise, security checks may last several minutes and lead to payment cancellation. + | +
The QENTA Data Storage is used for storing sensitive payment data of the consumer during the payment process of the online shop. By using the functionality merchant is able to retrieve, send and store e.g. credit card numbers of the consumer without using the web server. This ensures that online shops and web servers don’t need to be PCI-compliant.
+QENTA Data Storage can be initialized at the beginning of the payment process in the online shop. +After initialization, the Data Storage session for a specific consumer is valid for 30 minutes after the last access from the online shop to the Data Storage. After 30 minutes the session becomes invalid and a new Data Storage has to be initialized.
+| + + | ++For PHP we provide an example code on GitHub. + | +
The QENTA Data Storage is only required for the following payment methods which manage sensitive payment data of the consumer:
+Maestro SecureCode
+| + + | ++For all other supported payment methods data doesn’t need to be stored in the Data Storage before starting the payment process itself. + | +
To initialize the QENTA Data Storage, send a server-to-server request from the web server to a specific URL containing some specific request parameters: https://api.qenta.com/seamless/dataStorage/init.
Enable server-to-server requests within the configuration of the web server and firewall settings for sending data from the server to api.qenta.com (212.183.46.16/28).
For a valid request, the correct HTTP header elements have to be set within the request:
+| HTTP header parameter | +Description and value | +
|---|---|
|
+Domain name of server, value: |
+
|
+User agent string of client |
+
|
+MIME type of the body, value: |
+
|
+Length of the body in bytes |
+
|
+Type of connection, value: |
+
| + + | ++Incorrect setting of the header parameters results in an HTTP 403 error message of the QENTA Checkout Server. + | +
If the optional parameters shopId and `javascriptScriptVersion`are not used then they must be omitted in the fingerprint string.
Concatenation of the request parameters and the secret has to be done in the following order: customerId,shopId,orderIdent,returnUrl,language,javascriptScriptVersion,secret
Required, optional request and response parameters for Initialization of QENTA Data Storage.
+Required, optional request and response parameters for Initialization of QENTA Data Storage.
+| + + | ++After the Data Storage initiation request is sent as a server-to-server request from the web server to the QENTA Checkout Server the merchant will get the result as key-value pairs returned in the content of the response. + | +
For example, a successful initiation of the QENTA Data Storage would return:
+storageId=73171af0b8990b9ef2d11b2070f54ad3&javascriptUrl=\https://api.qenta.com/seamless/dataStorage/init/js/D200001/seamless/73171af0b8990b9ef2d11b2070f54ad3/dataStorage.jsIf the initialization did not succeed the merchant will get parameters describing the error.
+Example of possible error:
+error.1.errorCode=11500&error.1.message=CUSTOMERID+is+missing.&error.2.errorCode=11009&error.2.message=Language+is+missing.&error.3.errorCode=15300&error.3.message=ORDERIDENT+has+an+invalid+length.&error.4.errorCode=11301&error.4.message=RETURNURL+is+missing.&error.5.errorCode=11506&error.5.message=REQUESTFINGERPRINT+is+missing.&errors=5Before using the store operation the merchant should ensure that is the returned JavaScript URL included in the return parameter of the Data Storage initialization within the HTML page. Load the JavaScript at the bottom of the page to speed up the page loading time.
+JavaScript URL in PHP by the following code fragment should be included, where $javascriptURL is the URL the merchant has to include to the HTML page for using the JavaScript-based storing functions and objects.
<script src="<?php echo $javascriptURL; ?>" type="text/javascript"></script>Then create an instance of the JavaScript class QentaCEE_DataStorage, which is defined within the previously included URL.
var dataStorage = new QentaCEE_DataStorage();Then create a new and empty JavaScript object which will be filled with the sensitive payment data:
+var paymentInformation = {};Depending on the payment method the merchant adds various properties to this JavaScript object, e.g. for Credit Card, Credit Card-Mail Order and Telephone Order, and Maestro SecureCode add the following properties (the values of these properties are directly taken from the HTML form by accessing the values of the form elements via the DOM of the web browser):
+paymentInformation.pan = document.getElementById('cc_pan').value;
+paymentInformation.expirationMonth = document.getElementById('cc_expirationMonth').value;
+paymentInformation.expirationYear = document.getElementById('cc_expirationYear').value;
+paymentInformation.cardholdername = document.getElementById('cc_cardholdername').value;
+paymentInformation.cardverifycode = document.getElementById('cc_cardverifycode').value;
+paymentInformation.issueMonth = document.getElementById('cc_issueMonth').value;
+paymentInformation.issueYear = document.getElementById('cc_issueYear').value;
+paymentInformation.issueNumber = document.getElementById('cc_issueNumber').value;After setting all properties to the paymentInformation object the merchant only needs to call a specific JavaScript function which is also available in the JavaScript file that is included before:
Credit Card
+dataStorage.storeCreditCardInformation(paymentInformation, callbackFunction);Credit Card-Mail Order and Telephone Order
+dataStorage.storeCreditCardMotoInformation(paymentInformation, callbackFunction);Maestro SecureCode
+dataStorage.storeMaestroInformation(paymentInformation, callbackFunction);The callbackFunction is a JavaScript function where the merchant is able to handle the result of the storage operation and use the following functions:
| Function | +Descritpion | +
|---|---|
|
+Returns 0 for a successful storage operation otherwise 1. |
+
|
+Returns anonymized payment information as a simple JavaScript object. |
+
|
+Returns the errors as a simple JavaScript object. |
+
A very simplified example of this callback function can be:
+callbackFunction = function(aResponse) {
+ // initiates the result string presented to the user
+ var s = "Response of QENTA Data Storage call:\n\n";
+ // checks if response status is without errors
+ if (aResponse.getStatus() == 0) {
+ // saves all anonymized payment information to a JavaScript object
+ var info = aResponse.getAnonymizedPaymentInformation();
+
+ //Response for paymentTypes: CCARD, CCARD-MOTO, MAESTRO
+ s + = "Response for paymentTypes: CCARD, CCARD-MOTO, MAESTRO\n";
+ s += "anonymousPan: " + info.anonymousPan + "\n";
+ s += "maskedPan: " + info.maskedPan + "\n";
+ s += "financialInstitution: " + info.financialInstitution + "\n";
+ s += "brand: " + info.brand + "\n";
+ s += "cardholdername: " + info.cardholdername + "\n";
+ s += "expiry: " + info.expiry + "\n";
+
+ //Response for paymentType: SEPA-DD
+ s + = "Response for paymentType: SEPA-DD\n";
+ s += "bankBic: " + info.bankBic + "\n";
+ s += "bankAccountIban: " + info.bankAccountIban + "\n";
+ s += "accountOwner: " + info.accountOwner + "\n";
+
+ } else {
+ // collects all occurred errors and adds them to the result string
+ var errors = aResponse.getErrors();
+ for (e in errors) {
+ s += "Error " + e + ": " + errors[e].message + " (Error Code: " + errors[e].errorCode + ")\n";
+ }
+ }
+ // presents result string to the user
+ alert(s);
+}To store the sensitive data of the consumer in the QENTA Data Storage the merchant should use the following payment-specific JavaScript functions, which are included as a JavaScript file before.
+dataStorage.storeCreditCardInformation(paymentInformation, callbackFunction);
+
+dataStorage.storeCreditCardMotoInformation(paymentInformation, callbackFunction);
+
+dataStorage.storeMaestroInformation(paymentInformation, callbackFunction);
+
+dataStorage.storeSepaDdInformation(paymentInformation, callbackFunction);If the initialization did not succeed the merchant will get parameters describing the error.
+Required, optional request and response parameters for payment methods Credit Card, Credit Card-Mail Order and Telephone Order, and MaestroSecureCode.
+Required, optional request and response parameters for payment methods Credit Card, Credit Card-Mail Order and Telephone Order, and MaestroSecureCode.
+The optional parameter brand may contain one of the following values:
+American Express |
+
Diners Club |
+
Discover |
+
Mastercard |
+
Visa |
+
Maestro SecureCode |
+
SEPA Direct Debit
+Required request and optional request parameters for SEPA Direct Debit.
+Code example for setting the properties within the paymentInformation JavaScript object:
+paymentInformation.bankBic = document.getElementById('sepa-dd_bankBic').value;
+paymentInformation.bankAccountIban = document.getElementById('sepa-dd_bankAccountIban').value;
+paymentInformation.accountOwner = document.getElementById('sepa-dd_accountOwner').value;After initializing the Data Storage the merchant is able to read at least the storageId for the current checkout of the consumer. The Data Storage session for a specific consumer is only valid for 30 minutes after the latest read or write access from the merchant side. After this time the merchant have to initialize the Data Storage again and to has also to store the sensitive payment data of the consumer again.
Testing if the session with that storageId is still valid or already invalidated.
Extending the session lifetime for another 30 minutes.
+Reading sensitive payment data that are stored to this Data Storage.
+The read operation for the QENTA Data Storage, sends a server-to-server request from the web server to a specific URL containing some specific request parameters: https://api.qenta.com/seamless/dataStorage/read.
| + + | ++Enable server-to-server requests within the configuration of the web server. + | +
For a proper request the merchant has to set the correct HTTP header elements within the request.
+If the optional parameters shopId and `javascriptScriptVersion`are not used then they must be omitted in the fingerprint string.
Concatenation of the request parameters and the secret has to be done in the following order: customerId,shopId,storageId.
Required, optional request and response parameters for Reading Stored Payment Data.
+Required, optional request and response parameters for Reading Stored Payment Data.
+After the Data Storage initiation request is sent as a server-to-server request from the web server to the QENTA Checkout Server the merchant will get the result as key-value pairs returned in the content of the response.
+Returned payment method specific parameters are dependent on the payment method the consumer chooses.
+Returned payment method specific parameters are dependent on the payment method the consumer chooses.
+If the read operation did not succeed the merchant will get parameters describing the error.
+An example of a possible error:
+error.1.errorCode=11500&error.1.message=CUSTOMERID+is+missing.&error.2.errorCode=11506&error.2.message=REQUESTFINGERPRINT+is+missing.&errors=2To initiate the payment process with QMORE Checkout Seamless a POST request needs to be sent to: https://api.qenta.com/seamless/frontend/init
| + + | ++For PHP we provide an example code on GitHub. + | +
+The consumer opens a shopping card that contains the previously selected items.
+Enters personal data and the shipping address into the provided input fields of a form.
+Selects one of the available payment methods enters the required payment method-specific data and commits the payment.
+Receives relevant information on the result of the payment and returns to the online shop to proceed.
+The merchant has to perform the main steps to integrate QMORE Checkout Seamless into the online shop:
+
+Initializing QENTA Data Storage
+The merchant has to initialize the QENTA Data Storage by making a server-side call to a specific URL of QMORE Checkout Seamless using parameters.
+The result of initialization is a Data Storage that the merchant can use to store sensitive payment method specific data of the consumer on the QMORE Checkout Seamless without having to handle these sensitive data in the online shop or on the web server.
+This Data Storage is available for 30 minutes after the last read or write access and after this time has expired, also every time a payment has been started the Data Storage becomes invalid and has to be initialized again.
+Storing sensitive payment data in initiated Data Storage
+After initializing the Data Storage the merchant receives a URL as a return parameter.
+With the URL the merchant is able to integrate JavaScript functionality of QENTA for storing sensitive payment data which the consumer entered in a web form in the online shop.
+These JavaScript functions allow the merchant to bypass the sensitive payment data of the consumer from the online shop and the web server.
+These data are directly sent to the QENTA Data Storage without transferring them through the online shop or the web server.
+Starting payment process
+After the sensitive payment data was stored in the QENTA Data Storage the merchant can start the payment process by making a server-side call of another URL of QMORE Checkout Seamless.
+The server-to-server call returns a URL to where the merchant redirects the consumer for executing the payment process and where external pages of financial institutions are displayed.
+Handling of a result of payment process
+When the consumer successfully finished the payment the merchant will get a confirmation regarding the result of the payment process.
+Based on this result the merchant can redirect the consumer to a success, cancel, error or pending page of the online shop and provide information about the payment result.
+| + + | ++Before the purchase is completed the merchant can include the displaying of order overviews, additional consumer-tailored information on discounts and special offers, as well as promotions that are perfectly catered to the consumers' interests and shopping preferences. + | +
From a technical point of view, the payment process involves the following parties:
+Consumer
+Online shop
+QMORE Checkout Seamless
+The payment process is typically composed of the following steps:
+
+First, the consumer clicks the "Checkout" button.
+Then the online shop initiates the Data Storage as a server-to-server request.
+QMORE Checkout Seamless returns the Data Storage ID and the JavaScript URL.
+The online shop displays the input form for entering payment data such as credit card number, expiration date, etc. to the consumer, and/or redirects the consumer to the financial service provider.
+Then the consumer enters the required payment data into the input form and the data are sent to QENTA.
+QMORE Checkout Seamless stores the payment data on a PCI-compliant server.
+The online shop receives and displays the anonymized payment data.
+Then the online shop displays the relevant order details to the consumer.
+Afterward, the consumer reviews the order details and commits the payment by clicking a relevant button.
+The transaction details are sent as a server-to-server request to QMORE Checkout Seamless.
+QMORE Checkout Seamless redirects the consumer to the external pages of the financial service provider.
+The consumer fills in the required payment details on the external pages of the financial service provider.
+QMORE Checkout Seamless confirms the transaction to the online shop by sending a server-to-server request.
+Now the online shop stores the transaction result.
+QMORE Checkout Seamless redirects the consumer to the successUrl, failureUrl, pendingUrl or cancelUrl.
Then, the online shop displays an appropriate page providing the consumer with information on the result of the payment process.
+After returning to the online shop, the consumer proceeds with browsing or shopping for additional items in the shop.
+Backend operations for QMORE Checkout Seamless are subdivided into two categories:
+Transaction-based operations depend on existing orders and non-transaction-based operations don’t.
+| + + | ++Backend operations are an optional feature and to enable it, contact our sales team. + | +
During test mode there is communication between the online shop and a test area provided for this purpose by the relevant financial service provider. The payment process is only simulated and no money is transferred.
+Payment Card Industry Data Security Standard Self-Assessment Questionnaire A is a security standard and best practices in the credit card industry. Following this standard, a merchant’s website is not allowed to handle sensitive credit card-specific data by itself.
+QENTA is a PCI DSS-certified third-party payment processor. The merchant or integrator can decide whether integrate QMORE Checkout Seamless without the "PCI DSS SAQ A Compliance" feature requiring PCI DSS v3.2.1 certification and compliance with SAQ A-EP, or with the "PCI DSS SAQ A Compliance" feature which was developed especially for QMORE Checkout Seamless and ensures compliance with PCI DSS v3.2.1 and is based on the less stringent SAQ A.
+When using QMORE Checkout Seamless, sensitive payment data are entered by the consumers in HTML forms in the online shop and directly transferred to QENTA via JavaScript to be stored in the QENTA Data Storage. Although sensitive data are never transferred to the online shop, compliance with the new PCI DSS v3.2.1 and corresponding SAQ A-EP is required.
+For "PCI DSS SAQ A Compliance" credit card relevant data are no longer transferred to QENTA via JavaScript but are entered directly in a web form delivered by QENTA. For this purpose, an iframe is displayed containing the relevant credit card input fields where the content of this iframe is directly delivered by QENTA.
+Request parameters are optional parameters used to display or hide credit card-related input fields.
+<div id="creditcardDataIframe"></div>
+
+<script type="text/javascript">
+ var wd = new QentaCEE_DataStorage();
+ wd.buildIframeCreditCard('creditcardDataIframe', '100%', '250px');
+</script><div id="creditcardMotoDataIframe"></div>
+
+<script type="text/javascript">
+ var wd = new QentaCEE_DataStorage();
+ wd.buildIframeCreditCardMoto('creditcardMotoDataIframe', '100%', '250px');
+</script><div id="MaestroDataIframe"></div>git
+
+<script type="text/javascript">
+ var wd = new QentaCEE_DataStorage();
+ wd.buildIframeMaestro('MaestroDataIframe', '100%', '250px');
+</script>The following 3 parameters may be set within the buildIframe* function:
| Function | +Parameter | +Description | +
|---|---|---|
|
+Parameter 1 |
+ID of HTML element into which the iframe will be loaded |
+
|
+||
|
+||
|
+Parameter 2 |
+Defines iframe width |
+
Parameter 3 |
+Defines iframe height |
+
|
+|
Parameter |
+Parameter 1 |
+
Description |
+ID of HTML element into which the iframe will be loaded |
+
|
+|
Parameter |
+Parameter 1 |
+
Description |
+ID of HTML element into which the iframe will be loaded |
+
|
+|
Parameter |
+Parameter 1 |
+
Description |
+ID of HTML element into which the iframe will be loaded |
+
|
+|
Parameter |
+Parameter 2 |
+
Description |
+Defines iframe width |
+
|
+|
Parameter |
+Parameter 3 |
+
Description |
+Defines iframe width |
+
In order to immediately verify the correctness of entered credit card data and to proceed to the next step of the payment process.
+Credit Card
+dataStorage.storeCreditCardInformation(null, callbackFunction);Credit Card-Mail Order and Telephone Order
+dataStorage.storeCreditCardMotoInformation(null, callbackFunction);Maestro SecureCode
+dataStorage.storeMaestroInformation(null, callbackFunction);callbackFunction is a JavaScript function that allows handling the result of the storage operations, however, this function is optional since credit card-specific data are already stored during input when the consumer changes from one field to another. The result is only returned if the consumer’s browser supports postMessages; otherwise, the returned value is null.
| + + | +
+Browser minimum versions that support postMessage are Internet Explorer v8.0, Mozilla Firefox v3.0, Google Chrome v1.0, Safari v4.0, and Opera 9.5; older Android versions, e.g. v 2.3, might not support postMessage.
+ |
+
QENTA ensures the possibility to customize the iframe input fields according to the needs by using the parameter iframeCssUrl.
To ensure that all elements within the checkout seamless are hosted by QENTA systems and in order to provide for SAQ A compliance, this CSS file is received via the given URL in the request parameter iframeCssUrl from the server to the QENTA server. After successful validation, the CSS file is subsequently loaded during each Data Storage init, parsed and delivered as an inline CSS file within the iframe.
Our system uses a URL-based caching mechanism for this iframeCssUrl. To disable this mechanism, append the current timestamp as GET parameter, e.g. https://www.servername.com/iframe.css?23472304897234789.
| + + | ++Due to security reasons, neither url() functions nor @import directives (e.g. external fonts) are allowed in the CSS file, and if they’re used they will be ignored. Never send any font changes within the CSS file, because security checks may last several minutes and lead to payment cancellation. + | +
After initializing the Data Storage the merchant is able to start the payment of all payment methods which don’t need to store sensitive data in the QENTA Data Storage. If the merchant supports payments that involve the handling of sensitive data then he needs to store these data in the Data Storage before the merchant starts the payment process.
+| + + | ++Data Storage session for a specific consumer is only valid for 30 minutes. Once this period of time has expired, the merchant has to initialize the Data Storage again and also has to store the sensitive payment data of the consumer again. + | +
At the start of the payment process, the merchant sends a server-to-server request from the web server to the QENTA Checkout Server to a specific URL containing some specific request parameters: https://api.qenta.com/seamless/frontend/init.
| + + | ++It’s sometimes necessary to enable server-to-server requests in the configuration of the web server. The issue arises typically on provider-managed web servers with PHP. + | +
For a proper request, the merchant has to set the correct HTTP header elements within the request.
+Check how is fingerprint computed.
+After the send the initiation request as a server-to-server request from the web server to the QENTA Checkout Server the merchant will get the result of the initiation as key-value pairs returned in the content of the response.
+If the initiation of the payment process was successful the merchant will receive a parameter called redirectUrl which he uses to redirect the consumer to the next page within the payment process. Typically the consumer is redirected to pages of financial institutions like internet banking pages or a page for entering the 3-D Secure code.
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Alphanumeric |
+URL to redirect the consumer. |
+
If the initialization did not succeed the error parameters will be received.
+Simplified code example for redirecting the consumer or retrieving errors if they occurred within the initiation:
+//--------------------------------------------------------------------------------//
+// Retrieves the value for the redirect URL.
+//--------------------------------------------------------------------------------//
+
+$redirectURL = "";
+foreach (explode('&', $curlResult) as $keyvalue) {
+ $param = explode('=', $keyvalue);
+ if (sizeof($param) == 2) {
+ $key = urldecode($param[0]);
+ if ($key == "redirectUrl") {
+ $redirectURL = urldecode($param[1]);
+ break;
+ }
+ }
+}
+
+//--------------------------------------------------------------------------------//
+// Redirects consumer to payment page.
+//--------------------------------------------------------------------------------//
+
+if ($redirectURL == "") {
+ echo "<pre>";
+ echo "Frontend Intitiation failed with errors:\n\n";
+ foreach (explode('&', $curlResult) as $keyvalue) {
+ $param = explode('=', $keyvalue);
+ if (sizeof($param) == 2) {
+ $key = urldecode($param[0]);
+ $value = urldecode($param[1]);
+ echo $key . " = " . $value . "\n";
+ }
+ }
+ echo "</pre>";
+} else {
+ header("Location: " . $redirectURL);
+}Four possible results can be returned from QMORE Checkout Seamless to the confirmUrl:
+| State | +Description | +
|---|---|
|
+The payment process has been successfully completed by the consumer. |
+
|
+The payment process has been canceled by the consumer. |
+
|
+The payment process has not been finished successfully by the consumer. |
+
|
+The result of the payment process has yet to be determined. Typically occurs on payment methods requiring additional checks or actions by financial service providers or the consumer. When QENTA retrieves updated information from the financial service provider, either a success or a failure is sent to the online shop. |
+
After the consumer has finished the payment process, QMORE Checkout Seamless sends the result to the online shop and the data is sent as a POST request. Be aware that the response parameters are only sent to the confirmUrl and not to the successUrl, cancelUrl, failureUrl or pendingUrl.
The result of the payment can be processed depending on the parameter paymentState as shown in this simplified example:
$paymentState = isset($_POST["paymentState"]) ? $_POST["paymentState"] : "undefined";
+
+$message = "The message text has not been set.";
+if (strcmp($paymentState, "CANCEL") == 0) {
+ $message = "The payment transaction has been canceled by the consumer.";
+} else
+if (strcmp($paymentState, "PENDING") == 0) {
+ $message = "The payment is pending and not yet finished.";
+} else
+if (strcmp($paymentState, "FAILURE") == 0) {
+ $failure_message = isset($_POST["message"]) ? $_POST["message"] : "";
+ $message = "An error occurred during the payment transaction: " . $failure_message;
+} else
+if (strcmp($paymentState,"SUCCESS") == 0) {
+ // check fingerprint and handle successful payment
+ $message = "The payment has been successfully completed.";
+}
+
+// store message and additional response parameter on the systemAfter the result of the payment which was effected by consumer is sent to the confirmUrl on the web server, the consumer is redirected to one of the following URLs provided in the request parameters:
successUrl
cancelUrl
failureUrl
+pendingUrl
+| + + | ++No additional parameters are sent when redirecting to one of these URLs. + | +
To check the authenticity of the return values sent from the QENTA Checkout Server to the online shop, compare the responseFingerprint with an hash of the return values.
Create a string by concatenating all returned parameters plus the secret based on the order in the return parameter responseFingerprintOrder. Then hash the string with an HMAC-SHA-512 algorithm using the secret as cryptographic key and compare the result with the value of the return parameter responseFingerprint. If both values are identical, the response is authentic, and if they’re not identical, re-check the calculation.
+Connection problems and technical issues on the web server may result in a loss of session-related information regarding consumer, e.g. the content of the shopping cart.
+Before starting the payment process in QMORE Checkout Seamless:
+Save all relevant data regarding the payment process in a persistent manner.
+Set the request parameter orderIdent to a unique ID regarding the session and order of consumer (session ID, an order number or a debit number).
+Use custom parameters to pass a unique ID corresponding to a payment process to the QENTA Checkout Server. All of the custom parameters are returned to the online shop as return values after the payment process has been completed.
+After the payment process is completed:
+Save all returned values or at least the returned order number the merchant receives from the QENTA Checkout Server. Also, the merchant can relate them to the initial data regarding the payment process.
+To check the integration of QMORE Checkout Seamless QENTA Checkout Journal can be used as a debugging tool that gives an overview of transaction details when doing a checkout.
+| + + | ++Due to data protection regulations access to the Journal for test transactions can’t be provided. + | +
Contact us and our dedicated team of integration specialists will support the implementation of our solutions.
+These logos are to be used exclusively for visualization purposes regarding the payment methods which are processed via the QENTA Payment CEE interface and offered in the online shop.
+| Logo | +Name | +
|---|---|
+
+
+
+ |
+QENTA Payment CEE |
+
+
+
+
+ |
+White QENTA Payment CEE |
+
+
+
+
+ |
+QCALL Checkout Terminal |
+
+
+
+
+ |
+QPAY Checkout Page |
+
+
+
+
+ |
+QMORE Checkout Seamless |
+
+
+
+
+ |
+QFILE Checkout Automated |
+
+
+
+
+ |
+QTILL Checkout Enterprise |
+
+
+
+
+ |
+QPBL PayByLink |
+
+
+
+
+ |
+QPBL PayByLink API |
+
| Logo | +English | +German | +Value of parameter paymentType |
+
|---|---|---|---|
+
+
+
+ |
+American Express |
+American Express |
+
|
+
+
+
+
+ |
+American Express SafeKey |
+American Express SafeKey |
+
|
+
+
+
+
+ |
+Credit Card |
+Kreditkarte |
+
|
+
+
+
+
+ |
+Diners Club |
+Diners Club |
+
|
+
+
+
+
+ |
+Discover |
+Discover |
+
|
+
+
+
+
+ |
+Maestro SecureCode |
+Maestro SecureCode |
+
|
+
+
+
+
+ |
+Mastercard |
+Mastercard |
+
|
+
+
+
+
+ |
+Mastercard ID Check |
+Mastercard ID Check |
+
|
+
+
+
+
+ |
+Visa |
+Visa |
+
|
+
+
+
+
+ |
+Visa Secure |
+Visa Secure |
+
|
+
| Logo | +English | +German | +Value of parameter paymentType |
+
|---|---|---|---|
+
+
+
+ |
+eps-Überweisung |
+eps-Überweisung |
+
|
+
+
+
+
+ |
+giropay |
+giropay |
+
|
+
+
+
+
+ |
+Przelewy24 |
+Przelewy24 |
+
|
+
+
+
+
+ |
+Klarna Pay Now |
+Sofort. |
+
|
+
| Logo | +English | +German | +Value of parameter paymentType |
+
|---|---|---|---|
+
+
+
+ |
+CVS |
+CVS |
+
|
+
+
+
+
+ |
+Circle K |
+Circle K |
+
|
+
+
+
+
+ |
+Dollar General |
+Dollar General |
+
|
+
+
+
+
+ |
+Invoice |
+Kauf auf Rechnung |
+
|
+
+
+
+
+ |
+oBucks |
+oBucks |
+
|
+
+
+
+
+ |
+PayPal |
+PayPal |
+
|
+
+
+
+
+ |
+paysafecard |
+paysafecard |
+
|
+
+
+
+
+ |
+PagoEfectivo |
+PagoEfectivo |
+
|
+
+
+
+
+ |
+Riverty |
+Riverty |
+
|
+
+
+
+
+ |
+Safetypay |
+Safetypay |
+
|
+
| Logo | +English | +German | +Value of parameter paymentType |
+
|---|---|---|---|
+
+
+
+ |
+SEPA Direct Debit |
+SEPA Lastschrift |
+
|
+
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Alphanumeric, 16 characters |
+Unique ID of the online shop if several configurations are used within one |
+
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Boolean |
+Sets whether credit card details are stored for later use. |
+
| + | Enumeration |
+Sets the periodic type of initial and recurring payments. |
+
merchantTokenizationFlag |
+|
|---|---|
Data |
+Value |
+
Data type |
+Boolean |
+
Description |
+Sets whether credit card details are stored for later use. |
+
| + | |
Data |
+Value |
+
Data type |
+Enumeration |
+
Description |
+Sets the periodic type of initial and recurring payments. |
+
| Parameters | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
| + |
+
+
+
+Required
+ |
+ASCII up to 128 characters, but may differ for specific payment methods. |
+Unique order reference ID sent from merchant to financial institution. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric up to 254 characters that may be restricted for specific payment methods. |
+Text displayed on bank statement issued to the consumer by the financial service provider. |
+
When multiple deposits and refunds are made the orderReference may not suffice as a sole reference, so the additional reference for each operation can therefore be set with the parameter merchantReference.
merchantReference |
+|
|---|---|
Data |
+Value |
+
Within fingerprint |
+Required if used. |
+
Data type |
+ASCII up to 128 characters, but may differ for specific payment methods. |
+
Description |
+Unique order reference ID sent from merchant to financial institution. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used. |
+
Data type |
+Alphanumeric up to 254 characters that may be restricted for specific payment methods. |
+
Description |
+Text displayed on bank statement issued to the consumer by the financial service provider. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Enumeration |
+Possible values: |
+
| + | Alphanumeric, up to 254 characters that may be restricted for specific payment methods. |
+Text displayed on bank statement issued to the consumer by the financial service provider. |
+
| + | Numeric, up to 9 digits. |
+Order number of payment. |
+
| + | Alphanumeric, up to 128 characters. |
+Unique order reference ID sent from merchant to financial institution. |
+
autoDeposit |
+|
|---|---|
Data |
+Value |
+
Data type |
+Enumeration |
+
Description |
+Possible values: |
+
| + | |
Data |
+Value |
+
Data type |
+Alphanumeric, up to 254 characters that may be restricted for specific payment methods. |
+
Description |
+Text displayed on bank statement issued to the consumer by the financial service provider. |
+
| + | |
Data |
+Value |
+
Data type |
+Numeric, up to 9 digits. |
+
Description |
+Order number of payment. |
+
| + | |
Data |
+Value |
+
Data type |
+Alphanumeric, up to 128 characters. |
+
Description |
+Unique order reference ID sent from merchant to financial institution. |
+
| + + | ++Always use the same upper and lower case writing of the parameter names and values as described. + | +
QENTA Checkout Server has restrictions regarding the parameter names and values:
+| Parameter | +Data type | +Description | +
|---|---|---|
| + | Alphanumeric, fixed 7 characters |
+Unique ID of merchant. |
+
|
+Alphanumeric with special characters |
+The password for backend operations using QPAY Checkout Page. |
+
|
+Alphabetic |
+Different types of operations to be executed e.g. approveRevarsal. |
+
| + | Alphabetic, fixed 2 characters |
+Language for returned texts and error messages. |
+
| + | Alphanumeric, fixed 7 characters |
+Computed fingerprint of the parameter values and the secret. |
+
customerId |
+|
|---|---|
Data |
+Value |
+
Data type |
+Alphanumeric, fixed 7 characters |
+
Description |
+Unique ID of merchant. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+The password for backend operations using QPAY Checkout Page. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphabetic |
+
Description |
+Different types of operations to be executed e.g. approveRevarsal. |
+
| + | |
Data |
+Value |
+
Data type |
+Alphabetic, fixed 2 characters |
+
Description |
+Language for returned texts and error messages. |
+
| + | |
Data |
+Value |
+
Data type |
+Alphanumeric, fixed 7 characters |
+
Description |
+Computed fingerprint of the parameter values and the secret. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Numeric, up to 9 digits |
+Order number of payment. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Numeric, up to 9 digits |
+Order number of payment. |
+
| + | Amount |
+Deposited amount. |
+
| + | Alphabetic or numeric, fixed 3 characters |
+Currency code of amount. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Numeric, up to 9 digits |
+Order number of payment. |
+
|
+Numeric, up to 9 digits |
+Payment number which is typically the same as the order number. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Numeric, up to 9 digits. |
+Order number of payment. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Amount |
+Debit amount. |
+
| + | Alphabetic or numeric, fixed 3 characters |
+Currency code of amount. |
+
| + | Alphanumeric, up to 255 characters. |
+Textual description of order. |
+
|
+Numeric, up to 9 digits. |
+Original order number used for a new payment. |
+
| Parmeter | +Data type | +Description | +
|---|---|---|
| + | Numeric, fixed 9. |
+Order number of payment. |
+
| + | Amount |
+Debit amount. |
+
| + | Alphabetic or numeric, fixed 3 characters |
+Currency code of amount. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Numeric, up to 9 digits |
+Order number of payment. |
+
|
+Numeric, up to 9 digits |
+Credit number which has to be canceled. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Alphanumeric, 8 to 11 characters. |
+BIC of bank. |
+
|
+Alphanumeric, 16 to 34 characters. |
+IBAN of account. |
+
|
+Alphanumeric with special characters, 1 to 255 |
+Name of owner of account. |
+
|
+String with value "SEPA-CT". |
+Fund transfer type SEPA-CT. |
+
The number of response parameters is not fixed but depends on the payment method.
+Always use the same upper and lower case writing of the parameter names and values as described. Check all responses of the QENTA Checkout Server by using the fingerprint method.
+For each backend operation these response parameters will always be returned.
+Additional response parameters are returned which are specific to the particular backend operation, both transaction-based and non-transaction-based operations.
+| + + | ++If the backend operation was not successful parameters describing the error are returned. + | +
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Numeric, fixed 5. |
+Numeric error code which should be logged for later use. |
+
|
+Alphanumeric with special characters. |
+Error message in English. |
+
|
+Alphanumeric with special characters. |
+Error message specific to payment method and financial institution which is only relevant for the merchant. |
+
|
+Alphanumeric with special characters |
+Specific error provided by the acquirer/issuer. If this parameter is not sent for |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Numeric |
+Number of errors that occurred. |
+
|
+Numeric, fixed 5. |
+Numeric error code which should be logged for later use. |
+
|
+Alphanumeric with special characters. |
+Error message in English. |
+
|
+Alphanumeric with special characters. |
+Error message in localized language for consumer. |
+
|
+Alphanumeric with special characters. |
+Payment method system specific error message only relevant for merchant. |
+
|
+Alphanumeric with special characters |
+Specific error provided by the acquirer/issuer. If this parameter is not sent for |
+
errors |
+|
|---|---|
Data |
+Value |
+
Data type |
+Numeric |
+
Description |
+Number of errors that occurred. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric, fixed 5. |
+
Description |
+Numeric error code which should be logged for later use. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters. |
+
Description |
+Error message in localized language for consumer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters. |
+
Description |
+Payment method system specific error message only relevant for merchant. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters. |
+
Description |
+Specific error provided by the acquirer/issuer. If this parameter is not sent for |
+
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Numeric, up to 9 digits. |
+Order number of payment. |
+
| Parameter | +Date type | +Description | +
|---|---|---|
| + | Date as |
+Date when payment is debited from consumer’s bank account. |
+
| + | Alphanumeric, up to 35 characters. |
+Identifier of displayed mandate. |
+
| + | Date as |
+Date when the mandate was signed by the consumer. |
+
dueDate |
+|
|---|---|
Data |
+Value |
+
Data type |
+Date as |
+
Description |
+Date when payment is debited from consumer’s bank account. |
+
| + | |
Data |
+Value |
+
Data type |
+Alphanumeric, up to 35 characters. |
+
Description |
+Identifier of displayed mandate. |
+
| + | |
Data |
+Value |
+
Data type |
+Date as |
+
Description |
+Date when the mandate was signed by the consumer. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Numeric, up to 9 digits. |
+A new payment number is returned if a new payment object has been created due to a split capture. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Numeric, fixed 9. |
+Number of a credit note. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Numeric, up to 9 digits. |
+Number of a credit note. |
+
Some parameters will occur more than once, so we use the letters n and m as placeholders for digits. Currently, n is always 1 because getOrderDetails returns only one order and m indicates that there may be more than one payment or credit object returned.
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Numeric |
+Always 1 if a corresponding order has been found; otherwise 0. |
+
|
+Numeric, fixed 9 digits. |
+ID of merchant. |
+
|
+Numeric, up to 9 digits. |
+Order number. |
+
|
+Alphanumeric, up to 32 characters. |
+Payment type of order. |
+
|
+Amount |
+Amount of order. |
+
|
+Alphanumeric, up to 255 characters. |
+Brand of payment method. |
+
|
+Alphabetic or numeric, fixed 3 characters |
+Currency code of amount. |
+
|
+Alphanumeric, up to 255 characters. |
+Unique description of the consumer’s order in a human-readable form. |
+
|
+Alphanumeric |
+Acquirer |
+
|
+Alphanumeric including special characters, up to 255 characters. |
+Contract number of the financial service provider. |
+
|
+Alphanumeric including special characters. |
+Comma-separated string of available backend operations or an empty string if no backend operation is possible. |
+
|
+Numeric, up to 128 digits. |
+Order reference. |
+
|
+Alphanumeric, up to 254 characters that may be restricted for specific payment methods. |
+Text visible for the consumer on the bank statement. |
+
|
+Alphanumeric, up to 254 characters. |
+Order text reduced to ASCII-character set. |
+
|
+Date |
+Date and time when order has been created. |
+
|
+Date |
+Date and time when an order has been modified the last time. |
+
|
+Alphanumeric, up to 16 characters. |
+Current state of order - |
+
|
+Numeric, up to 9 digits. |
+Source order number if there is a connection to another order. |
+
|
+Numeric |
+Count of corresponding payment objects. |
+
|
+Numeric |
+Count of corresponding credit objects. |
+
|
+Numeric |
+ID of merchant. |
+
|
+Numeric, up to 9 digits. |
+Number of payment. |
+
|
+Numeric, up to 9 digits. |
+Number of order. |
+
|
+Alphanumeric |
+Approval code of financial service provider may be an empty string. |
+
|
+Numeric, up to 9 digits. |
+Only available if day-end closing was done the order. |
+
|
+Amount |
+Approved amount of order. |
+
|
+Amount |
+Debit amount of order. |
+
|
+Alphabetic or numeric, fixed 3 characters |
+Currency code. |
+
|
+Date |
+Date and time when payment has been created. |
+
|
+Date |
+Date and time when payment has been modified the last time. |
+
|
+Alphabetic, up to 32 characters. |
+Current state of payment- |
+
|
+Alphanumeric, up to 64 characters. |
+Technical property used for the transaction. |
+
|
+Alphanumeric including special characters. |
+Comma-separated string of available backend operations or an empty string if no backend operation is possible. |
+
|
+Alphanumeric including special characters, up to 255 characters. |
+Technical reference number of corresponding financial service provider. |
+
|
+Alphanumeric including special characters, up to 255 characters. |
+Technical reference number of the corresponding financial service provider or acquirer. |
+
|
+Alphanumeric including special characters, up to 5 characters. |
+Result code of AVS check. |
+
|
+Alphanumeric including special characters and up to 256 characters. |
+Result text of AVS check. |
+
|
+Alphanumeric including special characters, up to 5 characters. |
+Provider result code of AVS check. |
+
|
+Alphanumeric including special characters, up to 256 characters. |
+Provider result text of AVS check. |
+
|
+Numeric |
+ID of merchant. |
+
|
+Numeric, up to 9 digits. |
+Credit number. |
+
|
+Numeric, up to 9 digits. |
+Order number. |
+
|
+Numeric, up to 9 digits. |
+Batch number for corresponding day-end closing. |
+
|
+Amount |
+Amount of credit. |
+
|
+Alphabetic or numeric, fixed 3 characters |
+Currency code of amount. |
+
|
+Date |
+Date and time when credit has been created. |
+
|
+Date |
+Date and time when the credit has been modified the last time. |
+
|
+Alphabetic including special characters. |
+Current state of credit- |
+
|
+Alphanumeric including special characters. |
+Comma-separated string of available backend operations or an empty string if no backend operation is possible. |
+
|
+Alphanumeric including special characters, up to 255 characters. |
+Technical reference number of corresponding financial service provider. |
+
|
+Alphanumeric including special characters, up to 255 characters. |
+Technical reference number of corresponding financial service provider or acquirer. |
+
orders |
+|
|---|---|
Data |
+Value |
+
Data type |
+Numeric |
+
Description |
+Always 1 if a corresponding order has been found; otherwise 0. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric, fixed 9 digits. |
+
Description |
+ID of merchant. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric, up to 9 digits. |
+
Description |
+Order number. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 32 characters. |
+
Description |
+Payment type of order. |
+
|
+|
Data |
+Value |
+
Data type |
+Amount |
+
Description |
+Amount of order. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 255 characters. |
+
Description |
+Brand of payment method. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphabetic or numeric, fixed 3 characters. |
+
Description |
+Currency code of amount. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 255 characters. |
+
Description |
+Unique description of the consumer’s order in a human-readable form. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric |
+
Description |
+Acquirer |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters, up to 255 characters. |
+
Description |
+Contract number of the financial service provider. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters. |
+
Description |
+Comma-separated string of available backend operations or an empty string if no backend operation is possible. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric, up to 128 digits. |
+
Description |
+Order reference. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 254 characters that may be restricted for specific payment methods. |
+
Description |
+Text visible for the consumer on the bank statement. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 254 characters. |
+
Description |
+Order text reduced to ASCII-character set. |
+
|
+|
Data |
+Value |
+
Data type |
+Date |
+
Description |
+Date and time when order has been created. |
+
|
+|
Data |
+Value |
+
Data type |
+Date |
+
Description |
+Date and time when an order has been modified the last time. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 16 characters. |
+
Description |
+Current state of order - |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 16 characters. |
+
Description |
+Current state of order - |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric, up to 9 digits. |
+
Description |
+Source order number if there is a connection to another order. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric |
+
Description |
+Count of corresponding payment objects. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric |
+
Description |
+Count of corresponding credit objects. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric |
+
Description |
+ID of merchant. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric, up to 9 digits. |
+
Description |
+Number of payment. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric, up to 9 digits. |
+
Description |
+Number of order. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric |
+
Description |
+Approval code of financial service provider may be an empty string. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric, up to 9 digits. |
+
Description |
+Only available if day-end closing was done the order. |
+
|
+|
Data |
+Value |
+
Data type |
+Amount |
+
Description |
+Approved amount of order. |
+
|
+|
Data |
+Value |
+
Data type |
+Amount |
+
Description |
+Debit amount of order. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphabetic or numeric, fixed 3 characters |
+
Description |
+Currency code. |
+
|
+|
Data |
+Value |
+
Data type |
+Date |
+
Description |
+Date and time when payment has been created. |
+
|
+|
Data |
+Value |
+
Data type |
+Date |
+
Description |
+Date and time when payment has been modified the last time. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphabetic, up to 32 characters. |
+
Description |
+Current state of payment- |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 64 characters. |
+
Description |
+Technical property used for the transaction. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters. |
+
Description |
+Comma-separated string of available backend operations or an empty string if no backend operation is possible. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters, up to 255 characters. |
+
Description |
+Technical reference number of corresponding financial service provider. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters, up to 255 characters. |
+
Description |
+Technical reference number of the corresponding financial service provider or acquirer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters, up to 5 characters. |
+
Description |
+Result code of AVS check. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters and up to 256 characters. |
+
Description |
+Result text of AVS check. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters, up to 5 characters. |
+
Description |
+Provider result code of AVS check. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters, up to 256 characters. |
+
Description |
+Provider result text of AVS check. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric |
+
Description |
+ID of merchant. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric, up to 9 digits. |
+
Description |
+Credit number. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric, up to 9 digits. |
+
Description |
+Order number. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric, up to 9 digits. |
+
Description |
+Batch number for corresponding day-end closing. |
+
|
+|
Data |
+Value |
+
Data type |
+Amount |
+
Description |
+Amount of credit. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphabetic or numeric, fixed 3 characters |
+
Description |
+Currency code of amount. |
+
|
+|
Data |
+Value |
+
Data type |
+Date |
+
Description |
+Date and time when credit has been created. |
+
|
+|
Data |
+Value |
+
Data type |
+Date |
+
Description |
+Date and time when the credit has been modified the last time. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphabetic including special characters. |
+
Description |
+Current state of credit- |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters. |
+
Description |
+Comma-separated string of available backend operations or an empty string if no backend operation is possible. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters, up to 255 characters. |
+
Description |
+Technical reference number of corresponding financial service provider. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters, up to 255 characters. |
+
Description |
+Technical reference number of corresponding financial service provider or acquirer. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Alphanumeric, up to 13 characters. |
+ID of PayPal consumer. |
+
|
+Alphanumeric including special characters, up to 19 characters. |
+Billing agreement ID created by PayPal which can be used for recurring payments. |
+
|
+Alphanumeric including special characters, up to 127 characters. |
+E-mail of PayPal consumer. |
+
|
+Alphanumeric, up to 64 characters. |
+First name of PayPal consumer. |
+
|
+Alphanumeric, up to 64 characters. |
+Last name of PayPal consumer. |
+
|
+Alphabetic, up to 50 characters. |
+Country of PayPal consumer. |
+
|
+Alphabetic, fixed 2 characters. |
+Country code (ISO 3166-1) of PayPal consumer. |
+
|
+Alphabetic, up to 40 characters. |
+Ciy of PayPal consumer. |
+
|
+Alphabetic, fixed 2 characters. |
+State of PayPal consumer. |
+
|
+Alphanumeric, up to 100 characters. |
+Address name of PayPal consumer. |
+
|
+Alphanumeric, up to 100 characters. |
+Street (1) of PayPal consumer. |
+
|
+Alphanumeric, up to 100 characters. |
+Street (2) of PayPal consumer. |
+
|
+Alphanumeric, up to 32 characters. |
+Zip code of PayPal consumer. |
+
|
+Alphanumeric, up to 32 characters. |
+State of address verification of PayPal consumer. |
+
|
+Alphanumeric, up to 32 characters. |
+Information regarding PayPal merchant protection. |
+
payment.{n}.{m}.paypalPayerID |
+|
|---|---|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 13 characters. |
+
Description |
+ID of PayPal consumer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters, up to 19 characters. |
+
Description |
+Billing agreement ID created by PayPal which can be used for recurring payments. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters, up to 127 characters. |
+
Description |
+E-mail of PayPal consumer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 64 characters. |
+
Description |
+First name of PayPal consumer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 64 characters. |
+
Description |
+Last name of PayPal consumer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphabetic, up to 50 characters. |
+
Description |
+Country of PayPal consumer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphabetic, fixed 2 characters. |
+
Description |
+Country code (ISO 3166-1) of PayPal consumer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphabetic, up to 40 characters. |
+
Description |
+Ciy of PayPal consumer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphabetic, fixed 2 characters. |
+
Description |
+State of PayPal consumer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 100 characters. |
+
Description |
+Address name of PayPal consumer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 100 characters. |
+
Description |
+Street (1) of PayPal consumer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 100 characters. |
+
Description |
+Street (2) of PayPal consumer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 20 characters. |
+
Description |
+Zip code of PayPal consumer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 32 characters. |
+
Description |
+State of address verification of PayPal consumer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 32 characters. |
+
Description |
+Information regarding PayPal merchant protection. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Alphanumeric including special characters, up to 255 characters. |
+Name of the owner of an account returned by Sofort. |
+
|
+Alphanumeric including special characters, up to 255 characters. |
+Number of the account returned by Sofort. |
+
|
+Numeric, up to 30 digits. |
+Bank number of account returned by Sofort. |
+
|
+Numeric, up to 30 digits. |
+Name of a bank as returned by Sofort. |
+
|
+Alphanumeric, up to 50 characters. |
+BIC of account returned by Sofort. |
+
|
+Alphanumeric, up to 50 characters. |
+IBAN of account returned by Sofort. |
+
|
+Alphabetic, fixed 2 characters. |
+Country code of sender returned by Sofort. |
+
|
+Numeric with a fixed length of 1 digit. |
+Security criterion returned values: |
+
payment.{n}.{m}.senderAccountOwner |
+|
|---|---|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters, up to 255 characters. |
+
Description |
+Name of the owner of an account returned by Sofort. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric including special characters, up to 255 characters. |
+
Description |
+Number of the account returned by Sofort. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric, up to 30 digits. |
+
Description |
+Bank number of account returned by Sofort. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric, up to 30 digits. |
+
Description |
+Name of a bank as returned by Sofort. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 50 characters. |
+
Description |
+BIC of account returned by Sofort. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 50 characters. |
+
Description |
+IBAN of account returned by Sofort. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphabetic, fixed 2 characters. |
+
Description |
+Country code of sender returned by Sofort. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric with a fixed length of 1 digit. |
+
Description |
+Security criterion returned values: |
+
To initialize the QENTA Data Storage the merchant has to set all required parameters to their corresponding values that are needed within the online shop. If one or more of these required parameters are missing an error message will be accrued.
+| Parameter | +Data type | +Description | +
|---|---|---|
| + | Alphanumeric, fixed 7 |
+Unique ID of merchant. |
+
| + | Alphanumeric |
+Unique reference to the order of the consumer. |
+
| + | Alphanumeric |
+Return URL for outdated browsers. |
+
| + | Alphabetic, fixed 2. |
+Language for returned texts and error messages. |
+
| + | Alphanumeric, 128. |
+Computed fingerprint of the parameter values and the secret. |
+
customerId |
+|
|---|---|
Data |
+Value |
+
Data type |
+Alphanumeric, fixed 7 |
+
Description |
+Unique ID of merchant. |
+
| + | |
Data |
+Value |
+
Data type |
+Alphanumeric |
+
Description |
+Unique reference to the order of the consumer. |
+
| + | |
Data |
+Value |
+
Data type |
+Alphanumeric |
+
Description |
+Return URL for outdated browsers. |
+
| + | |
Data |
+Value |
+
Data type |
+Alphabetic, fixed 2. |
+
Description |
+Language for returned texts and error messages. |
+
| + | |
Data |
+Value |
+
Data type |
+Alphanumeric, 128. |
+
Description |
+Computed fingerprint of the parameter values and the secret. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Numeric, length of 13 to 19 |
+Credit card number. |
+
|
+Numeric, fixed 2 |
+Expiration month of credit card. |
+
|
+Numeric, fixed 2 |
+Expiration year of credit card. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Alphanumeric with special characters. |
+Name of owner of account. |
+
|
+Alphanumeric, up to 34 characters. |
+IBAN of account. |
+
|
+Alphanumeric, up to 12 characters. |
+BIC of bank. Required only for Hobex |
+
| Parameter | +Data type | +Short description | +
|---|---|---|
| + | Alphanumeric, fixed 7 |
+Unique ID of merchant. |
+
| + | Alphanumeric, fixed 32 |
+Unique ID of Data Storage. |
+
| + | Alphanumeric, fixed 128 |
+Computed fingerprint of the parameter values and the secret. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Alphanumeric with a variable length of 16 |
+Unique ID of the online shop. |
+
| + | Alphanumeric, fixed 4 characters |
+The value |
+
shopId |
+|
|---|---|
Data |
+Value |
+
Data type |
+Alphanumeric with a variable length of 16 |
+
Description |
+Unique ID of the online shop. |
+
| + | |
Data |
+Value |
+
Data type |
+Alphanumeric, fixed 4 characters |
+
Description |
+The value |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Alphanumeric, up to 30. |
+Name of owner of a credit card. |
+
|
+Numeric, of 1 to 4. |
+Verification code of a credit card. |
+
|
+Numeric, fixed 2. |
+Issuing month of a credit card. |
+
|
+Numeric, fixed 2. |
+Issuing year of a credit card. |
+
|
+Numeric, of 1 to 3. |
+Issuing number of a credit card. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Alphanumeric with special characters. |
+Name of the bank. |
+
| Parameter | +Data type | +Short description | +
|---|---|---|
| + | Alphanumeric, 16 |
+Unique ID of the online shop. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+URL |
+URL to a CSS file on the server to perform customizations of the iframe input fields. |
+
|
+Alphanumeric, 32 characters |
+Placeholder text for the credit card number field. |
+
|
+Alphanumeri, 32 characters |
+Placeholder text for the credit card verification number field. |
+
|
+Alphanumeric, 32 characters |
+Placeholder text for the credit cardholder field. |
+
|
+Alphanumeric, 32 characters |
+Placeholder text for the credit card issue number. |
+
|
+Boolean |
+Display placeholder text for the credit card expiration date. |
+
|
+Boolean |
+Display placeholder text for the credit card issue date. |
+
|
+Boolean |
+Display field containing cardholder name. |
+
|
+Boolean |
+Display CVC field. |
+
|
+Boolean |
+Display field containing the card issue date. |
+
|
+Boolean |
+Display field containing the card issue number. |
+
iframeCssUrl |
+|
|---|---|
Data |
+Value |
+
Data type |
+URL |
+
Description |
+URL to a CSS file on the server to perform customizations of the iframe input fields. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, 32 characters |
+
Description |
+Placeholder text for the credit card number field. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, 32 characters |
+
Description |
+Placeholder text for the credit card verification number field. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, 32 characters |
+
Description |
+Placeholder text for the credit cardholder field. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, 32 characters |
+
Description |
+Placeholder text for the credit card issue number. |
+
|
+|
Data |
+Value |
+
Data type |
+Boolean |
+
Description |
+Display placeholder text for the credit card expiration date. |
+
|
+|
Data |
+Value |
+
Data type |
+Boolean |
+
Description |
+Display placeholder text for the credit card issue date. |
+
|
+|
Data |
+Value |
+
Data type |
+Boolean |
+
Description |
+Display field containing cardholder name. |
+
|
+|
Data |
+Value |
+
Data type |
+Boolean |
+
Description |
+Display CVC field. |
+
|
+|
Data |
+Value |
+
Data type |
+Boolean |
+
Description |
+Display field containing the card issue date. |
+
|
+|
Data |
+Value |
+
Data type |
+Boolean |
+
Description |
+Display field containing the card issue number. |
+
| + + | ++These fields must not be included in the fingerprint calculation. + | +
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Alphanumeric, fixed 32. |
+Unique ID of the online shop. |
+
|
+Alphanumeric |
+Version number of JavaScript. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Numeric, fixed 4. |
+Anonymized credit card number containing only the rightmost 4 digits. |
+
|
+Numeric with special characters and a variable length of 13 to 19. |
+Masked credit card number: first 6 numbers followed by |
+
| + | Enumeration |
+Financial institution |
+
|
+Enumeration |
+Brand depending on payment method. |
+
|
+Alphanumeric with special characters. |
+Name of the cardholder. |
+
|
+Numeric with special characters. |
+Expiry date of credit card in the format |
+
anonymousPan |
+|
|---|---|
Data |
+Value |
+
Data type |
+Numeric, fixed 4. |
+
Description |
+Anonymized credit card number containing only the rightmost 4 digits. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric with special characters and a variable length of 13 to 19. |
+
Description |
+Masked credit card number: first 6 numbers followed by |
+
| + | |
Data |
+Value |
+
Data type |
+Enumeration |
+
Description |
+Financial institution |
+
|
+|
Data |
+Value |
+
Data type |
+Enumeration |
+
Description |
+Brand depending on payment method. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters. |
+
Description |
+Name of the cardholder. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric with special characters. |
+
Description |
+Expiry date of credit card in the format |
+
| Parameter | +Data type | +Description | +
|---|---|---|
| + | Alphanumeric, fixed 32. |
+Unique ID of Data Storage. |
+
|
+Numeric |
+Number of stored payment methods. |
+
|
+Alphabetic |
+Name of payment method. |
+
storageId |
+|
|---|---|
Data |
+Value |
+
Data type |
+Alphanumeric, fixed 32. |
+
Description |
+Unique ID of Data Storage. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric |
+
Description |
+Number of stored payment methods. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphabetic |
+
Description |
+Name of payment method. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Numeric with a fixed length of 4. |
+Anonymized credit card number containing only the rightmost 4 digits. |
+
|
+Numeric with special characters and a variable length of 13 to 19. |
+Masked credit card number: first 6 numbers followed by |
+
|
+Enumeration |
+Financial institution. |
+
|
+Enumeration |
+Brand of Credit Card. |
+
|
+Alphanumeric with special characters. |
+Name of the cardholder. |
+
|
+Numeric with special characters. |
+Expiry date of credit card in the format |
+
|
+Alphanumeric with special characters. |
+Name of the owner of the account. |
+
|
+Alphanumeric with special characters. |
+Name of the bank. |
+
|
+Alphabetic with a fixed length of 2. |
+Country code of the bank. |
+
|
+Alphanumeric with a variable length of 1 to 11. |
+Account number. |
+
|
+Numeric with a variable length of 1 to 8. |
+Bank number. |
+
|
+Alphanumeric with a variable length of 1 to 255. |
+BIC of the bank. |
+
|
+Alphanumeric with a variable length of 1 to 255. |
+IBAN of account. |
+
paymentInformation.{n}.anonymousPan |
+|
|---|---|
Data |
+Value |
+
Data type |
+Numeric with a fixed length of 4. |
+
Description |
+Anonymized credit card number containing only the rightmost 4 digits. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric with special characters and a variable length of 13 to 19. |
+
Description |
+Masked credit card number: first 6 numbers followed by |
+
|
+|
Data |
+Value |
+
Data type |
+Enumeration |
+
Description |
+Financial institution. |
+
|
+|
Data |
+Value |
+
Data type |
+Enumeration |
+
Description |
+Brand of Credit Card. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters. |
+
Description |
+Name of the cardholder. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters. |
+
Description |
+Expiry date of credit card in the format |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters. |
+
Description |
+Name of the owner of the account. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters. |
+
Description |
+Name of the bank. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphabetic with a fixed length of 2. |
+
Description |
+Country code of the bank. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with a variable length of 1 to 11. |
+
Description |
+Account number. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric with a variable length of 1 to 8. |
+
Description |
+Bank number. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with a variable length of 1 to 255. |
+
Description |
+BIC of the bank. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with a variable length of 1 to 255. |
+
Description |
+IBAN of account. |
+
| + + | +
+Be aware that due to PCI DSS compliance, hashedPan can’t be returned either with maskedPan or anonymousPan.
+ |
+
The amount parameter defines the payment amount which is to be done by the consumer of the online shop.
| + + | ++Thousand separators are not permitted. + | +
The maximum number of decimal places depends on the selected currency within the currency parameter:
+| Currency | +Decimal places | +
|---|---|
Euro |
+Maximum of 2 decimal places (100 Cent = 1 Euro). |
+
US Dollar |
+Maximum of 2 decimal places (100 Cent = 1 US$). |
+
Yen |
+No decimal places allowed. |
+
Libyan Dinar |
+Maximum of 3 decimal places (1000 Dirham = 1 Dinar). |
+
cancelUrl has to contain the URL of the page where the consumer is forwarded when the payment process is canceled. The consumer should be informed about the cancellation of the payment process and offered possibilities to retry the payment attempt or get in contact with the merchant.
cssUrl contains an URL to a CSS file stored on the server and accessible from the Internet. The CSS file is used to adjust the responsive design of QMORE Checkout Seamless and QPAY Checkout Page.
The currency parameter defines the currency used in the payment.
| + + | ++By default, only EUR is enabled as currency. If additional currencies are required contact our sales team. + | +
| Alphabetic value | +Numeric value | +Currency | +
|---|---|---|
|
+
|
+Swiss Franc |
+
|
+
|
+Czech Koruna |
+
|
+
|
+Euro |
+
|
+
|
+Pound Sterling |
+
|
+
|
+Hungarian Forint |
+
|
+
|
+Polish Zloty |
+
|
+
|
+US Dollar |
+
| + + | ++Not all available payment methods support all currencies. + | +
The customerId parameter represents the unique ID of the merchant using the QENTA Checkout Server.
For production mode, the customerId, as well as a secret, will be provided by our integration specialists.
The failureUrl parameter defines the URL of the online shop where the consumer is forwarded when the payment process has failed for any reason. On this page, the possibility to retry the payment or get in contact with support team.
The language parameter defines the language used for all messages of the QPAY Checkout Page and QMORE Checkout Seamless that are displayed to the consumer of the online shop.
| + + | ++By default, only English and German languages are activated. If the selected language is not supported by the respective financial service provider, the financial service provider decides which language is displayed to the consumer. + | +
| Value | +Language | +
|---|---|
|
+Arabian |
+
|
+Bosnian |
+
|
+Bulgarian |
+
|
+Chinese |
+
|
+Croatian |
+
|
+Czech |
+
|
+Danish |
+
|
+Dutch |
+
|
+English |
+
|
+Estonian |
+
|
+Finnish |
+
|
+French |
+
|
+German |
+
|
+Greek |
+
|
+Hebrew |
+
|
+Hindi |
+
|
+Hungarian |
+
|
+Italian |
+
|
+Japanese |
+
|
+Korean |
+
|
+Latvian |
+
|
+Lithuanian |
+
|
+Macedonian |
+
|
+Norwegian |
+
|
+Polish |
+
|
+Portuguese |
+
|
+Romanian |
+
|
+Russian |
+
|
+Serbian |
+
|
+Slovakian |
+
|
+Slovenian |
+
|
+Spanish |
+
|
+Swedish |
+
|
+Turkish |
+
|
+Ukrainian |
+
The merchantTokenizationFlag parameter can be used to set the recurring flaggings for specific orders. To save the consumer’s card details for later use, the aforementioned parameter must be set to TRUE.
The orderDescription parameter is a description of what the consumer paid for, e.g. a text cross-referencing the order made in the online shop.
| + + | ++This text is not transmitted to any financial service provider and is therefore NEVER displayed on any consumer’s invoice or statement. The text is displayed in the QPC Payment Center. + | +
If the optional request parameter displayText is not used the orderDescription text will also be visible as consumer information in QPAY Checkout Page.
| + + | +
+The value of orderDescription must not contain any special characters or line breaks. Including such characters causes the fingerprint computation to fail and the error message "Invalid fingerprint!" is displayed.
+ |
+
The paymentType parameter is the name of the payment method the user selected in the online shop.
| + + | ++To use a payment method, it must be purchased by the merchant and enabled by QENTA. If additional payment methods are required, contact our sales team. + | +
Value of paymentType parameter |
+Payment method | +
|---|---|
|
+The consumer may select one of the activated payment methods directly in QPAY Checkout Page. |
+
|
++ |
|
+Credit Card, Maestro SecureCode |
+
|
++ |
|
++ |
|
++ |
|
++ |
|
++ |
|
++ |
|
+Invoice: Payolution |
+
|
++ |
|
++ |
|
++ |
|
++ |
|
++ |
|
++ |
|
++ |
The periodicType parameter defines the periodic type of initial and recurring payments.
| periodicType value | +Description | +
|---|---|
|
+For unscheduled recurring payments with different amounts. |
+
|
+For recurring payments like subscriptions with the same interval and same amount. |
+
returnUrl is used for browsers that are not capable of fully supporting CORS (Cross Origin Resource Sharing). In that case, the communication between the HTML page and the QENTA Checkout Server will be done within an iframe where the anonymized payment data are returned to JavaScript objects.
The requestFingerprint parameter contains the computed fingerprint based on the values of parameters defined in the requestFingerprintOrder parameter. This method is used for security reasons to verify the parameters the online shop sends to the QENTA Checkout Server.
| + + | ++At least one of the parameters used for computing the fingerprint needs to be unique to each order to prevent sending the same hash-value! + | +
To authenticate, all requests to the QENTA Checkout Server need to contain the aforementioned requestFingerprint. To generate the said fingerprint, the HMAC-SHA-512 construction is used by combining the cryptographic hash function SHA-512 with the secret as the cryptographic key to hash the concatenated request parameter values in the order defined in the requestFingerprintOrder.
The parameter requestFingerprintOrder needs to contain a comma-separated list of all parameter names, the values of which – and in that exact order — are used to create the fingerprint.
The parameter names in the requestFingerprintOrder parameter may be listed in any order, but this exact ordering must be used for the respective parameter values when calculating the fingerprint accordingly, e.g.
customerId,amount,currency,language,orderDescription,successUrl,requestFingerprintOrder,secret
The serviceUrl parameter is used to define the URL of a web page in an online shop which informs the consumer about the different possibilities to get in contact with the merchant.
| + + | ++Do not use this URL to link to the shopping basket of the consumer! + | +
If the optional parameter imageUrl is not included, the serviceUrl is not used in the QPAY Checkout Page and the consumer has no possibility to access the service page in the online shop during the payment process.
The serviceURL has to be accessible over the internet via port 80 or port 443 and may not be hosted on a local server that can’t be accessed by the QENTA Checkout Server.
The autoDeposit parameter enables an automatic deposit and day-end closing of payments. After a consumer has completed payment in online shop, the payment is only approved and not yet deposited.
| + + | ++Not deposited (uncaptured) approvals will expire after 7-14 calendar days. The exact deadline depends on the regulations provided by each financial service provider. After exceeding the individual deadline these payments can no longer be submitted or received. Contact our sales team to activate this feature. + | +
The backgroundColor parameter defines background color for the HTML pages in the custom CSS for QPAY Checkout Page and value is hex-coded RGB e.g. f0f0f0.
Background color for the brand image that contains the credit card logos can be set.
+The confirmMail parameter defines one e-mail address of the merchant for receiving payment details regarding the orders of consumers in the online shop. This e-mail may contain information about payment state, order number, payment method, payment amount and payment currency.
QENTA can activate one of the two options:
+QENTA will send the confirmation to the confirmMail only if the confirmUrl is not available.
QENTA will always send the confirmation to the confirmMail in any case.
| + + | ++Contact sales team to activate the feature. + | +
|
+The payment has been successfully finished by the consumer. |
+
|
+The payment process has been canceled by the consumer and has not been successfully finished. |
+
|
+A problem occurred during the payment process and the payment has not been successfully finished. |
+
|
+The payment is in progress. The merchant can’t be informed about the success or failure of the payment. |
+
The confirmUrl defines the URL of online shop that is used by QENTA Checkout Server to send the result of the payment process back.
For QPAY Checkout Page confirmUrl is optional because the same parameters and values are posted to successUrl, failureUrl, cancelUrl or pendingUrl.
For QMORE Checkout Seamless confirmUrl is required because no return parameters are sent to the successUrl.
Use the confirmUrl to save the result of each payment process in the database for later use. Additionally, if consumer does not receive the page of the successUrl, the confirmUrl informs about the result of the payment process anyway.
| + + | +
+The URL has to be accessible over the Internet via port 80 (HTTP) or port 443 (HTTPS) and may not be hosted on a local server that can’t be accessed by the QENTA Checkout Server via the Internet. Also, ensure that firewall configurations allow receiving the confirmation sent via 212.183.46.16/28. For HTTPS communication only TLS can be used, older protocols are not supported.
+ |
+
QENTA does not verify whether or not the confirmation was successfully received by the web server. Redelivery attempts can be enabled by our integration specialists, they will set the intervals for redelivery attempts according to the requirements. The intervals are set in minutes, the minimum is one minute, or hours, and the maximum is 99 hours. During times of high load on the QENTA Checkout Server, a redelivery attempt may start a bit delayed, however, it will never start before the defined interval. To use this feature, the request parameter confirmUrl has to be sent. Optionally the request parameter confirmMail can be used to send confirmation e-mails individually per transaction.
If the confirmation was successfully received, the response will be OK; otherwise, the response will be NOK and a message which specifies the error. Use one of the following three possibilities to configure the response parameters.
The following content is possible for HTML comments and plain response: <QPAY-CONFIRMATION-RESPONSE result="OK|NOK" message="ans..255"/>
+ 
+ 
+ 
+ <!--<QPAY-CONFIRMATION-RESPONSE result="OK" /> -→ (1)
+<!--<QPAY-CONFIRMATION-RESPONSE result="NOK" message="Fingerprint validation failed."/> -→ (2)| 1 | +for confirming the successful receipt of our confirmation. | +
| 2 | +for confirming the unsuccessful receipt of our confirmation. | +
<QPAY-CONFIRMATION-RESPONSE result="OK" /> (1)
+<QPAY-CONFIRMATION-RESPONSE result="NOK" message="Session not found." /> (2)| 1 | +for confirming the successful receipt of our confirmation. | +
| 2 | +for confirming the unsuccessful receipt of our confirmation. | +
{"status":"OK","errorCodes":null,"QPAY-CONFIRMATION-RESPONSE":{"result": "OK"}} (1)
+{"status":"NOK","errorCodes":12345,"QPAY-CONFIRMATION-RESPONSE":{"result": "NOK","message":"Session not found."}} (2)| 1 | +for confirming the successful receipt of our confirmation. | +
| 2 | +for confirming the unsuccessful receipt of our confirmation. | +
| + + | +
+If web server is down for some reason or can’t be accessed by the QENTA Checkout Server, the confirmation can’t be delivered to the confirmURL, and no responses may be sent. QENTA will continue to resend the confirmation until receiving the %%result="OK"%% or until the last redelivery attempt was made.
+ |
+
In case QENTA has sent a confirmation and no response was received by the time the last redelivery attempt was made, only one final information is sent to the given e-mail address.
+If the consumer in online shop has terminated a session unexpectedly e.g. closing the browser window, the first confirmation is sent automatically and not earlier than 30 minutes after the request was sent by QENTA.
+The customerStatement parameter defines a text which is displayed on the bank statement issued to a consumer by the financial service provider.
The set of allowed characters and the allowed maximum length depends on the restrictions for payment methods and the corresponding financial service providers.
+The displayText parameter defines a text which is displayed during the payment process on the QPAY Checkout Page. If displayText is not used, the required parameter OrderDescription will be used instead.
This text is not transmitted to any financial service provider and is therefore NEVER displayed on any consumer’s invoice or statement.
+The duplicateRequestCheck parameter checks if the same order has been unintentionally sent more than once by a consumer. The consumer may unintentionally resend the same order by pressing the reload button of the browser because of problems with the internet connection.
For this check ensure that the required parameter orderDescription or any other customer parameter used in the fingerprint calculation is different for each order to prevent false-positive detection of duplicate requests. Since for each request, a hash of all parameter values is sent, i.e. the fingerprint, QENTA can easily detect any identical request that has been sent in the last 30 minutes.
| + + | ++QENTA can check for duplicate requests, and for that set the value of parameter to “yes”; otherwise, don’t send this parameter. + | +
financialInstitution can be used in conjunction with the parameter paymentType, when a specific payment method is selected by the consumer in the online shop. One or more financial institutions can be defined as what is wanted to offer to consumers based on the selected payment method. The individual brands may be listed in any order within the parameter:
Allow all brands, force 3-D Secure for brands that support 3-D Secure:
+financialInstitution=amexsafekey,DinersProtectBuy,DiscoverProtectBuy,MCSC,Maestro,VbV
Limit to American Express SafeKey, Mastercard, and Visa 3-D Secure:
+financialInstitution=amexsafekey,MCSC,VbV
| + + | ++Payment method EPS/Giropay only allows one value, while other payment methods like Credit Card allows a comma-separated list of values. + | +
financialInstitution by paymentTypePossible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Installment for Riverty |
+
|
+Invoice for Riverty |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Mastercard ID Check |
+
|
+Mastercard |
+
|
+Maestro SecureCode |
+
|
+Visa |
+
|
+Visa Secure |
+
|
+American Express |
+
|
+American Express SafeKey |
+
|
+Diners Club |
+
|
+Discover |
+
|
+Diners Protect Buy |
+
|
+Discover Protect Buy |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+EPS SELECT OPTION |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Invoice by payolution |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+PayPal |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Przelewy24 |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+SEPA Direct Debit |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Sofort. |
+
The imageUrl parameter defines the URL to an image on a web server. The image will be displayed during the payment process on QPAY Checkout Page. Image size should have a width of 200 pixels and a height of 100 pixels and the supported image formats are gif, jpg, and png.
| + + | ++For security reasons we don’t accept .svg images provided by the customer, so use .png instead. + | +
There must be an image available within the given image URL; the loading of QPAY Checkout Page will be delayed until a time-out for the missing image occurs.
+If imageUrl is not used then the required parameter serviceUrl will not be used too. Otherwise, the image will be encapsulated by a link to the serviceUrl, so that the consumer can click on the image to view the HTML page available at the serviceUrl.
| + + | +
+This URL has to be accessible over the internet https:// and must be accessible by the QENTA Checkout Server.
+ |
+
javascriptScriptVersion defines the version of the used JavaScript for managing the JavaScript-based communication between the HTML page and the QENTA Data Storage. If the parameter is set to pci3, QENTA data storage creates an iFrame that can be integrated into the homepage.
If the parameter is not set the javascript fields will be delivered to the to the system.
+The parameter mandateId defines a two-party mandate between the merchant and the debtor and is required for SEPA Direct Debit payments. The mandate is an agreement giving the merchant permission to debit the consumer’s account for the sum that the two parties agreed upon. Every mandate has an ID provided by the merchant that has to be unique for the creditor.
The parameter mandateSignatureDate defines the date on which the above-mentioned mandate was signed by the consumer.
The maxRetries parameter defines the maximum number of payment attempts regarding a unique order.
| Value | +Behavior | +
|---|---|
|
+No restriction regarding the number of retries a consumer can do. |
+
|
+No retry is possible for the consumer. If an error occurs the consumer will be redirected to the |
+
|
+Maximum number of retries the consumer can do before redirecting to the |
+
| + + | ++Contact our sales team to activate this feature. + | +
With the parameter noScriptInfoURL define the URL to an information page of the online shop which is displayed to the consumer if the web browser of the consumer has JavaScript disabled.
This information page within the online shop informs consumers of the requirement to enable JavaScript and a guide on how to do this in the web browser.
+The orderIdent parameter defines a unique reference to a specific order of a specific consumer within an online shop. This parameter is used within the QENTA Data Storage together with the customerId, shopId and storageId so that only the merchant is able to access the specific session of the QENTA Data Storage.
The value of the orderIdent has to be unique for each order of the consumer. Use the same value for initializing the QENTA Data Storage and for initiating the payment process.
orderNumber defines a unique ID for the order and when the value of the parameter is set it’s not possible to use that order number for the second time. Even if the consumer could not successfully finalize the payment process, therefore orderNumber can only be used if the parameter maxRetries is set to 0.
| + + | +
+The feature has to be activated by our sales team, otherwise QENTA is generating the orderNumber.
+ |
+
The orderReference parameter defines a unique transaction ID that will be forwarded to the financial institution.
The set of allowed characters and the allowed maximum length depends on the restrictions for payment methods and the corresponding financial service providers.
+paymenttypeSortOrder defines the sort order of all displayed payment methods and their corresponding sub-methods if paymentType is set to SELECT.
Offer a county-specific sort order by the payment methods with this parameter.
+| + + | ++The sort order of the payment methods can be set by using a comma-separated list as defined within the parameter paymentType. Also, all available sub-methods can be found within the description of the parameter financialInstitution, and add them to the list. + | +
The pendingUrl parameter defines the URL of online shop where a consumer is forwarded when the payment process could not determine a result yet.
| + + | +
+When using the optional parameter pendingUrl, the use of the parameter confirmUrl is mandatory.
+ |
+
The pendingUrl is an optional request parameter for backward compatibility with existing online shops, but use the parameter for handling asynchronous payment methods or payment methods that may have sometimes a delay in returning a final state of a transaction.
When the QENTA Checkout Server receives a final state from the corresponding financial service provider the information to the confirmUrl will be sent.
| paymentType | +Required | +Highly recommended | +Not needed | +
|---|---|---|---|
|
++ | ✔ |
++ |
|
++ | ✔ |
++ |
|
++ | ✔ |
++ |
|
++ | ✔ |
++ |
|
++ | + | ✔ |
+
|
++ | ✔ |
++ |
|
++ | ✔ |
++ |
|
++ | ✔ |
++ |
|
++ | + | ✔ |
+
|
++ | ✔ |
++ |
If the consumer has entered or changed his shipping or billing information after initialization, e.g. when using QPBL PayByLink then purchaseInformation is returned in the confirmation request made to confirmUrl. It is a Base64 encoded string that contains consumer, basket and order data as well as any additional parameters sent during initialization in JSON.
purchaseInformation=ewogICAgImFkZGl0aW9uYWxQYXJhbWV0ZXJzIjogewogICAgICAgICJDT05TVU1FUl9NRVJDSEFOVF9DUk1fSUQiOiAiMTIzNDIzNTM0NiIsCiAgICAgICAgInNob3BuYW1lX2N1c3RvbVBhcmFtZXRlcjEiOiAieW91ciBmaXJzdCBjdXN0b20gcGFyYW1ldGVyIiwKICAgICAgICAic2hvcG5hbWVfY3VzdG9tUGFyYW1ldGVyMiI6ICJ5b3VyIHNlY29uZCBjdXN0b20gcGFyYW1ldGVyIgogICAgfSwKICAgICJvcmRlckRlc2NyaXB0aW9uIjogIlRlc3Q6MDAwMCIsCiAgICAiY3VzdG9tZXJTdGF0ZW1lbnQiOiAiWW91ciBTaG9wbmFtZTogT3JkZXI6IDEyM3BhZ2UiLAogICAgIm9yZGVyUmVmZXJlbmNlIjogIjEyM3BhZ2UiLAogICAgImNvbnN1bWVyQmlsbGluZ0ZpcnN0TmFtZSI6ICJBbmRlcmVyQmlsbGluZyIsCiAgICAiY29uc3VtZXJCaWxsaW5nTGFzdE5hbWUiOiAiQmlsaW5nbmFjaG5hbWUiLAogICAgImNvbnN1bWVyQmlsbGluZ0FkZHJlc3MxIjogIkNcL08gS1x1MDBmY25pYmVydCBHcm9cdTAwZGYiLAogICAgImNvbnN1bWVyQmlsbGluZ0FkZHJlc3MyIjogIkJpbGxpbmdzdHJhXHUwMGRmZSAxMCIsCiAgICAiY29uc3VtZXJCaWxsaW5nQ2l0eSI6ICJHcmF6IiwKICAgICJjb25zdW1lckJpbGxpbmdaaXBDb2RlIjogIjgwMjAiLAogICAgImNvbnN1bWVyQmlsbGluZ0NvdW50cnkiOiAiU1IiLAogICAgImNvbnN1bWVyQmlsbGluZ1N0YXRlIjogIndvaXNkYXMiLAogICAgImNvbnN1bWVyU2hpcHBpbmdGaXJzdE5hbWUiOiAiU2hpcFZvcm5hbWVOZXUiLAogICAgImNvbnN1bWVyU2hpcHBpbmdMYXN0TmFtZSI6ICJTaGlwTmFjaG5hbWVOZXUiLAogICAgImNvbnN1bWVyU2hpcHBpbmdBZGRyZXNzMSI6ICJTaGlwcGluZ3N0cmFcdTAwZGZlIDEwYSIsCiAgICAiY29uc3VtZXJTaGlwcGluZ0FkZHJlc3MyIjogIjVcL0EgLSAzMyBTdC4gMTAwMCIsCiAgICAiY29uc3VtZXJTaGlwcGluZ0NpdHkiOiAiR3JheiIsCiAgICAiY29uc3VtZXJTaGlwcGluZ1ppcENvZGUiOiAiODAyMCIsCiAgICAiY29uc3VtZXJTaGlwcGluZ1N0YXRlIjogIkFuZHJlclN0YWF0IiwKICAgICJjb25zdW1lclNoaXBwaW5nQ291bnRyeSI6ICJHVSIsCiAgICAiY29uc3VtZXJTaGlwcGluZ0l0ZW1BdmFpbGFiaWxpdHkiOiAiMDEiLAogICAgImNvbnN1bWVyU2hpcHBpbmdNZXRob2QiOiAiaG9tZV9kZWxpdmVyeSIsCiAgICAiY29uc3VtZXJTaGlwcGluZ0FkZHJlc3NGaXJzdFVzZURhdGUiOiAiMTAuMTIuMjAyMSIsCiAgICAiYmFza2V0SXRlbXMiOiAiMyIsCiAgICAiYmFza2V0SXRlbSI6IHsKICAgICAgICAiMSI6IHsKICAgICAgICAgICAgImFydGljbGVOdW1iZXIiOiAiQTAwMSIsCiAgICAgICAgICAgICJxdWFudGl0eSI6ICIxIiwKICAgICAgICAgICAgIm5hbWUiOiAiUHJvZHVjdCBBMSIsCiAgICAgICAgICAgICJ1bml0R3Jvc3NBbW91bnQiOiAiMTAuODAiLAogICAgICAgICAgICAidW5pdE5ldEFtb3VudCI6ICI5LjAwIiwKICAgICAgICAgICAgInVuaXRUYXhBbW91bnQiOiAiMS44MCIsCiAgICAgICAgICAgICJ1bml0VGF4UmF0ZSI6ICIyMC4wMDAiCiAgICAgICAgfSwKICAgICAgICAiMiI6IHsKICAgICAgICAgICAgImFydGljbGVOdW1iZXIiOiAiQTAwMiIsCiAgICAgICAgICAgICJxdWFudGl0eSI6ICIxIiwKICAgICAgICAgICAgIm5hbWUiOiAiUHJvZHVjdCBBMiIsCiAgICAgICAgICAgICJ1bml0R3Jvc3NBbW91bnQiOiAiMTQuOTQiLAogICAgICAgICAgICAidW5pdE5ldEFtb3VudCI6ICIxMi40NSIsCiAgICAgICAgICAgICJ1bml0VGF4QW1vdW50IjogIjIuNDkiLAogICAgICAgICAgICAidW5pdFRheFJhdGUiOiAiMjAuMDAwIgogICAgICAgIH0sCiAgICAgICAgIjMiOiB7CiAgICAgICAgICAgICJhcnRpY2xlTnVtYmVyIjogIlMwMDEiLAogICAgICAgICAgICAicXVhbnRpdHkiOiAiMSIsCiAgICAgICAgICAgICJuYW1lIjogIlNoaXBwaW5nIiwKICAgICAgICAgICAgInVuaXRHcm9zc0Ftb3VudCI6ICI5NzQuMjUiLAogICAgICAgICAgICAidW5pdE5ldEFtb3VudCI6ICI5NzQuMjUiLAogICAgICAgICAgICAidW5pdFRheEFtb3VudCI6ICIwLjAwIiwKICAgICAgICAgICAgInVuaXRUYXhSYXRlIjogIjAuMDAwIgogICAgICAgIH0KICAgIH0sCiAgICAiY29uc3VtZXJFbWFpbCI6ICJlZGl0aWVydGUuZW1haWwuYWRyZXNzZUB0ZXN0LmNvbSIsCiAgICAiY29uc3VtZXJTaGlwcGluZ1Bob25lIjogIjEyMzQ1Njc4MzQ1NjciLAogICAgImNvbnN1bWVySXBBZGRyZXNzIjogIjE3Mi4yMC4wLjIwMyIsCiAgICAiY29uc3VtZXJCaXJ0aERhdGUiOiAiMjAwMS0wMy0wMSIKfQ=={
+ "additionalParameters": {
+ "CONSUMER_MERCHANT_CRM_ID": "1234235346",
+ "shopname_customParameter1": "first custom parameter",
+ "shopname_customParameter2": "second custom parameter"
+ },
+ "orderDescription": "Test:0000",
+ "customerStatement": "Your Shopname: Order: 123page",
+ "orderReference": "123page",
+ "consumerBillingFirstName": "AndererBilling",
+ "consumerBillingLastName": "Bilingnachname",
+ "consumerBillingAddress1": "C\/O K\u00fcnibert Gro\u00df",
+ "consumerBillingAddress2": "Billingstra\u00dfe 10",
+ "consumerBillingCity": "Graz",
+ "consumerBillingZipCode": "8020",
+ "consumerBillingCountry": "SR",
+ "consumerBillingState": "woisdas",
+ "consumerShippingFirstName": "ShipVornameNeu",
+ "consumerShippingLastName": "ShipNachnameNeu",
+ "consumerShippingAddress1": "Shippingstra\u00dfe 10a",
+ "consumerShippingAddress2": "5\/A - 33 St. 1000",
+ "consumerShippingCity": "Graz",
+ "consumerShippingZipCode": "8020",
+ "consumerShippingState": "AndrerStaat",
+ "consumerShippingCountry": "GU",
+ "consumerShippingItemAvailability": "01",
+ "consumerShippingMethod": "home_delivery",
+ "consumerShippingAddressFirstUseDate": "10.12.2021",
+ "basketItems": "3",
+ "basketItem": {
+ "1": {
+ "articleNumber": "A001",
+ "quantity": "1",
+ "name": "Product A1",
+ "unitGrossAmount": "10.80",
+ "unitNetAmount": "9.00",
+ "unitTaxAmount": "1.80",
+ "unitTaxRate": "20.000"
+ },
+ "2": {
+ "articleNumber": "A002",
+ "quantity": "1",
+ "name": "Product A2",
+ "unitGrossAmount": "14.94",
+ "unitNetAmount": "12.45",
+ "unitTaxAmount": "2.49",
+ "unitTaxRate": "20.000"
+ },
+ "3": {
+ "articleNumber": "S001",
+ "quantity": "1",
+ "name": "Shipping",
+ "unitGrossAmount": "974.25",
+ "unitNetAmount": "974.25",
+ "unitTaxAmount": "0.00",
+ "unitTaxRate": "0.000"
+ }
+ },
+ "consumerEmail": "editierte.email.adresse@test.com",
+ "consumerShippingPhone": "1234567834567",
+ "consumerIpAddress": "172.20.0.203",
+ "consumerBirthDate": "2001-03-01"
+}The shopId defines the unique identifier for the online shop within customerId. This is used if the merchant has multiple online shops or one online shop with multiple configurations within one customerId.
| + + | +
+The use of shopId has to clarify with the support, so contact integration specialists.
+ |
+
The parameter storageId is the unique ID to the QENTA Data Storage of a specific consumer within a specific payment process. The storageId is valid for 30 minutes after the latest use of an initialization, store or read operation on that Data Storage.
| + + | +
+storageId gets invalid after a successful initiation of the payment process.
+ |
+
The transactionIdentifier parameter defines whether a transaction is a single transaction or an initial transaction followed by many subsequent ones. Value SINGLE is a standard singular transaction for which authorization is given once by the consumer to collect only one transaction and value INITIAL for the first transaction of a series of recurring payments.
| + + | +
+If the parameter transactionIdentifier is used, the configuration setting is overwritten correspondingly, if is not used, the value set in the merchant configuration is used.
+ |
+
Currently, the transactionIdentifier may be used for payment methods PayPal and SEPA Direct Debit and it’s required to distinguish between a single transaction or the first transaction with subsequent transaction based on the first one.
| + + | +
+Backend operation recurPayment may only be carried out if the transactionIdentifier value INITIAL is used. For using the value INITIAL for subsequent recurring transactions, additional approval from the financial service provider needs to be obtained e.g. for PayPal. After receiving approval contact our integration specialists to enable the feature.
+ |
+
The windowName parameter defines the name of the pop-up window of iframe where QPAY Checkout Page or an additional payment window is opened.
| + + | +
+windowName is required if the merchant offered payment methods that open an additional pop-up window like eps-Überweisung or PayPal. It ensures a proper return to the checkout process after that payment method-specific pop-up window is closed.
+ |
+
The window name must contain uppercase and lowercase letters and underscores, and must not contain any whitespace characters or foreign characters.
+Opening QPAY Checkout Page or QMORE Checkout Seamless within a pop-up window may cause problems to the consumers if they have enabled a pop-up blocker within their browsers or it’s activated by default.
+The parameter creditorId identifies a merchant and allows consumers to manage their mandates with merchants more easily.
The parameter dueDate defines the day when payment is debited from the consumer’s bank account.
+financialInstitution by paymentTypePossible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Installment for Riverty |
+
|
+Invoice for Riverty |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Mastercard |
+
|
+Maestro SecureCode |
+
|
+Visa |
+
|
+American Express |
+
|
+Diners Club |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+EPS SELECT OPTION |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Invoice by payolution |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+PayPal |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Przelewy24 |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+SEPA Direct Debit |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Sofort. |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+PAYSAFECARD |
+
The information on the consumer’s country can’t be derived from the delivery address, so they will be taken from the data returned to QENTA by the respective financial service provider. E.g. in the case of credit cards, the country of the credit card issuer is returned and used to determine the consumer’s country.
+instrumentCountry can be used for payment methods: Credit Card, PayPal, and Sofort.
To check the authenticity of the return values sent from the QENTA Checkout Server to the online shop, compare the responseFingerprint with a hash of the return values.
Create a string by concatenating all returned parameters based on the order in the return parameter responseFingerprintOrder. Then hash the string with an HMAC-SHA-512 algorithm using the secret as cryptographic key and compare the result with the value of the return parameter responseFingerprint. If both values are identical, the response is authentic, i.e. the confirmation was indeed sent by QENTA. If these values are not identical, recheck the calculation and consider that someone compromised the return values or has sent a possibly false confirmation for the payment. Therefore, don’t trust these return values and don’t assume that the payment was made even if it appears that way!
To ensure secure communication it’s essential that never disclose or share the secret with persons who are not involved in developing the online shop. Also, never forward the secret via unsecured communication channels e.g. mail, e-mail, fax or instant messaging. When the secret is submitted by fax make sure that the contents of the fax are disclosed only to authorized persons!
+If the merchant suspect that the secret has been revealed to unauthorized individuals, contact our integration specialists immediately and request a new secret!
+Each error code returned by the QENTA Checkout Server consists of 5 digits.
+If the validation of a parameter detects an error, the error code will always start with the digit 1 and is assembled as following: error code = error message + parameter
+| + + | +
+An error code of 11500 means 11000 for the error message and 500 for the parameter causing that error, so for example 11500 would mean: "Parameter CUSTOMERID missing".
+ |
+
All error codes that begin with {0} have a replacementText.
+| Error code | +English | +German | +
|---|---|---|
|
+Unknown error. {0} |
+Unbekannter Fehler für {0}. |
+
|
+{0} is missing. |
+{0} fehlt. |
+
|
+{0} is missing or is not allowed. |
+{0} fehlt oder ist in diesem Kommando nicht erlaubt. |
+
|
+{0} cannot be used twice. Probably the transaction has already been processed. |
+{0} darf nur einmal vergeben werden. Wahrscheinlich wurde die Transaktion bereits bearbeitet. |
+
|
+{0} is not allowed. |
+{0} ist nicht erlaubt. |
+
|
+{0} has an invalid length. |
+{0} hat eine ungültige Länge. |
+
|
+{0} is invalid. |
+{0} hat ein ungültiges Format. |
+
|
+{0} is not numeric. |
+{0} ist keine Zahl. Bitte korrigieren Sie Ihre Eingabe. |
+
|
+{0} is invalid. |
+{0} ist ungültig. |
+
|
+{0} is not allowed. |
+{0} ist für dieses Kommando nicht erlaubt. |
+
|
+The financial institution has declined the transaction. Please check the data you have entered. |
+Die Transaktion wurde von der Zahlungsstelle abgewiesen. Bitte überprüfen Sie Ihre Eingabe. |
+
|
+The financial institution has declined the transaction. Please check the data you have entered. |
+Die Transaktion wurde von der Zahlungsstelle abgewiesen. Bitte überprüfen Sie Ihre Eingabe. |
+
|
+The financial institution has declined the transaction. Please check the data you have entered. |
+Die Transaktion wurde von der Zahlungsstelle abgewiesen. Bitte überprüfen Sie Ihre Eingabe. |
+
|
+The financial institution has declined the transaction. Please check the data you have entered. |
+Die Transaktion wurde von der Kartengesellschaft abgewiesen. Bitte überprüfen Sie Ihre Eingabe. |
+
|
+The credit card has already expired. |
+Diese Kreditkarte ist abgelaufen. |
+
|
+The financial institution has declined the transaction. Please contact your issuing bank. |
+Die Transaktion wurde von der Kreditkartengesellschaft abgewiesen. Bitte kontaktieren Sie den Herausgeber Ihrer Karte. |
+
|
+The authorisation has been expired. |
+Die Genehmigung/Autorisierung ist bereits abgelaufen. |
+
|
+The batch close could not be completed. |
+Ein Fehler bezüglich eines Tagesabschlusses ist aufgetreten. |
+
|
+A payment was processed too soon after another one. Please try later once more. |
+Eine Zahlung wurde zu früh nach einer anderen durchgeführt. Bitte versuchen Sie es zu einem späteren Zeitpunkt erneut. |
+
|
+The transaction has not been authorised. |
+Die Zahlung wurde von Ihnen nicht autorisiert. |
+
|
+The financial institution cannot be contacted. Please try again later. |
+Die Zahlungsstelle ist derzeit nicht erreichbar. |
+
|
+Transaction failed. Please contact the support. |
+Transaktion fehlgeschlagen. Bitte kontaktieren Sie Ihren Händler. |
+
|
+Your card could not be identified. Please contact your issuing bank. |
+Ihre Kreditkarte konnte nicht identifiziert werden. Bitte kontaktieren Sie den Herausgeber Ihrer Karte. |
+
|
+Your card is not activated for Visa Secure. Please contact your issuing bank. |
+Ihre Kreditkarte ist noch nicht für Visa Secure angemeldet. Bitte kontaktieren Sie den Herausgeber Ihrer Karte. |
+
|
+Your card is not activated for Mastercard ID Check. Please contact your issuing bank. |
+Ihre Kreditkarte ist noch nicht für Mastercard ID Check angemeldet. Bitte kontaktieren Sie den Herausgeber Ihrer Karte. |
+
|
+Your card could not be identified. Please contact your issuing bank. |
+Ihre Kreditkarte konnte nicht identifiziert werden. Bitte kontaktieren Sie den Herausgeber Ihrer Karte. |
+
|
+The the financial institution has declined the transaction. Please check the data you have entered. |
+Die Transaktion wurde von der Zahlungsstelle abgewiesen. Bitte überprüfen Sie Ihre Eingabe. Kartennummer ungültig. |
+
|
+The the financial institution has declined the transaction. Please check the data you have entered. |
+Die Transaktion wurde von der Zahlungsstelle abgewiesen. Bitte überprüfen Sie Ihre Eingabe. Kartenprüfnummer ungültig. |
+
|
+The the financial institution has declined the transaction. Please check the data you have entered. |
+Die Transaktion wurde von der Zahlungsstelle abgewiesen. Bitte überprüfen Sie Ihre Eingabe. Transaktion für diese Karte nicht erlaubt. |
+
|
+The transaction has been aborted. Please try it again. |
+Sie haben die Transaktion abgebrochen. Bitte versuchen Sie es erneut. |
+
|
+Your mobile phone number is not activated for contents of this type. Please contact your mobile phone provider. |
+Ihre Rufnummer ist für Inhalte dieser Kategorie nicht freigeschaltet. Bitte wenden Sie sich an Ihren Mobilfunkbetreiber. |
+
|
+Your purchase limit has been exceeded. Please contact your mobile phone provider. |
+Ihr Einkaufslimit ist überschritten. Bitte wenden Sie sich an Ihren Mobilfunkbetreiber. |
+
|
+Your card is not activated for Maestro SecureCode. Please contact your issuing bank. |
+Ihre Karte ist noch nicht für Maestro SecureCode angemeldet. Bitte kontaktieren Sie Ihren Kartenausgeber. |
+
|
+Your card could not be identified. Please contact your issuing bank. |
+Die Identifizierung Ihrer Karte schlug fehl. Bitte kontaktieren Sie Ihren Kartenausgeber. |
+
|
+The transaction has been declined. Please contact the shop service line. |
+Die Transaktion wurde abgewiesen. Bitte kontaktieren Sie den Shop-Betreiber. |
+
|
+Trying to use synchronous fallback mechanism. |
+Es wird versucht, einen synchronen Fallback durchzuführen. |
+
|
+Bank details not allowed. |
+Bankverbindung nicht zugelassen. |
+
|
+The transaction was reversed and is not valid anymore. |
+Die Transaktion wurde bereits storniert und ist nicht mehr gültig. |
+
|
+The given bank is not participating. |
+Die angegebene Bank nimmt an diesem Verfahren nicht teil. |
+
|
+The given account is not activated (yet). |
+Das angegebene Konto ist (noch) nicht aktiviert. |
+
|
+Unfortunately your transaction was not accomplishable. This decision was made by an automated data processing process. Read the terms & conditions for further information. |
+Leider konnte Ihre Transaktion nicht durchgeführt werden. Diese Entscheidung wurde durch einen automatischen Datenverarbeitungsprozess getroffen. Lesen Sie die allgemeinen Geschäftsbedingungen für weitere Informationen. |
+
|
+The payment has been declined because of one of the following reasons: +- Some input fields were not correctly completed (address or name incorrectly spelled, etc.). +- You have recently moved and changed your address. +- Your name has recently changed (e.g. change of name following marriage). +- The indicated address is not your residential address or your delivery address differs from your billing address. +- As a result of automated risk monitoring the use of a different payment method is advised. +- An invoice has become due but is still outstanding. +- Bank details were not correctly entered or information was entered in the wrong input fields (when paying in installments from Germany). |
+Die Zahlung wurde aus einem der folgenden Gründe abgewiesen: +- Nicht alle Eingabefelder wurden korrekt ausgefüllt (Adresse, Name falsch geschrieben…). +- Es fand bei Ihnen vor kurzem ein Umzug statt. +- Ihr Name hat sich kürzlich (z.B. durch Heirat) geändert. +- Die angegebene Adresse entspricht nicht dem Wohnsitz bzw. Ihre Lieferadresse weicht von der Rechnungsadresse ab. +- Eine automatisierte Risikoüberprüfung legt ein anderes Zahlungsmittel nahe. +- Es gibt bereits eine inzwischen fällige aber noch offene Rechnung. +- Bankdaten wurden nicht korrekt eingegeben oder Felder vertauscht (bei Ratenzahlung aus Deutschland). |
+
|
+The voucher is not applicable for this operation. |
+Der Gutschein ist für diese Operation nicht vorgesehen. |
+
|
+Insufficient voucher balance. |
+Unzureichendes Gutschein-Guthaben. |
+
|
+Your card is not activated for American Express SafeKey. Please contact your issuing bank. |
+Ihre Kreditkarte ist noch nicht für American Express SafeKey angemeldet. Bitte kontaktieren Sie den Herausgeber Ihrer Karte. |
+
|
+Your card could not be identified. Please contact your issuing bank. |
+Ihre Kreditkarte konnte nicht identifiziert werden. Bitte kontaktieren Sie den Herausgeber Ihrer Karte. |
+
|
+Unknown error. |
+Unbekannte Error-ID. |
+
|
+This means of payment is not supported (yet). |
+Die angegebene Zahlungsart wird (noch) nicht unterstützt. |
+
|
+Invalid merchant configuration. |
+Ungültige Händlerkonfiguration. |
+
|
+The payment cannot be processed now. Please try it later once more. |
+Durchführung dieser Transaktion ist derzeit leider nicht möglich. Bitte versuchen Sie es zu einem späteren Zeitpunkt erneut. |
+
|
+The payment cannot be processed now. Please try it later once more. |
+Durchführung dieser Transaktion ist derzeit leider nicht möglich. Bitte versuchen Sie es zu einem späteren Zeitpunkt erneut. |
+
|
+The payment cannot be processed now. Please try it later once more. |
+Durchführung dieser Transaktion ist derzeit leider nicht möglich. Bitte versuchen Sie es zu einem späteren Zeitpunkt erneut. |
+
|
+A fatal error occurred. |
+QTILL meldet einen einen schwerwiegenden Systemfehler. |
+
|
+This command is not available for this type of payment. |
+Dieses Kommando ist für diese Zahlungsart nicht verfügbar. |
+
|
+The payment cannot be processed now. Please try it later once more. |
+Durchführung dieser Transaktion ist derzeit leider nicht möglich. Bitte versuchen Sie es zu einem späteren Zeitpunkt erneut. |
+
|
+The payment cannot be processed now. Please try it later once more. |
+Durchführung dieser Transaktion ist derzeit leider nicht möglich. Bitte versuchen Sie es zu einem späteren Zeitpunkt erneut. |
+
|
+The usage of real payment information (e.g. credit card number) is not allowed in demo mode. |
+Die Verwendung von echten Zahlungsinformationen (z.B. Kreditkartennummern) ist im Demo-Modus nicht erlaubt. |
+
|
+The payment cannot be processed now. Please try it later once more. |
+Durchführung dieser Transaktion ist derzeit leider nicht möglich. Bitte versuchen Sie es zu einem späteren Zeitpunkt erneut. |
+
|
+Invalid response. |
+Ungültige Antwort. |
+
|
+The requested operation is not allowed. |
+Die angefragte Operation ist nicht erlaubt. |
+
|
+The final state of the transaction could not yet be determined. |
+Der finale Status der Transaktion konnte noch nicht festgestellt werden. |
+
|
+{0} is not activated. |
+{0} ist nicht aktiviert. |
+
|
+You can only proceed with the transaction if you agree to the following conditions listed. |
+Sie können die Transaktion nur fortsetzen, wenn Sie mit den angeführten Bedingungen einverstanden sind. |
+
|
+POST data necessary for fullfilling the request is missing. Please configure your security software properly. |
+Für die Abwicklung der Transaktion notwendige POST-Daten fehlen. Bitte konfigurieren Sie Ihre Sicherheitsprogramme entsprechend. |
+
|
+The specified workflow was manipulated. Please use only the specified buttons for navigation. |
+Die vorgegebene Reihenfolge der Seitenaufrufe wurde manipuliert. Bitte verwenden Sie zum Navigieren nur die vorgegebenen Schaltflächen. |
+
|
+The page was called with data missing. |
+Die Seite wurden nicht mit den erwarteten Daten aufgerufen. |
+
|
+Your card could not be recognized from Netswipe. |
+Ihre Karte konnte von Netswipe nicht gelesen werden. |
+
|
+Session timed out after 30 minutes without activity. |
+Die Benutzersitzung wurde nach 30 minütiger Inaktivität beendet. |
+
|
+No payment information available for this payment method. |
+Für diese Zahlungsart sind keine Zahlungsinformationen verfügbar. |
+
Error code |
+|
|
+|
Language |
+Message |
+
English |
+Unknown error. {0} |
+
German |
+Unbekannter Fehler für {0}. |
+
|
+|
Language |
+Message |
+
English |
+{0} is missing. |
+
German |
+{0} fehlt. |
+
|
+|
Language |
+Message |
+
English |
+{0} is missing or is not allowed. |
+
German |
+{0} fehlt oder ist in diesem Kommando nicht erlaubt. |
+
|
+|
Language |
+Message |
+
English |
+{0} cannot be used twice. Probably the transaction has already been processed. |
+
German |
+{0} darf nur einmal vergeben werden. Wahrscheinlich wurde die Transaktion bereits bearbeitet. |
+
|
+|
Language |
+Message |
+
English |
+{0} is not allowed. |
+
German |
+{0} ist nicht erlaubt. |
+
|
+|
Language |
+Message |
+
English |
+{0} has an invalid length. |
+
German |
+{0} hat eine ungültige Länge. |
+
|
+|
Language |
+Message |
+
English |
+{0} is invalid. |
+
German |
+{0} hat ein ungültiges Format. |
+
|
+|
Language |
+Message |
+
English |
+{0} is not numeric. |
+
German |
+{0} ist keine Zahl. Bitte korrigieren Sie Ihre Eingabe. |
+
|
+|
Language |
+Message |
+
English |
+{0} is invalid. |
+
German |
+{0} ist ungültig. |
+
|
+|
Language |
+Message |
+
English |
+{0} is not allowed. |
+
German |
+{0} ist für dieses Kommando nicht erlaubt. |
+
|
+|
Language |
+Message |
+
English |
+The financial institution has declined the transaction. Please check the data you have entered. |
+
German |
+Die Transaktion wurde von der Zahlungsstelle abgewiesen. Bitte überprüfen Sie Ihre Eingabe. |
+
|
+|
Language |
+Message |
+
English |
+The financial institution has declined the transaction. Please check the data you have entered. |
+
German |
+Die Transaktion wurde von der Zahlungsstelle abgewiesen. Bitte überprüfen Sie Ihre Eingabe. |
+
|
+|
Language |
+Message |
+
English |
+The financial institution has declined the transaction. Please check the data you have entered. |
+
German |
+Die Transaktion wurde von der Zahlungsstelle abgewiesen. Bitte überprüfen Sie Ihre Eingabe. |
+
|
+|
Language |
+Message |
+
English |
+The financial institution has declined the transaction. Please check the data you have entered. |
+
German |
+Die Transaktion wurde von der Kartengesellschaft abgewiesen. Bitte überprüfen Sie Ihre Eingabe. |
+
|
+|
Language |
+Message |
+
English |
+The credit card has already expired. |
+
German |
+Diese Kreditkarte ist abgelaufen. |
+
|
+|
Language |
+Message |
+
English |
+The financial institution has declined the transaction. Please contact your issuing bank. |
+
German |
+Die Transaktion wurde von der Kreditkartengesellschaft abgewiesen. Bitte kontaktieren Sie den Herausgeber Ihrer Karte. |
+
|
+|
Language |
+Message |
+
English |
+The authorisation has been expired. |
+
German |
+Die Genehmigung/Autorisierung ist bereits abgelaufen. |
+
|
+|
Language |
+Message |
+
English |
+The batch close could not be completed. |
+
German |
+Ein Fehler bezüglich eines Tagesabschlusses ist aufgetreten. |
+
|
+|
Language |
+Message |
+
English |
+A payment was processed too soon after another one. Please try later once more. |
+
German |
+Eine Zahlung wurde zu früh nach einer anderen durchgeführt. Bitte versuchen Sie es zu einem späteren Zeitpunkt erneut. |
+
|
+|
Language |
+Message |
+
English |
+The transaction has not been authorised. |
+
German |
+Die Zahlung wurde von Ihnen nicht autorisiert. |
+
|
+|
Language |
+Message |
+
English |
+The financial institution cannot be contacted. Please try again later. |
+
German |
+Die Zahlungsstelle ist derzeit nicht erreichbar. |
+
|
+|
Language |
+Message |
+
English |
+Transaction failed. Please contact the support. |
+
German |
+Transaktion fehlgeschlagen. Bitte kontaktieren Sie Ihren Händler. |
+
|
+|
Language |
+Message |
+
English |
+Your card could not be identified. Please contact your issuing bank. |
+
German |
+Ihre Kreditkarte konnte nicht identifiziert werden. Bitte kontaktieren Sie den Herausgeber Ihrer Karte. |
+
|
+|
Language |
+Message |
+
English |
+Your card is not activated for Visa Secure. Please contact your issuing bank. |
+
German |
+Ihre Kreditkarte ist noch nicht für Visa Secure angemeldet. Bitte kontaktieren Sie den Herausgeber Ihrer Karte. |
+
|
+|
Language |
+Message |
+
English |
+Your card is not activated for Mastercard ID Check. Please contact your issuing bank. |
+
German |
+Ihre Kreditkarte ist noch nicht für Mastercard ID Check angemeldet. Bitte kontaktieren Sie den Herausgeber Ihrer Karte. |
+
|
+|
Language |
+Message |
+
English |
+Your card could not be identified. Please contact your issuing bank. |
+
German |
+Ihre Kreditkarte konnte nicht identifiziert werden. Bitte kontaktieren Sie den Herausgeber Ihrer Karte. |
+
|
+|
Language |
+Message |
+
English |
+The the financial institution has declined the transaction. Please check the data you have entered. |
+
German |
+Die Transaktion wurde von der Zahlungsstelle abgewiesen. Bitte überprüfen Sie Ihre Eingabe. Kartenprüfnummer ungültig. |
+
|
+|
Language |
+Message |
+
English |
+The the financial institution has declined the transaction. Please check the data you have entered. |
+
German |
+Die Transaktion wurde von der Zahlungsstelle abgewiesen. Bitte überprüfen Sie Ihre Eingabe. Transaktion für diese Karte nicht erlaubt. |
+
|
+|
Language |
+Message |
+
English |
+The transaction has been aborted. Please try it again. |
+
German |
+Sie haben die Transaktion abgebrochen. Bitte versuchen Sie es erneut. |
+
|
+|
Language |
+Message |
+
English |
+Your mobile phone number is not activated for contents of this type. Please contact your mobile phone provider. |
+
German |
+Ihre Rufnummer ist für Inhalte dieser Kategorie nicht freigeschaltet. Bitte wenden Sie sich an Ihren Mobilfunkbetreiber. |
+
|
+|
Language |
+Message |
+
English |
+Your purchase limit has been exceeded. Please contact your mobile phone provider. |
+
German |
+Ihr Einkaufslimit ist überschritten. Bitte wenden Sie sich an Ihren Mobilfunkbetreiber. |
+
|
+|
Language |
+Message |
+
English |
+Your card is not activated for Maestro SecureCode. Please contact your issuing bank. |
+
German |
+Ihre Karte ist noch nicht für Maestro SecureCode angemeldet. Bitte kontaktieren Sie Ihren Kartenausgeber. |
+
|
+|
Language |
+Message |
+
English |
+Your card could not be identified. Please contact your issuing bank. |
+
German |
+Die Identifizierung Ihrer Karte schlug fehl. Bitte kontaktieren Sie Ihren Kartenausgeber. |
+
|
+|
Language |
+Message |
+
English |
+The transaction has been declined. Please contact the shop service line. |
+
German |
+Die Transaktion wurde abgewiesen. Bitte kontaktieren Sie den Shop-Betreiber. |
+
|
+|
Language |
+Message |
+
English |
+Trying to use synchronous fallback mechanism. |
+
German |
+Es wird versucht, einen synchronen Fallback durchzuführen. |
+
|
+|
Language |
+Message |
+
English |
+Bank details not allowed. |
+
German |
+Bankverbindung nicht zugelassen. |
+
|
+|
Language |
+Message |
+
English |
+The transaction was reversed and is not valid anymore. |
+
German |
+Die Transaktion wurde bereits storniert und ist nicht mehr gültig. |
+
|
+|
Language |
+Message |
+
English |
+The given bank is not participating. |
+
German |
+Die angegebene Bank nimmt an diesem Verfahren nicht teil. |
+
|
+|
Language |
+Message |
+
English |
+The given account is not activated (yet). |
+
German |
+Das angegebene Konto ist (noch) nicht aktiviert. |
+
|
+|
Language |
+Message |
+
English |
+Unfortunately your transaction was not accomplishable. This decision was made by an automated data processing process. Read the terms & conditions for further information. |
+
German |
+Leider konnte Ihre Transaktion nicht durchgeführt werden. Diese Entscheidung wurde durch einen automatischen Datenverarbeitungsprozess getroffen. Lesen Sie die allgemeinen Geschäftsbedingungen für weitere Informationen. |
+
|
+|
Language |
+Message |
+
English |
+The payment has been declined because of one of the following reasons: +- Some input fields were not correctly completed (address or name incorrectly spelled, etc.). +- You have recently moved and changed your address. +- Your name has recently changed (e.g. change of name following marriage). +- The indicated address is not your residential address or your delivery address differs from your billing address. +- As a result of automated risk monitoring the use of a different payment method is advised. +- An invoice has become due but is still outstanding. +- Bank details were not correctly entered or information was entered in the wrong input fields (when paying in installments from Germany). |
+
German |
+Die Zahlung wurde aus einem der folgenden Gründe abgewiesen: +- Nicht alle Eingabefelder wurden korrekt ausgefüllt (Adresse, Name falsch geschrieben…). +- Es fand bei Ihnen vor kurzem ein Umzug statt. +- Ihr Name hat sich kürzlich (z.B. durch Heirat) geändert. +- Die angegebene Adresse entspricht nicht dem Wohnsitz bzw. Ihre Lieferadresse weicht von der Rechnungsadresse ab. +- Eine automatisierte Risikoüberprüfung legt ein anderes Zahlungsmittel nahe. +- Es gibt bereits eine inzwischen fällige aber noch offene Rechnung. +- Bankdaten wurden nicht korrekt eingegeben oder Felder vertauscht (bei Ratenzahlung aus Deutschland). |
+
|
+|
Language |
+Message |
+
English |
+The voucher is not applicable for this operation. |
+
German |
+Der Gutschein ist für diese Operation nicht vorgesehen. |
+
|
+|
Language |
+Message |
+
English |
+Insufficient voucher balance. |
+
German |
+Unzureichendes Gutschein-Guthaben. |
+
|
+|
Language |
+Message |
+
English |
+Your card is not activated for American Express SafeKey. Please contact your issuing bank. |
+
German |
+Ihre Kreditkarte ist noch nicht für American Express SafeKey angemeldet. Bitte kontaktieren Sie den Herausgeber Ihrer Karte. |
+
|
+|
Language |
+Message |
+
English |
+Your card could not be identified. Please contact your issuing bank. |
+
German |
+Ihre Kreditkarte konnte nicht identifiziert werden. Bitte kontaktieren Sie den Herausgeber Ihrer Karte. |
+
|
+|
Language |
+Message |
+
English |
+Unknown error. |
+
German |
+Unbekannte Error-ID. |
+
|
+|
Language |
+Message |
+
English |
+This means of payment is not supported (yet). |
+
German |
+Die angegebene Zahlungsart wird (noch) nicht unterstützt. |
+
|
+|
Language |
+Message |
+
English |
+Invalid merchant configuration. |
+
German |
+Ungültige Händlerkonfiguration. |
+
|
+|
Language |
+Message |
+
English |
+The payment cannot be processed now. Please try it later once more. |
+
German |
+Durchführung dieser Transaktion ist derzeit leider nicht möglich. Bitte versuchen Sie es zu einem späteren Zeitpunkt erneut. |
+
|
+|
Language |
+Message |
+
English |
+The payment cannot be processed now. Please try it later once more. |
+
German |
+Durchführung dieser Transaktion ist derzeit leider nicht möglich. Bitte versuchen Sie es zu einem späteren Zeitpunkt erneut. |
+
|
+|
Language |
+Message |
+
English |
+The payment cannot be processed now. Please try it later once more. |
+
German |
+Durchführung dieser Transaktion ist derzeit leider nicht möglich. Bitte versuchen Sie es zu einem späteren Zeitpunkt erneut. |
+
|
+|
Language |
+Message |
+
English |
+A fatal error occurred. |
+
German |
+QTILL meldet einen einen schwerwiegenden Systemfehler. |
+
|
+|
Language |
+Message |
+
English |
+This command is not available for this type of payment. |
+
German |
+Dieses Kommando ist für diese Zahlungsart nicht verfügbar. |
+
|
+|
Language |
+Message |
+
English |
+The payment cannot be processed now. Please try it later once more. |
+
German |
+Durchführung dieser Transaktion ist derzeit leider nicht möglich. Bitte versuchen Sie es zu einem späteren Zeitpunkt erneut. |
+
|
+|
Language |
+Message |
+
English |
+The payment cannot be processed now. Please try it later once more. |
+
German |
+Durchführung dieser Transaktion ist derzeit leider nicht möglich. Bitte versuchen Sie es zu einem späteren Zeitpunkt erneut. |
+
|
+|
Language |
+Message |
+
English |
+The usage of real payment information (e.g. credit card number) is not allowed in demo mode. |
+
German |
+Die Verwendung von echten Zahlungsinformationen (z.B. Kreditkartennummern) ist im Demo-Modus nicht erlaubt. |
+
|
+|
Language |
+Message |
+
English |
+The payment cannot be processed now. Please try it later once more. |
+
German |
+Durchführung dieser Transaktion ist derzeit leider nicht möglich. Bitte versuchen Sie es zu einem späteren Zeitpunkt erneut. |
+
|
+|
Language |
+Message |
+
English |
+Invalid response. |
+
German |
+Ungültige Antwort. |
+
|
+|
Language |
+Message |
+
English |
+The requested operation is not allowed. |
+
German |
+Die angefragte Operation ist nicht erlaubt. |
+
|
+|
Language |
+Message |
+
English |
+The final state of the transaction could not yet be determined. |
+
German |
+Der finale Status der Transaktion konnte noch nicht festgestellt werden. |
+
|
+|
Language |
+Message |
+
English |
+{0} is not activated. |
+
German |
+{0} ist nicht aktiviert. |
+
|
+|
Language |
+Message |
+
English |
+You can only proceed with the transaction if you agree to the following conditions listed. |
+
German |
+Sie können die Transaktion nur fortsetzen, wenn Sie mit den angeführten Bedingungen einverstanden sind. |
+
|
+|
Language |
+Message |
+
English |
+POST data necessary for fullfilling the request is missing. Please configure your security software properly. |
+
German |
+Für die Abwicklung der Transaktion notwendige POST-Daten fehlen. Bitte konfigurieren Sie Ihre Sicherheitsprogramme entsprechend. |
+
|
+|
Language |
+Message |
+
English |
+The specified workflow was manipulated. Please use only the specified buttons for navigation. |
+
German |
+Die vorgegebene Reihenfolge der Seitenaufrufe wurde manipuliert. Bitte verwenden Sie zum Navigieren nur die vorgegebenen Schaltflächen. |
+
|
+|
Language |
+Message |
+
English |
+The page was called with data missing. |
+
German |
+Die Seite wurden nicht mit den erwarteten Daten aufgerufen. |
+
|
+|
Language |
+Message |
+
English |
+The card could not be recognized from Netswipe. |
+
German |
+Ihre Karte konnte von Netswipe nicht gelesen werden. |
+
|
+|
Language |
+Message |
+
English |
+Session timed out after 30 minutes without activity. |
+
German |
+Die Benutzersitzung wurde nach 30 minütiger Inaktivität beendet. |
+
|
+|
Language |
+Message |
+
English |
+No payment information available for this payment method. |
+
German |
+Für diese Zahlungsart sind keine Zahlungsinformationen verfügbar. |
+
| Error code | +English | +German | +
|---|---|---|
|
+Unknown Error |
+Unbekannte Parameter-ID |
+
|
+MERCHANTKEY |
+Händlerschlüssel |
+
|
+LOGWRITER |
+LOGWRITER |
+
|
+TOOLKIT PASSWORD |
+Toolkit Passwort |
+
|
+Socket Proxy Host |
+Socket Proxy Host |
+
|
+Socket Proxy Port |
+Socket Proxy Port |
+
|
+Command |
+Kommando |
+
|
+Language |
+Sprache |
+
|
+order number |
+Auftragsnummer |
+
|
+payment number |
+Zahlungsnummer |
+
|
+credit number |
+Gutschriftsnummer |
+
|
+batch number |
+Tagesabschlussnummer |
+
|
+amount |
+Betrag |
+
|
+Base exponent |
+Betragsexponent |
+
|
+currency |
+Währung |
+
|
+order description |
+Auftragsbeschreibung |
+
|
+account id |
+Kontennummer |
+
|
+SUCCESSURL |
+SUCCESSURL |
+
|
+FAILUREURL |
+FAILUREURL |
+
|
+CANCELURL |
+CANCELURL |
+
|
+PROCESSINGURL |
+PROCESSINGURL |
+
|
+SERVICEURL |
+SERVICEURL |
+
|
+SET extension field |
+SET-Erweiterungsfeld |
+
|
+ACCOUNTTYPE |
+ACCOUNTTYPE |
+
|
+TRANSACTIONPURPOSE |
+TRANSACTIONPURPOSE |
+
|
+CUSTOMERDATA |
+CUSTOMERDATA |
+
|
+FINGERPRINT |
+FINGERPRINT |
+
|
+PAYMENTTYPE |
+PAYMENTTYPE |
+
|
+Card number |
+Kartennummer |
+
|
+Expiration date |
+Ablaufdatum |
+
|
+Card security code |
+Kartenprüfnummer |
+
|
+Account number |
+Kontonummer |
+
|
+Bank sorting code |
+Bankleitzahl |
+
|
+phone number |
+Rufnummer |
+
|
+password |
+Passwort |
+
|
+PaRes |
+PaRes |
+
|
+MD |
+MD |
+
|
+USER_AGENT |
+User Agent |
+
|
+Country |
+Land der Bank |
+
|
+Bank name |
+Name der Bank |
+
|
+network operator |
+Mobilfunkbetreiber |
+
|
+Account owner |
+Kontoinhaber |
+
|
+Username |
+Benutzername |
+
|
+PAN |
+PAN |
+
|
+IP-Address |
+IP-Adresse |
+
|
+window name |
+Fenstername |
+
|
+airline extension |
+Flugdatenerweiterung |
+
|
+cardholder |
+Karteninhaber |
+
|
+IBAN |
+IBAN |
+
|
+BIC |
+BIC |
+
|
+iDEAL Issuer |
+iDEAL Issuer |
+
|
+ENTRANCE_CODE |
+ENTRANCE_CODE |
+
|
+Issue number |
+Kartenfolgenummer |
+
|
+Issue date |
+Kartenausgabedatum |
+
|
+Source ORDERNUMBER |
+Quell-Auftragsnummer |
+
|
+SUPPOSEDORDERNUMBER |
+Erwartete Auftragsnummer |
+
|
+FALLBACK |
+FALLBACK |
+
|
+OVERWRITE_WUM |
+OVERWRITE_WUM |
+
|
+DEPOSITFLAG |
+DEPOSITFLAG |
+
|
+SUPPRESS |
+SUPPRESS |
+
|
+XHTML_WAKE_UP_MESSAGES |
+XHTML_WAKE_UP_MESSAGES |
+
|
+CONFIRMURL |
+CONFIRMURL |
+
|
+VOUCHER_ID |
+Gutschein-Code (VOUCHER_ID) |
+
|
+INITIATION |
+INITIATION |
+
|
+amount authorised |
+Genehmigungsbetrag |
+
|
+amount deposited |
+Buchungsbetrag |
+
|
+QUERYFOR |
+QUERYFOR |
+
|
+minimum amount |
+Mindestbetrag |
+
|
+maximum amount |
+Maximalbetrag |
+
|
+begin create time |
+Anfangszeit der Erstellung der Transaktionen |
+
|
+end create time |
+Endzeit der Erstellung der Transaktionen |
+
|
+begin modify time |
+Anfangszeit der Änderung der Transaktionen |
+
|
+end modifiy time |
+Endzeit der Änderung der Transaktionen |
+
|
+begin open time |
+Anfangszeit der Öffnung der Tagesabschlüsse |
+
|
+end open time |
+Anfangszeit der Durchführung der Tagesabschlüsse |
+
|
+begin close time |
+Endzeit der Öffnung der Tagesabschlüsse |
+
|
+end close time |
+Endzeit der Durchführung der Tagesabschlüsse |
+
|
+Brand |
+Marke |
+
|
+RETURNATMOST |
+RETURNATMOST |
+
|
+order reference |
+Auftragsreferenz |
+
|
+customer statement |
+Abrechnungstext |
+
|
+order text |
+Auftragstext |
+
|
+SKIPFIRST |
+SKIPFIRST |
+
|
+ORDERBY |
+ORDERBY |
+
|
+ORDERIDENT |
+ORDERIDENT |
+
|
+RETURNURL |
+RETURNURL |
+
|
+STORAGEID |
+STORAGEID |
+
|
+JAVASCRIPT SCRIPT VERSION |
+JAVASCRIPT SCRIPT VERSION |
+
|
+HTTP-header count |
+Anzahl der HTTP-Header |
+
|
+HTTP-header name |
+Name eines HTTP-Headers |
+
|
+HTTP-header value |
+Wert eines HTTP-Headers |
+
|
+Consumers mail address |
+Mail-Adresse des Konsumenten |
+
|
+Consumers birth date |
+Geburtsdatum des Konsumenten |
+
|
+Consumers tax identification number |
+Steueridentifikationsnummer des Konsumenten |
+
|
+Consumers drivers license number |
+Führerscheinnummer des Konsumenten |
+
|
+Consumers drivers license state |
+Bundesstaat in dem der Führerschein des Konsumenten ausgestellt wurde |
+
|
+Consumers drivers license country |
+Land in dem der Führerschein des Konsumenten ausgestellt wurde |
+
|
+Billing address first name |
+Vorname der Rechnungsadresse |
+
|
+Billing address last name |
+Nachname der Rechnungsadresse |
+
|
+Billing address first line |
+Rechnungsadresse Teil 1 |
+
|
+Billing address second line |
+Rechnungsadresse Teil 2 |
+
|
+Billing city |
+Ort der Rechnungsadresse |
+
|
+Billing zip code |
+Postleitzahl der Rechungsadresse |
+
|
+Billing state |
+Bundesstaat der Rechnungsadresse |
+
|
+Billing country |
+Land der Rechnungsadresse |
+
|
+Billing phone |
+Telefonnummer der Rechnungsadresse |
+
|
+Billing fax |
+Faxnummer der Rechnungsadresse |
+
|
+Shipping address first name |
+Vorname der Lieferadresse |
+
|
+Shipping address last name |
+Nachname der Lieferadresse |
+
|
+Shipping address first line |
+Lieferadresse Teil 1 |
+
|
+Shipping address second line |
+Lieferadresse Teil 2 |
+
|
+Shipping city |
+Ort der Lieferadresse |
+
|
+Shipping zip code |
+Postleitzahl der Lieferadresse |
+
|
+Shipping state |
+Bundesstaat der Lieferadresse |
+
|
+Shipping country |
+Land der Lieferadresse |
+
|
+Shipping phone |
+Telefonnummer der Lieferadresse |
+
|
+Shipping fax |
+Faxnummer der Lieferadresse |
+
|
+Consumers language |
+Sprache des Konsumenten |
+
|
+Consumers device ID |
+Device ID des Konsumenten |
+
|
+Consumers ip address |
+IP-Adresse des Konsumenten |
+
|
+Shopping basket amount |
+Betrag des Warenkorbs |
+
|
+Shopping basket currency |
+Währung des Warenkorbs |
+
|
+Shopping basket item count |
+Anzahl der Artikel im Warenkorb |
+
|
+Shopping basket item article number |
+Artikelnummer eines Artikels im Warenkorb |
+
|
+Shopping basket item quantity |
+Anzahl eines Artikels im Warenkorb |
+
|
+Shopping basket item unit price |
+Preis eines Artikels im Warenkorb |
+
|
+Shopping basket item tax |
+Steuerbetrag eines Artikels im Warenkorb |
+
|
+Shopping basket item description |
+Beschreibung eines Artikels im Warenkorb |
+
|
+Shopping basket content |
+Inhalt des Warenkorbs |
+
|
+Shopping basket item image-URL |
+URL zu Bild/Logo eines Artikels im Warenkorb |
+
|
+Shopping basket item unit net amount |
+Nettopreis eines Artikels im Warenkorb |
+
|
+Shopping basket item unit tax amount |
+Steuerbetrag eines Artikels im Warenkorb |
+
|
+Shopping basket item unit tax rate |
+Steuersatz eines Artikels im Warenkorb |
+
|
+Shopping basket item unit gross amount |
+Bruttopreis eines Artikels im Warenkorb |
+
|
+Shopping basket item name |
+Bezeichnung eines Artikels im Warenkorb |
+
|
+Costumers company name |
+Firmenname des Kunden |
+
|
+Costumers company VAT identification number |
+Umsatzsteuer-Identifikationsnummer des Kunden |
+
|
+Customers company commercial register number |
+Firmenbuch-/Handelsregisternummer des Kunden |
+
|
+Customers other company registration key |
+Sonstige Firmenregistrierungsnummer des Kunden |
+
|
+CUSTOMERID |
+CUSTOMERID (Kundennummer) |
+
|
+SHOPID |
+SHOPID |
+
|
+FINANCIALINSTITUTION |
+FINANCIALINSTITUTION |
+
|
+DISPLAYTEXT |
+DISPLAYTEXT |
+
|
+CONFIRMURL |
+CONFIRMURL |
+
|
+IMAGEURL |
+IMAGEURL |
+
|
+REQUESTFINGERPRINT |
+REQUESTFINGERPRINT |
+
|
+DUPLICATEREQUESTCHECK |
+DUPLICATEREQUESTCHECK |
+
|
+REQUESTFINGERPRINTORDER |
+REQUESTFINGERPRINTORDER |
+
|
+SECRET |
+SECRET |
+
|
+MAXRETRIES |
+MAXRETRIES |
+
|
+BACKGROUNDCOLOR |
+BACKGROUNDCOLOR |
+
|
+NOSCRIPTINFOURL |
+NOSCRIPTINFOURL |
+
|
+CONFIRMMAIL |
+CONFIRMMAIL |
+
|
+AUTODEPOSIT |
+AUTODEPOSIT |
+
|
+PENDINGURL |
+PENDINGURL |
+
|
+PAYMENTTYPESORTORDER |
+PAYMENTTYPESORTORDER |
+
|
+LAYOUT |
+LAYOUT |
+
|
+SHIPPING_PROFILE |
+SHIPPING_PROFILE |
+
Error code |
+|
|
+|
Language |
+Message |
+
English |
+Unknown Error |
+
German |
+Unbekannte Parameter-ID |
+
|
+|
Language |
+Message |
+
English |
+MERCHANTKEY |
+
German |
+Händlerschlüssel |
+
|
+|
Language |
+Message |
+
English |
+LOGWRITER |
+
German |
+LOGWRITER |
+
|
+|
Language |
+Message |
+
English |
+TOOLKIT PASSWORD |
+
German |
+Toolkit Passwort |
+
|
+|
Language |
+Message |
+
English |
+Socket Proxy Host |
+
German |
+Socket Proxy Host |
+
|
+|
Language |
+Message |
+
English |
+Socket Proxy Port |
+
German |
+Socket Proxy Port |
+
|
+|
Language |
+Message |
+
English |
+Command |
+
German |
+Kommando |
+
|
+|
Language |
+Message |
+
English |
+Language |
+
German |
+Sprache |
+
|
+|
Language |
+Message |
+
English |
+order number |
+
German |
+Auftragsnummer |
+
|
+|
Language |
+Message |
+
English |
+payment number |
+
German |
+Zahlungsnummer |
+
|
+|
Language |
+Message |
+
English |
+credit number |
+
German |
+Gutschriftsnummer |
+
|
+|
Language |
+Message |
+
English |
+batch number |
+
German |
+Tagesabschlussnummer |
+
|
+|
Language |
+Message |
+
English |
+amount |
+
German |
+Betrag |
+
|
+|
Language |
+Message |
+
English |
+Base exponent |
+
German |
+Betragsexponent |
+
|
+|
Language |
+Message |
+
English |
+currency |
+
German |
+Währung |
+
|
+|
Language |
+Message |
+
English |
+order description |
+
German |
+Auftragsbeschreibung |
+
|
+|
Language |
+Message |
+
English |
+account id |
+
German |
+Kontennummer |
+
|
+|
Language |
+Message |
+
English |
+SUCCESSURL |
+
German |
+SUCCESSURL |
+
|
+|
Language |
+Message |
+
English |
+FAILUREURL |
+
German |
+FAILUREURL |
+
|
+|
Language |
+Message |
+
English |
+CANCELURL |
+
German |
+CANCELURL |
+
|
+|
Language |
+Message |
+
English |
+PROCESSINGURL |
+
German |
+PROCESSINGURL |
+
|
+|
Language |
+Message |
+
English |
+SERVICEURL |
+
German |
+SERVICEURL |
+
|
+|
Language |
+Message |
+
English |
+SET extension field |
+
German |
+SET-Erweiterungsfeld |
+
|
+|
Language |
+Message |
+
English |
+ACCOUNTTYPE |
+
German |
+ACCOUNTTYPE |
+
|
+|
Language |
+Message |
+
English |
+TRANSACTIONPURPOSE |
+
German |
+TRANSACTIONPURPOSE |
+
|
+|
Language |
+Message |
+
English |
+CUSTOMERDATA |
+
German |
+CUSTOMERDATA |
+
|
+|
Language |
+Message |
+
English |
+FINGERPRINT |
+
German |
+FINGERPRINT |
+
|
+|
Language |
+Message |
+
English |
+PAYMENTTYPE |
+
German |
+PAYMENTTYPE |
+
|
+|
Language |
+Message |
+
English |
+Card number |
+
German |
+Kartennummer |
+
|
+|
Language |
+Message |
+
English |
+Expiration date |
+
German |
+Ablaufdatum |
+
|
+|
Language |
+Message |
+
English |
+Card security code |
+
German |
+Kartenprüfnummer |
+
|
+|
Language |
+Message |
+
English |
+Account number |
+
German |
+Kontonummer |
+
|
+|
Language |
+Message |
+
English |
+Bank sorting code |
+
German |
+Bankleitzahl |
+
|
+|
Language |
+Message |
+
English |
+phone number |
+
German |
+Rufnummer |
+
|
+|
Language |
+Message |
+
English |
+password |
+
German |
+Passwort |
+
|
+|
Language |
+Message |
+
English |
+PaRes |
+
German |
+PaRes |
+
|
+|
Language |
+Message |
+
English |
+MD |
+
German |
+MD |
+
|
+|
Language |
+Message |
+
English |
+USER_AGENT |
+
German |
+User Agent |
+
|
+|
Language |
+Message |
+
English |
+Country |
+
German |
+Land der Bank |
+
|
+|
Language |
+Message |
+
English |
+Bank name |
+
German |
+Name der Bank |
+
|
+|
Language |
+Message |
+
English |
+network operator |
+
German |
+Mobilfunkbetreiber |
+
|
+|
Language |
+Message |
+
English |
+Account owner |
+
German |
+Kontoinhaber |
+
|
+|
Language |
+Message |
+
English |
+Username |
+
German |
+Benutzername |
+
|
+|
Language |
+Message |
+
English |
+PAN |
+
German |
+PAN |
+
|
+|
Language |
+Message |
+
English |
+IP-Address |
+
German |
+IP-Adresse |
+
|
+|
Language |
+Message |
+
English |
+window name |
+
German |
+Fenstername |
+
|
+|
Language |
+Message |
+
English |
+airline extension |
+
German |
+Flugdatenerweiterung |
+
|
+|
Language |
+Message |
+
English |
+cardholder |
+
German |
+Karteninhaber |
+
|
+|
Language |
+Message |
+
English |
+IBAN |
+
German |
+IBAN |
+
|
+|
Language |
+Message |
+
English |
+BIC |
+
German |
+BIC |
+
|
+|
Language |
+Message |
+
English |
+iDEAL Issuer |
+
German |
+iDEAL Issuer |
+
|
+|
Language |
+Message |
+
English |
+ENTRANCE_CODE |
+
German |
+ENTRANCE_CODE |
+
|
+|
Language |
+Message |
+
English |
+Issue number |
+
German |
+Kartenfolgenummer |
+
|
+|
Language |
+Message |
+
English |
+Issue date |
+
German |
+Kartenausgabedatum |
+
|
+|
Language |
+Message |
+
English |
+Source ORDERNUMBER |
+
German |
+Quell-Auftragsnummer |
+
|
+|
Language |
+Message |
+
English |
+SUPPOSEDORDERNUMBER |
+
German |
+Erwartete Auftragsnummer |
+
|
+|
Language |
+Message |
+
English |
+FALLBACK |
+
German |
+FALLBACK |
+
|
+|
Language |
+Message |
+
English |
+OVERWRITE_WUM |
+
German |
+OVERWRITE_WUM |
+
|
+|
Language |
+Message |
+
English |
+DEPOSITFLAG |
+
German |
+DEPOSITFLAG |
+
|
+|
Language |
+Message |
+
English |
+SUPPRESS |
+
German |
+SUPPRESS |
+
|
+|
Language |
+Message |
+
English |
+XHTML_WAKE_UP_MESSAGES |
+
German |
+XHTML_WAKE_UP_MESSAGES |
+
|
+|
Language |
+Message |
+
English |
+CONFIRMURL |
+
German |
+CONFIRMURL |
+
|
+|
Language |
+Message |
+
English |
+VOUCHER_ID |
+
German |
+Gutschein-Code (VOUCHER_ID) |
+
|
+|
Language |
+Message |
+
English |
+INITIATION |
+
German |
+INITIATION |
+
|
+|
Language |
+Message |
+
English |
+amount authorised |
+
German |
+Genehmigungsbetrag |
+
|
+|
Language |
+Message |
+
English |
+amount deposited |
+
German |
+Buchungsbetrag |
+
|
+|
Language |
+Message |
+
English |
+QUERYFOR |
+
German |
+QUERYFOR |
+
|
+|
Language |
+Message |
+
English |
+minimum amount |
+
German |
+Mindestbetrag |
+
|
+|
Language |
+Message |
+
English |
+maximum amount |
+
German |
+Maximalbetrag |
+
|
+|
Language |
+Message |
+
English |
+begin create time |
+
German |
+Anfangszeit der Erstellung der Transaktionen |
+
|
+|
Language |
+Message |
+
English |
+end create time |
+
German |
+Endzeit der Erstellung der Transaktionen |
+
|
+|
Language |
+Message |
+
English |
+begin modify time |
+
German |
+Anfangszeit der Änderung der Transaktionen |
+
|
+|
Language |
+Message |
+
English |
+end modifiy time |
+
German |
+Endzeit der Änderung der Transaktionen |
+
|
+|
Language |
+Message |
+
English |
+begin open time |
+
German |
+Anfangszeit der Öffnung der Tagesabschlüsse |
+
|
+|
Language |
+Message |
+
English |
+end open time |
+
German |
+Anfangszeit der Durchführung der Tagesabschlüsse |
+
|
+|
Language |
+Message |
+
English |
+begin close time |
+
German |
+Endzeit der Öffnung der Tagesabschlüsse |
+
|
+|
Language |
+Message |
+
English |
+end close time |
+
German |
+Endzeit der Durchführung der Tagesabschlüsse |
+
|
+|
Language |
+Message |
+
English |
+Brand |
+
German |
+Marke |
+
|
+|
Language |
+Message |
+
English |
+RETURNATMOST |
+
German |
+RETURNATMOST |
+
|
+|
Language |
+Message |
+
English |
+order reference |
+
German |
+Auftragsreferenz |
+
|
+|
Language |
+Message |
+
English |
+customer statement |
+
German |
+Abrechnungstext |
+
|
+|
Language |
+Message |
+
English |
+order text |
+
German |
+Auftragstext |
+
|
+|
Language |
+Message |
+
English |
+SKIPFIRST |
+
German |
+SKIPFIRST |
+
|
+|
Language |
+Message |
+
English |
+ORDERBY |
+
German |
+ORDERBY |
+
|
+|
Language |
+Message |
+
English |
+ORDERIDENT |
+
German |
+ORDERIDENT |
+
|
+|
Language |
+Message |
+
English |
+RETURNURL |
+
German |
+RETURNURL |
+
|
+|
Language |
+Message |
+
English |
+STORAGEID |
+
German |
+STORAGEID |
+
|
+|
Language |
+Message |
+
English |
+JAVASCRIPT SCRIPT VERSION |
+
German |
+JAVASCRIPT SCRIPT VERSION |
+
|
+|
Language |
+Message |
+
English |
+HTTP-header count |
+
German |
+Anzahl der HTTP-Header |
+
|
+|
Language |
+Message |
+
English |
+HTTP-header name |
+
German |
+Name eines HTTP-Headers |
+
|
+|
Language |
+Message |
+
English |
+HTTP-header value |
+
German |
+Wert eines HTTP-Headers |
+
|
+|
Language |
+Message |
+
English |
+Consumers mail address |
+
German |
+Mail-Adresse des Konsumenten |
+
|
+|
Language |
+Message |
+
English |
+Consumers birth date |
+
German |
+Geburtsdatum des Konsumenten |
+
|
+|
Language |
+Message |
+
English |
+Consumers tax identification number |
+
German |
+Steueridentifikationsnummer des Konsumenten |
+
|
+|
Language |
+Message |
+
English |
+Consumers drivers license number |
+
German |
+Führerscheinnummer des Konsumenten |
+
|
+|
Language |
+Message |
+
English |
+Consumers drivers license state |
+
German |
+Bundesstaat in dem der Führerschein des Konsumenten ausgestellt wurde |
+
|
+|
Language |
+Message |
+
English |
+Consumers drivers license country |
+
German |
+Land in dem der Führerschein des Konsumenten ausgestellt wurde |
+
|
+|
Language |
+Message |
+
English |
+Billing address first name |
+
German |
+Vorname der Rechnungsadresse |
+
|
+|
Language |
+Message |
+
English |
+Billing address last name |
+
German |
+Nachname der Rechnungsadresse |
+
|
+|
Language |
+Message |
+
English |
+Billing address first line |
+
German |
+Rechnungsadresse Teil 1 |
+
|
+|
Language |
+Message |
+
English |
+Billing address second line |
+
German |
+Rechnungsadresse Teil 2 |
+
|
+|
Language |
+Message |
+
English |
+Billing city |
+
German |
+Ort der Rechnungsadresse |
+
|
+|
Language |
+Message |
+
English |
+Billing zip code |
+
German |
+Postleitzahl der Rechungsadresse |
+
|
+|
Language |
+Message |
+
English |
+Billing state |
+
German |
+Bundesstaat der Rechnungsadresse |
+
|
+|
Language |
+Message |
+
English |
+Billing country |
+
German |
+Land der Rechnungsadresse |
+
|
+|
Language |
+Message |
+
English |
+Billing phone |
+
German |
+Telefonnummer der Rechnungsadresse |
+
|
+|
Language |
+Message |
+
English |
+Billing fax |
+
German |
+Faxnummer der Rechnungsadresse |
+
|
+|
Language |
+Message |
+
English |
+Shipping address first name |
+
German |
+Vorname der Lieferadresse |
+
|
+|
Language |
+Message |
+
English |
+Shipping address last name |
+
German |
+Shipping address last name |
+
|
+|
Language |
+Message |
+
English |
+Shipping address first line |
+
German |
+Lieferadresse Teil 1 |
+
|
+|
Language |
+Message |
+
English |
+Shipping address second line |
+
German |
+Lieferadresse Teil 2 |
+
|
+|
Language |
+Message |
+
English |
+Shipping city |
+
German |
+Ort der Lieferadresse |
+
|
+|
Language |
+Message |
+
English |
+Shipping zip code |
+
German |
+Postleitzahl der Lieferadresse |
+
|
+|
Language |
+Message |
+
English |
+Shipping state |
+
German |
+Bundesstaat der Lieferadresse |
+
|
+|
Language |
+Message |
+
English |
+Shipping country |
+
German |
+Land der Lieferadresse |
+
|
+|
Language |
+Message |
+
English |
+Shipping phone |
+
German |
+Telefonnummer der Lieferadresse |
+
|
+|
Language |
+Message |
+
English |
+Shipping fax |
+
German |
+Faxnummer der Lieferadresse |
+
|
+|
Language |
+Message |
+
English |
+Consumers language |
+
German |
+Sprache des Konsumenten |
+
|
+|
Language |
+Message |
+
English |
+Consumers device ID |
+
German |
+Device ID des Konsumenten |
+
|
+|
Language |
+Message |
+
English |
+Consumers IP address |
+
German |
+IP-Adresse des Konsumenten |
+
|
+|
Language |
+Message |
+
English |
+Shopping basket amount |
+
German |
+Betrag des Warenkorbs |
+
|
+|
Language |
+Message |
+
English |
+Shopping basket currency |
+
German |
+Währung des Warenkorbs |
+
|
+|
Language |
+Message |
+
English |
+Shopping basket item count |
+
German |
+Anzahl der Artikel im Warenkorb |
+
|
+|
Language |
+Message |
+
English |
+Shopping basket item article number |
+
German |
+Artikelnummer eines Artikels im Warenkorb |
+
|
+|
Language |
+Message |
+
English |
+Shopping basket item quantity |
+
German |
+Anzahl eines Artikels im Warenkorb |
+
|
+|
Language |
+Message |
+
English |
+Shopping basket item unit price |
+
German |
+Preis eines Artikels im Warenkorb |
+
|
+|
Language |
+Message |
+
English |
+Shopping basket item tax |
+
German |
+Steuerbetrag eines Artikels im Warenkorb |
+
|
+|
Language |
+Message |
+
English |
+Shopping basket item description |
+
German |
+Beschreibung eines Artikels im Warenkorb |
+
|
+|
Language |
+Message |
+
English |
+Shopping basket content |
+
German |
+Inhalt des Warenkorbs |
+
|
+|
Language |
+Message |
+
English |
+Shopping basket item image-URL |
+
German |
+URL zu Bild/Logo eines Artikels im Warenkorb |
+
|
+|
Language |
+Message |
+
English |
+Shopping basket item unit net amount |
+
German |
+Nettopreis eines Artikels im Warenkorb |
+
|
+|
Language |
+Message |
+
English |
+Shopping basket item unit tax amount |
+
German |
+Steuerbetrag eines Artikels im Warenkorb |
+
|
+|
Language |
+Message |
+
English |
+Shopping basket item unit tax rate |
+
German |
+Steuersatz eines Artikels im Warenkorb |
+
|
+|
Language |
+Message |
+
English |
+Shopping basket item unit gross amount |
+
German |
+Bruttopreis eines Artikels im Warenkorb |
+
|
+|
Language |
+Message |
+
English |
+Shopping basket item name |
+
German |
+Bezeichnung eines Artikels im Warenkorb |
+
|
+|
Language |
+Message |
+
English |
+Costumers company name |
+
German |
+Firmenname des Kunden |
+
|
+|
Language |
+Message |
+
English |
+Costumers company VAT identification number |
+
German |
+Umsatzsteuer-Identifikationsnummer des Kunden |
+
|
+|
Language |
+Message |
+
English |
+Customers company commercial register number |
+
German |
+Firmenbuch-/Handelsregisternummer des Kunden |
+
|
+|
Language |
+Message |
+
English |
+Customers other company registration key |
+
German |
+Sonstige Firmenregistrierungsnummer des Kunden |
+
|
+|
Language |
+Message |
+
English |
+CUSTOMERID |
+
German |
+CUSTOMERID (Kundennummer) |
+
|
+|
Language |
+Message |
+
English |
+SHOPID |
+
German |
+SHOPID |
+
|
+|
Language |
+Message |
+
English |
+FINANCIALINSTITUTION |
+
German |
+FINANCIALINSTITUTION |
+
|
+|
Language |
+Message |
+
English |
+DISPLAYTEXT |
+
German |
+DISPLAYTEXT |
+
|
+|
Language |
+Message |
+
English |
+CONFIRMURL |
+
German |
+CONFIRMURL |
+
|
+|
Language |
+Message |
+
English |
+IMAGEURL |
+
German |
+IMAGEURL |
+
|
+|
Language |
+Message |
+
English |
+REQUESTFINGERPRINT |
+
German |
+REQUESTFINGERPRINT |
+
|
+|
Language |
+Message |
+
English |
+DUPLICATEREQUESTCHECK |
+
German |
+DUPLICATEREQUESTCHECK |
+
|
+|
Language |
+Message |
+
English |
+REQUESTFINGERPRINTORDER |
+
German |
+REQUESTFINGERPRINTORDER |
+
|
+|
Language |
+Message |
+
English |
+SECRET |
+
German |
+SECRET |
+
|
+|
Language |
+Message |
+
English |
+MAXRETRIES |
+
German |
+MAXRETRIES |
+
|
+|
Language |
+Message |
+
English |
+BACKGROUNDCOLOR |
+
German |
+BACKGROUNDCOLOR |
+
|
+|
Language |
+Message |
+
English |
+NOSCRIPTINFOURL |
+
German |
+NOSCRIPTINFOURL |
+
|
+|
Language |
+Message |
+
English |
+CONFIRMMAIL |
+
German |
+CONFIRMMAIL |
+
|
+|
Language |
+Message |
+
English |
+AUTODEPOSIT |
+
German |
+AUTODEPOSIT |
+
|
+|
Language |
+Message |
+
English |
+PENDINGURL |
+
German |
+PENDINGURL |
+
|
+|
Language |
+Message |
+
English |
+PAYMENTTYPESORTORDER |
+
German |
+PAYMENTTYPESORTORDER |
+
|
+|
Language |
+Message |
+
English |
+LAYOUT |
+
German |
+LAYOUT |
+
|
+|
Language |
+Message |
+
English |
+SHIPPING_PROFILE |
+
German |
+SHIPPING_PROFILE |
+
| Parameter | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
| + |
+
+
+
+Required
+ |
+Alphanumeric with special characters |
+URL of the online shop where QENTA sends a server-to-server confirmation |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric with special characters, up to 254 characters |
+Text displayed on bank statement issued to the consumer by the financial service provider. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric with special characters, up to 128 characters |
+Unique order reference ID sent from merchant to financial institution. Correlate the order numbers of the online shop with the affected payments. |
+
| + |
+
+
+
+Optional
+ |
+Alphanumeric with special characters |
+URL of the online shop when the result of the payment process could not be determined yet. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+URL of the online shop where QENTA sends a server-to-server confirmation |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric with special characters, up to 254 characters |
+
Description |
+Text displayed on bank statement issued to the consumer by the financial service provider. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric with special characters, up to 128 characters |
+
Description |
+Unique order reference ID sent from merchant to financial institution. Correlate the order numbers of the online shop with the affected payments. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+URL of the online shop when the result of the payment process could not be determined yet. |
+
| + + | ++The consumer billing data, consumer shipping data, and shopping basket data should be implemented from the beginning since these are required for certain payment methods. + | +
| Parameter | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
| + |
+
+
+
+Optional
+ |
+Alphanumeric with special characters |
+URL of the online shop where the information page regarding deactivated JavaScript resides |
+
| + |
+
+
+
+Required
+ |
+Numeric, up to 9 |
+Order number of payment |
+
| + |
+
+
+
+Optional
+ |
+Alphanumeric |
+Window name of browser window where payment page is opened. |
+
| + |
+
+
+
+Required
+ |
+Boolean |
+Check for duplicate requests done by the consumer. |
+
| + |
+
+
+
+Required
+ |
+Enumeration |
+Possible values are |
+
| + |
+
+
+
+Optional
+ |
+URL |
+URL to a CSS file on the server to perform customizations |
+
|
+
+
+
+
+Required
+ |
+Enumeration |
+It identifies the type of ISO transaction and the values are derived from ISO 8583. This field is required in some markets (e.g. for Merchants in Brazil), otherwise optional. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+URL of the online shop where the information page regarding deactivated JavaScript resides |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Numeric, up to 9 |
+
Description |
+Order number of payment |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+Alphanumeric |
+
Description |
+Window name of browser window where payment page is opened. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Boolean |
+
Description |
+Check for duplicate requests done by the consumer. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Enumeration |
+
Description |
+Possible values are |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+URL |
+
Description |
+URL to a CSS file on the server to perform customizations |
+
|
+|
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Enumeration |
+
Description |
+It identifies the type of ISO transaction and the values are derived from ISO 8583. This field is required in some markets (e.g. for Merchants in Brazil), otherwise optional. Accepted values: |
+
| Parameter | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
| + |
+
+
+
+Optional
+ |
+Alphanumeric with special characters |
+Text displayed to the consumer during the payment process. |
+
| + |
+
+
+
+Optional
+ |
+Alphanumeric with special characters |
+URL of the online shop where the online shop logo is located. |
+
| + |
+
+
+
+Optional
+ |
+Alphanumeric |
+Hex code RGB color value as background color for the brand image containing the credit card logos. |
+
| + |
+
+
+
+Optional
+ |
+Enumeration |
+Sub-selection of financial institutions regarding the pre-selected payment method. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+Text displayed to the consumer during the payment process. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+URL of the online shop where the online shop logo is located. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+Alphanumeric |
+
Description |
+Hex code RGB color value as background color for the brand image containing the credit card logos. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+Enumeration |
+
Description |
+Sub-selection of financial institutions regarding the pre-selected payment method. |
+
| Parameter | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
| + |
+
+
+
+Required
+ |
+Alphanumeric with special characters |
+Unique ID of order which has to be the same as used for initiating the Data Storage. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric with a fixed length of 32 |
+Unique ID of Data Storage for a specific consumer. |
+
| + + | +
+Parameters orderIdent and storageID become mandatory if data storage is used.
+ |
+
These parameters are used to pass on detailed information to the consumer and some specific payment methods are required.
+| Parameter | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
| + |
+
+
+
+Required
+ |
+Alphanumeric with special characters, up to 256 characters |
+E-mail address of the consumer. |
+
| + |
+
+
+
+Required
+ |
+Numeric with special characters, fixed-length 10 |
+Birth date of the consumer in the format |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric with special characters, up to 32 characters |
+Tax identification number of consumer. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric with special characters, up to 32 characters |
+Drivers license number of consumer. |
+
| + |
+
+
+
+Required
+ |
+Alphabetic with a fixed length of 2 for the US and CA; otherwise, up to 40 |
+State which issued the driver’s license of the consumer. |
+
| + |
+
+
+
+Required
+ |
+Alphabetic, fixed length of 2 characters |
+Country which issued the drivers license of consumer. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 50 characters |
+Unique ID identifying the consumer of the online shop. The parameter must not be a human-readable e-mail address. |
+
| + |
+
+
+
+Required
+ |
+Enumeration |
+Type of consumer login in the shop. Accepted values: |
+
| + |
+
+
+
+Required
+ |
+Timestamp |
+Date and time of the consumer login to the shop. Accepted format: |
+
| + |
+
+
+
+Required
+ |
+Numeric with special characters, fixed length of 10 |
+Date that the consumer’s card was added to their account in the shop for card-on-file payments. Accepted format: |
+
| + |
+
+
+
+Required
+ |
+Numeric, up to 9 characters |
+Number of cards the consumer has attempted to add to their account in the shop for card-on-file payments in the past 24 hours. |
+
| + |
+
+
+
+Required
+ |
+Enumeration |
+Specifies whether transaction shall be subject to Strong Customer Authentication (SCA). |
+
| + |
+
+
+
+Required
+ |
+Boolean |
+Indicates if merchants have experienced suspicious activities by the consumer. |
+
| + |
+
+
+
+Required
+ |
+Enumeration |
+Delivery time frame. Accepted values: |
+
| + |
+
+
+
+Required
+ |
+Numeric with special characters, fixed length of 10 |
+The expected date that the item will be available for a pre-ordered purchase. Accepted format: |
+
| + |
+
+
+
+Required
+ |
+Enumeration |
+Indicates if the consumer is reordering previously purchased items. Accepted values: |
+
| + |
+
+
+
+Required
+ |
+Numeric with special characters, fixed length of 10 |
+Registration date of the consumer’s account in the shop. Accepted format: |
+
| + |
+
+
+
+Required
+ |
+Numeric with special characters, fixed length of 10 |
+Date that the consumer last made changes to their account in the shop. |
+
| + |
+
+
+
+Required
+ |
+Numeric with special characters, fixed length of 10 |
+Date that the consumer last changed/reset their password in the shop. Accepted format: |
+
| + |
+
+
+
+Required
+ |
+Numeric, up to 9 characters |
+Number of successful orders by the consumer in the shop within the past six months. |
+
| + |
+
+
+
+Required
+ |
+Numeric, up to 9 characters |
+Number of transactions that the consumer has attempted in the past 24 hours. Does not include merchant-initiated transactions. |
+
| + |
+
+
+
+Required
+ |
+Numeric, up to 9 characters |
+Number of transactions that the consumer has attempted in the past year. Does not include merchant-initiated transactions. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric with special characters, up to 256 characters |
+
Description |
+E-mail address of the consumer. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Numeric with special characters, fixed-length 10 |
+
Description |
+Birth date of the consumer in the format |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric with special characters, up to 32 characters |
+
Description |
+Tax identification number of consumer. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric with special characters, up to 32 characters |
+
Description |
+Drivers license number of consumer. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphabetic with a fixed length of 2 for the US and CA; otherwise, up to 40 |
+
Description |
+State which issued the driver’s license of the consumer. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphabetic, fixed length of 2 characters |
+
Description |
+Country which issued the drivers license of consumer. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 50 characters |
+
Description |
+Unique ID identifying the consumer of the online shop. The parameter must not be a human-readable e-mail address. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Enumeration |
+
Description |
+Specifies whether transaction shall be subject to Strong Customer Authentication (SCA). |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Boolean |
+
Description |
+Indicates if merchants have experienced suspicious activities by the consumer. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Enumeration |
+
Description |
+Delivery time frame. Accepted values: |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Numeric with special characters, fixed length of 10 |
+
Description |
+The expected date that the item will be available for a pre-ordered purchase. Accepted format: |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Enumeration |
+
Description |
+Indicates if the consumer is reordering previously purchased items. Accepted values: |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Numeric with special characters, fixed length of 10 |
+
Description |
+Registration date of the consumer’s account in the shop. Accepted format: |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Numeric with special characters, fixed length of 10 |
+
Description |
+Date that the consumer last made changes to their account in the shop. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Numeric with special characters, fixed length of 10 |
+
Description |
+Date that the consumer last changed/reset their password in the shop. Accepted format: |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Numeric, up to 9 characters |
+
Description |
+Number of successful orders by the consumer in the shop within the past six months. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Numeric, up to 9 characters |
+
Description |
+Number of transactions that the consumer has attempted in the past 24 hours. Does not include merchant-initiated transactions. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Numeric, up to 9 characters |
+
Description |
+Number of transactions that the consumer has attempted in the past year. Does not include merchant-initiated transactions. |
+
| Parameter | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
| + |
+
+
+
+Required
+ |
+First character has to be alphabetic, any other characters ASCII, up to 30 bytes |
+First name of consumer. |
+
| + |
+
+
+
+Required
+ |
+First character has to be alphabetic, any other characters ASCII, up to 30 bytes |
+Last name of consumer. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 100 bytes |
+Name of the street and optionally the house number. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 100 bytes |
+The house number if not already set in |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 100 bytes |
+Further details regarding consumer’s address. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 32 bytes |
+Billing city |
+
| + |
+
+
+
+Required
+ |
+If the |
+Billing state |
+
| + |
+
+
+
+Required
+ |
+Alphabetic, fixed 2 characters |
+Billing country code ISO 3166-1. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 12 characters |
+Billing zip code. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 20 characters |
+Phone number of consumer. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 18 characters |
+Mobile phone number of consumer. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 20 characters |
+Fax number of consumer. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+First character has to be alphabetic, any other characters ASCII, up to 30 bytes |
+
Description |
+First name of consumer. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+First character has to be alphabetic, any other characters ASCII, up to 30 bytes |
+
Description |
+Last name of consumer. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 100 bytes |
+
Description |
+Name of the street and optionally the house number. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 100 bytes |
+
Description |
+The house number if not already set in |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 100 bytes |
+
Description |
+Further details regarding consumer’s address. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 32 bytes |
+
Description |
+Billing city |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+If the |
+
Description |
+Billing state |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphabetic, fixed 2 characters |
+
Description |
+Billing country code ISO 3166-1. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 12 characters |
+
Description |
+Billing zip code. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 20 characters |
+
Description |
+Phone number of consumer |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 18 characters |
+
Description |
+Mobile phone number of consumer. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 18 characters |
+
Description |
+Fax number of consumer. |
+
| Parameter | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
| + |
+
+
+
+Required
+ |
+First character has to be alphabetic, any other characters ASCII, up to 30 bytes |
+First name of the consumer. |
+
| + |
+
+
+
+Required
+ |
+First character has to be alphabetic, any other characters ASCII, up to 30 bytes |
+Last name of the consumer. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 100 bytes |
+Name of the street and optionally the house number. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 100 bytes |
+The house number if not already set in |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 32 bytes |
+Shipping city. |
+
| + |
+
+
+
+Required
+ |
+If the |
+Shipping state. |
+
| + |
+
+
+
+Required
+ |
+Alphabetic, fixed 2 characters |
+Shipping country code ISO 3166-1. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 12 |
+Shipping ZIP code. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 20 |
+Shipping phone number. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 20 |
+Shipping fax number. |
+
| + |
+
+
+
+Required
+ |
+Enumeration |
+Indicates whether consumer is placing an order for an item that is not yet available or which is currently available. |
+
| + |
+
+
+
+Required
+ |
+Enumeration |
+Shipping method chosen by the consumer. Accepted values: |
+
| + |
+
+
+
+Required
+ |
+Numeric with special characters, fixed 10 |
+Date that the consumer first used this shipping address in the shop. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+First character has to be alphabetic, any other characters ASCII, up to 30 bytes |
+
Description |
+First name of the consumer. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+First character has to be alphabetic, any other characters ASCII, up to 30 bytes |
+
Description |
+Last name of the consumer. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 100 bytes |
+
Description |
+Name of the street and optionally the house number. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 100 bytes |
+
Description |
+The house number if not already set in |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 32 bytes |
+
Description |
+Shipping city. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+If the |
+
Description |
+Shipping state. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphabetic, fixed 2 characters |
+
Description |
+Shipping country code ISO 3166-1. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 12 |
+
Description |
+Shipping ZIP code. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 20 |
+
Description |
+Shipping phone number. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 20 |
+
Description |
+Shipping fax number. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Enumeration |
+
Description |
+Indicates whether consumer is placing an order for an item that is not yet available or which is currently available. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Enumeration |
+
Description |
+Shipping method chosen by the consumer. Accepted values: |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Numeric with special characters, fixed 10 |
+
Description |
+Date that the consumer first used this shipping address in the shop. |
+
Parameters that allow passing on detailed information about the content of a consumer’s shopping basket. By default are optional, but some specific payment methods like invoice or installment are required.
+| + + | +
+Although the following parameters are optional, all parameters need to be set, except for basketItem(n)Description and basketItem(n)ImageUrl which remain optional.
+ |
+
| + + | +
+Set possible shipping costs as a separate basketItem; otherwise, the validation of the sum of the individual items and the total sum will fail. If different shipping costs apply to the different articles in the basket, the individual shipping costs must be stated as separate basketItem.
+ |
+
The following simple example is intended to contribute to a better understanding of how to set the basket parameters.
+The parameters for describing the items in the shopping basket of the consumer would be:
+These optional parameters enhance the functionality and usability of the payment process regarding specific features and functions. To enable these parameters, contact our integration specialists.
+| Parameter | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
|
+
+
+
+
+Required
+ |
+
|
+Enable automated debiting of payments. |
+
|
+
+
+
+
+Required
+ |
+Alphanumeric with special characters, up to 127. |
+One payment confirmation mail address for the merchant. |
+
|
+
+
+
+
+Required
+ |
+Alphanumeric, up to 16. |
+Unique ID of the online shop within the customer ID to enable various configurations of the online shop. |
+
|
+|
Data |
+Value |
+
Within fingerprint |
+Required if used. |
+
Data type |
+
|
+
Description |
+Enable automated debiting of payments. |
+
|
+|
Data |
+Value |
+
Within fingerprint |
+Required if used. |
+
Data type |
+Alphanumeric with special characters, up to 127. |
+
Description |
+One payment confirmation mail address for the merchant. |
+
|
+|
Data |
+Value |
+
Within fingerprint |
+Required if used. |
+
Data type |
+Alphanumeric, up to 16. |
+
Description |
+Unique ID of the online shop within the customer ID to enable various configurations of the online shop. |
+
This feature allows the consumer to enter his shipping or billing information after opening the payment link. Contact our integration specialists to enable the feature.
+| Parameter | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
|
+
+
+
+
+Optional
+ |
+Enumeration |
+
|
+
|
+
|
+|
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+Enumeration |
+
Description |
+
|
+
| + + | ++Provide basket items to init or via QPBL PayByLink. Items or amounts can’t be changed by the consumer afterward. + | +
| Parameter | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
|
+
+
+
+
+Optional
+ |
+Enumeration |
+
|
+
|
+|||
|
+
|
+|
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+Enumeration |
+
Description |
+
|
+
| + + | +
+If set to Y the merchant must provide the Shipping Data to display during init or via QPBL PayByLink.
+ |
+
| Parameter | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
|
+
+
+
+
+Optional
+ |
+Enumeration |
+
|
+
|
+|||
|
+
|
+|
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+Enumeration |
+
Description |
+
|
+
| + + | ++If no billing data is sent to init but shipping Data is, then a consumer can choose to use shipping data as billing data. + | +
If any of displayBasket, displayBillingData, displayShippingData is set to Y or E an additional return parameter will be received during confirmation that contains the consumer’s information.
| Parameter | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
|
+
+
+
+
+Required
+ |
+Numeric |
+Maximum number of payment attempts for the same order. |
+
|
+
+
+
+
+Optional
+ |
+Enumeration/list |
+Sort order of payment methods and sub-methods if the consumer uses |
+
|
+|
Data |
+Value |
+
Within fingerprint |
+Required if used. |
+
Data type |
+Numeric |
+
Description |
+Maximum number of payment attempts for the same order. |
+
|
+|
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+Enumeration/list |
+
Description |
+Sort order of payment methods and sub-methods if the consumer uses |
+
| Acquirer | +Brand | +Data type | +
|---|---|---|
American Express |
+American Express |
+ASCII, up to 254 characters |
+
B+S |
+Mastercard, Visa |
+ASCII, up to 254 characters |
+
card complete |
+Maestro SecureCode, Mastercard, Visa |
+Alphanumeric, up to 25 characters. |
+
ConCardis |
+Maestro SecureCode, Mastercard, Visa |
+ASCII, up to 254 characters. |
+
b4payment |
+b4payment |
+ASCII, up to 254 characters. |
+
DC Bank |
+Diners Club |
+ASCII, up to 254 characters |
+
EPS |
+EPS |
+ASCII, up to 254 characters. |
+
Giropay |
+Giropay |
+ASCII, up to 254 characters. |
+
Hobex |
+Maestro SecureCode, Mastercard, Visa |
+
|
+
Hobex |
+SEPA Direct Debit |
+ASCII, up to 254 characters. |
+
Klarna |
+Sofort |
+ASCII, up to 254 characters. |
+
PayPal |
+PayPal |
+ASCII, up to 254 characters. |
+
Przelewy24 |
+Przelewy24 |
+ASCII, up to 25 characters. |
+
paysafecard |
+paysafecard |
+ASCII, up to 254 characters. |
+
payolution |
+payolution |
+ASCII, up to 254 characters. |
+
Riverty |
+Riverty |
+ASCII, up to 254 characters |
+
SIX Pay |
+Maestro SecureCode, Mastercard, Visa |
+ASCII, up to 254 characters |
+
SIX Payment Services |
+Maestro SecureCode, Mastercard, Visa |
+ASCII, up to 254 characters |
+
Sofort |
+Sofort |
+ASCII, up to 254 characters |
+
Worldline |
+Maestro SecureCode, Mastercard, Visa |
+Alphanumeric with special characters, up to 22 characters |
+
| Acquirer | +Brand | +Data type | +
|---|---|---|
American Express |
+American Express |
+Not supported |
+
B+S |
+Mastercard, Visa |
+Not supported |
+
ConCardis |
+Mastercard, Visa |
+Not supported |
+
card complete |
+Maestro SecureCode, Mastercard, Visa |
+Alphanumeric, up to 25 characters. |
+
b4payment |
+b4payment |
+ASCII, up to 128 characters. |
+
DC Bank |
+Diners Club |
+ASCII, up to 128 characters |
+
Eps |
+Eps |
+ASCII, up to 35 characters. |
+
Giropay |
+Giropay |
+Variable, up to 32 characters. Allowed characters are [0-9a-zA-Z]. |
+
Hobex |
+SEPA Direct Debit |
+ASCII, up to 128 characters. |
+
Hobex |
+Maestro SecureCode, Mastercard, Visa |
+Alphanumeric, up to 20 characters |
+
Przelewy24 |
+Przelewy24 |
+ASCII, up to 64 characters. |
+
paysafecard |
+paysafecard |
+ASCII, up to 128 characters. |
+
payolution |
+payolution |
+ASCII, up to 128 characters. |
+
PayPal |
+PayPal |
+ASCII, up to 128 characters. |
+
Riverty |
+Riverty |
+ASCII, up to 254 characters |
+
SIX Payment Services |
+Maestro SecureCode, Mastercard, Visa |
+Not supported |
+
SIX Pay |
+Maestro SecureCode, Mastercard, Visa |
+Not supported |
+
Sofort |
+Sofort |
+ASCII, up to 254 characters |
+
| + | Maestro SecureCode, Mastercard, Visa |
+Numeric and special characters between 10 and 64 characters. |
+
| Parameter | +Within fingerprint | +Data type | +Short description | +
|---|---|---|---|
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 35. |
+Identifier of displayed mandate. |
+
| + |
+
+
+
+Required
+ |
+Date as |
+Date when mandate was signed. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric, up to 35. |
+
Short description |
+Identifier of displayed mandate. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Date as |
+
Short description |
+Date when mandate was signed. |
+
| + + | +
+If mandateId is not set QENTA will generate it and if mandateSignatureDate is not set QENTA will use the current date as a signature date.
+ |
+
| + + | ++Always use the same upper and lower case writing of the parameter names and values as described. + | +
QENTA Checkout Server has restrictions regarding the parameter names and values:
+Max. number of parameters that can be used is 1024.
+Max. length of a parameter name must not exceed 64 characters.
+Max. length of the value of a parameter must not exceed 2048 characters.
+Max. number of parameters that can be used is 12000.
+Max. length of a parameter name must not exceed 64 characters.
+Max. length of the value of a parameter must not exceed 65000 characters.
+Custom parameters can be added when starting the payment process. Any names can be used for custom parameters except for those that already exist as our request parameters.
+| + + | +
+To prevent naming conflicts with possible future extensions of QENTA solutions use a prefix for custom parameter names e.g. yourWebshopName_customValueXYZ.
+ |
+
For QPAY Checkout Page all of the custom parameters are returned without any modification to the online shop via successUrl,cancelUrl, pendingUrl, failureUrl or confirmUrl.
+For QMORE Checkout Seamless all of the custom parameters are returned without modifications to the online shop via the confirmUrl.
+| + + | ++No parameters are returned to the successUrl when using QMORE Checkout Seamless. + | +
The fingerprint is computed by concatenating all request parameter values plus the secret in the order defined in the parameter requestFingerprintOrder without any dividers in between and using the secret as a cryptographic key for the hashing function.
| + + | ++Be aware that the concatenation of the request parameters and the secret has to be done in the order as defined within the detailed description of each backend operation. + | +
After concatenating all values to a single string create an HMAC-SHA-512 hash with a secret as a cryptographic key. The result is the fingerprint that must be added as a request parameter to the server-to-server call.
+The QENTA Checkout Server is thus able to check whether the received parameters are manipulated by a 3rd party.
+| + + | ++To initiate the payment process set all required parameters to particular values. If one of them is missing error message will be shown. + | +
| Parameter | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
+
+ |
+
+
+
+
+Required
+ |
+Alphanumeric, fixed 7 characters |
+Unique ID assigned to each merchant by QENTA. |
+
| + |
+
+
+
+Required
+ |
+Alphabetic, fixed 2 characters |
+Language for displayed texts on the payment page. |
+
| + |
+
+
+
+Optional
+ |
+Enumeration |
+Selected payment method of the consumer. |
+
| + |
+
+
+
+Required
+ |
+Amount |
+Amount of payment. |
+
| + |
+
+
+
+Required
+ |
+Alphabetic or numeric, fixed 3 characters |
+Currency code of amount. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric, up to 255 |
+Unique description of the consumer’s order in a human readable form. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric with special characters |
+URL of the online shop when payment process was successful. |
+
| + |
+
+
+
+Optional
+ |
+Alphanumeric with special characters |
+URL of the online shop when payment process has been canceled. |
+
| + |
+
+
+
+Optional
+ |
+Alphanumeric with special characters |
+URL of the online shop when an error occurred within payment process. |
+
| + |
+
+
+
+Optional
+ |
+Alphanumeric with special characters, up to 255 |
+URL of web page containing the contact information. |
+
| + |
+
+
+
+Required
+ |
+Alphanumeric with special characters |
+Ordered list of parameters used for calculating the fingerprint. |
+
| + |
+
+
+
+Never
+ |
+Alphanumeric with a fixed length of 128 for hash mechanism |
+Computed fingerprint of the parameter values as given in the |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required |
+
Data type |
+Alphanumeric, fixed 7 characters |
+
Description |
+Unique ID assigned to each merchant by QENTA. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required |
+
Data type |
+Alphabetic, fixed 2 characters |
+
Description |
+Language for displayed texts on the payment page. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+Enumeration |
+
Description |
+Selected payment method of the consumer. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required |
+
Data type |
+Amount |
+
Description |
+Amount of payment. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required |
+
Data type |
+Alphabetic or numeric, fixed 3 characters |
+
Description |
+Currency code of amount. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required |
+
Data type |
+Alphanumeric, up to 255 |
+
Description |
+Unique description of the consumer’s order in a human readable form. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+URL of the online shop when payment process was successful. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+URL of the online shop when payment process has been canceled. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+URL of the online shop when an error occurred within payment process. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+Alphanumeric with special characters, up to 255 |
+
Description |
+URL of web page containing the contact information. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Required |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+Ordered list of parameters used for calculating the fingerprint. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Never |
+
Data type |
+Alphanumeric with a fixed length of 128 for hash mechanism HMAC-SHA-512 |
+
Description |
+Computed fingerprint of the parameter values as given in the |
+
confirmUrl |
+|
|---|---|
Data |
+Value |
+
Within fingerprint |
+Required |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+URL of the online shop where QENTA sends a server-to-server confirmation. |
+
|
+|
Data |
+Value |
+
Within fingerprint |
+Required |
+
Data type |
+Numeric with special characters |
+
Description |
+IP address of the consumer. |
+
|
+|
Data |
+Value |
+
Within fingerprint |
+Required |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+User-agent of the browser of the consumer. |
+
| + | |
Data |
+Value |
+
Within fingerprint |
+Optional |
+
Data type |
+Enumeration |
+
Description |
+Based on pre-selected payment method a sub-selection of financial institutions regarding the pre-selected payment method. |
+
The number of response parameters is not fixed but depends on the payment method.
+Use exact names and values of parameters.
+Check all responses of the QENTA Checkout Server by using the fingerprint method.
| Parameter | +Data type | +Description | +Value | +
|---|---|---|---|
|
+Enumeration |
+Result of payment process |
+
|
+
|
+|||
|
+|||
|
+
financialInstitution |
+|
|---|---|
Data |
+Value |
+
Data type |
+Enumeration |
+
Description |
+Sub-selection of financial institutions regarding to pre-selected payment method. |
+
| + | |
Data |
+Value |
+
Data type |
+Alphabetic, fixed 2 characters |
+
Description |
+Language used for displayed texts on payment page. |
+
| + | |
Data |
+Value |
+
Data type |
+Numeric value, up to 9 digits |
+
Description |
+Unique number identifying the payment. |
+
| + | |
Data |
+Value |
+
Data type |
+Enumeration |
+
Description |
+Selected payment method of consumer. |
+
| + | |
Data |
+Value |
+
Data type |
+Alphanumeric with a fixed length of 128. |
+
Description |
+Returned fingerprint of the parameter values as given in the |
+
| + | |
Data |
+Value |
+
Data type |
+Alphanumeric with special characters. |
+
Description |
+Ordered list of parameters used for calculating the fingerprint. |
+
amount |
+|
|---|---|
Data |
+Value |
+
Data type |
+Amount |
+
Description |
+AmountOfPayment. |
+
| + | |
Data |
+Value |
+
Data type |
+Alphabetic, fixed 3 characters |
+
Description |
+Currency code of amount. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters, up to 255 characters |
+
Description |
+Contract number of the processor or acquirer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters, up to 255 characters |
+
Description |
+Technical reference number of the processor. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters, up to 255 characters |
+
Description |
+Technical reference number of the financial service provider or acquirer. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Alphanumeric with special characters |
+Error text describing the failure. |
+
|
+Alphanumeric with special characters |
+Specific error provided by the acquirer/issuer. If this parameter is not sent for |
+
|
+Alphanumeric with special characters. |
+Error message specific to payment method and financial institution which is only relevant for the merchant. |
+
|
+Alphanumeric with special characters |
+Error message in localized language for consumer. |
+
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Numeric |
+Number of errors occurred. |
+
|
+Numeric, fixed 5 characters |
+Numeric error code which should be logged for later use. |
+
|
+Alphanumeric with special characters |
+Error message in English. |
+
|
+Alphanumeric with special characters |
+Error message in localized language for consumer. |
+
|
+Alphanumeric with special characters |
+Payment method system-specific error message only relevant for a merchant. |
+
|
+Alphanumeric with special characters |
+Specific error provided by the acquirer/issuer. If this parameter is not sent for |
+
errors |
+|
|---|---|
Data |
+Value |
+
Data type |
+Numeric |
+
Description |
+Number of errors occurred. |
+
|
+|
Data |
+Value |
+
Data type |
+Numeric, fixed 5 characters |
+
Description |
+Numeric error code which should be logged for later use. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+Error message in English. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+Error message in localized language for consumer. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+Payment method system-specific error message only relevant for a merchant. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric with special characters |
+
Description |
+Specific error provided by the acquirer/issuer. If this parameter is not sent for |
+
| Parameter | +State | +Data type | +Description | +
|---|---|---|---|
|
+
+
+
+
+Success
+ |
+Alphabetic, fixed 1 character and possible value of |
+Only available and returns |
+
|
+
+
+
+
+Success
+ |
+Alphabetic, fixed 2 characters. |
+Country of the consumer which has been detected and returned by the financial service provider. |
+
liabilityShiftIndicator |
+|
|---|---|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphabetic, fixed 1 character and possible value of |
+
Description |
+Only available and returns |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphabetic, fixed 2 characters. |
+
Description |
+Country of the consumer which has been detected and returned by the financial service provider. |
+
| Parameter | +State | +Data type | +Description | +
|---|---|---|---|
|
+
+
+
+
+Success
+ |
+Alphanumeric with a fixed length of 128 (hash mechanism HMAC-SHA-512). |
+Hashed credit card number. |
+
The parameter can be used to check if a certain credit card has been used by consumer before, i.e. for recognizing a new registration with a different name but with the same credit card. Safely store this hash without circumventing PCI compliance.
+| + + | +
+Be aware that due to PCI DSS compliance hashedPan can’t be returned either with maskedPan nor anonymousPan.
+ |
+
| Parameter | +State | +Data type | +Description | +
|---|---|---|---|
|
+
+
+
+
+Success
+ |
+Alphabetic with a variable length of up to 80. |
+Name of holder of credit card which can only be used if the acquirer supports it. |
+
|
+
+
+
+
+Success
+ |
+Numeric with special characters and a fixed length of 7. |
+Expiry date of credit card in format |
+
|
+
+
+
+
+Success
+ |
+Numeric with special characters and a variable length of up to 19. |
+PCI-compliant masked card number in the format: first 6 digits and last 4 digits of card number with "*" in-between depending on the current format of the card number. |
+
| Parameter | +State | +Data type | +Description | +
|---|---|---|---|
|
+
+
+
+
+Success
+ |
+Numeric with 4 numbers. |
+Last four digits of the credit card number. |
+
|
+
+
+
+
+Success
+ |
+Boolean |
+Returns |
+
| + + | +
+The parameter authenticated is always returned if the payment was successful. If the consumer was authenticated by an additional security method, such as 3-D Secure, Mastercard ID Check, Visa Secure, YES will be returned.
+ |
+
| Parameter | +State | +Data type | +Description | +
|---|---|---|---|
|
+
+
+
+
+Success
+ |
+Alphanumeric with special characters, up to 255. |
+Transaction ID of authorization. |
+
|
+
+
+
+
+Success
+ |
+Alphanumeric, up to 19. |
+Billing agreement ID returned by PayPal. |
+
|
+
+
+
+
+Success
+ |
+Alphanumeric, up to 40 characters. |
+City of shipping address. |
+
|
+
+
+
+
+Success
+ |
+Alphabetic, up to 50. |
+Country of shipping address. |
+
|
+
+
+
+
+Success
+ |
+Alphabetic, fixed length of 2. |
+Country code (ISO 3166-1) of shipping address. |
+
|
+
+
+
+
+Success
+ |
+Alphanumeric with a variable length of up to 32. |
+Name of shipping address. |
+
|
+
+
+
+
+Success
+ |
+Alphanumeric with a variable length of up to 32. |
+State of shipping address. |
+
|
+
+
+
+
+Success
+ |
+Alphanumeric with a variable length of up to 40. |
+Street line 1 of shipping address. |
+
|
+
+
+
+
+Success
+ |
+Alphanumeric with a variable length of up to 100. |
+Street line 2 of shipping address. |
+
|
+
+
+
+
+Success
+ |
+Alphanumeric with a variable length of up to 20. |
+ZIP code of shipping address. |
+
|
+
+
+
+
+Success
+ |
+Alphanumeric with special characters and a variable length of up to 127. |
+E-mail address of consumer as returned by PayPal. |
+
|
+
+
+
+
+Success
+ |
+Alphanumeric with a variable length of up to 64. |
+First name of the consumer as returned by PayPal. |
+
|
+
+
+
+
+Success
+ |
+Alphanumeric with a variable length of up to 13. |
+ID of the consumer as returned by PayPal. |
+
|
+
+
+
+
+Success
+ |
+Alphanumeric with a variable length of up to 64. |
+Last name of the consumer as returned by PayPal. |
+
gatewayReferenceNumber |
+|
|---|---|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric with special characters, up to 255. |
+
Description |
+Transaction ID of authorization. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric, up to 19. |
+
Description |
+Billing agreement ID returned by PayPal. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric, up to 40 characters. |
+
Description |
+City of shipping address. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphabetic, up to 50. |
+
Description |
+Country of shipping address. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphabetic, fixed length of 2. |
+
Description |
+Country code (ISO 3166-1) of shipping address. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric with a variable length of up to 32. |
+
Description |
+Name of shipping address. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric with a variable length of up to 32. |
+
Description |
+State of shipping address. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric with a variable length of up to 40. |
+
Description |
+Street line 1 of shipping address. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric with a variable length of up to 100. |
+
Description |
+Street line 2 of shipping address. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric with a variable length of up to 20. |
+
Description |
+ZIP code of shipping address. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric with special characters and a variable length of up to 127. |
+
Description |
+E-mail address of consumer as returned by PayPal. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric with a variable length of up to 64. |
+
Description |
+First name of the consumer as returned by PayPal. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric with a variable length of up to 13. |
+
Description |
+ID of the consumer as returned by PayPal. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric with a variable length of up to 64. |
+
Description |
+Last name of the consumer as returned by PayPal. |
+
When a consumer enters billing or shipping information after initialization e.g. when using QPBL PayByLink these data are contained in the confirmation sent to the confirmUrl.
+| Parameter | +Data type | +Description | +
|---|---|---|
| + | String, Base64 encoded JSON |
+Contains all consumer information in JSON format. |
+
| Parameter | +State | +Data type | +Description | +
|---|---|---|---|
|
+
+
+
+
+Success
+ |
+Numeric, fixed 1. |
+Always set to |
+
|
+
+
+
+
+Success
+ |
+Numeric, up to 30. |
+Account number of the sender as returned by Sofort. |
+
|
+
+
+
+
+Success
+ |
+Alphanumeric with special characters, up to 255. |
+Owner of account as returned by Sofort. |
+
|
+
+
+
+
+Success
+ |
+Alphanumeric with special characters, up to 255. |
+Name of a bank as returned by Sofort. |
+
|
+
+
+
+
+Success
+ |
+Numeric, up to 30. |
+Number of banks as returned by Sofort. |
+
|
+
+
+
+
+Success
+ |
+Alphanumeric, up to 50. |
+BIC of the sender as returned by Sofort. |
+
|
+
+
+
+
+Success
+ |
+Alphabetic, fixed 2. |
+Country code of sender as returned by Sofort. |
+
|
+
+
+
+
+Success
+ |
+Alphanumeric, up to 50. |
+IBAN of the sender as returned by Sofort. |
+
securityCriteria |
+|
|---|---|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Numeric, fixed 1. |
+
Description |
+Always set to |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Numeric, up to 30. |
+
Description |
+Account number of the sender as returned by Sofort. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric with special characters, up to 255. |
+
Description |
+Owner of account as returned by Sofort. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric with special characters, up to 255. |
+
Description |
+Name of a bank as returned by Sofort. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Numeric, up to 30. |
+
Description |
+Number of banks as returned by Sofort. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric, up to 50. |
+
Description |
+BIC of the sender as returned by Sofort. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphabetic, fixed 2. |
+
Description |
+Country code of sender as returned by Sofort. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric, up to 50. |
+
Description |
+IBAN of the sender as returned by Sofort. |
+
| Parameter | +Data type | +Descritpion | +
|---|---|---|
| + | Alphanumeric, up to 35. |
+Unique identification of creditor. |
+
| + | Date as |
+Date when payment is debited from consumer’s bank account. |
+
| + | Alphanumeric, up to 35. |
+Identifier of the displayed mandate. |
+
| + | Date as |
+Date when the mandate was signed by the consumer. |
+
creditorId |
+|
|---|---|
Data |
+Value |
+
Data type |
+Alphanumeric, up to 35. |
+
Description |
+Unique identification of creditor. |
+
| + | |
Data |
+Value |
+
Data type |
+Date as |
+
Description |
+Date when payment is debited from consumer’s bank account. |
+
| + | |
Data |
+Value |
+
Data type |
+Alphanumeric, up to 35. |
+
Description |
+Identifier of the displayed mandate. |
+
| + | |
Data |
+Value |
+
Data type |
+Date as |
+
Description |
+Date when the mandate was signed by the consumer. |
+
SCA is a European regulatory requirement to combat and reduce fraud and make online payments more secure in every aspect.
+There are three elements, that must be independent of one another, and have to be considered to verify the identity of the consumer: PIN or password, smartphone, and scan or fingerprint.
+Supported brands are Mastercard, VISA, American Express, Diners Club, and Discover.
+| + + | +
+It is mandatory to send these request optional parameters: consumerEmail, consumerBillingFirstname, and consumerBillingLastname.+If "emerchantpay" is the chosen acquirer, parameters consumerBillingAddress1, consumerBillingCity, consumerBillingZipCode, and consumerBillingCountry must be added.
+ |
+
To start the payment process a request must be sent to a specific URL containing 3D Secure 2 request parameters for QPAY Checkout Page and QMORE Checkout Seamless.
+One-time payment is a fast way to make a single, non-recurring payment. Every transaction is consumer-initiated, therefore SCA based on PSD2 is required.
+Each One-click checkout transaction falls under the SCA requirements because it’s executed by the consumer in session. Merchants have to store credit card data as a token in their webshops for recurring payments. The advantage is that consumers can initialize the transaction just in a few steps with data stored in the shop. Every transaction is consumer-initiated so they need to give permission the first time for one-click checkout.
+In the first request set:
+consumerBillingFirstname, consumerBillingLastname and consumerEmail are mandatory parameters,
consumerChallengeIndicator must be set to 04,
merchantTokenizationFlag must be set to true.
| + + | +
+We recommend optional parameters consumerAuthenticationMethod and consumerShippingItemAvailability.
+ |
+
If the result is received after the payment is done then the 3DS2 process is completed for the first payment. If the consumer wants to pay again, the checkout has to be initialized again. Set the sourceOrderNumber with the orderNumber value from the previous payment in the new request. If the process is done by QMORE Checkout Seamless then don’t refer to any Data Storage session again and proceed to the frontend init.
| + + | +
+Parameters orderIdent and storageID must not use combined with the parameter sourceOrderNumber.
+ |
+
With this model, consumers must be informed regarding the terms of the agreement when setting up the recurring payment plan and the first transaction needs an SCA since transactions are merchant-initiated.
+In the first request set:
+consumerBillingFirstname, consumerBillingLastname and consumerEmail are mandatory parameters,
consumerChallengeIndicator must be set to 04,
merchantTokenizationFlag must be set to true.
| + + | +
+We recommend optional parameters consumerAuthenticationMethod and consumerShippingItemAvailability.
+ |
+
If the result is received after the payment is done then the 3DS2 process is completed for the first payment.
+The merchant has to use the recurPayment backend operation with the sourceOrderNumber, the merchantTokenizationFlag with the value true and the periodicType with the value recurring. The sourceOrderNumber is the orderNumber from the last recurring transaction and if the last transaction was the initial transaction, use this orderNumber for the sourceOrderNumber instead.
Unlike the subscription model where recurring payments happen with the same amount on a fixed date, PSD2 has the possibility to execute unscheduled merchant-initiated transactions (UCOF). Merchants have to consider that consumers must be informed regarding the terms of the unscheduled credential on file. The first transaction needs an SCA since transactions are merchant-initiated.
+In the first request set:
+consumerBillingFirstname, consumerBillingLastname and consumerEmail are mandatory parameters,
consumerChallengeIndicator must be set to 04,
merchantTokenizationFlag must be set to true.
| + + | +
+We recommend optional parameters consumerAuthenticationMethod and consumerShippingItemAvailability.
+ |
+
If the result is received after the payment is done then the 3DS2 process is completed for the first payment.
+The merchant has to use the recurPayment backend operation with the sourceOrderNumber, the merchantTokenizationFlag with the value true and the periodicType with the value ucof. The sourceOrderNumber is the orderNumber from the last recurring transaction and if the last transaction was the initial transaction, use this orderNumber for the sourceOrderNumber instead.
Circle K is a gift card payment option that is added by paysafecard.
+Circle K payment method can be initialized if the merchant sends CIRCLEK for parameter paymentType.
| + + | ++The parameter consumerMerchantCrmId is required by Circle K when initiating a payment. + | +
| + + | ++The parameter consumerMerchantCrmId is required by Circle K when initiating a payment. + | +
Optional request parameters customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed. Starting from this operation it’s possible to carry out different transaction-based operations.
+| + + | ++For the explanation of the different status descriptions included in this diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+A credit card allows cardholders to borrow funds from a pre-approved limit to pay for goods and services. When a purchase is made, the cardholder agrees to pay the card issuer and agrees to pay by signing a receipt with a record of the card details and indicating the amount to be paid or by entering a PIN.
+For transactions where the card is not shown e.g. e-commerce merchants additionally verify that the consumer is in physical possession of the card and is the authorized user by asking for additional information such as the CVC (card verification code), date of expiry, and billing address.
+| Brand name | +Description | +
|---|---|
American Express |
+American Express including American Express SafeKey |
+
Diners Club |
++ |
Discover |
++ |
Maestro SecureCode |
+Maestro SecureCode |
+
Mastercard |
+Master Card including Mastercard ID Check |
+
Visa |
+Visa including Visa Secure |
+
| Brand | +Length | +BIN range | +
|---|---|---|
American Express |
+15 |
+
|
+
Diners Club |
+14 |
+
|
+
Mastercard |
+16 |
+
|
+
16 |
+
|
+|
Visa |
+16 |
+
|
+
13 |
+
|
+
The merchant needs to send CCARD for parameter paymentType.
Optional request parameters customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+| + + | +
+The parameter orderReference becomes mandatory if the Worldline is used as an acquirer.
+ |
+
When using the payment methods Credit Card, Credit Card-Mail Order and Telephone Order in online shop, QENTA will return additional parameters.
+According to credit card company requirements for risk minimization, there are two parameters for recurring payments for QPAY Checkout Page and QMORE Checkout Seamless.
+The optional feature specific response parameter enhances the functionality and usability of the payment process regarding specific features and functions and is enabled by QENTA on the merchant’s behalf.
+
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed. Starting from this operation it’s possible to carry out different transaction-based operations.
+| + + | ++For the explanation of the different status descriptions included in this diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+CVS Pharmacy is a gift card payment option that is added by paysafecard.
+CVC payment method can be initialized if the merchant sends CVSPHARMACY for parameter paymentType.
| + + | ++The parameter consumerMerchantCrmId is required by CVS when initiating a payment. + | +
| + + | ++The parameter consumerMerchantCrmId is required by CVS when initiating a payment. + | +
Optional request parameter customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed. Starting from this operation it’s possible to carry out different transaction-based operations.
+| + + | ++For the explanation of the different status descriptions included in this diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+The amount parameter defines the payment amount which is to be done by the consumer of the online shop.
| + + | ++Thousand separators are not permitted. + | +
The maximum number of decimal places depends on the selected currency within the currency parameter:
+| Currency | +Decimal places | +
|---|---|
Euro |
+Maximum of 2 decimal places (100 Cent = 1 Euro). |
+
US Dollar |
+Maximum of 2 decimal places (100 Cent = 1 US$). |
+
Yen |
+No decimal places allowed. |
+
Libyan Dinar |
+Maximum of 3 decimal places (1000 Dirham = 1 Dinar). |
+
cancelUrl has to contain the URL of the page where the consumer is forwarded when the payment process is canceled. The consumer should be informed about the cancellation of the payment process and offered possibilities to retry the payment attempt or get in contact with the merchant.
cssUrl contains an URL to a CSS file stored on the server and accessible from the Internet. The CSS file is used to adjust the responsive design of QMORE Checkout Seamless and QPAY Checkout Page.
The currency parameter defines the currency used in the payment.
| + + | ++By default, only EUR is enabled as currency. If additional currencies are required contact our sales team. + | +
| Alphabetic value | +Numeric value | +Currency | +
|---|---|---|
|
+
|
+Swiss Franc |
+
|
+
|
+Czech Koruna |
+
|
+
|
+Euro |
+
|
+
|
+Pound Sterling |
+
|
+
|
+Hungarian Forint |
+
|
+
|
+Polish Zloty |
+
|
+
|
+US Dollar |
+
| + + | ++Not all available payment methods support all currencies. + | +
The customerId parameter represents the unique ID of the merchant using the QENTA Checkout Server.
For production mode, the customerId, as well as a secret, will be provided by our integration specialists.
The failureUrl parameter defines the URL of the online shop where the consumer is forwarded when the payment process has failed for any reason. On this page, the possibility to retry the payment or get in contact with support team.
The language parameter defines the language used for all messages of the QPAY Checkout Page and QMORE Checkout Seamless that are displayed to the consumer of the online shop.
| + + | ++By default, only English and German languages are activated. If the selected language is not supported by the respective financial service provider, the financial service provider decides which language is displayed to the consumer. + | +
| Value | +Language | +
|---|---|
|
+Arabian |
+
|
+Bosnian |
+
|
+Bulgarian |
+
|
+Chinese |
+
|
+Croatian |
+
|
+Czech |
+
|
+Danish |
+
|
+Dutch |
+
|
+English |
+
|
+Estonian |
+
|
+Finnish |
+
|
+French |
+
|
+German |
+
|
+Greek |
+
|
+Hebrew |
+
|
+Hindi |
+
|
+Hungarian |
+
|
+Italian |
+
|
+Japanese |
+
|
+Korean |
+
|
+Latvian |
+
|
+Lithuanian |
+
|
+Macedonian |
+
|
+Norwegian |
+
|
+Polish |
+
|
+Portuguese |
+
|
+Romanian |
+
|
+Russian |
+
|
+Serbian |
+
|
+Slovakian |
+
|
+Slovenian |
+
|
+Spanish |
+
|
+Swedish |
+
|
+Turkish |
+
|
+Ukrainian |
+
The merchantTokenizationFlag parameter can be used to set the recurring flaggings for specific orders. To save the consumer’s card details for later use, the aforementioned parameter must be set to TRUE.
The orderDescription parameter is a description of what the consumer paid for, e.g. a text cross-referencing the order made in the online shop.
| + + | ++This text is not transmitted to any financial service provider and is therefore NEVER displayed on any consumer’s invoice or statement. The text is displayed in the QPC Payment Center. + | +
If the optional request parameter displayText is not used the orderDescription text will also be visible as consumer information in QPAY Checkout Page.
| + + | +
+The value of orderDescription must not contain any special characters or line breaks. Including such characters causes the fingerprint computation to fail and the error message "Invalid fingerprint!" is displayed.
+ |
+
The paymentType parameter is the name of the payment method the user selected in the online shop.
| + + | ++To use a payment method, it must be purchased by the merchant and enabled by QENTA. If additional payment methods are required, contact our sales team. + | +
Value of paymentType parameter |
+Payment method | +
|---|---|
|
+The consumer may select one of the activated payment methods directly in QPAY Checkout Page. |
+
|
++ |
|
+Credit Card, Maestro SecureCode |
+
|
++ |
|
++ |
|
++ |
|
++ |
|
++ |
|
++ |
|
+Invoice: Payolution |
+
|
++ |
|
++ |
|
++ |
|
++ |
|
++ |
|
++ |
|
++ |
The periodicType parameter defines the periodic type of initial and recurring payments.
| periodicType value | +Description | +
|---|---|
|
+For unscheduled recurring payments with different amounts. |
+
|
+For recurring payments like subscriptions with the same interval and same amount. |
+
returnUrl is used for browsers that are not capable of fully supporting CORS (Cross Origin Resource Sharing). In that case, the communication between the HTML page and the QENTA Checkout Server will be done within an iframe where the anonymized payment data are returned to JavaScript objects.
The requestFingerprint parameter contains the computed fingerprint based on the values of parameters defined in the requestFingerprintOrder parameter. This method is used for security reasons to verify the parameters the online shop sends to the QENTA Checkout Server.
| + + | ++At least one of the parameters used for computing the fingerprint needs to be unique to each order to prevent sending the same hash-value! + | +
To authenticate, all requests to the QENTA Checkout Server need to contain the aforementioned requestFingerprint. To generate the said fingerprint, the HMAC-SHA-512 construction is used by combining the cryptographic hash function SHA-512 with the secret as the cryptographic key to hash the concatenated request parameter values in the order defined in the requestFingerprintOrder.
The parameter requestFingerprintOrder needs to contain a comma-separated list of all parameter names, the values of which – and in that exact order — are used to create the fingerprint.
The parameter names in the requestFingerprintOrder parameter may be listed in any order, but this exact ordering must be used for the respective parameter values when calculating the fingerprint accordingly, e.g.
customerId,amount,currency,language,orderDescription,successUrl,requestFingerprintOrder,secret
The serviceUrl parameter is used to define the URL of a web page in an online shop which informs the consumer about the different possibilities to get in contact with the merchant.
| + + | ++Do not use this URL to link to the shopping basket of the consumer! + | +
If the optional parameter imageUrl is not included, the serviceUrl is not used in the QPAY Checkout Page and the consumer has no possibility to access the service page in the online shop during the payment process.
The serviceURL has to be accessible over the internet via port 80 or port 443 and may not be hosted on a local server that can’t be accessed by the QENTA Checkout Server.
The autoDeposit parameter enables an automatic deposit and day-end closing of payments. After a consumer has completed payment in online shop, the payment is only approved and not yet deposited.
| + + | ++Not deposited (uncaptured) approvals will expire after 7-14 calendar days. The exact deadline depends on the regulations provided by each financial service provider. After exceeding the individual deadline these payments can no longer be submitted or received. Contact our sales team to activate this feature. + | +
The backgroundColor parameter defines background color for the HTML pages in the custom CSS for QPAY Checkout Page and value is hex-coded RGB e.g. f0f0f0.
Background color for the brand image that contains the credit card logos can be set.
+The confirmMail parameter defines one e-mail address of the merchant for receiving payment details regarding the orders of consumers in the online shop. This e-mail may contain information about payment state, order number, payment method, payment amount and payment currency.
QENTA can activate one of the two options:
+QENTA will send the confirmation to the confirmMail only if the confirmUrl is not available.
QENTA will always send the confirmation to the confirmMail in any case.
| + + | ++Contact sales team to activate the feature. + | +
|
+The payment has been successfully finished by the consumer. |
+
|
+The payment process has been canceled by the consumer and has not been successfully finished. |
+
|
+A problem occurred during the payment process and the payment has not been successfully finished. |
+
|
+The payment is in progress. The merchant can’t be informed about the success or failure of the payment. |
+
The confirmUrl defines the URL of online shop that is used by QENTA Checkout Server to send the result of the payment process back.
For QPAY Checkout Page confirmUrl is optional because the same parameters and values are posted to successUrl, failureUrl, cancelUrl or pendingUrl.
For QMORE Checkout Seamless confirmUrl is required because no return parameters are sent to the successUrl.
Use the confirmUrl to save the result of each payment process in the database for later use. Additionally, if consumer does not receive the page of the successUrl, the confirmUrl informs about the result of the payment process anyway.
| + + | +
+The URL has to be accessible over the Internet via port 80 (HTTP) or port 443 (HTTPS) and may not be hosted on a local server that can’t be accessed by the QENTA Checkout Server via the Internet. Also, ensure that firewall configurations allow receiving the confirmation sent via 212.183.46.16/28. For HTTPS communication only TLS can be used, older protocols are not supported.
+ |
+
QENTA does not verify whether or not the confirmation was successfully received by the web server. Redelivery attempts can be enabled by our integration specialists, they will set the intervals for redelivery attempts according to the requirements. The intervals are set in minutes, the minimum is one minute, or hours, and the maximum is 99 hours. During times of high load on the QENTA Checkout Server, a redelivery attempt may start a bit delayed, however, it will never start before the defined interval. To use this feature, the request parameter confirmUrl has to be sent. Optionally the request parameter confirmMail can be used to send confirmation e-mails individually per transaction.
If the confirmation was successfully received, the response will be OK; otherwise, the response will be NOK and a message which specifies the error. Use one of the following three possibilities to configure the response parameters.
The following content is possible for HTML comments and plain response: <QPAY-CONFIRMATION-RESPONSE result="OK|NOK" message="ans..255"/>
<!--<QPAY-CONFIRMATION-RESPONSE result="OK" /> -→ (1)
+<!--<QPAY-CONFIRMATION-RESPONSE result="NOK" message="Fingerprint validation failed."/> -→ (2)| 1 | +for confirming the successful receipt of our confirmation. | +
| 2 | +for confirming the unsuccessful receipt of our confirmation. | +
<QPAY-CONFIRMATION-RESPONSE result="OK" /> (1)
+<QPAY-CONFIRMATION-RESPONSE result="NOK" message="Session not found." /> (2)| 1 | +for confirming the successful receipt of our confirmation. | +
| 2 | +for confirming the unsuccessful receipt of our confirmation. | +
{"status":"OK","errorCodes":null,"QPAY-CONFIRMATION-RESPONSE":{"result": "OK"}} (1)
+{"status":"NOK","errorCodes":12345,"QPAY-CONFIRMATION-RESPONSE":{"result": "NOK","message":"Session not found."}} (2)| 1 | +for confirming the successful receipt of our confirmation. | +
| 2 | +for confirming the unsuccessful receipt of our confirmation. | +
| + + | +
+If web server is down for some reason or can’t be accessed by the QENTA Checkout Server, the confirmation can’t be delivered to the confirmURL, and no responses may be sent. QENTA will continue to resend the confirmation until receiving the %%result="OK"%% or until the last redelivery attempt was made.
+ |
+
In case QENTA has sent a confirmation and no response was received by the time the last redelivery attempt was made, only one final information is sent to the given e-mail address.
+If the consumer in online shop has terminated a session unexpectedly e.g. closing the browser window, the first confirmation is sent automatically and not earlier than 30 minutes after the request was sent by QENTA.
+The customerStatement parameter defines a text which is displayed on the bank statement issued to a consumer by the financial service provider.
The set of allowed characters and the allowed maximum length depends on the restrictions for payment methods and the corresponding financial service providers.
+The displayText parameter defines a text which is displayed during the payment process on the QPAY Checkout Page. If displayText is not used, the required parameter OrderDescription will be used instead.
This text is not transmitted to any financial service provider and is therefore NEVER displayed on any consumer’s invoice or statement.
+The duplicateRequestCheck parameter checks if the same order has been unintentionally sent more than once by a consumer. The consumer may unintentionally resend the same order by pressing the reload button of the browser because of problems with the internet connection.
For this check ensure that the required parameter orderDescription or any other customer parameter used in the fingerprint calculation is different for each order to prevent false-positive detection of duplicate requests. Since for each request, a hash of all parameter values is sent, i.e. the fingerprint, QENTA can easily detect any identical request that has been sent in the last 30 minutes.
| + + | ++QENTA can check for duplicate requests, and for that set the value of parameter to “yes”; otherwise, don’t send this parameter. + | +
financialInstitution can be used in conjunction with the parameter paymentType, when a specific payment method is selected by the consumer in the online shop. One or more financial institutions can be defined as what is wanted to offer to consumers based on the selected payment method. The individual brands may be listed in any order within the parameter:
Allow all brands, force 3-D Secure for brands that support 3-D Secure:
+financialInstitution=amexsafekey,DinersProtectBuy,DiscoverProtectBuy,MCSC,Maestro,VbV
Limit to American Express SafeKey, Mastercard, and Visa 3-D Secure:
+financialInstitution=amexsafekey,MCSC,VbV
| + + | ++Payment method EPS/Giropay only allows one value, while other payment methods like Credit Card allows a comma-separated list of values. + | +
financialInstitution by paymentTypePossible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Installment for Riverty |
+
|
+Invoice for Riverty |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Mastercard ID Check |
+
|
+Mastercard |
+
|
+Maestro SecureCode |
+
|
+Visa |
+
|
+Visa Secure |
+
|
+American Express |
+
|
+American Express SafeKey |
+
|
+Diners Club |
+
|
+Discover |
+
|
+Diners Protect Buy |
+
|
+Discover Protect Buy |
+
|
+Description |
+
|
+EPS SELECT OPTION |
+
|
+Description |
+
|
+Invoice by payolution |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+PayPal |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Przelewy24 |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+SEPA Direct Debit |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Sofort. |
+
The imageUrl parameter defines the URL to an image on a web server. The image will be displayed during the payment process on QPAY Checkout Page. Image size should have a width of 200 pixels and a height of 100 pixels and the supported image formats are gif, jpg, and png.
| + + | ++For security reasons we don’t accept .svg images provided by the customer, so use .png instead. + | +
There must be an image available within the given image URL; the loading of QPAY Checkout Page will be delayed until a time-out for the missing image occurs.
+If imageUrl is not used then the required parameter serviceUrl will not be used too. Otherwise, the image will be encapsulated by a link to the serviceUrl, so that the consumer can click on the image to view the HTML page available at the serviceUrl.
| + + | +
+This URL has to be accessible over the internet https:// and must be accessible by the QENTA Checkout Server.
+ |
+
javascriptScriptVersion defines the version of the used JavaScript for managing the JavaScript-based communication between the HTML page and the QENTA Data Storage. If the parameter is set to pci3, QENTA data storage creates an iFrame that can be integrated into the homepage.
If the parameter is not set the javascript fields will be delivered to the to the system.
+The parameter mandateId defines a two-party mandate between the merchant and the debtor and is required for SEPA Direct Debit payments. The mandate is an agreement giving the merchant permission to debit the consumer’s account for the sum that the two parties agreed upon. Every mandate has an ID provided by the merchant that has to be unique for the creditor.
The parameter mandateSignatureDate defines the date on which the above-mentioned mandate was signed by the consumer.
The maxRetries parameter defines the maximum number of payment attempts regarding a unique order.
| Value | +Behavior | +
|---|---|
|
+No restriction regarding the number of retries a consumer can do. |
+
|
+No retry is possible for the consumer. If an error occurs the consumer will be redirected to the |
+
|
+Maximum number of retries the consumer can do before redirecting to the |
+
| + + | ++Contact our sales team to activate this feature. + | +
With the parameter noScriptInfoURL define the URL to an information page of the online shop which is displayed to the consumer if the web browser of the consumer has JavaScript disabled.
This information page within the online shop informs consumers of the requirement to enable JavaScript and a guide on how to do this in the web browser.
+The orderIdent parameter defines a unique reference to a specific order of a specific consumer within an online shop. This parameter is used within the QENTA Data Storage together with the customerId, shopId and storageId so that only the merchant is able to access the specific session of the QENTA Data Storage.
The value of the orderIdent has to be unique for each order of the consumer. Use the same value for initializing the QENTA Data Storage and for initiating the payment process.
orderNumber defines a unique ID for the order and when the value of the parameter is set it’s not possible to use that order number for the second time. Even if the consumer could not successfully finalize the payment process, therefore orderNumber can only be used if the parameter maxRetries is set to 0.
| + + | +
+The feature has to be activated by our sales team, otherwise QENTA is generating the orderNumber.
+ |
+
The orderReference parameter defines a unique transaction ID that will be forwarded to the financial institution.
The set of allowed characters and the allowed maximum length depends on the restrictions for payment methods and the corresponding financial service providers.
+paymenttypeSortOrder defines the sort order of all displayed payment methods and their corresponding sub-methods if paymentType is set to SELECT.
Offer a county-specific sort order by the payment methods with this parameter.
+| + + | ++The sort order of the payment methods can be set by using a comma-separated list as defined within the parameter paymentType. Also, all available sub-methods can be found within the description of the parameter financialInstitution, and add them to the list. + | +
The pendingUrl parameter defines the URL of online shop where a consumer is forwarded when the payment process could not determine a result yet.
| + + | +
+When using the optional parameter pendingUrl, the use of the parameter confirmUrl is mandatory.
+ |
+
The pendingUrl is an optional request parameter for backward compatibility with existing online shops, but use the parameter for handling asynchronous payment methods or payment methods that may have sometimes a delay in returning a final state of a transaction.
When the QENTA Checkout Server receives a final state from the corresponding financial service provider the information to the confirmUrl will be sent.
| paymentType | +Required | +Highly recommended | +Not needed | +
|---|---|---|---|
|
++ | ✔ |
++ |
|
++ | ✔ |
++ |
|
++ | ✔ |
++ |
|
++ | ✔ |
++ |
|
++ | + | ✔ |
+
|
++ | ✔ |
++ |
|
++ | ✔ |
++ |
|
++ | ✔ |
++ |
|
++ | + | ✔ |
+
|
++ | ✔ |
++ |
If the consumer has entered or changed his shipping or billing information after initialization, e.g. when using QPBL PayByLink then purchaseInformation is returned in the confirmation request made to confirmUrl. It is a Base64 encoded string that contains consumer, basket and order data as well as any additional parameters sent during initialization in JSON.
purchaseInformation=ewogICAgImFkZGl0aW9uYWxQYXJhbWV0ZXJzIjogewogICAgICAgICJDT05TVU1FUl9NRVJDSEFOVF9DUk1fSUQiOiAiMTIzNDIzNTM0NiIsCiAgICAgICAgInNob3BuYW1lX2N1c3RvbVBhcmFtZXRlcjEiOiAieW91ciBmaXJzdCBjdXN0b20gcGFyYW1ldGVyIiwKICAgICAgICAic2hvcG5hbWVfY3VzdG9tUGFyYW1ldGVyMiI6ICJ5b3VyIHNlY29uZCBjdXN0b20gcGFyYW1ldGVyIgogICAgfSwKICAgICJvcmRlckRlc2NyaXB0aW9uIjogIlRlc3Q6MDAwMCIsCiAgICAiY3VzdG9tZXJTdGF0ZW1lbnQiOiAiWW91ciBTaG9wbmFtZTogT3JkZXI6IDEyM3BhZ2UiLAogICAgIm9yZGVyUmVmZXJlbmNlIjogIjEyM3BhZ2UiLAogICAgImNvbnN1bWVyQmlsbGluZ0ZpcnN0TmFtZSI6ICJBbmRlcmVyQmlsbGluZyIsCiAgICAiY29uc3VtZXJCaWxsaW5nTGFzdE5hbWUiOiAiQmlsaW5nbmFjaG5hbWUiLAogICAgImNvbnN1bWVyQmlsbGluZ0FkZHJlc3MxIjogIkNcL08gS1x1MDBmY25pYmVydCBHcm9cdTAwZGYiLAogICAgImNvbnN1bWVyQmlsbGluZ0FkZHJlc3MyIjogIkJpbGxpbmdzdHJhXHUwMGRmZSAxMCIsCiAgICAiY29uc3VtZXJCaWxsaW5nQ2l0eSI6ICJHcmF6IiwKICAgICJjb25zdW1lckJpbGxpbmdaaXBDb2RlIjogIjgwMjAiLAogICAgImNvbnN1bWVyQmlsbGluZ0NvdW50cnkiOiAiU1IiLAogICAgImNvbnN1bWVyQmlsbGluZ1N0YXRlIjogIndvaXNkYXMiLAogICAgImNvbnN1bWVyU2hpcHBpbmdGaXJzdE5hbWUiOiAiU2hpcFZvcm5hbWVOZXUiLAogICAgImNvbnN1bWVyU2hpcHBpbmdMYXN0TmFtZSI6ICJTaGlwTmFjaG5hbWVOZXUiLAogICAgImNvbnN1bWVyU2hpcHBpbmdBZGRyZXNzMSI6ICJTaGlwcGluZ3N0cmFcdTAwZGZlIDEwYSIsCiAgICAiY29uc3VtZXJTaGlwcGluZ0FkZHJlc3MyIjogIjVcL0EgLSAzMyBTdC4gMTAwMCIsCiAgICAiY29uc3VtZXJTaGlwcGluZ0NpdHkiOiAiR3JheiIsCiAgICAiY29uc3VtZXJTaGlwcGluZ1ppcENvZGUiOiAiODAyMCIsCiAgICAiY29uc3VtZXJTaGlwcGluZ1N0YXRlIjogIkFuZHJlclN0YWF0IiwKICAgICJjb25zdW1lclNoaXBwaW5nQ291bnRyeSI6ICJHVSIsCiAgICAiY29uc3VtZXJTaGlwcGluZ0l0ZW1BdmFpbGFiaWxpdHkiOiAiMDEiLAogICAgImNvbnN1bWVyU2hpcHBpbmdNZXRob2QiOiAiaG9tZV9kZWxpdmVyeSIsCiAgICAiY29uc3VtZXJTaGlwcGluZ0FkZHJlc3NGaXJzdFVzZURhdGUiOiAiMTAuMTIuMjAyMSIsCiAgICAiYmFza2V0SXRlbXMiOiAiMyIsCiAgICAiYmFza2V0SXRlbSI6IHsKICAgICAgICAiMSI6IHsKICAgICAgICAgICAgImFydGljbGVOdW1iZXIiOiAiQTAwMSIsCiAgICAgICAgICAgICJxdWFudGl0eSI6ICIxIiwKICAgICAgICAgICAgIm5hbWUiOiAiUHJvZHVjdCBBMSIsCiAgICAgICAgICAgICJ1bml0R3Jvc3NBbW91bnQiOiAiMTAuODAiLAogICAgICAgICAgICAidW5pdE5ldEFtb3VudCI6ICI5LjAwIiwKICAgICAgICAgICAgInVuaXRUYXhBbW91bnQiOiAiMS44MCIsCiAgICAgICAgICAgICJ1bml0VGF4UmF0ZSI6ICIyMC4wMDAiCiAgICAgICAgfSwKICAgICAgICAiMiI6IHsKICAgICAgICAgICAgImFydGljbGVOdW1iZXIiOiAiQTAwMiIsCiAgICAgICAgICAgICJxdWFudGl0eSI6ICIxIiwKICAgICAgICAgICAgIm5hbWUiOiAiUHJvZHVjdCBBMiIsCiAgICAgICAgICAgICJ1bml0R3Jvc3NBbW91bnQiOiAiMTQuOTQiLAogICAgICAgICAgICAidW5pdE5ldEFtb3VudCI6ICIxMi40NSIsCiAgICAgICAgICAgICJ1bml0VGF4QW1vdW50IjogIjIuNDkiLAogICAgICAgICAgICAidW5pdFRheFJhdGUiOiAiMjAuMDAwIgogICAgICAgIH0sCiAgICAgICAgIjMiOiB7CiAgICAgICAgICAgICJhcnRpY2xlTnVtYmVyIjogIlMwMDEiLAogICAgICAgICAgICAicXVhbnRpdHkiOiAiMSIsCiAgICAgICAgICAgICJuYW1lIjogIlNoaXBwaW5nIiwKICAgICAgICAgICAgInVuaXRHcm9zc0Ftb3VudCI6ICI5NzQuMjUiLAogICAgICAgICAgICAidW5pdE5ldEFtb3VudCI6ICI5NzQuMjUiLAogICAgICAgICAgICAidW5pdFRheEFtb3VudCI6ICIwLjAwIiwKICAgICAgICAgICAgInVuaXRUYXhSYXRlIjogIjAuMDAwIgogICAgICAgIH0KICAgIH0sCiAgICAiY29uc3VtZXJFbWFpbCI6ICJlZGl0aWVydGUuZW1haWwuYWRyZXNzZUB0ZXN0LmNvbSIsCiAgICAiY29uc3VtZXJTaGlwcGluZ1Bob25lIjogIjEyMzQ1Njc4MzQ1NjciLAogICAgImNvbnN1bWVySXBBZGRyZXNzIjogIjE3Mi4yMC4wLjIwMyIsCiAgICAiY29uc3VtZXJCaXJ0aERhdGUiOiAiMjAwMS0wMy0wMSIKfQ=={
+ "additionalParameters": {
+ "CONSUMER_MERCHANT_CRM_ID": "1234235346",
+ "shopname_customParameter1": "first custom parameter",
+ "shopname_customParameter2": "second custom parameter"
+ },
+ "orderDescription": "Test:0000",
+ "customerStatement": "Your Shopname: Order: 123page",
+ "orderReference": "123page",
+ "consumerBillingFirstName": "AndererBilling",
+ "consumerBillingLastName": "Bilingnachname",
+ "consumerBillingAddress1": "C\/O K\u00fcnibert Gro\u00df",
+ "consumerBillingAddress2": "Billingstra\u00dfe 10",
+ "consumerBillingCity": "Graz",
+ "consumerBillingZipCode": "8020",
+ "consumerBillingCountry": "SR",
+ "consumerBillingState": "woisdas",
+ "consumerShippingFirstName": "ShipVornameNeu",
+ "consumerShippingLastName": "ShipNachnameNeu",
+ "consumerShippingAddress1": "Shippingstra\u00dfe 10a",
+ "consumerShippingAddress2": "5\/A - 33 St. 1000",
+ "consumerShippingCity": "Graz",
+ "consumerShippingZipCode": "8020",
+ "consumerShippingState": "AndrerStaat",
+ "consumerShippingCountry": "GU",
+ "consumerShippingItemAvailability": "01",
+ "consumerShippingMethod": "home_delivery",
+ "consumerShippingAddressFirstUseDate": "10.12.2021",
+ "basketItems": "3",
+ "basketItem": {
+ "1": {
+ "articleNumber": "A001",
+ "quantity": "1",
+ "name": "Product A1",
+ "unitGrossAmount": "10.80",
+ "unitNetAmount": "9.00",
+ "unitTaxAmount": "1.80",
+ "unitTaxRate": "20.000"
+ },
+ "2": {
+ "articleNumber": "A002",
+ "quantity": "1",
+ "name": "Product A2",
+ "unitGrossAmount": "14.94",
+ "unitNetAmount": "12.45",
+ "unitTaxAmount": "2.49",
+ "unitTaxRate": "20.000"
+ },
+ "3": {
+ "articleNumber": "S001",
+ "quantity": "1",
+ "name": "Shipping",
+ "unitGrossAmount": "974.25",
+ "unitNetAmount": "974.25",
+ "unitTaxAmount": "0.00",
+ "unitTaxRate": "0.000"
+ }
+ },
+ "consumerEmail": "editierte.email.adresse@test.com",
+ "consumerShippingPhone": "1234567834567",
+ "consumerIpAddress": "172.20.0.203",
+ "consumerBirthDate": "2001-03-01"
+}The shopId defines the unique identifier for the online shop within customerId. This is used if the merchant has multiple online shops or one online shop with multiple configurations within one customerId.
| + + | +
+The use of shopId has to clarify with the support, so contact integration specialists.
+ |
+
The parameter storageId is the unique ID to the QENTA Data Storage of a specific consumer within a specific payment process. The storageId is valid for 30 minutes after the latest use of an initialization, store or read operation on that Data Storage.
| + + | +
+storageId gets invalid after a successful initiation of the payment process.
+ |
+
The transactionIdentifier parameter defines whether a transaction is a single transaction or an initial transaction followed by many subsequent ones. Value SINGLE is a standard singular transaction for which authorization is given once by the consumer to collect only one transaction and value INITIAL for the first transaction of a series of recurring payments.
| + + | +
+If the parameter transactionIdentifier is used, the configuration setting is overwritten correspondingly, if is not used, the value set in the merchant configuration is used.
+ |
+
Currently, the transactionIdentifier may be used for payment methods PayPal and SEPA Direct Debit and it’s required to distinguish between a single transaction or the first transaction with subsequent transaction based on the first one.
| + + | +
+Backend operation recurPayment may only be carried out if the transactionIdentifier value INITIAL is used. For using the value INITIAL for subsequent recurring transactions, additional approval from the financial service provider needs to be obtained e.g. for PayPal. After receiving approval contact our integration specialists to enable the feature.
+ |
+
The windowName parameter defines the name of the pop-up window of iframe where QPAY Checkout Page or an additional payment window is opened.
| + + | +
+windowName is required if the merchant offered payment methods that open an additional pop-up window like eps-Überweisung or PayPal. It ensures a proper return to the checkout process after that payment method-specific pop-up window is closed.
+ |
+
The window name must contain uppercase and lowercase letters and underscores, and must not contain any whitespace characters or foreign characters.
+Opening QPAY Checkout Page or QMORE Checkout Seamless within a pop-up window may cause problems to the consumers if they have enabled a pop-up blocker within their browsers or it’s activated by default.
+The parameter creditorId identifies a merchant and allows consumers to manage their mandates with merchants more easily.
The parameter dueDate defines the day when payment is debited from the consumer’s bank account.
+Values of financialInstitution by paymentType
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Installment for Riverty |
+
|
+Invoice for Riverty |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Mastercard |
+
|
+Maestro SecureCode |
+
|
+Visa |
+
|
+American Express |
+
|
+Diners Club |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+EPS SELECT OPTION |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Invoice by payolution |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+PayPal |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Przelewy24 |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+SEPA Direct Debit |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+Sofort. |
+
Possible value(s) of financialInstitution |
+Description | +
|---|---|
|
+PAYSAFECARD |
+
The information on the consumer’s country can’t be derived from the delivery address, so they will be taken from the data returned to QENTA by the respective financial service provider. E.g. in the case of credit cards, the country of the credit card issuer is returned and used to determine the consumer’s country.
+instrumentCountry can be used for payment methods: Credit Card, PayPal, and Sofort.
To check the authenticity of the return values sent from the QENTA Checkout Server to the online shop, compare the responseFingerprint with a hash of the return values.
Create a string by concatenating all returned parameters based on the order in the return parameter responseFingerprintOrder. Then hash the string with an HMAC-SHA-512 algorithm using the secret as cryptographic key and compare the result with the value of the return parameter responseFingerprint. If both values are identical, the response is authentic, i.e. the confirmation was indeed sent by QENTA. If these values are not identical, recheck the calculation and consider that someone compromised the return values or has sent a possibly false confirmation for the payment. Therefore, don’t trust these return values and don’t assume that the payment was made even if it appears that way!
To ensure secure communication it’s essential that never disclose or share the secret with persons who are not involved in developing the online shop. Also, never forward the secret via unsecured communication channels e.g. mail, e-mail, fax or instant messaging. When the secret is submitted by fax make sure that the contents of the fax are disclosed only to authorized persons!
+If the merchant suspect that the secret has been revealed to unauthorized individuals, contact our integration specialists immediately and request a new secret!
+Dollar General is a gift card payment option that is added by paysafecard.
+Dollar General payment method can be initialized if the merchant sends DOLLARGENERAL for parameter paymentType.
| + + | ++The parameter consumerMerchantCrmId is required by Dollar General when initiating a payment. + | +
| + + | ++The parameter consumerMerchantCrmId is required by Dollar General when initiating a payment. + | +
Optional request parameters customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed. Starting from this operation it’s possible to carry out different transaction-based operations.
+| + + | ++For the explanation of the different status descriptions included in this diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+| + + | ++Eps-Überweisung is offered by Austrian banks and Giropay is offered by German banks. + | +
Eps-Überweisung and Giropay allows consumers to make online payments via their online banking applications. After successful login, a form will open on eps-Überweisung containing the transfer order for the consumer’s bank. All relevant details of the purchase e.g. amount and consumer details are already filled in and the consumer needs to authorize the transaction. Once the transfer order has been accepted by the consumer’s bank the merchant will receive a confirmation.
+The merchant needs to conclude and sign an eps merchant contract with the account-holding bank.
+If the merchant has stated card complete as the acquirer, QENTA will receive a PIN which is required by our integration specialists to complete the configuration of the account.
+If the merchant did not state card complete as the acquirer, the PIN letter, IBAN and BIC of the bank account need to be forwarded to QENTA; otherwise, the configuration can’t be finished.
+Eps/Giropay payment methods can be initialized if the merchant sends EPS for parameter paymentType.
| + + | +
+The value EPS-SO has to be forwarded for the request parameter financialInstitution which is required for QMORE Checkout Seamless.
+ |
+
Optional request parameters customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+QENTA offers different layouts for the consumers bank statement with a maximum length of 35 characters. Be aware that orderReference and/or customerStatement must be defined in the request to be used. Contact our integration specialists to choose a different option.
+Example:
+orderNumber = 843160
+orderReference = 1234567890
+customerStatement = customerStatement12345
Option 1: orderNumber + orderReference + customerStatement = ”000000843160 1234567890 customerSta”
Option 2: orderNumber + Localtime = ”0000843160-20211220-150839”
Option 3: orderReference = ”001234567890”
Option 4: orderNumber + customerStatement = ”000000843160 customerStatement12345”
| + + | ++Option 1 is enabled by default. + | +
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed.
+| + + | ++For the explanation of the different status descriptions included in this diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+The Google Pay API enables fast, simple checkout on the website, and gives the merchant convenient access to hundreds of millions of cards saved to Google Accounts worldwide.
+Before Google Pay API implementation is production-ready, register with Google, accept the Terms of Service, and receive a Google merchant ID after the website passes a Google review.
+Before applying for production access check the following:
+A Google Account
+A supported payments gateway or a Payment Card Industry Data Security Standard (PCI DSS) compliant server environment that’s suitable to store decrypted payment information
+A list of fully qualified domains, which includes subdomains, from which the merchant intend to call the Google Pay API
+After the website is approved, the merchant will receive a Google merchant ID that must be included with each Google Pay API request.
+| + + | ++Once merchant ID is generated it should be forwarded to the integration specialist. + | +
Google Pay API payment method can be initialized if the merchant sends GOOGLEPAY for parameter paymentType.
allowedCardNetworks
MERCHANTS can set the ccard brand for google pay and allowedCardNetworks in checkbox should be chosen:
allowedCardNetworks=AMEX,DISCOVER,DINERS,MASTERCARD,VISA
Possible value(s) of allowedCardNetworks |
+Description | +
|---|---|
|
+American Express |
+
|
+Discover |
+
|
+Diners Club |
+
|
+Mastercard |
+
|
+Visa |
+
By default all brands will be activated.
+QENTA integrated 
for web merchants based on the following documentations:
Google Pay Web developer documentation
+| + + | ++There is no need to follow these integration guidelines as they are already covered within the QENTA products. + | +
Information about the authorization methods can be found here.
+QENTA offers in the hosted payment solutions, which allows the merchant to communicate directly with the QENTA API.
encrypted payment information (cryptogram) is handled directly by QENTA.
In general, gateway credentials are mandatory for the integration.
+The gateway and gatewayMerchantId are set by QENTA and are not needed to be set by the merchant.
QENTA Payment CEE allows using a variety of methods in the online shop. Some of these payment methods require specific integration steps or an additional external registration or setup process on the website of the corresponding financial service provider.
+QENTA offers download logos for payment methods free of charge to optimize the online shop.
+Using the payment methods invoice and installment with payment guarantee the respective amount will be received from the selected financial service provider even if the payment was not yet affected by the consumer in the online shop.
+Invoice
+The items purchased in the online shop are sent to the consumer together with the relevant invoice. The consumer then affects the transfer of the respective amounts within the due date for payment.
+Installment
+The items purchased in the online shop are sent to the consumer. The relevant partial amounts are collected from the consumer’s account through direct debit every month.
+If the online shop is enabled for payment methods invoice or installment use the required additional request parameters listed on the corresponding pages of the provider. These request parameters must have been set previously whenever the payment method is set to INVOICE or AFTERPAY or the consumer selects those payment methods after QPAY Checkout Page is invoked with payment method SELECT.
If an invoice or installment payment is accepted, the response parameter paymentState with the value SUCCESS is returned, same as gatewayReferenceNumber. The reference number of the invoice should be stored for tracking purposes.
| + + | ++For payment method invoice the otherwise optional request parameters for consumer billing data are required for all providers. + | +
Mail Order and Telephone Order which is also known as CCARD-MOTO, standing for credit card payments based on a Mail Order or Telephone Order, is intended for back office transactions and is suited for any system that’s capable of storing orders, such as ERP systems and call center applications.
+When using this payment method, consumers have two options to order services or items:
+Per mail, fax or letter: Consumer forwards the order and the payment method details to the merchant in written form.
+Per telephone: Consumer calls e.g. the service center to place the order and communicates the payment method details by telephone.
+| + + | ++When the service center staff has access to an ERP system, they may verify whether the products which are ordered via phone or fax are available while at the same time checking the validity of the consumer’s credit card data. + | +
The merchant configuration has to be changed by our integration specialists on merchant’s behalf, and acquirers might require to meet additional and special conditions to fulfill PCI security standards in their acceptance contracts.
+Any sensible credit card details must only be accessible for entitled persons such as the service center staff which in turn must have received a special security training for handling such sensitive consumer and payment data. Consumers must never disclose their 3-D Secure code to the service center staff when placing mail or telephone orders.
+| + + | ++The entry of the CVC might be optional depending on tge acquirer and the concluded acceptance contract. + | +
QENTA offers three solutions to handle credit card transaction based on mail and telephone orders:
+After integration into the online shop consumers may call the service center and place orders by telling their credit card details. Ensure that this payment method is only available to the service center staff and is not accessible to consumers.
+| + + | ++Any backend operations such as refund or recurring transactions are carried out in the usual manner described. + | +
Here are parameters for Mail Order and Telephone Order.
+oBucks is a gift card payment option that is added by paysafecard.
+oBucks payment method can be initialized if the merchant sends OPENBUCKSCARD for parameter paymentType.
| + + | ++The parameter consumerMerchantCrmId is required by oBucks when initiating a payment. + | +
| + + | ++The parameter consumerMerchantCrmId is required by oBucks when initiating a payment. + | +
Optional request parameters customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed. Starting from this operation it’s possible to carry out different transaction-based operations.
+| + + | ++For the explanation of the different status descriptions included in this diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+Przelewy24 is a real-time bank transfer of payments, consumers based in Poland can use it to transfer funds directly to merchants from their bank accounts.
+Przelewy24 accepts consumer’s payments to its account, confirms payment processing to the merchant, and transfers these payments to the merchant’s account. Each transaction result sent to the merchant is immediately verified in order to confirm that the sender was Przelewy24.
+P24 payment method can be initialized if the merchant sends PRZELEWY24 for parameter paymentType.
| + + | ++The required request parameter is consumerEmail. + | +
| + + | ++The required request parameter is consumerEmail. + | +
Optional request parameters customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+For Prezelewy24 only PLN as currency is available.
+
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed.
+| + + | ++For the explanation of the different status descriptions included in this diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+PagoEfectivo is part of paysafecard portfolio of cash-based payment methods.
+PagoEfectivo payment method can be initialized if the merchant sends PAGOEFECTIVO for parameter paymentType.
| + + | ++The parameter consumerMerchantCrmId is required by PagoEfectivo when initiating a payment. + | +
| + + | ++The parameter consumerMerchantCrmId is required by PagoEfectivo when initiating a payment. + | +
Optional request parameters customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed. Starting from this operation it’s possible to carry out different transaction-based operations.
+| + + | ++For the explanation of the different status descriptions included in this diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+Payolution (part of Unzer) offers invoice payments for the Austrian, German, and Swiss online markets. The currency used has to be EUR.
+The consumer must be older than 18 years of age, the billing address and the delivery address must be the same and the order amount must not be below or exceed the limits as contractually agreed with payolution. The delivery country must be accepted by payolution. Gift vouchers must be excluded and may not be purchased via invoice or installment.
+| + + | ++The title of this payment method to be displayed in the shop may be freely chosen during shop plugin configuration. Since payolution is a white label product it’s recommended to choose a neutral title such as "invoice". + | +
Payolution will communicate the required live data to merchants only after the final tests of the integration were successfully completed and the entire installation was found adequate.
+Required request parameters from consumer billing data table are: consumerBillingFirstname, consumerBillingLastname, consumerBillingAddress1, consumerBillingAddress2, consumerBillingCity, consumerBillingCountry, consumerBillingZipCode, consumerEmail and consumerBirthDate.
| + + | ++Payolution recommends sending consumer shipping data in addition. + | +
Optional request parameters customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+| Parameter | +Data type | +Descritpion | +
|---|---|---|
|
+Alphanumeric, of 1 to 100. |
+Name of company. |
+
If the parameter companyName is used, the parameter consumerBirthDate is not required anymore.
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Alphanumeric, of 0 to 50. |
+VAT ID of company. |
+
|
+Alphanumeric, of 0 to 50. |
+Trade registration number of company. |
+
|
+Alphanumeric, of 0 to 50. |
+Additional or alternative register key of company. |
+
companyVatId |
+|
|---|---|
Data |
+Value |
+
Data type |
+Alphanumeric, of 0 to 50. |
+
Description |
+VAT ID of company. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, of 0 to 50. |
+
Description |
+Trade registration number of company. |
+
|
+|
Data |
+Value |
+
Data type |
+Alphanumeric, of 0 to 50. |
+
Description |
+Additional or alternative register key of company. |
+
| Parameter | +State | +Data type | +Descritpion | +
|---|---|---|---|
|
+Success |
+Alphanumeric with special characters, up to 255. |
+Technical reference number of the payment processing at QENTA. |
+
|
+Success |
+Alphanumeric with special characters, up to 255. |
+Reference number of the invoice. |
+
gatewayReferenceNumber |
+|
|---|---|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric with special characters, up to 255. |
+
Description |
+Technical reference number of the payment processing at QENTA. |
+
|
+|
Data |
+Value |
+
State |
+Success |
+
Data type |
+Alphanumeric with special characters, up to 255. |
+
Description |
+Reference number of the invoice. |
+
For further information about backend operation refer to the backend.
+| + + | ++Split capture is possible only for invoices and it must be enabled by payolution and by our integration specialists. + | +
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed. Starting from this operation it’s possible to carry out different transaction-based operations.
+| + + | ++For the explanation of the different status descriptions included in this diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+Paypal is an online financial service that allows to pay for items using a secure internet account.
+PayPal transactions are by default set to be approved and deposited in one step, but it can be split it up into a two-step process. That allows distinguishing between approved and deposited payments and performing certain actions for each of them.
+To separate the transaction flow into authorization and capture, get in contact with the integration specialists. Look at the order flow diagram of the payment method for closer information.
+The new paypal integration offers 3 payment options:
+Paypal will be initiated over QENTA with a specific amount and the consumer enters his credentials for this One Time payment. The amount will be deposited automatically after QENTA received the result of PayPal. Recurring on this specific payment is not allowed.
+Paypal will be initiated over QENTA with a specific amount and the consumers enters his credentials for this payment. The amount will be deposited automatically after QENTA received the result of PayPal. Based on the QENTA Ordernumber, recurrings are allowed.
| + + | +
+To flag transactions for later recur the parameter transactionIdentifier must be set to INITIAL
+ |
+
Paypal will be initiated over QENTA with a Zero amount and the consumers enters his credentials for this payment. In this case, the consumer gives permission for follow-up operations like recurrings. No payment was made for the initial transaction. Based on the QENTA Ordernumber, recurrings are allowed.
| + + | +
+To flag transactions for later recur the parameter transactionIdentifier must be set to INITIAL
+ |
+
PayPal payment method can be initialized if the merchant sends PAYPAL for parameter paymentType.
| + + | ++Parameters of consumer billing data and shopping basket data are required for PayPal Seller Protection. + | +
| Parameter | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
|
+Required if used |
+Alphanumeric with special characters, up to 128 characters. |
+Unique ID of article n in the shopping basket. |
+
|
+Required if used |
+Alphanumeric with special characters, up to 128 characters. |
+Product description of article n in the shopping basket. |
+
basketItem(n)ArticleNumber |
+|
|---|---|
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric with special characters, up to 128 characters. |
+
Description |
+Unique ID of article n in the shopping basket. |
+
|
+|
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric with special characters, up to 128 characters. |
+
Description |
+Product description of article n in the shopping basket. |
+
| + + | ++State pending is only used if the parameter pendingUrl is set in combination with the parameter confirmUrl; otherwise, a failure will get instead of a pending state. + | +
Optional request parameters customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+basketItem to redeem VouchersIf the consumer in the online shop redeems a voucher or coupon during the payment process, the optional request parameterbasketItem must be used. This parameter must contain the negative amount corresponding to the voucher or coupon value. For vouchers with a percentage discount, the percentage to be deducted must first be converted into an absolute value. The total basket amount displayed to the consumer in the online shop will then show both the voucher amount and the total basket amount reduced by the voucher amount.
Although the shopping basket data parameters are in general optional, all parameters need to be set, except for basketItem(n)Description and basketItem(n)ImageUrl which remain optional and these two parameters are not part of the fingerprint.
If the parameter consumerShippingCountry is set, PayPal will display its own pages in the language of that country; otherwise, PayPal will use the language configured within the web browser of the consumer.
+| + + | ++If no shipping address is entered e.g. only digital goods are sold and there is no shipping then the respective parameter is NOSHIPPING=1. To prevent the consumer in the online shop from editing the shipping address then the respective parameter is ADDROVERRIDE=1. + | +
Contact our integration specialists team for changes in a merchant configuration.
+| Color | +Shape Pill | +Shape Rectangular | +
|---|---|---|
Gold |
+
+
+
+
+ |
+
+
+
+
+ |
+
Blue |
+
+
+
+
+ |
+
+
+
+
+ |
+
Silver |
+
+
+
+
+ |
+
+
+
+
+ |
+
White |
+
+
+
+
+ |
+
+
+
+
+ |
+
Black |
+
+
+
+
+ |
+
+
+
+
+ |
+
| + + | ++The design in the first row is the default one, contact our integration specialists team for change. + | +
+| + + | ++Contact our integration specialists team to enable this workflow. + | +
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed. Starting from the operation it’s possible to carry out different transaction-based operations.
+| + + | ++For the explanation of the different status descriptions included in this diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+Paypal is an online financial service that allows paying for items using a secure internet account.
+| + + | +
+Store the PayPal TRANSACTIONID of the payment as returned by the parameter gatewayReferenceNumber within the data regarding the corresponding session and order for documentation purposes.
+ |
+
PayPal transactions are by default set to be approved and deposited in one step, but it can be split it up into a two-step process. That allows distinguishing between approved and deposited payments and performing certain actions for each of them.
+To separate the transaction flow into authorization and capture, get in contact with the integration specialists. Look at the order flow diagram of the payment method for closer information.
+To enable the integration of PayPal into the online shop in our QENTA Checkout solutions some third-party permissions have to be added to the PayPal Business Account for accessing PayPal-related payment information. Follow the required setup steps described in 3rd party permissions.
+PayPal payment method can be initialized if the merchant sends PAYPAL for parameter paymentType.
| + + | ++Parameters of consumer billing data and shopping basket data are required for PayPal Seller Protection. + | +
| Parameter | +Within fingerprint | +Data type | +Description | +
|---|---|---|---|
|
+Required if used |
+Alphanumeric with special characters, up to 128 characters. |
+Unique ID of article n in the shopping basket. |
+
|
+Required if used |
+Alphanumeric with special characters, up to 128 characters. |
+Product description of article n in the shopping basket. |
+
basketItem(n)ArticleNumber |
+|
|---|---|
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric with special characters, up to 128 characters. |
+
Description |
+Unique ID of article n in the shopping basket. |
+
|
+|
Data |
+Value |
+
Within fingerprint |
+Required if used |
+
Data type |
+Alphanumeric with special characters, up to 128 characters. |
+
Description |
+Product description of article n in the shopping basket. |
+
| + + | ++State pending is only used if the parameter pendingUrl is set in combination with the parameter confirmUrl; otherwise, a failure will be obtained instead of a pending state. + | +
Optional request parameters customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+basketItem to redeem VouchersIf the consumer in the online shop redeems a voucher or coupon during the payment process, the optional request parameterbasketItem must be used. This parameter must contain the negative amount corresponding to the voucher or coupon value. For vouchers with a percentage discount, the percentage to be deducted must first be converted into an absolute value. The total basket amount displayed to the consumer in the online shop will then show both the voucher amount and the total basket amount reduced by the voucher amount.
| + + | ++The additional parameters will be returned. + | +
The optional request parameter consumerDeviceId is required by PayPal for on-demand payments initiated by the consumer in the online shop.
| Parameter | +Data type | +Description | +
|---|---|---|
|
+Alphanumeric with special characters, up to 32 characters. |
+Unique token which serves as a method of fraud protection. |
+
| + + | +
+consumerDeviceId is not part of the fingerprint.
+ |
+
Although the shopping basket data parameters are in general optional, all parameters need to be set, except for basketItem(n)Description and basketItem(n)ImageUrl which remain optional and these two parameters are not part of the fingerprint.
| + + | +
+To be marked as a transaction that will recur later, the parameter transactionIdentifier must be set to INITIAL.
+ |
+
For using the backend operation recurPayment a request approval is needed, so contact PayPal Customer Support or the PayPal account representative. After receiving approval from PayPal, contact our integration specialists to enable this feature.
+If the parameter consumerShippingCountry is set, PayPal will display its own pages in the language of that country; otherwise, PayPal will use the language configured within the web browser of the consumer.
| + + | ++If no shipping address is entered e.g. only digital goods are sold and there is no shipping then the respective parameter is NOSHIPPING=1. To prevent the consumer in the online shop from editing the shipping address then the respective parameter is ADDROVERRIDE=1. + | +
Contact our integration specialists team for changes in a merchant configuration.
+
+| + + | ++Contact our integration specialists team to enable this workflow. + | +
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed. Starting from the operation it’s possible to carry out different transaction-based operations.
+| + + | ++For the explanation of the different status descriptions included in this diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+Paysafecard is a payment method for mainly online shopping. When using my paysafecard during the payment process in an online shop, there is no need to enter the PIN again, only a username and password are required.
When paying with paysafecard, the consumer enters the 16 digit number and the amount tendered is deducted from the paysafecard balance. Combining PINs allows consumers to use up any remaining credit on a paysafecard PIN. The current balance of each paysafecard as well as its transaction history and production date can be viewed at the official paysafecard site by entering the respective 16 PIN code.
+| + + | ++Payments for goods or services other than Euros are converted into Euros at the conversion rate at the time of purchase. + | +
Paysafecard payment method can be initialized if the merchant sends PSC for parameter paymentType.
| + + | ++The parameter consumerMerchantCrmId is required by paysafecard when initiating a payment. + | +
| + + | ++The parameter consumerMerchantCrmId is required by paysafecard when initiating a payment. + | +
Optional request parameters customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed. Starting from this operation it’s possible to carry out different transaction-based operations.
+| + + | ++For the explanation of the different status descriptions included in this diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+To activate Sofort following steps should be performed:
+Here is a link for the completion of the registration.
+New project > Gateway project > Create project to generate a project after the registration process is completed.
+
+The Shop system field is mandatory and QENTA should be chosen.
+
+The fields should be left free in Setting for all payment methods, and the Automatic redirection should be checked.
+
+Specify the following values for the connection via QENTA Payment CEE:
+| + + | ++Fields marked with an asterisk (*) are mandatory and must be filled in. + | +
Enable Sofort as the preferred payment method.
+Tick the test mode box to test the shop.
+
+To activate Sofort the following information are needed:
+Customer number
+Project ID
+API key
+Configuration key
+These credentials are findable in PROJECTS > my Projects.
+| + + | ++These data should be forwarded to our integration specialists. + | +
+Riverty supports consumers in purchasing the items they desire by providing them with the freedom to pay whenever and however they find it most convenient. This is achieved by separating the checkout and the post-purchase experience.
+Shoppers who choose Riverty’s invoice are subject to predefined payment terms to pay the invoice and shall pay the full purchase amount on the invoice due date. The due date is always calculated based on the dispatch date of the goods, not the purchase date.
+The most common terms of payment are within 14 days after the purchase, which gives shoppers enough time to experience the goods before paying. The full purchase amount is to be paid by the due date.
+Through its partial payment option, Riverty allows shoppers to pay a particular purchase over time, enabling them to make higher-order value purchases while limiting their monthly spending.
+Riverty offers fixed installment plans with predefined maturities of 3, 6, 12, or 24 months. The Payment API determines which of these installment plans can be offered. The monthly amount to be paid in a fixed installment plan is the same during the entire plan.
+Riverty payment method can be initialized if the merchant sends AFTERPAY for parameter paymentType.
Init form example:
+<form action='https://api.qenta.com/page/init.php' method='post' name='checkout' target='_self'>
+ <input type='hidden' name='customerId' value='D200001' />
+ <input type='hidden' name='language' value='en' />
+ <input type='hidden' name='paymentType' value='AFTERPAY' />
+ <input type='hidden' name='amount' value='300.00' />
+ <input type='hidden' name='currency' value='EUR' />
+ <input type='hidden' name='orderDescription' value='Order 12345 6789 0' />
+ <input type='hidden' name='successUrl' value='https://your-online-shop.com/return.php' />
+ <input type='hidden' name='cancelUrl' value='https://your-online-shop.com/return.php' />
+ <input type='hidden' name='failureUrl' value='https://your-online-shop.com/return.php' />
+ <input type='hidden' name='pendingUrl' value='https://your-online-shop.com/return.php' />
+ <input type='hidden' name='confirmUrl' value='https://your-online-shop.com/confirm.php' />
+ <input type='hidden' name='serviceUrl' value='https://your-online-shop.com/service.html' />
+ <input type='hidden' name='requestFingerprintOrder' value='customerId,language,amount,currency,orderDescription,paymentType,successUrl, ….. requestFingerprintOrder,secret' />
+ <input type='hidden' name='requestFingerprint' value='…' />
+ <input type='hidden' name='consumerBillingFirstname' value='John' />
+ <input type='hidden' name='consumerBillingLastname' value='Doe' />
+ <input type='hidden' name='consumerEmail' value='email@email.com' />
+ <input type='hidden' name='consumerBillingAddress1' value='Reininghausstraße 10' />
+ <input type='hidden' name='consumerBillingZipCode' value='8020' />
+ <input type='hidden' name='consumerBillingCity' value='Graz' />
+ <input type='hidden' name='consumerBillingCountry' value='AT' />
+ <input type='hidden' name='basketItem(1)ArticleNumber' value='0001' />
+ <input type='hidden' name='basketItem(1)Description' value='item 1 description' />
+ <input type='hidden' name='basketItem(1)Quantity' value='5' />
+ <input type='hidden' name='basketItem(1)UnitGrossAmount' value='12.00' />
+ <input type='hidden' name='basketItem(1)UnitNetAmount' value='10.00' />
+ <input type='hidden' name='basketItem(1)UnitTaxAmount' value='2.00' />
+ <input type='hidden' name='basketItem(n)UnitTaxRate' value='20.00' />
+ <input type='submit' name='submit' value='Start Checkout'>
+</form>When the customer on session chooses to take invoice or installment by Riverty, an authorization request has to be sent to QENTA Checkout Server with the necessary customer and basket details.
+After completing the payment process, consumers are redirected to the online shop and receive relevant information on the result or state of the payment which is sent to the respective successUrl, cancelUrl, failureUrl or pendingUrl.
| + + | ++The otherwise optional request parameters for consumer billing data are required. + | +
In addition to these optional request parameters, also is recommended to send Riverty consumer shipping data containing detailed information regarding consumers.
+| + + | +
+Optional request parameter financialInstitution is required for QMORE Checkout Seamless.
+ |
+
Optional request parameters customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+For further information about backend operation refer to the backend.
+
+| + + | ++Contact our integration specialists team to enable this workflow. + | +
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed. Starting from this operation it’s possible to carry out different transaction-based operations.
+| + + | ++For the explanation of the different status descriptions included in the diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+Safetypay is part of paysafecard portfolio of cash-based payment methods.
+Safetypay payment method can be initialized if the merchant sends SAFETYPAY for parameter paymentType.
| + + | ++The parameter consumerMerchantCrmId is required by Safetypay when initiating a payment. + | +
| + + | ++The parameter consumerMerchantCrmId is required by Safetypay when initiating a payment. + | +
Optional request parameters customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed. Starting from this operation it’s possible to carry out different transaction-based operations.
+| + + | ++For the explanation of the different status descriptions included in this diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+SEPA Direct Debit is based on the following concept: both debtor and creditor must hold an account with a financial service provider located within the SEPA area. The transfer of money between the debtor’s bank and the creditor’s bank always takes place in Euro.
+Cashless transactions will be made and received in and between the SEPA member countries regardless of their location. Existing sorting codes and account numbers will be replaced by an International Bank Account Number (IBAN) and a Bank Identifier Code (BIC).
+If b4payment is the chosen acquirer, the parameter consumerMerchantCrmId must be added.
+If b4payment is the chosen acquirer, the parameter consumerMerchantCrmId must be added.
+Hobex draws the direct debits from the debtor’s bank to one joint account, so no individual creditor IDs are available and any value within the request parameter creditorId will be ignored.
| + + | ++Hobex is only available for customers in Germany, Austria or the Netherlands. + | +
SEPA payment method can be initialized if the merchant sends SEPA-DD for parameter paymentType.
Additional optional request parameters for Sepa are mandateId and mandateSignatureDue.
After successful payments some additional response parameters are returned.
+Optional request parameters customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+For further information about backend operation refer to the backend.
+
+| + + | ++Contact our integration specialists team to enable this workflow. + | +
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed. Starting from this operation it’s possible to carry out different transaction-based operations.
+| + + | ++For the explanation of the different status descriptions included in this diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+Third-party permission to the PayPal Business Account for accessing PayPal-related payment information is needed for integrating PayPal into an online shop.
+| + + | ++The recommendation is to set the browser language to English to display all available permissions. + | +
If the PayPal account doesn’t already exist, then PayPal Business Account needs to be registered at PayPal.
+The steps from the PayPal documentation Grant a third-party permissions should be followed and office_api1.qenta.at used as the username.
The following types of permissions should be selected on the Add New Third Party Permissions page:
+Use Express Checkout to process payments.
+Issue a refund for a specific transaction.
+Authorize and capture the PayPal transactions.
+Obtain information about a single transaction.
+Charge an existing customer based on a prior transaction.
+Create and manage Recurring Payments.
+Use Express Checkout to process mobile payments.
+
+The PayPal registration e-mail address should be sent to our integration specialists.
+Sofort is a payment method that arranges transactions between the online shop and the customer’s banking account. After selection, all transfer data will be handed over automatically so the consumer only needs to log into the bank account using the account number, PIN and to authorize the transaction, so the information will be send to the bank in encrypted form.
+To integrate and offer the payment method Sofort to the consumers in the online shop some requirements needed to be fulfilled:
+Registering and setting up an account for Sofort.
+Use the specific response parameters as defined below in the payment process of the online shop.
+Visual present of the online shop branding guidlines.
+Sofort payment method can be initialized if the merchant sends SOFORTUEBERWEISUNG for parameter paymentType.
Optional request parameters customerStatement and orderReference are more restricted about their length and allowed characters than usual.
+The QPAY Checkout Page will return additional parameters to the online shop.
+The backend operation recurPayment is only possible via payment method SEPA Direct Debit, i.e. support SEPA Direct Debit is must to do recurring payments for Sofort.
+The text displayed on the account statement is composed of orderReference and customerStatement
[orderReference] [customerStatement]+
[orderReference] +[customerStatement]+
customerStatement is not set[orderReference] Order [orderNumber]+
orderReference is not set[orderNumber] [customerStatement]+
[orderNumber] Order [orderNumber]+
| + + | ++Be aware that for SEPA each line of text must not exceed 35 characters. + | +
+To interpret this diagram, the successful completion of a NEW PAYMENT is assumed. Starting from this operation it’s possible to carry out the transaction based operation recurPayment. SEPA Direct Debit has to be supported for recurring payments for Sofort.
+| + + | ++For the explanation of the different status descriptions included in this diagram have a look at getOrderDetails. + | +
All possible states of transaction for all specific acquirers can be found here.
+Our solutions can be integrated by downloading, installing and configuring a plugin, which is a software component tailored for the specific shop system, adding QPAY Checkout Page.
+| Shop System | +QPAY Checkout Page | +
|---|---|
WooCommerce (WordPress) |
++ |
Magento 2 |
++ |
OpenMage |
++ |
OpenCart |
++ |
Oxid 4 |
++ |
PrestaShop |
++ |
Shopware 5 |
++ |
Virtuemart 3 |
++ |
| + + | ++Development for Checkout Seamless Plugins was discontinued but can be still found here. + | +
For detailed technical information use the detailed descriptions of the parameters that are used for communication between the shop and QENTA Checkout.
+| + + | ++Since plugins are open source third-party developers may also provide integration possibilities but QENTA can’t offer any support regarding that integration. + | +
By installing the plugin into the shop system the customer agrees to these terms of use and uninstalling the plugin may result in the loss of data.
+Operation in an enhanced, customized configuration is at the own risk and QENTA Payment CEE does not provide any guarantee or accept any liability for any errors, so a comprehensive test phase by the user of the plugin is required.
+No warranty can be granted on any alterations and/or new implementations as well as resulting diverging usage not supported or described here.
+QENTA Payment CEE will only be made liable for specifications and functions that are described here.
+The installation guide shows the step-by-step installation of the plugin to an installed shop system on a web server. Test the online shop and the plugin’s configuration on a test system before installing the plugin on a production system.
+To install the plugin via the zip file, upload the file containing the QPAY Checkout Page plugin to the document root of Magento installation and unzip it. The zip archive already contains the directory path allowing the plugin to be stored automatically in the right folder.
+To unzip the file on a computer and then upload the plugin, maintain the directory structure which already exists in the zip file.
+| + + | ++To receive a notification when a new version is published, subscribe here and select Releases only. + | +
Navigate to System > Configuration > QENTA Checkout Page (on the left side).
+For a basic configuration enter customer ID, shop ID, and secret and set the URL to imprint page. Go over the settings and configure the plugin according to the requirements. Refer to the section advanced configuration for a more detailed description of the configuration possibilities.
+As described in Step 2 the plugin allows for some additional customization.
+Demo: Demo mode configuration. No communication with the financial service provider but only between the online shop and the QENTA Checkout Server.
+Test: During test mode, there is communication between the online shop and a test bank or demo bank provided for this purpose by the relevant financial service provider. However, the payment process is only simulated and no money is transferred.
+Production: Make sure all of the tests were properly executed before switching to Production mode.
+Automated deposit: To prevent the expiration of uncaptured payments, select the feature that enables an automated deposit and day-end closing of payments. Contact our sales teams to enable it; otherwise, an error message will be shown.
+Payment method sort order: The payments can be sorted in the order of the "Payment method sort order" and the payment with the smallest number entered in this field will be displayed first. Sort the payment methods according to which ones are mostly used by consumers.
+If this feature is enabled the plugin automatically identifies the consumer device. If a mobile device is identified, the corresponding request parameter layout is automatically set to the value tablet or smartphone and QPAY Checkout Page is optimized for the corresponding mobile device.
+| + + | ++Parameter layout is only relevant if the responsive design of QPAY Checkout Page is NOT used. For more information contact our integration specialists. + | +
For using payment methods "invoice" or "installment" the input field "date of birth" must be enabled in the Magento configuration. +Go to Stores > Configuration > Customers > Customer Configuration > Name and Address Options, and set Show Date of Birth to Required.
+"Invoice" or "installment" is only visible if the criteria defined in the contract concluded with the relevant financial Institution (e.g. payolution) are met. For more information, check the payment method-specific documentation for the invoice/installment provider:
+payolution: Invoice and Installment
+The field to enter the Company Trade Registration Number, which applies to B2B consumers, only appears if the consumer has also filled in the field Company Name.
+The installation guide shows the step-by-step installation of the plugin to the installed shop system on a web server. Test the online shop and the plugin’s configuration on a test system before installing the plugin on a production system.
+The installation needs to be done in the command line. Download the plugin via composer.
+composer require qenta/magento2-qcpThe plugin can be installed via command line:
+Command line
+php bin/magento setup:upgrade +php bin/magento setup:di:compile +php bin/magento setup:static-content:deploy +php bin/magento cache:clean+
Magento 2 Setup Wizard
+Navigate to System > Web Setup Wizard > Component Manager.
+chown -R www-data:www-data .+
| + + | ++To receive a notification when a new version is published, subscribe here and select Releases only. + | +
Navigate to Stores > Configuration > Sales > QENTA Checkout Page.
+For a basic configuration enter customer ID, shop ID, and secret and set the URL to imprint page. Go over the settings and configure the plugin according to the requirements. Refer to the section advanced configuration for a more detailed description of the configuration possibilities.
+As described in Step 2 the plugin allows for some additional customization.
+Demo: Demo mode configuration. No communication with the financial service provider but only between the online shop and the QENTA Checkout Server.
+Test: During test mode, there is communication between the online shop and a test bank or demo bank provided for this purpose by the relevant financial service provider. However, the payment process is only simulated and no money is transferred.
+Production: Make sure all of the tests were properly executed before switching to Production mode.
+Automated deposit: To prevent the expiration of uncaptured payments, select the feature that enables an automated deposit and day-end closing of payments. Contact our sales teams to enable it; otherwise, an error message will be shown.
+Payment method sort order: The payments can be sorted in the order of the "Payment method sort order" and the payment with the smallest number entered in this field will be displayed first. Sort the payment methods according to which ones are mostly used by consumers.
+If this feature is enabled the plugin automatically identifies the consumer device (either desktop, smartphone, or tablet). If a mobile device is identified, the corresponding request parameter layout is automatically set to the value tablet or smartphone, and QENTA Checkout Page is optimized for the corresponding mobile device.
+To improve usability for smartphones and tablets, the plugin automatically disables the embedding in an iframe on tablets and smartphones and redirects the consumer to QENTA Checkout Page. After the payment process is completed, a consumer is redirected to an online shop.
+For using payment methods "invoice" or "installment" the input field "date of birth" must be enabled in the Magento configuration. +Go to Stores > Configuration > Customers > Customer Configuration > Name and Address Options, and set Show Date of Birth to Required.
+"Invoice" or "installment" is only visible if the criteria defined in the contract concluded with the relevant financial Institution (e.g. payolution) are met. For more information, check the payment method-specific documentation for the invoice/installment provider:
+payolution: Invoice and Installment
+| + + | +
+Order with obligation to pay is not translated because the text is cached. Delete the file pub/static/frontend/Magento/luma/[YOUR_LANGUAGE]/js-translation.js. For example, German [YOUR_LANGUAGE] would be de_DE.
+ |
+
The installation guide shows the step-by-step installation of the plugin to the installed shop system on a web server. Test the online shop and the plugin’s configuration on a test system before installing the plugin on a production system.
+Log in as Administrator to the administration section (https://put.your-shop-address.here/admin) of OpenCart.
Select Extensions > Installer in the navigation menu on the left. Upload the zip package.
+
+| + + | ++To receive a notification when a new version is published, subscribe here and select Releases only. + | +
Select Extensions > Payments within the menu. All QENTA related payment methods begin with the name "QENTA" and are followed by the name of the payment method. Click on the plus [ + ] symbol to activate the plugin.
+
+To present a specific payment method to consumers in the online shop have to enable and configure that payment method.
+Click on the pencil [ ✎ ] symbol to configure and enable the plugin in the shop.
+
+| Enable | +Enables or disables a corresponding payment method. | +
|---|---|
Customer ID |
+Customer ID that is received from QENTA. |
+
Secret |
+Secret also received from QENTA. |
+
Success Status |
+Status for a successfully completed payment of the consumer. |
+
Failure Status |
+Status for a failed payment of the consumer. |
+
Cancel Status |
+Status for a payment canceled by the consumer. |
+
Auto Deposit |
+Activating or deactivating the automated deposit immediately after the successful payment of the consumer. (Has to be enabled by QENTA for Customer ID). |
+
Duplicate Request Check |
+Enables or disables checking if the same order has been unintentionally sent more than once by the consumer. This is useful to prevent the processing of the same order more than once, especially if the consumer presses the Reload button of the web browser. |
+
Max Retries |
+Defines the maximum number of retries the consumer can do within one payment. A value of |
+
Iframe |
+If enabled the QPAY Checkout Page will be displayed within an iframe in the online shop. Otherwise, it will be displayed within the current window of the web browser of the consumer. |
+
Send Customer Information |
+Enables or disables the sending of customer data. |
+
Shop ID |
+Contains the unique identifier for the shop within the QPAY Checkout Page. (Has to be enabled by QENTA for this Customer ID). |
+
Background Color |
+The background color of the QPAY Checkout Page, as hexadecimal RGB-values like |
+
Logo Url |
+Optional URL to an image that is used as an online shop logo within the QPAY Checkout Page. |
+
Display Text |
+Optional text that is displayed together with the data of the order. |
+
Confirm e-Mail Address |
+Contains an e-mail address of the merchant for receiving payment information details regarding the orders of the consumers of an online shop. (Has to be enabled by QENTA for Customer ID). |
+
Customer Statement |
+Contains a text which will be displayed on the invoice of the financial institution of the consumer. |
+
Entered all the values in the form and click the Save button.
+| + + | ++The different order-status have to be configured as shown in the screenshot. + | +
+The status of the payment method is now active and the payment method is available in the ordering process of the online shop.
+To test configuration use the test mode data.
+The installation guide shows the step-by-step installation of the plugin to the installed shop system on a web server. Test the online shop and the plugin’s configuration on a test system before installing the plugin on a production system.
+Upload the zip file containing the QPAY Checkout Page plugin to the document root of the OXID Shop installation and unzip the file. The zip archive already contains the directory path allowing the plugin to be stored automatically in the right folder.
+To first unzip the file on a computer and then upload the plugin, maintain the directory structure which already exists in the zip file.
+To enable the module, navigate to Extensions > Modules, select QPAY Checkout Page and click on Activate.
+
+| + + | ++To receive a notification when a new version is published, subscribe here and select Releases only. + | +
For a basic configuration enter customer ID, shop ID, and secret and set the URL to imprint page. Go over the settings and configure the plugin according to the requirements. Refer to the section advanced configuration for a more detailed description of the configuration possibilities.
+
+To enable the payment methods navigate to Shop Settings > Payment Methods.
+To activate payment methods so they are available to the consumers, click on the payment method, select Active and then Save button.
+| + |
| + |
Maestro SecureCode |
+
| + |
| + |
| + |
| + |
| + |
| + |
| + |
+Select Assign User Groups in the Main tab and Assign Countries in the Country tab that allow specific payment methods for specific user groups and countries.
+
+Additionally, the payment methods need to be assigned to shipping methods at Shop Settings > Shipping Methods. Select each shipping method, switch to the tab Payment, click Assign Payment Methods and assign those that will be available when the consumer selects the respective shipping method.
+
+As described in Step 2 the plugin allows for some additional customization.
+Demo: Demo mode configuration. No communication with the financial service provider but only between the online shop and the QENTA Checkout Server.
+Test: During test mode, there is communication between the online shop and a test bank or demo bank provided for this purpose by the relevant financial service provider. However, the payment process is only simulated and no money is transferred.
+Production: Make sure all of the tests were properly executed before switching to Production mode.
+Automated deposit: To prevent the expiration of uncaptured payments may select this feature which enables an automated deposit and day-end closing of payments. Contact our sales teams to enable it, otherwise, an error message will be shown.
+Payment method sort order: The payments can be sorted in the order of the "Payment method sort order" and the payment with the smallest number entered in this field will be displayed first. Sort the payment methods according to which ones are mostly used by consumers.
+Folder for orders: For each state of the payment a folder can be selected, for an order that should be stored.
+Iframe settings: It’s possible to differentiate how QPAY Checkout Page is displayed in the online shop. Per default, QPAY Checkout Page will be displayed in an iframe within the online shop. Disable the use of an iframe for each payment method. When disabled, the consumer will be redirected to QPAY Checkout Page and the online shop will momentarily not be visible. For more information refer to Integration Possibilities for Desktop Devices.
+| + + | ++OXID eShop Enterprise and Professional editions run only properly within Zend Guard Loader (former Zend Optimizer) but is not needed for the Community edition. + | +
The installation guide shows the step-by-step installation of the plugin to the installed shop system on a web server. Test the online shop and the plugin’s configuration on a test system before installing the plugin on a production system.
+Upload the zip package to PrestaShop (Modules > Module Manager > Upload a module), and the module will be installed.
+
+| + + | ++To receive a notification when a new version is published, subscribe here and select Releases only. + | +
Configure the plugin right after installation or go to Modules > Module Manager > QENTA Checkout Page > Configure and change the settings according to the requirements.
+
+
+If the minimum and maximum amounts for invoice and installment are set, then these payment methods will only be shown if the order is between these limits.
+
+To use a new currency perform two steps:
+Define currency: On the PrestaShop admin site, go to International > Localization > Currencies.
+
+Activate currency: On the PrestaShop admin site, go to Modules > Payment > Preferences > Currency Restrictions.
+Enable the checkbox for QENTA Checkout Page.
+
+| + + | ++For debugging purposes search the log files on the PrestaShop admin site > Advanced Parameters > Logs. + | +
Before installing the shop plugin install the Cron plugin, which is delivered together with the shop as standard, for shops in version 4.3.x.
+The installation guide shows the step-by-step installation of the plugin to the installed shop system on a web server. Test the online shop and the plugin’s configuration on a test system before installing the plugin on a production system.
+| + + | ++Don’t install the plugin from two sources at the same time. + | +
Log in to the administration section of the online shop. Select Configuration > Plugin Manager.
+Upload the zip file provided by QENTA. After uploading, the online shop will inform that the plugin has been successfully uploaded. The plugin is now displayed in the list of inactive Plugins.
+
+
+| + + | ++To receive a notification when a new version is published, subscribe here and select Releases only. + | +
Click on the green (+) icon to install the plugin to the online shop.
+
+In order to guarantee the proper operation of the plugin, it’s necessary to clear the Shopware cache and recompile the Shopware theme. Therefore confirm the following two dialog windows.
+
+Click "Activate" to activate the plugin and the plugin will be displayed in the list of active Plugins.
+
+| Customer ID | +customerId received from QENTA. |
+
|---|---|
Shop ID |
+Unique identifier for the shop. Has to be enabled by QENTA for this |
+
Secret |
+The secret that is also received from QENTA. |
+
Service Url |
+URL which leads to the imprint of the shop, this field is mandatory. |
+
Restore basket |
+If enabled, the original content of the shopping basket is restored if the consumer changed the basket during the payment process. If disabled, the order is not executed and is set to a clarification state. |
+
Confirmation mail |
+E-mail address of the merchant for receiving payment information details regarding the orders placed by the consumers in an online shop. Has to be enabled by QENTA for the |
+
Use auto-deposit |
+Activating or deactivating the automated deposit immediately after a successful payment was made by the consumer. Has to be enabled by QENTA for |
+
Max. retries |
+A maximum number of retry attempts during payment. |
+
Send additional data |
+Sending additional data regarding consumer data ( |
+
Use iframe |
+If enabled, QPAY Checkout Page is displayed within an iframe in an online shop. If disabled, QPAY Checkout Page is displayed in the current web browser window during the payment process. After the consumer finished the payment process a redirection to the online shop is performed automatically. Be aware that XHTML strict mode does not support iframes. |
+
Save QENTA response |
+The response of QENTA contains detailed information regarding the transaction. May store these data in an internal field that is not visible to the consumer. |
+
Logging |
+Enable logging for debugging . The log data are written to log files within the ”/ |
+
Delete log-file after x days |
+Count of days until log files are deleted. |
+
Shopware transaction ID |
+The |
+
Display text |
+Optional text is displayed together with the data of the order. |
+
Select Configuration > Shipping and in the window Shipping costs management one type of shipping for editing. A new window named Shipping costs opens. Select the Payments tab. Move required payment methods from the left list named Available to the right list named Selected by selecting the payment method and pressing the → button. Click the Save button and close this dialog.
+
+On the main menu select Configuration > Payment methods to activate the new payment methods. Select one payment method in the left list named Available payments and on the General tab check the Active checkbox.
+
+Optionally, it’s possible to modify the description of the payment method and this text is visible to the consumer during the payment process. Additionally, surcharges and discounts can be set per payment method. Within the Position field the sort order of the payment methods presented during the payment process in an online shop can change. After configuring the selected payment method, click the Save button and proceed with the next payment method.
+| + |
| + |
Maestro SecureCode |
+
| + |
| + |
| + |
| + |
| + |
| + |
| + |
Select Configuration > Shipping costs.
+Select one type of shipping in the window Shipping costs management for editing. A new window named Shipping costs opens.
+
+For implementation details of this plugin consult the inline documentation of the provided source code.
+The source of the plugin is structured into the following folders and files:
+The Bootstrap.php file is the starting file containing all configurations, hooks and events.
/Components contains the QENTA Library and the Zend framework. The files are automatically included via Loader.php.
/Controller manages the control flow between the QENTA Library, the models and the views. Each method ending with the suffix Action within the PaymentQENTACEE.php file can be directly called by a proper URL (e.g. https://www.yourserver.com/PaymentQENTACEE/saveOrder). Especially the confirmation of a successful payment can be done within the URL https://www.yourserver.com/PaymentQENTACEE/confirm. Be aware that this URL has to be reachable over the Internet either on port 80 for http or port 443 for https.
/Models manages the data, processing, resources, logs and the basket. Especially the method Config::getPaymentMethods() is used for configuring the different payment methods.
/View contains templates, HTML, JavaScript and style sheets for the plugin.
| + + | +
+Text resources can be customized and translated. Example files are available within the zip file at QENTACheckoutPage/assets/lang/<language>.php.
+ |
+
Information about the payment method that customer used can be retrieved for a transaction after the plugin has been deleted/uninstalled. After deleting or uninstalling the plugin, the payment method used for a transaction is not displayed anymore in the field Payment method and only an ID is shown instead (go to the administration section of the online shop, select Customers > Orders > Show details > Details).
+To be able to still retrieve information on the used payment method, on the Configuration tab select Plugin Manager. Click Installed, select QPAY Checkout Page, click Open and select Internal commentfield as value for Save QENTA response.
+The payment method used by the consumer is then displayed in the Customers tab. Select Orders > Show details > Communication to see the payment method.
+The installation guide shows the step-by-step installation of the plugin to the installed shop system on a web server. Test the online shop and the plugin’s configuration on a test system before installing the plugin on a production system.
+Select in the menu Extensions > Manage > Install.
+
+Upload the zip file containing the QPAY Checkout Page plugin, using Joomla! extension manager, or install it from the local file system of the web server.
+
+| + + | ++To receive a notification when a new version is published, subscribe here and select Releases only. + | +
Activate the plugin, then select Extensions > Plugins, search for the plugin and click on the status image and enable it.
+
+Add the new payment method to VirtueMart. Select in the menu VirtueMart > Payment Methods and click on QENTA Checkout Page.
+
+After pressing the Save button, configure the payment method. All required fields are marked with a *.
+
+After the installation is finished the field birthday may be missing in Shopper Fields. This field is mandatory for the payment methods Invoice and Installment.
+If it’s missing, go to VirtueMart > Configuration, select the Shopper Fields on the left and add this field.
+To remove the Main Menu and the Login Form boxes on the front end of the online shop, navigate to Extensions > Modules and disable the two extensions.
+| + + | ++The option "Keep orders despite of failed payment" is not available for VirtueMart version >= 3.0.10 due to the new ACL system. + | +
Invoice and installment are only visible if the criteria defined in the contract concluded with the financial institution (e.g. payolution) are met. For more information check the payment method-specific documentation for invoice/installment provider payolution: Invoice and Installment.
+The installation guide shows the step-by-step installation of the plugin to the installed shop system on a web server. Test the online shop and the plugin’s configuration on a test system before installing the plugin on a production system.
+Upload the zip file containing the QPAY Checkout Page plugin, using the Plugin management function of WordPress, or upload it directly to the wp-content/plugins directory of the WordPress installation.
+
+After installation, the plugin has to be activated, otherwise, it will not be available in WooCommerce.
+
+| + + | ++To receive a notification when a new version is published, subscribe here and select Releases only. + | +
Set the customer ID, shop ID, and secret in the access data. It’s also important to set the URL to contact page e.g. the URL to imprint!
+| + + | ++Credentials inside fields are ignored if test 3D or demo configuration is chosen. + | +
+It’s safe to deactivate or delete the plugin and then install it again because all the data will stay.
+
+
+Verify that the QPAY Checkout Page payment method is displayed on the checkout page.
+| + |
| + |
| + |
| + |
| + |
| + |
| + |
| + |
| + |
Invoice and installment are only visible if the criteria defined in a contract concluded with the financial institution (e.g. payolution) are met. For more information check the payment method-specific documentation for invoice/installment provider payolution: Invoice and Installment.
+Auf dieser Seite erhalten alle relevanten Informationen rund um das Thema Verarbeitung personenbezogener Daten durch Produkte der QENTA Payment CEE.
+| + + | ++Following information in English: Switch to English. + | +
Im Rahmen der Zahlungsabwicklung und abhängig vom jeweiligen Produkt werden von verschiedenen Stellen (z.B. Merchants, Endkunden) sowohl bestimmte Daten an QENTA Payment CEE übermittelt (Input-Daten), wie auch QENTA wiederum bestimmte Daten an diese Stellen zurück übermittelt (Output-Daten).
+QENTA Payment CEE erhält Daten von drei verschiedenen Stellen:
+Daten, die vom Zahlungsauslösenden je Produkt eingegeben werden (z.B. Dateneingaben des Endkunden im Zahlungsfenster)
+Daten, die vom Merchant an die QENTA Zahlungsschnittstelle gesendet werden (Request-Parameter)
+Plugin-spezifische Daten des Online-Shops
+Nachfolgend ist über Detailansichten zu einzelnen Produkten ersichtlich, welche Daten von welchem Produkt (inklusive Zahlungsmittel und/oder Zusatzfeatures) als Input- und Output-Daten verarbeitet werden. Sämtliche der darin angezeigten Parameter müssen verarbeitet werden, um den Vertragsgegenstand gegenüber dem Merchant erbringen zu können (Zweck der Datenverarbeitung):
+QPAY Checkout Page: Datenschutzhinweise QPAY
+QMORE Checkout Seamless: Datenschutzhinweise QMORE
+QFILE Checkout Automated: Datenschutzhinweise QFILE
+QCALL Checkout Terminal: Datenschutzhinweise QCALL
+Für die Erfüllung des Vertragsgegenstands bzw für die Abwicklung einer Zahlungstransaktion müssen eine Vielzahl an Daten (Parametern) sowohl vom Merchant oder dem Endkunden an die QENTA Zahlungsschnittstelle übermittelt werden (sog. Input-Daten), also auch wieder von QENTA an diese zurück gesendert werden (sog. Output-Daten).
+Für all jene Parameter, die ein personenbezogenes Datum darstellen und im Rahmen dieser Zahlungsabwicklung verarbeitet werden, wird auf nachfolgender Seite angegeben, worin der Personenbezug besteht, wer die betroffene Person ist, um welche Datenkategorie es sich handelt und worin der Zweck der Datenverarbeitung begründet liegt:
+This chapter intends to provide all relevant information regarding the processing of personal data by QENTA Payment CEE solutions.
+| + + | ++Für den Fall, dass Sie diese Informationen lieber in Deutsch lesen möchten: DE-Version. + | +
During payment processing and depending on the relevant solution, merchants, final consumers, etc. send certain data (input data) to QENTA Payment CEE while QENTA returns other specific data (output data) to them.
+QENTA Payment CEE receives data from three different sources:
+Data, which are entered when payment is triggered (depending on the relevant solution) e.g. the final consumer enters data in the payment window
+Data, which the merchant sends to the QENTA payment interface (request parameter)
+Plugin-specific data of the online shop
+The following chapters give detailed information on the input and output data that are processed by our solutions (including payment methods and additional features). All indicated parameters need to be processed in order to meet our contractual obligations to the merchant (purpose of the processing of data):
+QPAY Checkout Page: Data protection QPAY
+QMORE Checkout Seamless: Data protection QMORE
+QFILE Checkout Automated: Data protection QFILE
+QCALL Checkout Terminal: Data protection QCALL
+In order to fulfill the subject matter of the contract and to process a payment transaction, the merchant or final consumers needs to forward a variety of data (parameters) to the QENTA payment interface (so-called input data). In return, QENTA needs to send back these data (so called output data).
+For all parameters that relate to personal data and are involved in payment processing, the following chapters provide information on the nature of such personal data, data subjects, data categories and purpose of data processing:
+Folgende Parameter sind personenbezogene Daten im datenschutzrechlichen Sinn:
+| Datenkategorie | +Zweck der Datenverarbeitung | +
|---|---|
| + | Erforderliches Datum für erfolgreiche Zahlungsabwicklung |
+
Zahlungsdaten: Allgemein |
+Erforderliches Datum für Zahlungsmittel |
+
Zahlungsdaten: Features |
+Gewünschtes Feature des Merchant |
+
| + | Pflichtangaben für Risikobewertungsprozesse; Pflichtangaben für diverse Zahlungsmittelanbieter; Unterstützende Informationen zur Störungsbehebung und Fehleranalyse |
+
| + | Pflichtangaben für Zahlungsmittelanbieter von Invoice und Installment; Pflichtangaben für Risikobewertungsprozesse sowie zum Anzeigen von Transaktionsdetails für Wallets (z.B.: Paypal, Masterpass) |
+
Personendaten: Features |
+Gewünschtes Feature des Merchant |
+
Personendaten: Endkundendaten |
+Pflichtangaben für Zahlungsmittelanbieter von Invoice und Installment; Pflichtangaben für Risikobewertungsprozesse sowie zum Anzeigen von Transaktionsdetails für Wallets (zB Paypal, Masterpass) |
+
Personendaten: Payment Facilitator Modell |
+Minimumanforderung zur Realisierung der Marktplatzvariante (Payment Facilitator Modell): Zuordnung einer Transaktion zum Unternehmen (SubMerchant), welches auf einer Händlerplatform Produkte/Diensteistungen anbietet |
+
Personendaten: PayPal spezifisch |
+Rückgabedaten des Zahlungsanbieters PayPal |
+
| Parameter | +Typ | +Input/Output | +Betrifft | +Personenbezug | +
|---|---|---|---|---|
| + | Standard |
+Input, Output |
+Merchant |
+Vom Merchant bevorzugte Sprache für das Zahlungsfenster für diese Zahlungstransaktion |
+
| + | Standard |
+Input, Output |
+Merchant |
+Verwendetes Zahlungsmittel der Transaktion, die dem Merchant zuzuordnen ist |
+
| + | Standard |
+Input, Output |
+Merchant |
+Umsatzhöhe der Transaktion, die dem Merchant zuzuordnen ist |
+
| + | Standard |
+Input, Output |
+Merchant |
+Währung der Transaktion, die dem Merchant zuzuordnen ist |
+
| Parameter | +Typ | +Input/Output | +Betrifft | +Personenbezug | +
|---|---|---|---|---|
| + | Standard |
+Input, Output |
+Merchant, Endkunde (Zahlender) |
+In Transaktion involvierte Bank, von der aus der Merchant bezahlt wird. Kontoführendes Geldinsitut des Zahlenden |
+
| + | SEPA |
+Input, Output |
+Merchant |
+Numerischer Wert, der dem Merchant durch den Zahlungsmittelanbieter für SEPA-Transaktionen zugewiesen ist |
+
|
+SEPA |
+Input |
+Endkunde |
+Von paysafecard verpflichtend geforderter Parameter zur Identifizierung des Endkunden. Personenbezug abhängig von den durch den Merchant übermittelten Daten |
+
| Parameter | +Feature | +Input/Output | +Betrifft | +Personenbezug | +
|---|---|---|---|---|
|
+Kreditkarte |
+Output |
+Merchant |
+Staat, aus dem das ausgestellte Zahlungsmittel stammt, mit dem beim Merchant eingekauft wurde |
+
|
+Kreditkarte |
+Output |
+Endkunde (Kreditkarteninhaber) |
+Kreditkartennummer des Karteninhabers in Form eines Hash-Werts [1] |
+
|
+Kreditkarte |
+Output |
+Endkunde (Kreditkarteninhaber) |
+Name des Karteninhabers |
+
|
+Kreditkarte |
+Output |
+Endkunde (Kreditkarteninhaber) |
+Kreditkartennummer des Karteninhabers (10 der insgesamt 16 bis 19 Stellen sichtbar) |
+
Parameter |
+Feature |
+Input/Output |
+Betrifft |
+Personenbezug |
+
|
+iDEAL |
+Output |
+Endkunde (Zahlender) |
+Kontoinformationen (IBAN) des Kontoinhabers |
+
|
+iDEAL |
+Output |
+Endkunde (Zahlender) |
+Kontoinformationen (BIC) des Kontoinhabers |
+
|
+iDEAL |
+Output |
+Endkunde (Zahlender) |
+Name des Kontoinhabers |
+
|
+iDEAL |
+Output |
+Endkunde (Zahlender) |
+Kontoinformationen (IBAN) des Zahlenden |
+
|
+iDEAL |
+Output |
+Endkunde (Zahlender) |
+Stadt, in der Bankkonto des Kontoinhabers gelegen ist |
+
|
+Sofort |
+Output |
+Endkunde (Zahlender) |
+Bankkonto des Kontoinhabers |
+
|
+Sofort |
+Output |
+Endkunde (Zahlender) |
+Name des Kontoinhabers |
+
|
+Sofort |
+Output |
+Endkunde (Zahlender) |
+Bank des Kontoinhabers |
+
|
+Sofort |
+Output |
+Endkunde (Zahlender) |
+Bankkonto des Kontoinhabers |
+
|
+Sofort |
+Output |
+Endkunde (Zahlender) |
+Bankkonto des Kontoinhabers |
+
|
+Sofort |
+Output |
+Endkunde (Zahlender) |
+Land, in dem Bankkonto des Kontoinhabers gelegen ist |
+
|
+Sofort |
+Output |
+Endkunde (Zahlender) |
+Bankkonto des Kontoinhabers |
+
| Parameter | +Typ | +Input/Output | +Betrifft | +Personenbezug | +
|---|---|---|---|---|
|
+Standard |
+Input |
+Endkunde |
+IP-Adresse des Endkunden |
+
|
+Standard |
+Input |
+Endkunde |
+Vom Endkunden benutzter Browser |
+
| Parameter | +Typ | +Input/Output | +Betrifft | +Personenbezug | +
|---|---|---|---|---|
|
+Standard |
+Input |
+Merchant |
+Produkte, die der Merchant mit dieser Transaktion verkauft |
+
|
+Standard |
+Input |
+Merchant |
+Artikelnummer der Produkte, die der Merchant mit dieser Transaktion verkauft |
+
|
+Standard |
+Input |
+Merchant |
+Artikelbeschreibung der Produkte, die der Merchant mit dieser Transaktion verkauft |
+
|
+Standard |
+Input |
+Merchant |
+Aussehen der Produkte, die der Merchant mit dieser Transaktion verkauft |
+
|
+Standard |
+Input |
+Merchant |
+Name der Produkte, die der Merchant mit dieser Transaktion verkauft |
+
|
+Standard |
+Input |
+Merchant |
+Menge der Produkte, die der Merchant mit dieser Transaktion verkauft |
+
|
+Standard |
+Input |
+Merchant |
+Brutto Preis der Produkte, die der Merchant mit dieser Transaktion verkauft |
+
|
+Standard |
+Input |
+Merchant |
+Netto Preis der Produkte, die der Merchant mit dieser Transaktion verkauft |
+
|
+Standard |
+Input |
+Merchant |
+Steuerbetrag der Produkte, die der Merchant mit dieser Transaktion verkauft |
+
| Parameter | +Typ | +Input/Output | +Betrifft | +Personenbezug | +
|---|---|---|---|---|
| + | Feature |
+Input |
+Merchant |
+Email-Adresse des Merchants (seines Mitarbeiters) für den Erhalt des Confirm-Mails |
+
| Parameter | +Typ | +Input/Output | +Betrifft | +Personenbezug | +
|---|---|---|---|---|
|
+Standard |
+Input |
+Endkunde |
+Email-Adresse des Endkunden |
+
|
+Standard |
+Input |
+Endkunde |
+Geburtstag des Endkunden |
+
|
+Standard |
+Input |
+Endkunde |
+Steuer-Identifikationsnummer des Endkunden |
+
|
+Standard |
+Input |
+Endkunde |
+Führerscheinnummer des Endkunden |
+
|
+Standard |
+Input |
+Endkunde |
+Provinz innerhalb eines Staates, die den Führerschein des Endkunden ausgestellt hat |
+
|
+Standard |
+Input |
+Endkunde |
+Staat, der den Führerschein des Endkunden ausgestellt hat |
+
|
+Standard |
+Input |
+Endkunde |
+Vorname des Endkunden auf den die Rechnung ausgestellt ist |
+
|
+Standard |
+Input |
+Endkunde |
+Familienname des Endkunden auf den die Rechnung ausgestellt ist |
+
|
+Standard |
+Input |
+Endkunde |
+Straßenname des Endkunden auf den die Rechnung ausgestellt ist |
+
|
+Standard |
+Input |
+Endkunde |
+Hausnummer des Endkunden auf den die Rechnung ausgestellt ist |
+
|
+Standard |
+Input |
+Endkunde |
+Stadt des Endkunden auf den die Rechnung ausgestellt ist |
+
|
+Standard |
+Input |
+Endkunde |
+Provinz des Endkunden auf den die Rechnung ausgestellt ist |
+
|
+Standard |
+Input |
+Endkunde |
+Staat des Endkunden auf den die Rechnung ausgestellt ist |
+
|
+Standard |
+Input |
+Endkunde |
+Postleitzahl des Endkunden auf den die Rechnung ausgestellt ist |
+
|
+Standard |
+Input |
+Endkunde |
+Telefonnummer des Endkunden auf den die Rechnung ausgestellt ist |
+
|
+Standard |
+Input |
+Endkunde |
+Faxnummer des Endkunden auf den die Rechnung ausgestellt ist |
+
|
+Standard |
+Input |
+Endkunde |
+Vorname des Endkunden an den der Versand der Bestellung geht |
+
|
+Standard |
+Input |
+Endkunde |
+Name des Endkunden an den der Versand der Bestellung geht |
+
|
+Standard |
+Input |
+Endkunde |
+Straße des Endkunden an den der Versand der Bestellung geht |
+
|
+Standard |
+Input |
+Endkunde |
+Hausnummer des Endkunden an den der Versand der Bestellung geht |
+
|
+Standard |
+Input |
+Endkunde |
+Stadt des Endkunden an den der Versand der Bestellung geht |
+
|
+Standard |
+Input |
+Endkunde |
+Provinz des Endkunden an den der Versand der Bestellung geht |
+
|
+Standard |
+Input |
+Endkunde |
+Staat des Endkunden an den der Versand der Bestellung geht |
+
|
+Standard |
+Input |
+Endkunde |
+Postleitzahl des Endkunden an den der Versand der Bestellung geht |
+
|
+Standard |
+Input |
+Endkunde |
+Telefonnummer des Endkunden an den der Versand der Bestellung geht |
+
|
+Standard |
+Input |
+Endkunde |
+Faxnummer des Endkunden an den der Versand der Bestellung geht |
+
| Parameter | +Payment Facilitator Modell | +Input/Output | +Betrifft | +Personenbezug [2] | +
|---|---|---|---|---|
|
+Marktplatzmodell |
+Input |
+Sub Merchant |
+Kundennummer des Sub Merchants |
+
|
+Marktplatzmodell |
+Input |
+Sub Merchant |
+Kundennummer des Sub Merchants |
+
|
+Marktplatzmodell |
+Input |
+Sub Merchant |
+Staat des Sub Merchants |
+
|
+Marktplatzmodell |
+Input |
+Sub Merchant |
+Provinz des Sub Merchants |
+
|
+Marktplatzmodell |
+Input |
+Sub Merchant |
+Stadt des Sub Merchants |
+
|
+Marktplatzmodell |
+Input |
+Sub Merchant |
+Straße des Sub Merchants |
+
|
+Marktplatzmodell |
+Input |
+Sub Merchant |
+Postleitzahl des Sub Merchants |
+
| Parameter | +Typ | +Input/Output | +Betrifft | +Personenbezug | +
|---|---|---|---|---|
|
+PayPal |
+Output |
+Endkunde |
+Stadt in der Endkunde wohnt (Lieferadresse) |
+
|
+PayPal |
+Output |
+Endkunde |
+Staat in dem Endkunde wohnt (Lieferadresse) |
+
|
+PayPal |
+Output |
+Endkunde |
+Ländercode des Staats in dem Endkunde wohnt (Lieferadresse) |
+
|
+PayPal |
+Output |
+Endkunde |
+Name des Endkunden (Lieferadresse) |
+
|
+PayPal |
+Output |
+Endkunde |
+Provinz in der Endkunde wohnt (Lieferadresse) |
+
|
+PayPal |
+Output |
+Endkunde |
+Straße (Adresszeile 1) des Endkunden (Lieferadresse) |
+
|
+PayPal |
+Output |
+Endkunde |
+Straße (Adresszeile 2) des Endkunden (Lieferadresse) |
+
|
+PayPal |
+Output |
+Endkunde |
+Postleitzahl des Endkunden (Lieferadresse) |
+
|
+PayPal |
+Output |
+Endkunde (Zahlender) |
+Email-Adresse des PayPal-Kontoinhabers |
+
|
+PayPal |
+Output |
+Endkunde (Zahlender) |
+Vorname des PayPal-Kontoinhabers |
+
|
+PayPal |
+Output |
+Endkunde (Zahlender) |
+Nachname des PayPal-Kontoinhabers |
+
|
+PayPal |
+Output |
+Endkunde (Zahlender) |
+Numerischer Wert, der dem Endkunden durch den Zahlungsmittelanbieter für PayPal-Transaktionen zugewiesen ist |
+
Auf dieser Infoseite können Sie sich über alle Daten informieren, die das Produkt QFILE Checkout Automated verarbeitet.
+Die Datenverarbeitung von QFILE ist umso umfangreicher, je größer der vom Merchant bestellte Produktumfang ist. Bei der Bestellung des Produkts QFILE kann unterschieden werden zwischen
+1 Basisprodukt, optional erweitert um
+1 bis N Zahlungsmitteln, und/oder
+0 bis N optionalen Zusatzfeatures
+Die allgemeine Funktionsweise des Produkts QFILE-sowohl in seiner Basisversion als auch abhängig vom Einsatz verschiedener Zahlungsmittel-ist zudem hier ausführlich beschrieben: Bedienungsanleitung QFILE
+Sämtliche hier angegebenen personenbezogenen Parameter müssen verarbeitet werden, um das Produkt QFILE in seiner Basisversion dem Merchant zur Verfügung stellen zu können (Zweck der Datenverarbeitung).
+Die hier angezeigten Parameter unterteilen sich in Parameter
+die unabhängig vom Zahlungsmittel verarbeitet werden (Standard)
+die abhängig vom jeweiligen Zahlungsmittel verarbeitet werden (Zahlungsmittel)
+| Parameter | +Betroffene Person | +Personenbezug | +
|---|---|---|
Credit card number |
+Endkunde |
+Kreditkartennummer des Endkunden |
+
Expiration date |
+Endkunde |
+Ablaufdatum der benutzten Kreditkarte |
+
CVC |
+Endkunde |
+Kartenprüfnummer der Kreditkarte des Endkunden |
+
| Parameter | +Betroffene Person | +Personenbezug | +
|---|---|---|
IBAN |
+Endkunde |
+IBAN des Endkunden |
+
BIC |
+Endkunde |
+Bank Identification Code der Bank des Endkunden |
+
Nach dem Hochladen der Zahlungsdaten Ihrer Endkunden, wird die Datei verarbeitet. Sobald die Verarbeitung abgeschlossen ist, können die Transaktionen als CSV-Datei heruntergeladen werden, welche Sie wieder in eine Excel-Datei umwandeln können. Dadurch wird jedoch keine zusätzliche Verarbeitung von personenbezogenen Daten vorgenommen.
+Für jedes zusätzlich zum Basisprodukt QFILE bestellte Feature ist hier ersichtlich, welche Daten das jeweilige Feature verarbeitet.
+| Feature | +Verarbeitete Daten und Datenschutzinfos | +
|---|---|
1. Weitere Zugänge zum QENTA Payment Center |
+Für die Web-Applikationen des Händlerlogins wird ein neuer Zugang für den Merchant angelegt, der nicht personengebunden ist. Für den Zugang ist ein Benutzername und ein Passwort erforderlich. Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten. |
+
2. Zusätzliche Währungen |
+Abhängig vom Produktkatalog des Merchants sind bestimmte Produkte in 1 bis N Währungen zahlbar, die von QENTA als Konfigurationseinstellungen hinterlegt werden. Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten. Allerdings ist die Währung der Zahlung selbst ein personenbezogenes Datum, die über die Währung der abgewickelten Zahlungstransaktion des Merchants Auskunft gibt. |
+
3. Wiederkehrende Zahlung |
+Mit diesem Feature wird der Merchant über eine Konfigurationseinstellung seitens QENTA in die Lage versetzt, wiederkehrende Zahlungen durchführen. Für die Durchführung einer wiederkehrenden Zahlung ist das Batch-File wie in der QFILE-Dokumentation beschrieben auszufüllen. Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten. |
+
This chapter provides information on all data that are processed by our solution QFILE Checkout Automated.
+QFILE Checkout Automated data processing volume increases with the services contracted.
+When ordering QFILE Checkout Automated, the merchant may acquire:
+1 basic solution, optionally extendable with
+1 to N payment methods, and/or
+0 to N optional and additional features
+| + + | ++The general functioning of the product QFILE-both in its basic version and when using different payment methods-is also described in detail here: QFILE. + | +
All indicated parameters need to be processed to ensure that the solution QFILE Checkout Automated, 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)
+| Parameter | +Data Subject | +Personal Data | +
|---|---|---|
Credit card number |
+consumer |
+Credit card number of the consumer |
+
Expiration date |
+consumer |
+Expiration date of the credit card user by the consumer |
+
CVC |
+consumer |
+CVC of the credit card user by the consumer |
+
| Parameter | +Data Subject | +Personal Data | +
|---|---|---|
IBAN |
+consumer |
+Account Number of the consumer |
+
BIC |
+consumer |
+Bank Identification Code of the consumer’s bank |
+
After uploading the payment details of the customers, the file is processed. Once processing of the file is completed, the transactions can be downloaded as a tab-delimited text file which can be converted back into an xls-file. Thus, no additional processing of personal data takes place when downloading the payment response data.
+This chapter provides information on the data processed for each feature that has been added to the basic QFILE Checkout Automated solution.
+| Feature | +Processing of data and information on the protection of personal data | +
|---|---|
1. Additional access to the QPC Payment Center |
+For the web application of the QPC 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. |
+
2. Additional currencies |
+For the web application of the QPC 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. |
+
3. Recurring payment |
+Based on a configuration setting provided by QENTA, this feature allows the merchant to carry out recurring payment. A recurring payment is carried out by filling in the batch file as described in the QFILE. Thus, no additional processing of personal data takes place. |
+
Auf dieser Infoseite können Sie sich über alle Daten informieren, die das Produkt QPAY Checkout Page verarbeitet.
+Bei der Bestellung des Produkts QPAY Checkout Page kann unterschieden werden zwischen
+1 Basisprodukt, optional erweitert um
+1 bis N Zahlungsmitteln, und/oder
+0 bis N optionalen Zusatzfeatures
+Sollten Sie darüber hinaus noch Fragen zu datenschutzrechtlichen Details der einzelnen Parameter haben (zB betroffene Person, Datenkategorie etc), können Sie diesbezügliche Informationen unter individual parameter einsehen.
+Unter Auswahl eines Zahlungsmittels können Sie hier simulieren, welche Daten (Parameter) für eine Zahlungstransaktion mit einem bestimmten Zahlungsmittel verarbeitet werden. Angezeigt werden dabei sowohl Daten,
+die vom Merchant oder dem Endkunden an die QPAY Zahlungsschnittstelle gesendet werden (sog. Input-Daten)
+die von QPAY wieder an diese zurück gehen (sog. Output-Daten).
+Sämtliche hier angegebenen Parameter müssen verarbeitet werden, um das Produkt QPAY in seiner Basisversion dem Merchant zur Verfügung stellen zu können (Zweck der Datenverarbeitung).
+Die hier angezeigten Parameter unterteilen sich in Parameter
+die unabhängig vom Zahlungsmittel verarbeitet werden (Standard)
+die abhängig vom jeweiligen Zahlungsmittel verarbeitet werden (Zahlungsmittel)
+die vom Endkunden eingegeben werden (Interaktion Endkunde)
+Bitte wählen Sie ein Zahlungsmittel aus:
+| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Ausschließlich Externes Zahlungsfenster |
+Nein |
+
Ausschließlich QENTA Zahlungsfenster |
+Nein |
+
Teileingabe auf QENTA Zahlungsfenster |
+Ja |
+
Dateneingabe auf QENTA Seite |
+PAN, CVC, Name, Expiry Date, Issue Date, Cardholder Name |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Ausschließlich Externes Zahlungsfenster |
+Nein |
+
Ausschließlich QENTA Zahlungsfenster |
+Nein |
+
Teileingabe auf QENTA Zahlungsfenster |
+Ja |
+
Dateneingabe auf QENTA Seite |
+Bank |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Ausschließlich Externes Zahlungsfenster |
+Nein |
+
Ausschließlich QENTA Zahlungsfenster |
+Nein |
+
Teileingabe auf QENTA Zahlungsfenster |
+Ja |
+
Dateneingabe auf QENTA Seite |
+Bank, Kontonummer, Kontoinhaber |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Ausschließlich Externes Zahlungsfenster |
+Ja |
+
Ausschließlich QENTA Zahlungsfenster |
+Nein |
+
Teileingabe auf QENTA Zahlungsfenster |
+Nein |
+
Dateneingabe auf QENTA Seite |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Ausschließlich Externes Zahlungsfenster |
+Ja |
+
Ausschließlich QENTA Zahlungsfenster |
+Nein |
+
Teileingabe auf QENTA Zahlungsfenster |
+Nein |
+
Dateneingabe auf QENTA Seite |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Additonal Response Parameters |
++ |
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Ausschließlich Externes Zahlungsfenster |
+Ja |
+
Ausschließlich QENTA Zahlungsfenster |
+Nein |
+
Teileingabe auf QENTA Zahlungsfenster |
+Nein |
+
Dateneingabe auf QENTA Seite |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Ausschließlich Externes Zahlungsfenster |
+Ja |
+
Ausschließlich QENTA Zahlungsfenster |
+Nein |
+
Teileingabe auf QENTA Zahlungsfenster |
+Nein |
+
Dateneingabe auf QENTA Seite |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Ausschließlich Externes Zahlungsfenster |
+Ja |
+
Ausschließlich QENTA Zahlungsfenster |
+Nein |
+
Teileingabe auf QENTA Zahlungsfenster |
+Nein |
+
Dateneingabe auf QENTA Seite |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
+xref:parameters/frontend/optional-parameters.adoc#restrictionsForCustomerStatement |
+
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Additonal Response Parameters |
++ |
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Ausschließlich Externes Zahlungsfenster |
+Nein |
+
Ausschließlich QENTA Zahlungsfenster |
+Ja |
+
Teileingabe auf QENTA Zahlungsfenster |
+Nein |
+
Dateneingabe auf QENTA Seite |
+Kontoinhaber, BIC, IBAN |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Additonal Response Parameters |
++ |
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Ausschließlich Externes Zahlungsfenster |
+Nein |
+
Ausschließlich QENTA Zahlungsfenster |
+Ja |
+
Teileingabe auf QENTA Zahlungsfenster |
+Nein |
+
Dateneingabe auf QENTA Seite |
+Kontoinhaber, BIC, IBAN |
+
Für jedes zusätzlich zum Basisprodukt QPAY bestellte Feature ist hier ersichtlich, welche Daten das jeweilige Feature verarbeitet.
+Sämtliche für das jeweilige Feature angegebenen Parameter müssen verarbeitet werden, um dem Merchant zusätzlich zum Basisprodukt das gewünschte Feature zur Verfügung stellen zu können (Zweck der Datenverarbeitung).
+| Feature | +Verarbeitete Daten und Datenschutzinfos | +
|---|---|
1. Individuelles Layout für QPAY Checkout Page |
+Das Feature ermöglicht dem Merchant die Gestaltung der Checkout Page im Corporate Design. Die Layoutanpassung erfolgt über vorgefertigtes CSS-Template, das der |
+
2. Zahlungsmittel-Reihenfolge |
+Mit diesem Feature kann der Merchant die Reihenfolge der Zahlungsmittel in der Checkout Page selbst bestimmten. Diese Konfigurationseinstellung erfolgt über den Parameter paymenttypeSortOrder. Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten. |
+
3. Zusätzliche Sprachen |
+Um für jede Transaktion das Bezahlfenster in der für den Endkunden präferierten Sprache anzuzeigen, werden die Spracheinstellungen vom Merchant über den Browser des Endkunden erhoben und QPAY durch den Merchant über den Parameter language mitgeteilt. Als personenbezogenes Datum wird somit die Sprache des Endkunden verarbeitet, auch wenn der Endkunde mangels Kenntnis von Personendaten unbekannt bleibt. |
+
4. Zusätzliche Währungen |
+Abhängig vom Produktkatalog des Merchants sind bestimmte Produkte in 1 bis N Währungen zahlbar. Je nach Produkt und Auswahl des Endkunden wird die abzuwickelnde Währung QPAY über den Request Parameter currency mitgeteilt. Als personenbezogenes Datum wird somit die Währung der abgewickelten Zahlungstransaktion des Merchants verarbeitet. |
+
| Feature | +Verarbeitete Daten und Datenschutzinfos | +
|---|---|
5. Wiederkehrende Zahlung |
+Mit diesem Feature kann der Merchant über die Backend-Operation recurPayment wiederkehrende Zahlungen durchführen. Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten. |
+
6. Weitere Zugänge zum QPC Payment Center |
+Für die Web-Applikationen des Händlerlogins wird ein neuer Zugang für den Merchant angelegt, der nicht personengebunden ist. Für den Zugang ist ein Benutzername und ein Passwort erforderlich. Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten.) |
+
7. Rückgabe Karteninhaber Kreditkarte |
+Durch dieses Feature wird das personenbezogene Datum |
+
8. Rückgabe Maskierte Kartennummer Kreditkarte |
+Durch dieses Feature wird das personenbezogene Datum |
+
9. Rückgabe Referenznummer der Transaktion |
+Durch dieses Feature erhält der Merchant über den Parameter |
+
10. Rückgabe iDEAL Konsumentendaten |
+Durch dieses Feature werden dem Merchant nähere Infos zum Endkunden übermittelt, die alle personenbezogene Daten sind: |
+
11. Rückgabe PayPal Konsumentendaten |
+Durch dieses Feature werden dem Merchant nähere Infos zum Endkunden übermittelt, die alle personenbezogene Daten sind: |
+
12. Rückgabe Sofort Konsumentendaten |
+Durch dieses Feature werden dem Merchant nähere Infos zum Endkunden übermittelt, die alle personenbezogene Daten sind: |
+
13. Rückgabe Vertragsnummer, auf welche die Transaktion gelaufen ist |
+Dieses Feature übermittelt über den Parameter |
+
14. Rückgabe Land des Zahlungsmittels |
+Durch dieses Feature wird dem Merchant das personenbezogene Datum |
+
15. Rückgabe SEPA Konsumentendaten |
+Durch dieses Feature werden dem Merchant nähere Infos zum Endkunden übermittelt, die alle personenbezogene Daten sind: |
+
16. Rückgabe Address Verification System Daten Kreditkarte |
+Mit diesem Feature werden vom Merchant übermittelte personenbezogene Daten des Endkunden (zB Name, Adresse) auf deren Richtigkeit überprüft und das Ergebnis dieser Überprüfung dem Merchant über |
+
17. Anzeige einer "3-D Secure" Transaktion für Kreditkarte |
+Mit diesem Feature kann der Merchant festlegen, ob dem Endkunden auf der Payment Page ein Hinweis über die Durchführung der Zahlung mittels 3-D Secure Verfahren angezeigt wird. Durch diese Konfigurationseinstellung auf Seiten QPAYs kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten. |
+
18. Rückgabe Ablaufdatum der Kreditkarte |
+Dieses Feature liefert dem Merchant das Ablaufdatum der verwendeten Kreditkarte über den Parameter |
+
19. Rückgabe der Kreditkartennummer als Hash-Wert |
+Durch dieses Feature wird dem Merchant der Zufallswert |
+
20. Selektive automatische Buchung |
+Über den Parameter |
+
21. Auswahl der Kartenmarke |
+Mit diesem Feature kann der Merchant über den zusätzlich zu übermittelnden Parameter |
+
22. Maximale Anzahl an Fehlversuchen |
+Durch dieses Feature kann der Merchant selbstständig die Anzahl an Fehlversuchen für eine Zahlung festlegen. Diese Konfigurationseinstellung erfolgt über den Parameter |
+
23. Eigene Auftragsnummer |
+Zu Zwecke organisatorischer Erleichterung kann der Merchant über den Parameter |
+
24. Erweiterung der QPAY Checkout Page zur Backoffice Nutzung |
+Durch dieses Feature wird der Merchant in die Lage versetzt, das Produkt wie ein Endkunde zu nutzen. Eine weitere Verarbeitung von Datenkategorien ergibt sich dadurch jedoch nicht. |
+
| Feature | +Verarbeitete Daten und Datenschutzinfos | +
|---|---|
25. Zustellung der Zahlungsbenachrichtigung per E-Mail |
+Durch dieses Feature erhält der Merchant sämtliche Response Parameter, die er ansonsten über die confirmUrl erhält, im Email-Format sowie an die gewünschte Email-Adresse. Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten. Die entsprechenden Response Informationen sind hier ersichtlich. |
+
26. Wiederholte Zustellversuche der Zahlungsbenachrichtigung |
+Für den Fall, dass der Server des Merchants nicht erreichbar sein sollte, ermöglicht dieses Feature die erneute Zustellung der Zahlungsbenachrichtigung. Diese Konfigurationseinstellung bewirkt jedoch keine zusätzliche Verarbeitung von personenbezogenen Daten. |
+
This chapter provides information on all data that are processed by our solution QPAY Checkout Page.
+When ordering QPAY Checkout Page, the merchant may acquire:
+1 basic solution, optionally extendable with
+1 to N payment methods, and/or
+0 to N optional and additional features
+For any further questions regarding data protection details and individual parameters, e.g. data subjects, categories of data, etc., consult Datenschutzhinweise zu einzelnen Parametern for additional information.
+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 QPAY Checkout Page, 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 a payment method:
+| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Parameters regarding the status of a payment (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| Parameter type | +Processed data | +
|---|---|
Exclusively external payment page |
+No |
+
Exclusively QENTA payment page |
+No |
+
Entry of data partially in QENTA payment page |
+Yes |
+
Entry of data in QENTA payment page |
+PAN, CVC, Name, Expiry Date, Issue Date, Cardholder Name |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Parameters regarding the status of a payment (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| Parameter type | +Processed data | +
|---|---|
Exclusively external payment page |
+No |
+
Exclusively QENTA payment page |
+No |
+
Entry of data partially in QENTA payment page |
+Yes |
+
Entry of data in QENTA payment page |
+Bank |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Proce ssed data | +
|---|---|
Parameters regarding the status of a payment (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| Parameter type | +Processed data | +
|---|---|
Exclusively external payment page |
+No |
+
Exclusively QENTA payment page |
+No |
+
Entry of data partially in QENTA payment page |
+Yes |
+
Entry of data in QENTA payment page |
+Bank, Account number, Account owner |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Parameters regarding the status of a payment (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| Parameter type | +Processed data | +
|---|---|
Exclusively external payment page |
+Yes |
+
Exclusively QENTA payment page |
+No |
+
Entry of data partially in QENTA payment page |
+No |
+
Entry of data in QENTA payment page |
+- |
+
| Parameter type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter type | +Processed data | +
|---|---|
Parameters regarding the status of a payment (standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| Parameter type | +Processed data | +
|---|---|
Exclusively external payment page |
+Yes |
+
Exclusively QENTA payment page |
+No |
+
Entry of data partially in QENTA payment page |
+No |
+
Entry of data in QENTA payment page |
+- |
+
| Parameter type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter type | +Processed data | +
|---|---|
Additonal Response Parameters |
++ |
Parameters regarding the status of a payment (standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| Parameter type | +Processed data | +
|---|---|
Exclusively external payment page |
+Yes |
+
Exclusively QENTA payment page |
+No |
+
Entry of data partially in QENTA payment page |
+No |
+
Entry of data in QENTA payment page |
+- |
+
| Parameter type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter type | +Processed data | +
|---|---|
Parameters regarding the status of a payment (standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| Parameter type | +Processed data | +
|---|---|
Exclusively external payment page |
+Yes |
+
Exclusively QENTA payment page |
+No |
+
Entry of data partially in QENTA payment page |
+No |
+
Entry of data in QENTA payment page |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Parameters regarding the status of a payment (Standard) |
++ |
| Parameter type | +Processed data | +
|---|---|
Exclusively external payment page |
+Yes |
+
Exclusively QENTA payment page |
+No |
+
Entry of data partially in QENTA payment page |
+No |
+
Entry of data in QENTA payment page |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Additonal Response Parameters |
++ |
Parameters regarding the status of a payment (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| Parameter type | +Processed data | +
|---|---|
Exclusively external payment page |
+No |
+
Exclusively QENTA payment page |
+Yes |
+
Entry of data partially in QENTA payment page |
+No |
+
Entry of data in QENTA payment page |
+Account owner, BIC, IBAN |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Additonal Response Parameters |
++ |
Parameters regarding the status of a payment (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| Parameter type | +Processed data | +
|---|---|
Exclusively external payment page |
+No |
+
Exclusively QENTA payment page |
+Yes |
+
Entry of data partially in QENTA payment page |
+No |
+
Entry of data in QENTA payment page |
+Account owner, BIC, IBAN |
+
This chapter provides information on the data processed for each feature that has been added to the basic QPAY Checkout Page 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).
+| Feature | +Processing of data and information on the protection of personal data | +
|---|---|
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 |
+
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. |
+
| Feature | +Processing of data and information on the protection of personal data | +
|---|---|
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. |
+8. Return of masked credit card number |
+
This feature involves the processing of personal data, i.e. |
+9. Return of transaction reference number |
+
This feature allows the merchant to obtain a unique reference number of the transaction via parameter |
+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: |
+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: |
+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: |
+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 |
+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 |
+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: |
+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 |
+
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 |
+
19. Return of hashed credit card number |
+This feature allows the merchant to obtain the random value |
+
20. Selective automatic deposit |
+Via parameter |
+
21. Selection of credit card brand |
+This feature allows the merchant to define via the additional parameter |
+
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 |
+
23. Unique order number |
+The parameter |
+
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. |
+
| Feature | +Processing of data and information on the protection of personal data | +
|---|---|
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. |
+
Auf dieser Infoseite können Sie sich über alle Daten informieren, die das Produkt QMORE Checkout Seamlessverarbeitet.
+Bei der Bestellung des Produkts QMORE kann unterschieden werden zwischen
+1 Basisprodukt, optional erweitert um
+1 bis N Zahlungsmitteln, und/oder
+0 bis N optionalen Zusatzfeatures
+Sollten Sie darüber hinaus noch Fragen zu datenschutzrechtlichen Details der einzelnen Parameter haben (zB betroffene Person, Datenkategorie etc), können Sie diesbezügliche Informationen unter individual parameter einsehen.
+Unter Auswahl eines Zahlungsmittels können Sie hier simulieren, welche Daten (Parameter) für eine Zahlungstransaktion mit einem bestimmten Zahlungsmittel verarbeitet werden. Angezeigt werden dabei sowohl Daten,
+die vom Merchant oder dem Endkunden an die QENTA Zahlungsschnittstelle gesendet werden (sog. Input-Daten)
+die von QENTA wieder an diese zurück gehen (sog. Output-Daten).
+Sämtliche hier angegebenen Parameter müssen verarbeitet werden, um das Produkt QMORE in seiner Basisversion dem Merchant zur Verfügung stellen zu können (Zweck der Datenverarbeitung).
+Die hier angezeigten Parameter unterteilen sich in Parameter
+die unabhängig vom Zahlungsmittel verarbeitet werden (Standard)
+die abhängig vom jeweiligen Zahlungsmittel verarbeitet werden (Zahlungsmittel)
+die vom Endkunden eingegeben werden (Interaktion Endkunde)
+Bitte wählen Sie ein Zahlungsmittel aus:
+| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Dateneingabe auf QENTA Seite |
+PAN, CVC, Name, Expiry Date, Issue Date, Cardholder Name |
+
Datenweiterleitung an QENTA vor Zahlungsinitierung |
+Ja |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Dateneingabe auf QENTA Seite |
+Bank |
+
Datenweiterleitung an QENTA vor Zahlungsinitierung |
+Nein |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Dateneingabe auf QENTA Seite |
+Bank, Kontonummer, Kontoinhaber |
+
Datenweiterleitung an QENTA vor Zahlungsinitierung |
+Ja |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Dateneingabe auf QENTA Seite |
+- |
+
Datenweiterleitung an QENTA vor Zahlungsinitierung |
+Nein |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Dateneingabe auf QENTA Seite |
+- |
+
Datenweiterleitung an QENTA vor Zahlungsinitierung |
+Nein |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Additonal Response Parameters |
++ |
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Dateneingabe auf QENTA Seite |
+- |
+
Datenweiterleitung an QENTA vor Zahlungsinitierung |
+Nein |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Dateneingabe auf QENTA Seite |
+- |
+
Datenweiterleitung an QENTA vor Zahlungsinitierung |
+Nein |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Dateneingabe auf QENTA Seite |
+- |
+
Datenweiterleitung an QENTA vor Zahlungsinitierung |
+Nein |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Additonal Response Parameters |
++ |
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Dateneingabe auf QENTA Seite |
+Kontoinhaber, BIC, IBAN |
+
Datenweiterleitung an QENTA vor Zahlungsinitierung |
+Ja |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Required Request Parameters (Zahlungsmittel) |
++ |
Optional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters (Zahlungsmittel) |
++ |
Additional Request Parameters B2B (Zahlungsmittel) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
Plugin-spezifische Daten (Standard) |
+- |
+
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Additonal Response Parameters |
++ |
Parameter über Status der Zahlung (Standard) |
++ |
1 bis N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Verarbeitete Daten | +
|---|---|
Dateneingabe auf QENTA Seite |
+Kontoinhaber, BIC, IBAN |
+
Datenweiterleitung an QENTA vor Zahlungsinitierung |
+Ja |
+
In der Basisfunktion von QMORE inkludiert sind bereits einige Funktionen, die nachfolgend näher dargestellt werden.
+| Inklusivleistung | +Verarbeitete Daten und Datenschutzinfos | +
|---|---|
1. Rückgabe Karteninhaber Kreditkarte |
+Durch dieses Feature wird das personenbezogene Datum |
+
2. Rückgabe Maskierte Kartennummer Kreditkarte |
+Durch dieses Feature wird das personenbezogene Datum |
+
3. Rückgabe Referenznummer der Transaktion |
+Durch dieses Feature erhält der Merchant über den Parameter |
+
4. Rückgabe iDEAL Konsumentendaten |
+Durch dieses Feature werden dem Merchant nähere Infos zum Endkunden übermittelt, die alle personenbezogene Daten sind: |
+
5. Rückgabe PayPal Konsumentendaten |
+Durch dieses Feature werden dem Merchant nähere Infos zum Endkunden übermittelt, die alle personenbezogene Daten sind: |
+
6. Rückgabe Vertragsnummer, auf welche die Transaktion gelaufen ist |
+Dieses Feature übermittelt über den Parameter |
+
7. Rückgabe Sofort Konsumentendaten |
+Durch dieses Feature werden dem Merchant nähere Infos zum Endkunden übermittelt, die alle personenbezogene Daten sind: |
+
8. Rückgabe SEPA Konsumentendaten |
+Durch dieses Feature werden dem Merchant nähere Infos zum Endkunden übermittelt, die alle personenbezogene Daten sind: |
+
9. Rückgabe Ablaufdatum der Kreditkarte |
+Dieses Feature liefert dem Merchant das Ablaufdatum der verwendeten Kreditkarte über den Parameter |
+
10. Selektive automatische Buchung |
+Über den Parameter #autodeposit kann der Merchant für jede Transaktion einzeln bestimmen, wann die Zahlung durchgeführt wird. Dies ist eine Konfigurationseinstellung über einen Schritt, der im Rahmen der Zahlungsabwicklung ohnehin zu erfolgen hat. Der Parameter legt nur den Zeitpunkt dieses Schrittes fest. Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten. |
+
11. Auswahl der Kartenmarke |
+Mit diesem Feature kann der Merchant über den zusätzlich zu übermittelnden Parameter |
+
12. Eigene Auftragsnummer |
+Zu Zwecke organisatorischer Erleichterung kann der Merchant über den Parameter |
+
Für jedes zusätzlich zum Basisprodukt QMORE bestellte Feature ist hier ersichtlich, welche Daten das jeweilige Feature verarbeitet.
+Sämtliche für das jeweilige Feature angegebenen Parameter müssen verarbeitet werden, um dem Merchant zusätzlich zum Basisprodukt das gewünschte Feature zur Verfügung stellen zu können (Zweck der Datenverarbeitung).
+| Feature | +Verarbeitete Daten und Datenschutzinfos | +
|---|---|
1. Individuelles Layout für QMORE Checkout Seamless |
+Das Feature ermöglicht dem Merchant die Gestaltung von Checkout Seamless im Corporate Design. Die Layoutanpassung erfolgt über vorgefertigtes CSS-Template, das der shopId des Merchants hinterlegt wird. Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten. |
+
2. Zusätzliche Sprachen |
+Um für jede Transaktion das Bezahlfenster in der für den Endkunden präferierten Sprache anzuzeigen, werden die Spracheinstellungen vom Merchant über den Browser des Endkunden erhoben und QENTA durch den Merchant über den Parameter language mitgeteilt. Als personenbezogenes Datum wird somit die Sprache des Endkunden verarbeitet, auch wenn der Endkunde mangels Kenntnis von Personendaten unbekannt bleibt. |
+
3. Zusätzliche Währungen |
+Abhängig vom Produktkatalog des Merchants sind bestimmte Produkte in 1 bis N Währungen zahlbar. Je nach Produkt und Auswahl des Endkunden wird die abzuwickelnde Währung QENTA über den Request Parameter currency mitgeteilt. Als personenbezogenes Datum wird somit die Währung der abgewickelten Zahlungstransaktion des Merchants verarbeitet. |
+
| Feature | +Verarbeitete Daten und Datenschutzinfos | +
|---|---|
4. Wiederkehrende Zahlung |
+Mit diesem Feature kann der Merchant über die Backend-Operation recurPayment wiederkehrende Zahlungen durchführen. Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten. |
+
5. Weitere Zugänge zum QPC Payment Center |
+Für die Web-Applikationen des Händlerlogins wird ein neuer Zugang für den Merchant angelegt, der nicht personengebunden ist. Für den Zugang ist ein Benutzername und ein Passwort erforderlich. Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten.) |
+
6. Rückgabe der Kreditkartennummer als Hash-Wert |
+Durch dieses Feature wird dem Merchant der Zufallswert |
+
7. Erweiterung für QMORE Checkout Seamless zur Backoffice Nutzung |
+Durch dieses Feature wird der Merchant in die Lage versetzt, das Produkt wie ein Endkunde zu nutzen. Eine weitere Verarbeitung von Datenkategorien ergibt sich dadurch jedoch nicht. |
+
| Feature | +Verarbeitete Daten und Datenschutzinfos | +
|---|---|
8. Zustellung der Zahlungsbenachrichtigung per E-Mail |
+Durch dieses Feature erhält der Merchant sämtliche Response Parameter, die er ansonsten über die confirmUrl erhält, im Email-Format sowie an die gewünschte Email-Adresse. Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten. Die entsprechenden Response Informationen sind hier ersichtlich. |
+
9. Wiederholte Zustellversuche der Zahlungsbenachrichtigung |
+Für den Fall, dass der Server des Merchants nicht erreichbar sein sollte, ermöglicht dieses Feature die erneute Zustellung der Zahlungsbenachrichtigung. Diese Konfigurationseinstellung bewirkt jedoch keine zusätzliche Verarbeitung von personenbezogenen Daten. |
+
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.
+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 a payment method:
+| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Parameters regarding the status of a payment (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| 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 |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Parameters regarding the status of a payment (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Processed data | +
|---|---|
Entry of data in QENTA payment page |
+Bank |
+
Forwarding of data to QENTA prior to payment initiation |
+No |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Proce ssed data | +
|---|---|
Parameters regarding the status of a payment (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| 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 |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Parameters regarding the status of a payment (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Processed data | +
|---|---|
Entry of data in QENTA payment page |
+- |
+
Forwarding of data to QENTA prior to payment initiation |
+No |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Parameters regarding the status of a payment (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Processed data | +
|---|---|
Entry of data in QENTA payment page |
+- |
+
Forwarding of data to QENTA prior to payment initiation |
+No |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Additonal Response Parameters |
++ |
Parameters regarding the status of a payment (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Processed data | +
|---|---|
Entry of data in QENTA payment page |
+- |
+
Forwarding of data to QENTA prior to payment initiation |
+No |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Parameters regarding the status of a payment (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| Parameter Type | +Processed data | +
|---|---|
Entry of data in QENTA payment page |
+- |
+
Forwarding of data to QENTA prior to payment initiation |
+No |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Parameters regarding the status of a payment (Standard) |
++ |
| Parameter Type | +Processed data | +
|---|---|
Entry of data in QENTA payment page |
+- |
+
Forwarding of data to QENTA prior to payment initiation |
+No |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Additonal Response Parameters |
++ |
Parameters regarding the status of a payment (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| 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 |
+
| Parameter Type | +Processed data | +
|---|---|
Required Request Parameters (payment method) |
++ |
Optional Request Parameters (payment method) |
++ |
Additional Request Parameters (payment method) |
++ |
Additional Request Parameters B2B (payment method) |
++ |
Required Request Parameters (Standard) |
++ |
Additional Required Request Parameter (Standard) |
++ |
Optional Request Parameters (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
Plugin-Specific Data (Standard) |
+- |
+
| Parameter Type | +Processed data | +
|---|---|
Additonal Response Parameters |
++ |
Parameters regarding the status of a payment (Standard) |
++ |
1 to N Optional Custom Parameters (Standard) |
++ |
| 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 |
+
The basic version of QMORE already includes various functions that are described in detail below.
+| 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. |
+
2. Return of masked credit card number |
+This feature involves the processing of personal data, i.e. |
+
3. Return of transaction reference number |
+This feature allows the merchant to obtain a unique reference number of the transaction via parameter |
+
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: |
+
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: |
+
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 |
+
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: |
+
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: |
+
9. Return of credit card expiration date |
+This feature allows the merchant to obtain the expiration date of the used credit card via parameter |
+
10. Selective automatic deposit |
+Via parameter |
+
11. Selection of credit card brand |
+This feature allows the merchant to define via the additional parameter |
+
12. Unique order number |
+The parameter |
+
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).
+| 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. |
+
| 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. |
+
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. |
+
| 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. |
+
Auf dieser Infoseite können Sie sich über alle Daten informieren, die das Produkt QCALL Checkout Terminal verarbeitet.
+Die Datenverarbeitung von QCALL ist umso umfangreicher, je größer der vom Merchant bestellte Produktumfang ist. Bei der Bestellung des Produkts QCALL kann unterschieden werden zwischen
+1 Basisprodukt, optional erweitert um
+1 bis N Zahlungsmitteln, und/oder
+0 bis N optionalen Zusatzfeatures
+Die allgemeine Funktionsweise des Produkts QCALL-sowohl in seiner Basisversion als auch abhängig vom Einsatz verschiedener Zahlungsmittel-ist zudem hier ausführlich beschrieben: Bedienungsanleitung QCALL
+Sämtliche hier angegebenen personenbezogenen Parameter müssen verarbeitet werden, um das Produkt QCALL in seiner Basisversion dem Merchant zur Verfügung stellen zu können (Zweck der Datenverarbeitung).
+Die hier angezeigten Parameter unterteilen sich in Parameter
+die unabhängig vom Zahlungsmittel verarbeitet werden (Standard)
+die abhängig vom jeweiligen Zahlungsmittel verarbeitet werden (Zahlungsmittel)
+| Parameter | +Betroffene Person | +Personenbezug | +
|---|---|---|
Betrag |
+Merchant, Endkunde |
+Umsatzhöhe (Betrag) der Transaktion |
+
Währung |
+Merchant, Endkunde |
+Währungscode des Betrags |
+
| Parameter | +Betroffene Person | +Personenbezug | +
|---|---|---|
Vorname |
+Endkunde |
+Vorname des Endkunden |
+
Nachname |
+Endkunde |
+Nachname des Endkunden |
+
Firma |
+Endkunde |
+Firmenname, unter dem die betreffenden Artikel |
+
(Produkte) bestellt werden |
+Adresse |
+Endkunde |
+
| Parameter | +Betroffene Person | +Personenbezug | +
|---|---|---|
Karteninhaber der Kreditkarte |
+Endkunde |
+Name des Karteninhabers |
+
Credit card number |
+Endkunde |
+Kreditkartennummer des Endkunden |
+
Expiration date |
+Endkunde |
+Ablaufdatum der benutzten Kreditkarte |
+
CVC |
+Endkunde |
+Kartenprüfnummer der Kreditkarte des Endkunden |
+
| Parameter | +Betroffene Person | +Personenbezug | +
|---|---|---|
Kontoinhaber |
+Endkunde |
+Inhaber des Endkunden-Bankkontos |
+
IBAN |
+Endkunde |
+IBAN des Endkunden |
+
BIC |
+Endkunde |
+Bank Identification Code der Bank des Endkunden |
+
Für jedes zusätzlich zum Basisprodukt QCALL bestellte Feature ist hier ersichtlich, welche Daten das jeweilige Feature verarbeitet.
+| Feature | +Verarbeitete Daten und Datenschutzinfos | +
|---|---|
1. Weitere Zugänge zum QENTA Payment Center |
+Für die Web-Applikationen des Händlerlogins wird ein neuer Zugang für den Merchant angelegt, der nicht personengebunden ist. Für den Zugang ist ein Benutzername und ein Passwort erforderlich. Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten. |
+
2. Zusätzliche Währungen |
+Abhängig vom Produktkatalog des Merchants sind bestimmte Produkte in 1 bis N Währungen zahlbar, die von QENTA als Konfigurationseinstellungen hinterlegt werden. Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten. Allerdings ist die Währung der Zahlung selbst ein personenbezogenes Datum, die über die Währung der abgewickelten Zahlungstransaktion des Merchants Auskunft gibt. |
+
3. Wiederkehrende Zahlung |
+Mit diesem Feature wird der Merchant über eine Konfigurationseinstellung seitens QENTA in die Lage versetzt, wiederkehrende Zahlungen durchführen. Für die Durchführung einer wiederkehrenden Zahlung ist die Option "Recurring Payment" unter Angabe der Order Number auszuwählen wie in der QCALL-Dokumentation näher beschrieben. Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten. |
+
4. Sofortige Buchung |
+Über diese Konfigurationseinstellung wird die Buchung sofort durchgeführt (anstatt einer Genehmigung der Zahlungstransaktion mit anschließender manueller Buchung). Dadurch kommt es zu keiner zusätzlichen Verarbeitung von personenbezogenen Daten. |
+
This chapter provides information on all data that are processed by our solution QCALL Checkout Terminal.
+QCALL Checkout Terminal data processing volume increases with the services contracted. When ordering QCALL Checkout Terminal the merchant may acquire:
+1 basic solution, optionally extendable with
+1 to N payment methods, and/or
+0 to N optional and additional features
+Additionally, the general functioning of the product QCALL-both in its basic version and when using different payment methods-is also described in detail here: Using QCALL
+All indicated parameters need to be processed to ensure that the solution QCALL Checkout Terminal, 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)
+| Parameter | +Data Subject | +Personal Data | +
|---|---|---|
Amount |
+merchant, consumer |
+Amount of the transaction |
+
Currency |
+merchant, consumer |
+Currency used for the payment |
+
| Parameter | +Data Subject | +Personal Data | +
|---|---|---|
First Name |
+consumer |
+First name of the consumer |
+
Last Name |
+consumer |
+Last name of the consumer |
+
Company |
+consumer |
+Name of the company ordering the relevant items (products) |
+
Adresse |
+consumer |
+Address of the consumer |
+
| Parameter | +Data Subject | +Personal Data | +
|---|---|---|
Card holder |
+consumer |
+Name of the cardholder |
+
Credit card number |
+consumer |
+Credit card number of the consumer |
+
Expiration date |
+consumer |
+Ablaufdatum der benutzten Kreditkarte |
+
CVC |
+consumer |
+Expiration date of the credit card user by the consumer |
+
| Parameter | +Data Subject | +Personal Data | +
|---|---|---|
Account holder |
+consumer |
+Owner of the consumers bank account |
+
IBAN |
+consumer |
+Account Number of the consumer’s bank |
+
BIC |
+consumer |
+Bank Identification Code of the consumer’s bank |
+
This chapter provides information on the data processed for each feature that has been added to the basic QCALL Checkout Terminal solution.
+| Feature | +Processing of data and information on the protection of personal data | +
|---|---|
1. 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. |
+
2. Additional currencies |
+Depending on the merchant’s product portfolio, certain products may be paid in 1 to N currencies, which are defined by QENTA in the configuration setting. Thus, no additional processing of personal data takes place. However, the currency of the payment itself is considered personal data that relates to the currency of the processed transaction of the merchant. |
+
3. Recurring payment |
+Based on a configuration setting provided by QENTA, this feature allows the merchant to carry out recurring payments. A recurring payment is carried out by selecting option "Recurring Payment" and stating the respective order number as described in detail in the QCALL Documentation. Thus, no additional processing of personal data takes place. |
+
4. Immediate deposit |
+This configuration setting allows an immediate deposit (instead of an authorization of the transaction with subsequent manual deposit). Thus, no additional processing of personal data takes place. |
+
The Payment Card Data Security Standard is a binding set of rules and procedures established by four major credit card companies (Visa, Mastercard, Discover and American Express) in 2004 and is aimed at companies that accept credit cards as payment method. The primary objective of PCI DSS is the prevention of fraud and theft of credit card data on the Internet.
+Self-Assessment Questionnaires (SAQ) are tools that merchant may use upon request by the acquirer to determine whether the online shop meets established PCI DSS requirements.
+To ensure the highest level of data security, the acquirer will request to fill out a specific Self-Assessment Questionnaire (SAQ) prior to concluding an acceptance contract with the merchant. The handling and management of sensitive financial data in online shops is always a crucial issue in fulfilling the relevant SAQs and obtaining PCI-compliance. However, there is no need for the online shop to handle or store sensitive data since all necessary financial and personal data required for the payment process are handled by the QENTA Checkout Server.
+| + + | ++When choosing QENTA as the PCI-compliant third-party payment processor, it becomes much easier to comply with the relevant SAQ requested by the acquirer and no additional PCI-compliance for the online shop is required. + | +
There are various SAQ versions available to select from to best suit the business profile. The following SAQs are applicable when using QENTA products:
+| SAQ version | +Business scenario | +Applicable for QENTA solution | +
|---|---|---|
SAQ A |
+Applicable for card-not-present merchants, when all cardholder data functions are outsourced to a PCI-compliant payment processor. +Eligible e-commerce implementations: when the merchant website is entirely hosted and administered by a compliant third-party payment processor, or provides an iframe to a PCI-compliant third-party payment processor or contains a URL link redirecting consumers from the merchant website to a PCI-compliant payment processor. Visit implementation examples eligible for SAQ A vs. SAQ A-EP for more information and details. |
+QPAY Checkout Page in the native app as a web view. |
+
QMORE Checkout Seamless with "PCI DSS SAQ A Compliance" in the native app as a web view. |
+||
SAQ A-EP |
+Applicable for card-not-present merchants who partially outsource their e-commerce payment channel to PCI DSS validated third parties and don’t electronically store, process or transmit any cardholder data on their systems or premises. |
+QMORE Checkout Seamless without "PCI DSS SAQ A Compliance" in the native app as a web view. |
+
SAQ C-VT |
+Applicable for merchants using only web-based virtual terminals, without electronic cardholder Data Storage. |
+QCALL Checkout Terminal |
+
SAQ D |
+All other merchants not covered by any SAQ and all service providers defined by a payment brand as eligible to complete a SAQ. |
+QFILE Checkout Automated |
+
| + + | ++Put the file(s) where the secret or password is defined within a folder on the file system of the web server which can’t be accessed by users accessing the web server via their web browsers. + | +
It is strongly recommended to encrypt any communication in the online shop to allow access only by secure communication via https.
+QPAY Checkout Page and QMORE Checkout Seamless also use secure communication based on https and if the online shop or parts of the online shop are accessed by http the consumer in the online shop will receive the security warning from the web browser.
+It is strongly recommended to save all relevant order data of each purchase and of each consumer before starting the QPAY Checkout Page or QMORE Checkout Seamless immediately after the payment has been made by the consumer. This way assign and correlate each order with the relevant payment process results at a later date.
+Ensure, according to the functionalities of the online shop, that the consumer has no possibility to change the items in the shopping basket once the payment process was started.
+| + + | ++Check all security updates available for the software that is used within the online shop, database, and web server on a regular basis. + | +
Have a look at OWASP regarding typical security risks and their impacts on online sites.
+Configure scheduled backups for all order and checkout-related information of the consumers of the online shop to ensure that the merchant has these data at their disposal in case of any later complaints or frauds.
+A secret is a pre-shared key that is only known to the merchant, the integrator of the online shop and QENTA Payment CEE.
+The secret is used to secure the transfer of all sensitive parameters and their values between the online shop and the QPAY Checkout Page and QMORE Checkout Seamless.
+| + + | +
+
+
+
|
+
If there is any suspicion that the pre-shared key is known to unauthorized persons contact our integration specialists immediately to request the creation and submission of a new secret.
+A fingerprint is a method to ensure that sensitive parameters and their values sent from the online shop to the QENTA Checkout Server and vice versa are not changed by anyone while transferring the data over the Internet.
+A fingerprint is created by concatenating all parameter values to a string and hashing this string by an HMAC-SHA-512 algorithm using the secret as a cryptographic key.
+When submitting data from the online shop to QENTA Checkout products the merchant also transmits the fingerprint and the name and order of all parameters used for creating the fingerprint. The QENTA Checkout Server then creates the fingerprint of all received parameter values with the specific secret stored in the QENTA Checkout Server. If the fingerprint that is sent and the fingerprint computed on the QENTA Checkout Server are identical, the values of the parameters transmitted by the merchant were not modified, e.g. during a man-in-the-middle attack.
+| + + | +
+For response fingerprint calculation: if magic_quotes_gpc or magic_quotes_runtime is enabled on the server or in the shop, use slashes to remove unnecessary slashes within the fingerprint seed.
+ |
+
When integrating QPAY Checkout Page or QMORE Checkout Seamless into the online shop adjust the security settings of the firewall and enable outgoing communication to the server:
+api.qenta.com-212.183.46.18
To receive confirmation information from QENTA regarding a transaction via the confirmUrl enable incoming communication from our following IP address 212.183.46.16/28.
Merchants which are using our shop plugins have to switch the endpoint from Wirecard to new QENTA API.
+| Old endpoint | +New endpoint | +
|---|---|
|
+
|
+
|
+
| + + | +
+Change only the first part of the URL, everything after .com/ stays the same!
+ |
+
| From | +To | +
|---|---|
|
+
|
+
|
+
|
+
Choose the shop system in the list below and change the endpoint accordingly.
+| Plugin Name | +Repository | +Path | +Line | +
|---|---|---|---|
Checkout Client Library |
++ |
|
+35, 36 |
+
Checkout Client Library |
++ |
|
+34-36 |
+
Demandware (Salesforce Commerce Cloud) WCP |
++ |
|
+490 |
+
ePages WCP |
++ |
|
+20 |
+
Gambio WCP |
++ |
|
+42 |
+
Gambio WCS |
++ |
|
+34 -36 |
+
JTL-Shop WCP |
++ |
|
+35, 36 |
+
Magento QCP |
++ |
|
+35, 36 |
+
Magento QCS |
++ |
|
+34-36 |
+
Magento 2 QCP |
++ |
|
+35, 36 |
+
Magento 2 QCS |
++ |
|
+34-36 |
+
modified eCommerce WCP |
++ |
|
+35, 36 |
+
modified eCommerce WCS |
++ |
|
+34-36 |
+
Opencart QCP |
++ |
|
+35, 36 |
+
osCommerce WCP |
++ |
|
+32 |
+
OXID eSales QCS |
++ |
|
+34-36 |
+
OXID eSales WCP |
++ |
|
+45 |
+
Prestashop QCP |
++ |
|
+35, 36 |
+
Prestashop WCS |
++ |
|
+34-36 |
+
SAP Event Ticketing WCS |
++ |
|
+27-29 or 42-49 |
+
Shopware QCP |
++ |
|
+35, 36 |
+
Shopware QCS |
++ |
|
+34-36 |
+
Ubercard WCP |
++ |
|
+35, 36 |
+
Virtuemart 3 QCP |
++ |
|
+35, 36 |
+
WooCommerce QCP |
++ |
|
+35, 36 |
+
WooCommerce QCS |
++ |
|
+34 -36 |
+
xt:Commerce 3 WCP |
++ |
|
+28-30 |
+
xt:Commerce 4 WCP |
++ |
|
+35, 36 |
+
After completing integration and testing implementation the merchant can switch from demo mode to test mode. During test mode, there is communication between the online shop and a test area provided by the relevant financial service provider. The payment process is only simulated and no money is transferred.
+| + | QPAY Checkout Page | +QMORE Checkout Seamless | +
|---|---|---|
| + |
|
+|
|
+
|
+|
| + |
|
+
|
+
QPAY Checkout Page |
+|
Data |
+Value |
+
| + |
|
+
secret |
+
|
+
| + |
|
+
QMORE Checkout Seamless |
+|
Data |
+Value |
+
| + |
|
+
secret |
+
|
+
| + |
|
+
| + | QPAY Checkout Page | +QMORE Checkout Seamless | +
|---|---|---|
| + |
|
+|
| + |
|
+
|
+
|
+
|
+|
| Payment Method | +Credentials Available | +
|---|---|
| + | ✔ |
+
| + | + |
| + | + |
| + | + |
| + | ✔ |
+
| + | + |
| + | ✔ |
+
| + | ✔ |
+
| + | + |
| + | + |
Invoice (by Payolution) |
++ |
| + | + |
| + | ✔ |
+
| + | ✔ |
+
| + | + |
| + + | +
+For testing a Credit Card, the orderDescription parameter must be set to Test:0000, otherwise, the transaction will be declined.
+ |
+
| Brand | +Card number | +Expiry date | +CVC | +ACS password | +
|---|---|---|---|---|
Visa |
+
|
+Any in future |
+Any three digits |
+
|
+
Mastercard |
+
|
+Any in future |
+Any three digits |
+
|
+
Amex |
+
|
+Any in future |
+Any three digits |
+
|
+
| Brand | +Data | +Value | +
|---|---|---|
Visa |
+Card number |
+
|
+
Expiry date |
+Any in future |
+|
CVC |
+Any three digits |
+|
ACS password |
+
|
+|
Mastercard |
+Card number |
+
|
+
Expiry date |
+Any in future |
+|
CVC |
+Any three digits |
+|
ACS password |
+
|
+
The amount is limited to 1000€.
+Choose: “PSA Stuzza Bank (STZZATWWXXX)”
+
+Benutzername |
+
|
+
Passwort |
+
|
+
+Click “TAN anfordern” and use the TAN to sign the transaction.
+
+Click “TAN SENDEN” to finish the transaction.
+First, the merchant has to create a paypal sandbox account.
+After creating the account, the merchant can log in and test with their own credentials.
| + + | ++The consumerMerchantCrmId parameter is required when initiating a paysafecard payment, otherwise, the transaction will be declined. + | +
| + + | ++The consumerMerchantCrmId parameter is required when initiating a paysafecard payment, otherwise, the transaction will be declined. + | +
On the Paysafecard page, select “paysafecard”.
+
+Then enter the paysafecard key 5682326421231467.
+| Country | +Sort code | +User ID and password | +Account number | +TAN | +
|---|---|---|---|---|
Germany |
+88888888 |
+Arbitrary |
+Select one from the list. |
+Arbitrary |
+
Belgium |
+999 |
+Arbitrary |
+Select one from the list. |
+Arbitrary |
+
All other countries |
+00000 |
+Arbitrary |
+Select one from the list. |
+Arbitrary |
+
| Country | +Data | +Value | +
|---|---|---|
Germany |
+Sort code |
+
|
+
User ID and password |
+Arbitrary |
+|
Account number |
+Select one from the list. |
+|
TAN |
+Arbitrary |
+|
Belgium |
+Sort code |
+
|
+
User ID and password |
+Arbitrary |
+|
Account number |
+Select one from the list. |
+|
TAN |
+Arbitrary |
+|
All other countries |
+Sort code |
+
|
+
User ID and password |
+Arbitrary |
+|
Account number |
+Select one from the list. |
+|
TAN |
+Arbitrary |
+
Choose one of the described banks at the top:
+
+Choose any account number and PIN.
+
+Select an account.
+
+Use 12345 as TAN as described.
+| + + | ++The consumerMerchantCrmId parameter is required when initiating a SEPA payment, otherwise, the transaction will be declined. + | +
| + + | ++The consumerMerchantCrmId parameter is required when initiating a SEPA payment, otherwise, the transaction will be declined. + | +
Value of parameter IBAN |
+Status | +
|---|---|
|
+Not accepted. |
+
|
+Accepted, but not settled yet (will remain on status 1). |
+
|
+Accepted, but canceled before settlement (status 2 in the /transaction Request). |
+
|
+Status 3 (paid) in the /transaction Request. |
+
|
+Status 3 (paid) and later status 4 (Chargeback) with Token (RFND) in the /transaction Request. |
+
|
+Status 3 (paid) and later status 4 (Chargeback) with Token (ACT) in the /transaction Request. |
+
|
+Status 3 (paid) and later status 4 (Chargeback) with Token (NSF) in the /transaction Request. |
+
|
+Status 3 (paid) and later status 4 (Chargeback) with Token (OTHR) in the /transaction Request. |
+
|
+Status 3 (paid) and later status 4 (Chargeback) with Token (FRM) in the /transaction Request. |
+
In order to guarantee the highest level of security, we want our merchants that are using our QTILL Checkout Enterprise solution, to carry out a certain adaptation which includes a new truststore certificate and the new endpoints for QTILL Checkout Enterprise.
+| + + | ++As of January 24th 2021, the new endpoints have to be placed in the production system as the old ones won’t be accessible anymore. + | +
Endpoints
+Within qtill.properties values have to changed within QTILL_HOST_URL.
Settings accept only one URL.
+| Old Endpoints | +New Endpoint Notes | +
|---|---|
| + | + |
| + | + |
| + + | ++Be aware to use standard https port 443 and keep firewall settings in mind during updates. + | +
QTILL_HOST_URL=https://checkout.wirecard.com/enterprise-demo+
QTILL_HOST_URL=https://api.qenta.com/enterprise-demo+
+QTillSettings settings = QTillSettings(new URL("https://api.qenta.com/enterprise"));The new endpoint is using a server certificate from a different certificate authority. Therefore, the existing truststore file has to be replaced with the one in the following archive. Keep in mind that the certificate expires on November 2021. We will provide a new one in the course of time.
+Click here to download the truststore file.
+| Name of the old Truststore | +Name of the new Truststore | +Notes | +
|---|---|---|
|
+
|
+No changes to the password. The password from productive truststore has to be used! |
+
TRUSTSTOREFILE=/usr/local/qenta/qtill/wce-trust.jks +TRUSTSTOREPASSWORD=<your productive truststore password>+
TRUSTSTOREFILE=/usr/local/qenta/qtill/qtill-trust-old.jks +TRUSTSTOREPASSWORD=<your productive truststore password>+
settings.setTruststoreFile(new File("qtill-trust-old.jks"));
+settings.setTruststorePassword("<truststore password>");Click here to return to the start page for the upcoming changes in January 2021.
+In order to guarantee the highest level of security, we want our merchants that are using our QTILL Checkout Enterprise solution, to carry out a certain adaptation which includes a new truststore certificate.
+The existing truststore file has to be replaced with the one in the following archive: download here.
+| + + | ++There are no changes to the password and the file name. + | +
TRUSTSTOREFILE=/usr/local/qenta/qtill/qtill-trust-old.jks +TRUSTSTOREPASSWORD=<your productive truststore password>+
QFILE Checkout Automated is intended for non-real-time critical applications such as catalog orders and subscriptions. The payment details of the consumers are prepared in tabular format, uploaded, and automatically processed.
+Here is a demo access for testing purposes.
+The merchant needs to create a transaction file that includes all necessary payment data. It must be converted into a tab-delimited text file (image example below) since otherwise the transactions can’t be uploaded.
+
+After successful login, QFILE Checkout Automated opens and the merchant selects and uploads the relevant file which is then automatically processed.
+Example of an xls file to upload in QFILE Checkout Automated: request example.
+Defining the file format
+The max. number of uploaded transactions must not exceed 3000 transactions per file, the max. file size must not exceed 2 MB.
+Before uploading the file remember to convert the xls file into a tab-delimited text file since otherwise the transactions are not recognized and not uploaded.
+If the consumer is a company instead of a private person, enter Firma or Fa in the column "First name" and the relevant company’s name in the column "Last name".
+| + + | ++Do not use the special character “ ' “ e.g. “Sarah O’Brian” otherwise all transactions in the file can’t be processed. + | +
Use the following format for uploading the payment details of the customers and remember that the number of headers must correspond exactly to the number of columns.
+| Credit card number | +Data | +Value | +
|---|---|---|
|
+Expiration date |
+
|
+
CVC |
+Has to be empty. |
+|
Currency |
+
|
+|
Amount |
+
|
+|
First name |
+
|
+|
Last name |
+
|
+|
Number |
+
|
+|
Customer statement |
++ | |
Credit card number |
+Data |
+Value |
+
|
+Expiration date |
+
|
+
CVC |
+Has to be empty. |
+|
Currency |
+
|
+|
Amount |
+
|
+|
First name |
+
|
+|
Last name |
+
|
+|
Number |
+
|
+|
Customer statement |
++ | |
Credit card number |
+Data |
+Value |
+
|
+Expiration date |
+
|
+
CVC |
+Has to be empty. |
+|
Currency |
+
|
+|
Amount |
+
|
+|
First name |
+
|
+|
Last name |
+
|
+|
Number |
+
|
+|
Customer statement |
++ | |
Credit card number |
+Data |
+Value |
+
|
+Expiration date |
+
|
+
CVC |
+Has to be empty. |
+|
Currency |
+
|
+|
Amount |
+
|
+|
First name |
+
|
+|
Last name |
+
|
+|
Number |
+
|
+|
Customer statement |
+
|
+
| IBAN | +Data | +Value | +
|---|---|---|
|
+BIC |
++ |
Currency |
+
|
+|
Amount |
+
|
+|
First name |
+
|
+|
Last name |
+
|
+|
Number |
+
|
+|
Customer statement |
++ |
| IBAN | +Data | +Value | +
|---|---|---|
|
+BIC |
++ |
|
+
|
+|
|
+
|
+|
|
+
|
+|
|
+
|
+|
|
+
|
+|
|
+
|
+|
|
+
|
+|
|
+
|
+|
|
+
|
+|
|
+
|
+
| Data | +Value | +
|---|---|
IBAN |
+
|
+
BIC |
++ |
MandateId |
+
|
+
MandateSignatureDate |
+
|
+
CreatorId |
+
|
+
Due date |
+
|
+
Currency |
+
|
+
Amount |
+
|
+
First name |
+
|
+
Last name |
+
|
+
Number |
+
|
+
Customer statement |
+
|
+
| + + | ++Value for the column "BIC" for SEPA Direct Debit is optional. + | +
| Source order number | +Data | +Value | +
|---|---|---|
|
+Currency |
+
|
+
Amount |
+
|
+|
First name |
+
|
+|
Last name |
+
|
+|
Number |
+
|
+|
Customer statement |
++ | |
Merchant CRM ID |
++ | |
Source order number |
+Data |
+Value |
+
|
+Currency |
+
|
+
Amount |
+
|
+|
First name |
+
|
+|
Last name |
+
|
+|
Number |
+
|
+|
Customer statement |
+
|
+|
Merchant CRM ID |
++ | |
Source order number |
+Data |
+Value |
+
|
+Currency |
+
|
+
Amount |
+
|
+|
First name |
+
|
+|
Last name |
+
|
+|
Number |
+
|
+|
Customer statement |
+
|
+|
Merchant CRM ID |
+
|
+
| + + | ++Merchant CRM ID should have only 40 characters. + | +
After uploading the payment details of the customers, the file is processed and the transactions can be downloaded as a tab-delimited text file which can be converted back into an xls file.
+| + + | ++The format is representing the returned transactions and the number of headers must correspond exactly to the number of columns. + | +
| Credit card number | +Data | +Value | +
|---|---|---|
|
+Currency |
+
|
+
Amount |
+
|
+|
First name |
+
|
+|
Last name |
+
|
+|
Number |
+
|
+|
Order number |
+
|
+|
Authcode |
+
|
+|
Message |
+
|
+|
Credit card number |
+Data |
+Value |
+
|
+Currency |
+
|
+
Amount |
+
|
+|
First name |
+
|
+|
Last name |
+
|
+|
Number |
+
|
+|
Order number |
+
|
+|
Authcode |
+
|
+|
Message |
+
|
+|
Credit card number |
+Data |
+Value |
+
|
+Currency |
+
|
+
Amount |
+
|
+|
First name |
+
|
+|
Last name |
+
|
+|
Number |
+
|
+|
Order number |
+
|
+|
Authcode |
+
|
+|
Message |
+
|
+
| Credit card number | +Data | +Value | +
|---|---|---|
|
+Currency |
+
|
+
Amount |
+
|
+|
First name |
+
|
+|
Last name |
+
|
+|
Customer statement |
+
|
+|
Number |
+
|
+|
Order number |
+
|
+|
Authcode |
+
|
+|
Message |
+
|
+
| IBAN | +Data | +Value | +
|---|---|---|
|
+BIC |
++ |
Currency |
+
|
+|
Amount |
+
|
+|
First name |
+
|
+|
Last name |
+
|
+|
Number |
+
|
+|
Customer statement |
+
|
+|
Order number |
+
|
+|
Authcode |
+
|
+|
Message |
+
|
+
| IBAN | +Data | +Value | +
|---|---|---|
|
+BIC |
++ |
MandateId |
+
|
+|
Mandate signature date |
+
|
+|
Creditor Id |
+
|
+|
Due date |
+
|
+|
Currency |
+
|
+|
Amount |
+
|
+|
First name |
+
|
+|
Last name |
+
|
+|
Number |
+
|
+|
Customer statement |
+
|
+|
Order number |
+
|
+|
Authcode |
+
|
+|
Message |
+
|
+
| Data | +Value | +
|---|---|
IBAN |
+
|
+
BIC |
++ |
MandateId |
+
|
+
Mandate signature date |
+
|
+
Creditor Id |
+
|
+
Due date |
+
|
+
Currency |
+
|
+
Amount |
+
|
+
First name |
+
|
+
Last name |
+
|
+
Number |
+
|
+
Customer statement |
+
|
+
Order number |
+
|
+
Authcode |
+
|
+
Message |
+
|
+
| + + | ++Value for the column "BIC" for SEPA Direct Debit is optional. + | +
| Source order number | +Data | +Value | +
|---|---|---|
|
+Currency |
+
|
+
Amount |
+
|
+|
Order number |
+
|
+|
Authcode |
+
|
+|
Message |
+
|
+
| Source order number | +Data | +Value | +
|---|---|---|
|
+Currency |
+
|
+
Amount |
+
|
+|
Customer statement |
+
|
+|
Order number |
+
|
+|
Authcode |
+
|
+|
Message |
+
|
+
| Currency | +Amount | +Order number | +Message | +
|---|---|---|---|
|
+
|
+
|
+
|
+
| Currency | +Amount | +Customer statement | +Order number | +Message | +
|---|---|---|---|---|
|
+
|
+
|
+
|
+Credit note OK |
+
| Data | +Value | +
|---|---|
|
+
|
+
|
+
|
+
|
+
|
+
|
+
|
+
|
+
|
+
QENTA Checkout Journal is a web interface that analysis all transactions carried out in the Online Shop – independent of the payment result. It gives an overview of transaction details when doing a checkout for QPAY Checkout Page and QMORE Checkout Seamless. Can be used during the integration process and no installation of the software is required.
+The login can be found at the following link.
+
+The username and password must be entered
+When the login was successful, a summary of the login data is displayed.
+| + + | ++After the first login, a new password must be set. + | +
+| Field name | +Data Type | +Description | +||
|---|---|---|---|---|
| + | Numeric, up to 9. |
+The order number of payment. Only searchable if transaction was successful. |
+||
Date (not before) |
+Date as |
+All initiations after the chosen date. |
+||
Date (not after) |
+Date as |
+
+
+All initiations before the chosen date. +
+
|
+||
Status |
+Alphanumeric with special characters |
+
+
+The status of a transaction. +Accepted values: +
+
|
+||
Client IP |
+Alphanumeric with special characters. |
+Client IP address. |
+||
Initiation parameter value |
+Data type of used parameter. |
+Initiation parameter value (all parameters that are used for an initiation e.g. |
+||
Return parameter value |
+Data type of used parameter. |
+Return parameter value. |
+
| + + | ++Checkout Journal can display a maximum of 1000 sessions. + | +
+| Field name | +Description | +
|---|---|
Initiation timestamp |
+Timestamp of initiation payment e.g. |
+
Last activity timestamp |
+Timestamp of the last activity e.g. |
+
| + | Unique ID of the online shop within the customer ID. |
+
Session |
+Unique Session IDentifier for each invoked session. |
+
Result |
+Result of a payment process ( |
+
| + | The number that the merchant got after the transaction is successful. |
+
Transaction details include:
+| + + | ++All transaction details can be exported as a PDF file and the example below is based on this pdf example. + | +
This general information about a transaction can be included:
+| Field name | +Description | +
|---|---|
Initiation timestamp |
+Timestamp of initiation payment. |
+
Last activity timestamp |
+Timestamp of the last activity. |
+
| + | Unique ID assigned to each merchant by QENTA. |
+
| + | Unique ID of the online shop within the customer ID. |
+
Session |
+Unique Session IDentifier for each invoked session. |
+
Result |
+Result of a payment process ( |
+
| + | The unique order number of the successful payment within the session. |
+
UserAgent |
+User Agent that consumers have used. |
+
Client-IP |
+Client IP address. |
+
Protocol Version |
+The protocol version number. |
+
Application Version |
+The version of the application. |
+
Hostname |
+Hostname |
+
Initiation parameters are different depending on the transaction that is made.
+| Field name | +Description | +
|---|---|
|
+Specific URL. |
+
| + | Unique ID assigned to each merchant by QENTA. |
+
| + | The parameter defines the unique identifier for the online shop within |
+
| + | URL of the online shop when a payment process was successful. |
+
| + | URL of the online shop when an error occurred within a payment process. |
+
| + | URL of the online shop when a payment process has been canceled. |
+
| + | URL of web page containing the contact information. |
+
| + | URL of the online shop where the online shop logo is located. |
+
| + | Amount of payment. |
+
| + | Currency code of amount. |
+
| + | Language for displayed texts on the payment page. |
+
| + | Unique description of the consumer’s order. |
+
| + | Text displayed to the consumer during the payment process. |
+
|
+Custom parameter. |
+
|
+Custom parameter. |
+
| + | Check for duplicate requests done by the consumer. |
+
| + | Ordered list of parameters used for calculating the fingerprint. |
+
| + | Computed fingerprint of the parameter values as given in the |
+
|
+Custom parameter. |
+
| + | Hex code RGB color value as a background color for the brand image containing the credit card logos. |
+
| + | Selected payment method of the consumer. |
+
| + | Window name of a browser window where the payment page is opened. |
+
| + | E-mail address of the consumer. |
+
| + | Birth date of the consumer. |
+
| + | First name of the consumer. |
+
| + | Last name of the consumer. |
+
| + | Name of the street and optionally the house number. |
+
| + | The house number if not already set in |
+
| + | Billing city. |
+
| + | Billing zip code. |
+
| + | Billing state. |
+
| + | Billing country code ISO 3166-1. |
+
| Field name | +Description | +
|---|---|
| + | Amount of payment. |
+
| + | Currency code of amount. |
+
| + | Selected payment method of the consumer. |
+
| + | Sub-selection of financial institutions regarding to pre-selected payment method. |
+
| + | Language used for displayed texts on payment page. |
+
| + | The unique order number of the successful payment within the session. |
+
| + | Result of payment process ( |
+
|
+Custom parameter. |
+
|
+Custom parameter. |
+
|
+Custom parameter. |
+
| + | Returns |
+
| + | Last four digits of the credit card number. |
+
| + | Expiry date of credit card in format |
+
| + | Name of holder of credit card which can only be used if the acquirer supports it. |
+
| + | PCI-compliant masked card number in the format: first 6 digits and last 4 digits of card number with "*" in-between depending on the current format of the card number. |
+
| + | Technical reference number of the processor. |
+
| + | Ordered list of parameters used for calculating the fingerprint. |
+
| + | Returned fingerprint of the parameter values as given in the |
+
Administrative dashboard application for link management.
+
+| + + | ++Login credentials will be provided by our integration specialists. + | +
| + + | ++Merchant have to set manually their own URLs in PayByLink settings, otherwise the payment will be declined. + | +
| URL | +Description | +
|---|---|
| + | URL of online shop where the consumer is forwarded when the payment process has been completed. |
+
| + | URL of online shop where the consumer is forwarded when the payment process could not determine a result yet. |
+
| + | URL of the page where consumer is forwarded when the payment process has been canceled. |
+
| + | URL of online shop where consumer is forwarded when the payment process has failed for some reason. |
+
| + | URL of a web page in online shop which informs consumer about the different possibilities to get in contact with the merchant. |
+
| + + | ++If a merchant does not have own links, QENTA’s predefined links from table below can be used. + | +
|
+https://payments.qenta.com/success/ |
+
|
+https://payments.qenta.com/pending/ |
+
|
+https://payments.qenta.com/failure/ |
+
|
+https://payments.qenta.com/cancel/ |
+
| + + | +
+serviceUrl contains the imprint of the merchant web page so that’s why QENTA can’t provide that URL.
+ |
+
At the top of paybylink table choose which links will be shown by status:
+Status can be:
+Valid
+Expired
+Deactivated
+
+Adjust the table by marking active columns. Possibilities that can be selected:
+| Columns | +Description | +
|---|---|
Link |
+Name of the link. |
+
Status |
+Status of the link: |
+
Last Payment |
+Date of the last payment that is made. Either date is shown, or "no payment yet". |
+
Total Sales |
+Displays the sum of all payments with a link. |
+
Price per link |
+Displays how much is the price per link. |
+
Time created |
+Date when link is created. |
+
Valid From |
+Date when the link is valid from. |
+
Valid To |
+Date until the link is valid. |
+
The form of the date is DD/MONTH/YYYY.
On the right side, there is a search form for researching a table by the title of the links or their status.
+If the merchant does not want the link to be used anymore but wants to have information about the link in the table, then disable should be used.
+| + + | ++If the link is deleted there is no possibility of being returned and will not be visible in the table. + | +
For creating a new link fulfill the required Basic Link Settings.
+
+| Parameter | +Optional or required | +Description | +
|---|---|---|
Title |
+Required |
+Title of the link that will be shown in the table. |
+
Description |
+Required |
+The description will be shown to the Customer at Checkout. |
+
Amount |
+Required |
+The total amount of the payment. |
+
Currency |
+Required |
+Currency for the amount. |
+
Order reference |
+Optional |
+Only 15 numbers allowed. |
+
| + + | ++The amount from basic settings will be used except if the merchant adds products in the product settings, then the amount will be adjusted automatically after calculation. + | +
| + + | ++Extended settings are optional and the link can be created without them. + | +
+| Parameter | +Description | +
|---|---|
Link Valid From To |
+Duration of the link validity. |
+
Select Payment Method |
+Payment method for the link. The recommendation is to always choose |
+
+If "ask for billing info" and "ask for shipping info" are both unchecked, the customer has to fill in billing and shipping information in the form, and if they are both checked the customer will have to fulfill the information at the checkout.
+The products can be added to the basket and they will be part of the link.
+
+If the customer wants to add products the form is required except for the product photo and description.
+| Parameter | +Description | +
|---|---|
Title |
+Title of the product. |
+
Quantity |
+Quantity of the one product that will be sold by each payment. |
+
Net Price |
+Price of one product. |
+
Tax Rate(%) |
+The percentage at which a product is taxed. |
+
| + + | ++After fulfilling the form click on "Add Product" to add the product to the Basket. + | +
QPC Payment Center is an integral part of all QENTA Payment CEE solutions, designed as a bookkeeping interface that supports the management of payment transactions.
+Here is a demo access for testing purposes.
+The login can be found at the following link.
+
+The username and password must be entered.
+When the login was successful, a summary of the login data is displayed.
+| + + | ++After the first login, a new password must be set. + | +
| Field name | +Description | +
|---|---|
| + | The unique order number of a transaction. |
+
| + | The approved amount. |
+
Deposited |
+Amount captured by this approval. |
+
| + | Currency details for this transaction. |
+
Time created |
+Time (date and time) at which the approval was created. |
+
Code |
+Reference code of the financial service provider. In the case of credit card payments, the authorization code from the credit card company is +displayed here. |
+
| + | Freely selectable text for the relevant approval. |
+
Brand |
+Used brand for this transaction. |
+
Acquirer |
+Company that processes the authorization and settlement. |
+
The following actions can be carried out online using the QPC Payment Center:
+| Payment status | +Operations | +Description | +
|---|---|---|
| + | + | Approvals can be searched. |
+
| + | Approvals can be canceled. |
+|
| + | Approvals can be debited with full or in partial amounts. |
+|
| + | + | Deposits can be searched. |
+
| + | Deposits can be canceled. |
+|
| + | Deposits can be settled (completing a day-end closing). |
+|
| + | + | Closed credits can be searched. |
+
| + | Credits can be canceled if the day end closing of the credit was not finished yet. |
+|
| + | Refundable transactions can be searched. |
+|
| + | Credits can be settled (completing a day-end closing). |
+|
| + | + | The day-end closing is a deprecated function and is done automatically by the system. |
+
+| Function | +Description | +
|---|---|
| + | Approvals can be debited. |
+
| + | The day-end closing is a deprecated function and is done automatically by the system. |
+
Transactions Last 7 Days |
+A list of transactions from the last 7 days is opened. |
+
Batches Last 7 Days |
+A list of day-end closings from the last 7 days is opened. |
+
1) Main search screen.
+
+Transactions can be searched without any specific criteria but the date. Specifying search criteria like the amount will lower the displayed results.
+The maximum searchable and displayable period is 3 months. By default, the fields created after and created before are set from today to 3 months in the past.
+| + + | ++The period can be adjusted (eg. to a period in the last year), but again must not exceed 3 months. + | +
2) Overview after the search.
+
+The merchant can click on the particular order number and then execute offered functionalities. This can be done only for each payment individually and never for a few together. A list can be exported by clicking on the right upper button.
+
+Every approval has to be debited and every deposit has to be settled. The customer’s amounts from the financial service providers are received only from settled deposits.
+| + + | ++Uncaptured approvals expire after 7 - 14 calendar days for Credit Cards. For other payment methods, it depends on the acquirer. + | +
1) Main approvals search screen.
+
+| + + | +
+The merchant can search only by the approved order state and that field is immutable. That is one of the main differences between this search and a general search.
+ |
+
2) After entering the relevant search criteria, a limited selection of the current approvals will be displayed.
+
+3) Multiple order numbers can be selected at the checkbox on the left side or all of them with the select all button. With these options, the merchant can do multiple approvals→deposit. A list can be exported by clicking on the right upper button.
+Approvals can also be canceled, depending on the payment method.
+| + + | ++Deposits can’t be canceled with all payment methods, so more information can be gained here. For technical reasons, refunds can’t be issued for some payment methods. + | +
1) An overview of the current approvals will be displayed.
+
+Multiple order numbers can be selected at the checkbox on the left side or all of them with the select all button. With these options, the merchant can do multiple approvals→reverse. A list can be exported by clicking on the right upper button. When the cancellations have been completed, a list of the completed cancellations is displayed.
+2) The individual approvals can be canceled too. After clicking on the relevant order number in the overview, a window with the order details will be displayed. "Payments assigned to this order" > Approvals→Reverse
+
+1) An overview of the current depositable transactions will be displayed.
+
+2) Multiple order numbers can be selected at the checkbox on the left side or all of them with the select all button. With these options, the merchant can do multiple approvals→deposit. When the approvals have been debited, a list of the deposited approval is displayed. A list can be exported by clicking on the right upper button.
+Approvals can also be captured in partial amounts. The merchant can click on the relevant order number in the overview and a window with the order details will be displayed.
+The total amount is suggested by default and can be lowered manually.
+The confirmation of the debited approval will be displayed in the window.
+| + + | +
+
+
+An approval can be: +
+
+
+
+This depends always on the payment method and/or acquirer. + |
+
+Deposits can’t be canceled for all payment methods, more information can be gained here. For technical reasons, cancellation of deposits can’t be issued for some payment methods.
+1) Main deposits search screen.
+
+| + + | +
+The merchant can search only by the deposited order state and that field is immutable. That is the one of the main differences between this search and a general search.
+ |
+
2) After entering the relevant search criteria, a limited selection of the current deposits will be displayed. A list can be exported by clicking on the right upper button.
+
+3) Multiple order numbers can be selected at the checkboxes on the left side or all of them with the select all button. With these options, the merchant can do multiple deposits→reverse.
+1) An overview of the current reversible deposits will be displayed.
+
+2) Multiple order numbers can be selected at the checkbox on the left side or all of them with the select all button. With these options, the merchant can do multiple deposits→reverse. When the cancellations have been completed, a list of the completed cancellations is displayed. A list can be exported by clicking on the right upper button.
+3) The individual deposits can be canceled too. The merchant can click on the relevant order number in the overview and a window with the order details will be displayed. "Payments assigned to this order" > Deposits→Reverse
+
+The day-end closing is a deprecated function and now is done automatically by the system.
+
+| + + | ++For technical reasons, refunds can’t be issued for some payment methods. + | +
1) Main credits search screen.
+
+| + + | +
+The merchant can search only by the cleared order state and that field is immutable. That is one of the main differences between this search and a general search.
+ |
+
2) After entering the relevant search criteria, a list containing orders and the associated credit numbers will be displayed. A list can be exported by clicking on the right upper button.
+
+1) An overview of the current reversible credits will be displayed.
+
+2) The merchant can select the credits for reversing.
+3) The cancellations are carried out step by step.
+Credits can only be created against settled payments.
+A number of criteria can be used when searching for settled payments.
+On settlement, the credits are presented to the financial service provider (day end closing is completed).
+The provider then credits the amount to the customer’s (credit card) account.
+1) Main Issue screen.
+
+2) After entering the relevant search criteria the limited selection of refundable payments will be displayed.
+3) The merchant can click on the relevant order number in the overview and a window with the order details will be displayed, an example is shown in issuing partial credits. A list can be exported by clicking on the right upper button. When the credits have been created a list of the completed credits will be displayed.
+Individual payments can be selected from the list. Clicking on the order number a new window will open with the order details.
+
+If a credit has already been issued against this payment, the field credits issued for this order will also be displayed in the order details.
+Before clicking Credits→Issue the amount can be lowered.
+
+The confirmation Order refunded is displayed when the credit has been created.
+The day-end closing is a deprecated function and now is done automatically by the system.
+
+| Command | +Mark on the diagram | +Description | +
|---|---|---|
| + | a |
+A successful payment leads either to an |
+
| + | 1 |
+An |
+
| + | b1 |
+An |
+
| + | b2 |
+An |
+
| + | b3a/b3b |
+A |
+
| + | 2 |
+A |
+
| + | 3 |
+A transaction that has been |
+
| + | c |
+A transaction in status |
+
| + | 4 |
+A |
+
| + | d1 |
+A transaction in status |
+
| + | 5 |
+A |
+
| + | d2 |
+A |
+
| a | +|
|---|---|
Data |
+Value |
+
Command |
++ |
Description |
+A successful payment leads either to an |
+
1 |
+|
Data |
+Value |
+
Command |
++ |
Description |
+An |
+
b1 |
+|
Data |
+Value |
+
Command |
++ |
Description |
+An |
+
b2 |
+|
Data |
+Value |
+
Command |
++ |
Description |
+An |
+
b3a/b3b |
+|
Data |
+Value |
+
Command |
++ |
Description |
+A |
+
2 |
+|
Data |
+Value |
+
Command |
++ |
Description |
+A |
+
3 |
+|
Data |
+Value |
+
Command |
++ |
Description |
+A transaction that has been |
+
c |
+|
Data |
+Value |
+
Command |
++ |
Description |
+A transaction in status |
+
4 |
+|
Data |
+Value |
+
Command |
++ |
Description |
+A |
+
d1 |
+|
Data |
+Value |
+
Command |
++ |
Description |
+A transaction in status |
+
5 |
+|
Data |
+Value |
+
Command |
++ |
Description |
+A |
+
d2 |
+|
Data |
+Value |
+
Command |
++ |
Description |
+A |
+
QCALL Checkout Terminal is the solution for processing written or telephone order payment data. Payment details of the consumers are recorded in the web-based, password-protected interface and are processed automatically and immediately during the telephone order process. All successful transactions are available in the QPC Payment Center.
+Here is a demo access for testing purposes.
+| Field name | +Optional or required | +Maximum field length | +Description | +
|---|---|---|---|
Company |
+
+
+
+
+Optional
+ |
+Alphanumeric, up to 60 characters. |
+Name of company ordering the relevant items (products). |
+
First and last name |
+
+
+
+
+Optional
+ |
+Alphanumeric, up to 20 characters for the first name and 25 characters for the last name. |
+Consumer’s first and last name. |
+
Address |
+
+
+
+
+Optional
+ |
+Alphanumeric, up to 100 characters. |
+Consumer’s address. |
+
Order reference |
+
+
+
+
+Optional
+ |
+Alphanumeric, up to 128 characters, differs depending on the payment method used. |
+Unique order reference ID sent from merchant to financial service provider. |
+
Comment |
+
+
+
+
+Optional
+ |
+Alphanumeric, up to 255 characters. |
+Additional data relating to the order, e.g. invoice number or purchase number. |
+
Amount |
+
+
+
+
+Required
+ |
+Alphanumeric, up to 10 characters. |
+Payment to be effected by consumer. |
+
Currency |
+
+
+
+
+Required
+ |
+Alphabetic or numeric, fixed 3 characters |
+Currency code of amount. |
+
Payment method |
+
+
+
+
+Required
+ |
+Selection field. |
+Payment method used for the transaction: Credit Card, SEPA Direct Debit or recurring payment. |
+
| Data | +Value | +
|---|---|
Field name |
+Company |
+
Optional or required |
+Optional |
+
Maximum field length |
+Alphanumeric, up to 60 characters. |
+
Description |
+Name of company ordering the relevant items (products). |
+
Data |
+Value |
+
Field name |
+First and last name |
+
Optional or required |
+Optional |
+
Maximum field length |
+Alphanumeric, up to 20 characters for the first name and 25 characters for the last name. |
+
Description |
+Consumer’s first and last name. |
+
Data |
+Value |
+
Field name |
+Address |
+
Optional or required |
+Optional |
+
Maximum field length |
+Alphanumeric, up to 100 characters. |
+
Description |
+Consumer’s address. |
+
Data |
+Value |
+
Field name |
+Order reference |
+
Optional or required |
+Optional |
+
Maximum field length |
+Alphanumeric, up to 128 characters, differs depending on the payment method used. |
+
Description |
+Unique order reference ID sent from merchant to financial service provider. |
+
Data |
+Value |
+
Field name |
+Comment |
+
Optional or required |
+Optional |
+
Maximum field length |
+Alphanumeric, up to 255 characters. |
+
Description |
+Additional data relating to the order, e.g. invoice number or purchase number. |
+
Data |
+Value |
+
Field name |
+Amount |
+
Optional or required |
+Required |
+
Maximum field length |
+Alphanumeric, up to 10 characters. |
+
Description |
+Payment to be effected by a consumer. |
+
Data |
+Value |
+
Field name |
+Currency |
+
Optional or required |
+Required |
+
Maximum field length |
+Alphabetic or numeric, fixed 3 characters. |
+
Description |
+Currency code of amount. |
+
Data |
+Value |
+
Field name |
+Payment method |
+
Optional or required |
+Required |
+
Maximum field length |
+Selection field. |
+
Description |
+Payment method used for the transaction: Credit Card, SEPA Direct Debit or recurring payment. |
+
| + + | ++Depending on the specific requirements and the configuration settings, the number of fields and the field length and characteristics may differ, so if the maximum character length is exceeded, any additional characters are ignored. + | +
The login can be found at the following link.
+
+The username and password must be entered.
+When the login was successful, a summary of the login data is displayed.
+| + + | ++After the first login, a new password must be set. + | +
Steps for carrying out a payment using Credit Card.
+Order details:
+After completing the fields the merchant selects payment method > Credit Card.
+
+Payment details:
+The consumer’s credit card details: credit card number and expiration date (the card security code is not necessary).
+
+If the payment has been completed successfully, the message Transaction approved appears.
+
+If the credit card payment has been successfully processed, approval for the payment amount is displayed in the QPC Payment Center. But completed payments are not automatically deposited via QCALL Checkout Terminal, so to receive the outstanding amounts the approved amounts need to be deposited in the QPC Payment Center.
+QENTA carries out the deposit of approved payments and there are two configuration options:
+Daily fully automated deposit of all payments-all payments are deposited once during the night.
+Immediate capture-after affecting a payment, the payment is available immediately as a capture.
+| + + | ++Not deposited approvals will expire after 7-14 calendar days and after exceeding the individual deadline these payments can no longer be submitted or received. + | +
Steps for carrying out a payment using SEPA Direct Debit.
+Order details:
+After completing the fields the merchant selects payment method > SEPA Direct Debit.
+
+Payment details:
+The consumer’s bank details: account owner, IBAN, BIC,mandate reference, mandate signature date and due date.
+
+If the payment has been completed successfully, the message "Transaction approved" appears in the window that opens Order confirmation.
+
+At the same time, a unique order number is created automatically.
+Steps for recurring payment:
+Order details:
+After completing the fields the merchant selects payment method > Recurring payment.
+
+Payment details:
+Recurring payment details:
+
+Source order number: original order number. Enter the order number to which the recurring payment refers.
+A window opens and shows a summary of the source order data > Next.
+If the payment has been completed successfully, the message Transaction approved appears in the window Order confirmation.
+
+At the same time, a unique order number is issued automatically.
+| + + | ++Generally, payment for the source order number must not be older than 400 days for credit card payments. If the order is older than 400 days, the error message "Card number missing" is displayed. If the expiration date of the credit card of the stored source order was exceeded, the error message "Expiration date is invalid" is displayed. In both error cases, obtain the new credit card details from the consumer and initiate a new order since a recurring payment may not be carried out. + | +
There are currently no restrictions on payments using SEPA Direct Debit procedures.
+
+
+
+
+
+