seQura for Odoo 19
Spain's Buy Now Pay Later, native in your Odoo checkout
Let shoppers pay later, split in 3 or pay in instalments with seQura — and keep Odoo and seQura in step for the whole life of the order: approval, shipment, returns, cancellations, and the payout that eventually lands in your bank.
Verified end to end against a live seQura account: a real purchase approved, shipped, partially refunded, cancelled and reconciled.
Set up in two fields
Enter the username and password seQura emailed you and press Fetch merchant accounts. The connector reads the rest from seQura itself: the merchant reference for every country you sell in, the currencies, the assets key the widgets need, and the secret used to verify seQura's notifications. Nothing to transcribe, nothing to mistype.
Only what seQura actually contracted with you
Every seQura product is its own Odoo payment method, so the shopper chooses in Odoo's own form and seQura's identification form opens already set to what they picked. Products outside their contracted amount range, or whose seasonal campaign has closed, are never offered. Offering a product you have not contracted ends in a seQura error screen in front of the shopper, so the connector simply does not offer it.
In the shop, where it earns its keep
What moves conversion is the shopper seeing "from X per month" before the cart, not at the end. seQura's instalment simulator and its "how it works" pop-up go on product pages, product listings and the cart, styled with the JSON from seQura's own widget simulator. They are never shown for products your contract excludes.
The banner seQura asks you for, as a building block
Before going live, seQura asks merchants to say on the site itself that they finance — a permanent banner on the home page, the logo in the footer. That is usually theme work someone has to cut by hand. Here it is a block you drag into place from the website builder, with editable text and an editable image, so you can drop in whatever artwork seQura sends you without touching a template.
Get paid for what you ship
seQura only pays for orders it knows have shipped. Validating a delivery reports it immediately, and a nightly job re-sends anything that did not get through — because a missed report is money that never arrives. A dedicated screen shows what has been paid for but not yet claimed.
Returns done seQura's way
seQura has no refund endpoint: a refund is a smaller shipped cart. The connector models it exactly that way, from the credit note or from the transaction, and a refund larger than what is left is trimmed to what is left instead of being rejected. Cancelling in Odoo tells seQura to stop charging the shopper.
One payout, broken down into the orders it paid for
A BNPL payout never matches a single order, which is what makes reconciling one by hand miserable. Disbursements are imported with their per-order settlements — returns included, as negative lines — and linked to the Odoo sales orders.
Orders that need a person
seQura reviews a small share of orders by hand. They are real orders that may still be refused, so they get their own screen instead of hiding among every other transaction. The sales order is deliberately left unconfirmed until seQura approves, so nobody ships against a credit that was never granted.
Sales that never touch the website
Orders taken by phone or at a counter can be charged too. The connector solicits the order and asks seQura to text the shopper a link to its own form, which they complete on their own phone — which is exactly what seQura requires.
You decide where it appears
Gift cards, deposits or anything else you would rather not finance can be excluded by product or by product category, children included. Amount ranges, campaign windows and a test-mode IP allow-list are all per country, and seQura disappears from the checkout whenever the cart breaks a rule.
Every order, traceable
Each transaction keeps its seQura order reference, its state on both sides, what was reported as shipped and what was refunded, so a disagreement with seQura can be settled by looking rather than guessing.
What is included
| Checkout | Pay Later (i1), Split in 3 (sp1), Instalments (pp3), seasonal campaigns (pp5), pay by card (fp1), and seQura's own chooser (tbs) |
| Markets | Spain, Portugal, Italy and France, one merchant account per country, on the seQura or SVEA deployment |
| Order lifecycle | Solicitation, identification form, on-hold review, confirmation, Authorize & Capture, void, and the full notification protocol including its 404 / 409 / 410 / 5xx answers |
| Post-checkout | Shipment reporting on delivery validation, a nightly catch-up, partial and full refunds, two-way cancellation, and shipment references |
| Finance | Disbursement import with per-order settlements, fees and returns, matched to the sales orders |
| Availability rules | Excluded categories and their children, banned products, services with their own duration, per-product amount ranges, campaign windows, and a test-mode IP allow-list |
| Security | HMAC-SHA256 webhook verification over the raw body, callback tokens, credentials restricted to system users, and refusal to call any non-seQura host |
| Languages | English and Spanish |
Requirements
Odoo 19.0, Community or Enterprise · an active seQura merchant contract
Depends on payment, website_sale, account,
sale and stock
Built by FlexigoTech · comercial@flexigotech.com
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Invoicing (account) • eCommerce (website_sale) • Discuss (mail) • Website (website) |
| Lines of code | 3763 |
| Technical Name |
flexigo_sequra_bnpl |
| License | OPL-1 |
| Website | https://flexigotech.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module