QMORE Checkout Seamless

QMORE Checkout Seamless

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

Process Overview in General

Image

  1. The consumer opens a shopping card that contains the previously selected items.

  2. Enters personal data and the shipping address into the provided input fields of a form.

  3. Selects one of the available payment methods enters the required payment method-specific data and commits the payment.

  4. Receives relevant information on the result of the payment and returns to the online shop to proceed.

Process Overview for QMORE

The merchant has to perform the main steps to integrate QMORE Checkout Seamless into the online shop:

Image

  1. Initializing QENTA Data Storage

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

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

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

  2. Storing sensitive payment data in initiated Data Storage

    1. After initializing the Data Storage the merchant receives a URL as a return parameter.

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

    3. These JavaScript functions allow the merchant to bypass the sensitive payment data of the consumer from the online shop and the web server.

    4. These data are directly sent to the QENTA Data Storage without transferring them through the online shop or the web server.

  3. Starting payment process

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

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

  4. Handling of a result of payment process

    1. When the consumer successfully finished the payment the merchant will get a confirmation regarding the result of the payment process.

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

Payment Process in Detail

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:

Image

  1. First, the consumer clicks the "Checkout" button.

  2. Then the online shop initiates the Data Storage as a server-to-server request.

  3. QMORE Checkout Seamless returns the Data Storage ID and the JavaScript URL.

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

  5. Then the consumer enters the required payment data into the input form and the data are sent to QENTA.

  6. QMORE Checkout Seamless stores the payment data on a PCI-compliant server.

  7. The online shop receives and displays the anonymized payment data.

  8. Then the online shop displays the relevant order details to the consumer.

  9. Afterward, the consumer reviews the order details and commits the payment by clicking a relevant button.

  10. The transaction details are sent as a server-to-server request to QMORE Checkout Seamless.

  11. QMORE Checkout Seamless redirects the consumer to the external pages of the financial service provider.

  12. The consumer fills in the required payment details on the external pages of the financial service provider.

  13. QMORE Checkout Seamless confirms the transaction to the online shop by sending a server-to-server request.

  14. Now the online shop stores the transaction result.

  15. QMORE Checkout Seamless redirects the consumer to the successUrl, failureUrl, pendingUrl or cancelUrl.

  16. Then, the online shop displays an appropriate page providing the consumer with information on the result of the payment process.

  17. After returning to the online shop, the consumer proceeds with browsing or shopping for additional items in the shop.

Backend

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.

Test

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.

Parameters