When am I done?

Overview

We could say that the minimal checkout integration is complete once:

  1. You can start solicitations successfully
  2. You can fetch the identification form and present it to your shoppers
  3. You can put the order on hold when needed, and confirm them when they are approved
  4. You are confident that the data inside the confirmed order is real, and it corresponds to what is present in your merchant platform.
  5. And you are confident that the previous steps work for different scenarios

Start solicitations successfully

This means getting an HTTP success code (204, 200) and saving the order URL present in the Location HTTP header for later use. That URL will be required for the next steps.

It is also very important to handle failures adequately. If the solicitation cannot be started, you need to show the shopper a message telling them that the payment method is not available at this time and offer them the alternatives you have.

Check the documentation here.

Fetch the identification form

This means getting the HTML needed to load the form from SeQura, embedding it in the code delivered to the shopper’s browsers, and binding the form’s show action to the appropriate trigger.

To fetch the form, you will need the URL saved in the previous step.

Check the documentation here.

Place the order on hold and confirm it

You need to be able to handle the IPN requests (asynchronous notifications) and register the order references.

The IPN requests inform the shop that the order can be confirmed or that the order needs to be put on hold for a bit. We sometimes require a human to look at some transactions, but we are quick reviewing them!

Registering the order reference (or references) is important. We need some identifier that both you, the merchant, and the shopper recognize.

Check the details in the documentation.

Make sure the data inside the confirmed order is correct

You need to verify that the data sent to SeQura actually matches the one in your platform. Login to https://simbox.sequrapi.com (our Sandbox back-office), and make sure the information there is as expected:

  1. Customer data
  2. Shipping and invoicing addresses
  3. Product names, references, and prices
  4. Discounts, handling, fees, and total amounts

Make sure that the previous steps work for different scenarios

Depending on which SeQura methods are you integrating, and depending on your platform, you should test the previous steps under different conditions.:

  • Different SeQura payment methods, e.g. invoicing (i1), part payments (e.g. pp3), sliced payments (sp1), etc.
  • With and without handling fees, e.g. “free shipping”
  • With and without discounts items, e.g. “discounts coupons”
  • If you offer in-store pick-up, you should verify that this is correctly reflected in the payloads you send to SeQura
  • With invoice fee if it applies

Enhacing the integration

Obviously, for a smoother and better shopper and merchant experience, don’t forget to have a look at the Webhooks API.

Also, depending on your size and daily operations, you may need (and want!) to do some Post-Checkout integration.