Order API integration steps
To integrate seQura in your checkout, you need to make four API calls. Calls 1, 3, and 4 are almost identical, and call 2 is a simple GET with no mandatory parameters.
1. Start solicitation
Start by making an API call with the cart and customer data (see Order API Payload and Examples for exact specification).
This call returns a URL you'll use in the following steps. Read more
2. Present the identification form
This step lets the shopper accept service conditions and verify their identity. When you request the form, you also specify the financial product (invoicing, part payment, or seasonal campaign).
The form fields vary based on: data from step 1, cart contents, and financial requirements. Typical fields include birthdate and mobile number.
Depending on your integration type, you can either render the form on your website or send an SMS with a link to the form.
Important: the shopper must complete the identification form themselves—never a store operator or third party.
2.1 Online ecommerce
For online stores, render the form on your website. Fetch an HTML snippet and include it as-is in your checkout page. This snippet uses JavaScript to display the identification form and send responses back to seQura. Read more
2.2 Non-online sales channels
For sales not happening online—call centers, physical store POS, or delayed purchases—you can have seQura send an SMS to the shopper's phone.
Use the Forms Deliveries API to send an SMS directly to the shopper. The SMS contains a link that opens a form in the phone's browser, where the shopper completes identification. Read more
3. Confirm order
The shopper fills in the form fields, which are sent to seQura via AJAX. Additional fields may appear dynamically—for example, to enter a PIN code sent to their mobile, or to make a down payment.
Once seQura accepts the credit risk, the shopper is redirected to a return URL in your shop (you must include this URL in step 1 data).
When seQura approves the order, it sends an IPN request. Your shop must confirm the order is being placed. This ensures the cart hasn't changed during checkout. If the cart changed, restart the process. Read more
3.1 When you can't receive IPN
Some integrations can't receive inbound requests from seQura—for example, standalone POS software in a physical store. In these cases, a store operator must trigger the process manually. Read more
4. Register order reference
You can do this during step 3, or later if your ERP generates references separately.
If seQura approves the purchase and nothing has changed (for example, products are still available), convert the cart to a confirmed order and send your order reference to seQura. After this, you won't need the URL from step 1. Read more
Quick introduction guide
Download this document for a quick overview of the checkout process: Quick introduction guide
Common scenarios
Implement only the steps you need for your use case.
Online ecommerce
- Step 1. Start solicitation Read more
- Step 2. Fetch the identification form Read more
- Step 3. Confirm the order from IPN Read more
- Step 4. If it requires a different reference from a third ERP system, register the order reference Read more
Call center
- Step 1. Start solicitation Read more
- Step 2. Send the identification form by SMS Read more
- Step 3. Confirm the order from IPN Read more
- Step 4. If it requires a different reference from a third ERP system, register the order reference Read more
Client/Server TPV for a physical store
The TPV software is a client and the server is accessible from seQura.
- Step 1. Start solicitation Read more
- Step 2. Send the identification form by SMS Read more
- Step 3. Confirm the order from IPN Read more
- Step 4. If it requires a different reference from a third ERP system, register the order reference Read more
Isolated TPV software for a physical store
In this scenario the TPV software is autonomous.
Updated 20 days ago