FAQs

What does the workflow look like once integrated?

1. A shopper adds a product to their cart, goes to checkout, and selects seQura as payment method.
2. Your shop sends a solicitation to seQura with all the order data. seQura responds with a URL to use for this order's checkout.
3. Your shop fetches or sends the identification form using the URL from the previous step and shows it to the shopper.
4. The shopper interacts with seQura's form until all data is valid and approved. (This form communicates directly with seQura, bypassing your shop.)
5. seQura disables the form while processing and sends an IPN (Instant Payment Notification) to the notify_url provided in the initial API call.
6. Your shop receives the callback and either puts the order on hold or confirms it:
   1. Send an on hold or confirmation request to the order URL with up-to-date order data. seQura validates the order hasn't changed significantly and confirms or places it on hold.
   2. Create the order internally and assign an order number (if not done already), with the appropriate state (confirmed or on hold).
   3. Repeat the previous request, this time including the order number.
   4. Respond to the IPN request with a 200 OK status code.
7. seQura redirects the shopper to the return_url provided in the initial API call.
8. Your shop displays an order confirmation or on hold page.
9. If the order was placed on hold in step 6, once approved, your shop receives another IPN requesting confirmation:
   1. Send a confirmation request to the order URL with up-to-date order data. seQura validates the order and confirms it.
   2. If you already sent the order number, no additional steps are needed.

What's the validation code in sandbox?

The validation code is the last 5 digits of the phone number you entered.

What credit card details should I use in sandbox?

Use the following test data:

• Test Card Number: 4716773077339777

• Expiration date: 12/30

• CVV code: 123

Why am I not being redirected to the confirmation page after payment?

This could happen for several reasons:

• The notify_url isn't accessible—perhaps you're in a local development environment, or there are IP filters or other permission restrictions.
• The URL is accessible but the IPN processing isn't executing correctly and the order isn't being confirmed with an order reference.

What IPs does seQura use to send the IPN?

seQura uses 6 static IPs for both sandbox and production environments:

• 34.253.159.179
• 34.252.147.155
• 52.211.243.177
• 52.215.76.36
• 34.248.152.142
• 34.254.127.74

What is the nin_control field?

Physical multistore integrations require an additional field in step 1 of the checkout. This data is mandatory and validated to prevent fraud.

You can find this data on the back of a Spanish DNI or at the bottom of a NIE. See the image below. You can also use this image in your software.

How can I bypass SSL validation while testing?

The IPN requires a HTTPS URL. If your server doesn't have a valid SSL certificate, the IPN won't work.

However, you can bypass this in sandbox. Note: This won't work in production.

Prefix the URL with unverified-https://. For example: unverified-https://my.shop.tld/checkout/sequra-ipn/8765432

How can I test orders that go through the on hold state in sandbox?

When testing in sandbox, orders are normally approved directly with a single IPN.

To test the on hold → confirm flow: include Review Test Approve in the shopper name (capitalization doesn't matter).

To test the on hold → cancel flow: include Review Test Cancel in the shopper name (capitalization doesn't matter).

This helps you fully test IPN processing.