• Checkout Integration
• Shipping items on checkout
• 1. Start Solicitation
• Seasonal Campaigns
• 4. Register order reference
• Order API Integration Steps
  • 1. Start solicitation
  • 2. Send the identification form
  • 3. Confirm order
  • 4. Register order reference
• Order API
• 3. Confirm order
• 2. Send Form by SMS
• Overview
• When am I done?

• Post-Checkout Integration
• Order Update API
• Webhooks API
• Disbursement API
• Delivery Report and Statistics
• Overview

• Visual Integration
• Overview
• Promotional components
• Credit conditions
• Branding resources

• References
• Integration Modules
• FAQs

• APIs
• Statistics API
• Payment Methods API
• Order Update API
• Order API
• Disbursement API
• Delivery Report API

For SeQura’s integration in the online-shop checkout, the shop needs to make four of calls to SeQura’s API. Calls 1, 3 and 4 are almost identical, and call 2 is a POST.

1. Start solicitation

When the shop wants to offer SeQura payment to a customer, it starts by doing an API call passing the cart and all the customer data (see Order API Payload and Examples for exact specification).

The result of this call is a URL which will be used in the following steps. Read more

2. Send the identification form

The next step is to let the shopper to accept and validate the service conditions and identification details. To do this, the merchant uses the Forms Deliveries API to send a SMS directly to the shopper’s mobile phone. This SMS contains a URL that will open the phone’s web browser and render a HTML form. This HTML form will use javascript to present an identification form to the user and to send the user’s answers back to SeQura.

The identification form may contain different fields depending on a number of factors: known data from step 1, content of the cart, time of day, etc. Typical fields are birth date and mobile number. Read more

3. Confirm order

The user fills in the fields and sends the data to SeQura’s API using AJAX. Depending on the user’s answers, further fields might be added to the form dynamically, e.g. to ask the user to enter a PIN code that was sent to their mobile.

Once SeQura accepts the credit risk for this purchase, a message is disblayed in the shopper’s phone, to notify the order is approved (but not confirmed) and they can proceed with the confirmation.

At this moment, when the order isn’t confirmed yet, the shop must confirm that the order is actually being placed. The main purpose of this action is to validate in the POS the order is actually approved in SeQura and to sync both system, the POS and SeQura with the ticket reference. Also, it validates that there isn’t changes in the content of the cart. In case there have been any changes in the cart, the process must start again. Read more

4. Register order reference

This is the confirmation step where the shop sends the cart and customer info to SeQura again to make sure that nothing important has changed during the checkout.

If SeQura still thinks the purchase is OK and if nothing has changed in the shop to stop the order (e.g. if the checkout lasted two days and you have run out of certain products), it is time for you to convert the cart to a confirmed order. Once you have done that, you should send your order reference to SeQura. From this point, you will not need the URL that was obtained in step 1. Read more