EASY CHECKOUT GUIDE

Best practice on how to implement Easy and how to place the checkout on your website

The Easy checkout offers flexible implementation options to suit your customer journey

Embedded Checkout

In order to benefit from all consumer advantages, we recommend implementing the embedded Easy checkout on the basket page of your webshop.

This setup provides a one click checkout that handles payment methods and consumer shipping details, stored in a safe and secure manner.

The Easy checkout is designed to optimize the conversion rate and reduce dropouts by minimizing the number of steps required to complete a purchase.

Controlled by setting integrationType = EmbeddedCheckout

Hosted Payment Window

*HOSTED WINDOW FILLER*

In order to benefit from all consumer advantages, we recommend implementing the embedded Easy checkout on the basket page of your webshop. This setup provides a one click checkout that handles payment methods and consumer shipping details, stored in a safe and secure manner. The Easy checkout is designed to optimize the conversion rate and reduce dropouts by minimizing the number of steps required to complete a purchase.

Controlled by setting integrationType = HostedPaymentPage

Prefilled consumer address with Inject address functionality

All payment window flows are controlled by the merchantHandlesConsumerData-flag which the merchant can specify when setting up the payment.

The Easy checkout enables you to inject your existing customer data via the API in order to present your customer with a checkout where the consumer details such as email, phone number and address is already prefilled.

Example: merchant has a consumer name and shipping address, in addition to email and postal code

{
...
   "merchantHandlesConsumerData":true,

   "consumer":{
      "email":"john.doe@doemail.com",
      "shippingAddress":{
         "addressLine1":"Toodels street 1",
         "addressLine2":"Co/ John",
         "postalCode":"0956",
         "city":"Stockholm",
         "country":"SWE"
      },
      "phoneNumber":{
         "prefix":"+46",
         "number":"0123456789"
      },
      "privatePerson":{
         "firstName":"john",
         "lastName":"Doe"
      }
   }
}

  • Invoice and installments are available as payment methods if the shipping address country is the same as the country the merchant operates in
  • If we can't find a consumer in Easy based on the provided email and postalcode, we will not offer any cards stored on the device
  • If we find the consumer in Easy the consumer will only have to reenter pno when paying with invoice or installment if:
    • the address provided by the merchant is not the same as the previously used address for invoice or installment
    • the consumer has not paid with invoice or installment before

Sell digital products and services without requiring physical address

If your online business does not require physical shipping, you can implement the checkout without collecting the physical address. This means minimum input needed to complete a purchase.

Example: merchant only fills email and postal code

 

{
    ...
  "checkout": {
    ...
    "consumer": {
      "email": "john.doe@doemail.com",
      "shippingAddress": {
        "postalCode": "0956",
      }
    },
    "merchantHandlesConsumerData": true
  }
}

 

Main takeaways of the above flow:

  • We will use email and postal code to try and find a consumer in Easy
  • Cards, wallet (Vips, MobilePay) and account to account (Swish) payment methods are available
  • Invoice or installment is not available as payment methods because the merchant did not specify a shipping address
  • If we find a consumer:
    • Any stored cards are available as a payment method
    • Vipps, MobilePay and Swish are prefilled with phone number found on the consumer
  • If we don't find a consumer:
    • we will offer any stored cards on the device which the consumer is completing the purchase from.
    • Vipps, MobilePay and Swish is available as payment methods, but the consumer must enter a phone number to complete a purchase

 


The Easy checkout can be implemented embedded or hosted, please contact us for advise on the right setup for you business.

 

 

Easy flow

This flow is mandatory and cannot be changed. As an example: the merchant site cannot fetch the payment status, but must go through the Nets Checkout.

  1. The consumer navigates to the merchant’s Checkout page.
  2. The Merchant creates a new PaymentId through a server-to-server call (as already describe in the integration-guide) (*1)
  3. The Merchant stores the PaymentId gotten from the server-to-server call for future usage.
  4. The Merchant loads the Nets Checkout through the provided JavaScript code (as describe in the integration-guide). (*1) (*2)
  5. Nets Checkout starts and is ready for the consumer to pay.
  6. The Consumer is identified, selects payment method and presses the “Pay” button in Nets Checkout.
  7. (Optional) Nets Checkout sends a “pay-initialized” JavaScript event to the Merchant site. This optional event could be used to save the order in the Merchant database.
  8. (Optional) Merchant has handled the “pay-initialized” event, and is ready to send the control back to Nets Checkout. The Merchant site sends a “payment-order-finalized” JavaScript event with the result of the operation:
    a. true: the payment will continue
    b. false: an error message is shown to the Consumer
  9. The consumer is redirected to an external 3DS authentication form (*3) and completes the security check.
  10. The 3DS form is completed and the consumer is returned back to the merchant site again. The URL contains a reserved keyword “PaymentId”.
  11. The merchant loads Nets Checkout again with the same PaymentId.
  12. If the payment was successful, the Nets Checkout sends a JavaScript event “payment-completed”. If the payment fails (for instance due to failed 3D-Secure authentication), Nets Checkout will restart the payment process automatically.
  13. The merchant site is handling the JavaScript event “payment-completed” and it displays the “Thank you” page.
  14. The payment is completed successfully, and the consumer is notified.

Additional notes:

(*1) For security reasons, the Checkout URL parameter must match the URL where the Nets Checkout is loaded. An attempt to load the checkout in a different domain will raise an Ops error page.

(*2) List of common problems that raise an Ops error page:

  • Checkout URL specified in the Payment doesn’t match the URL where the checkout is loaded.
  • In the parameters sent to the Nets Checkout, the PaymentId is wrong or it’s expired (for security reason it leaves for 20 minutes).
  • The checkout parameters are not correct, like wrong “checkoutKey”, invalid language code, etc.
  • The PaymentId is created using the “test” environment, but the checkout is loaded using the “live” environment.

(*3) this is required only for credit card payments. For invoice payments the consumer is not redirected to the 3D-Secure form.

 

Easy checkout together with other payment method

A) Easy must always be shown as the primary option and load automatically loaded on the cart page.

B) If other payment method is offered, it should be displayed as a simple text link above the Nets checkout.

Page load animation

For a coherent design of the checkout you are welcome to use the gif animation below if needed e.g. when sending a customer to a confirmation page:

 

Do you have a question or need help?
Follow us
Nets Online Payments

Oslo: +47 21 55 44 00
Stockholm: +46 (0)8-527 525 00
København: +45 7020 3077
Jyväskylä: + 358 010 80 40 40
Close menu