FAQs

Once integrated, what does the workflow look like?

  1. A shopper puts a product in their cart, goes to the checkout and selects SeQura as payment method.
  2. The shop sends a solicitation to SeQura with all the order data. SeQura responds with a URL to use for the checkout of this order.
  3. The shop gets or sends the identification form for this order using the URL from the previous step and shows the form to the shopper.
  4. The shopper interacts with SeQura’s form until all the data is valid and approved. (This form talks directly to SeQura, bypassing the shop.)
  5. SeQura disables the form interaction making the customer wait and sends an “IPN” (Instant Payment Notification) to the notify_url that the shop provided in the initial API call.
  6. The shop receives the callback and puts the order on hold, or confirms it right away:
    1. The shop sends an on hold or confirmation request to the order URL with up-to-date order data. SeQura validates that the order has not changed too much and confirms or places the order on hold.
    2. The shop materializes the order internally and assigns an order number (if they haven’t already), assigning a proper state (depending if it’s confirmed already, or on hold):
    3. The shop repeats the previous request, this time including the order number.
    4. The shop responds to the IPN request with a 200 OK status code.
  7. SeQura redirects the shopper to the return_url that the shop provided in the initial API call.
  8. The shop displays an order confirmation or on hold page.
  9. If the order was placed on hold in step 6, once it’s approved, the shop will receive another IPN requesting the confirmation:
    1. The shop sends a confirmation requests to the order URL with up-to-date order data. SeQura validates that the order has not changed too much and confirms the order.
    2. If the shop already sent the order number, no additional steps are required.

I would like to complete the process using sandbox credentials and I have already introduced a phone number. Which is the validation code I need to use?

The validation code using sandbox credentials is the five last digits of the phone number that you have provided.

I would like to complete the payment process using sandbox credentials. Which are the credit card details I need to use?

You can use the following test data:

  • Test Card Number: 4716773077339777

  • Expiration date: 12/30

  • CVV code: 123

I have already completed the payment process, but I am not being redirected to the confirmation page ¿What is happening?

There could be different reasons for this:

  • The url provided in notify_url is not accessible, this could be because of working on a local development environment, because of IP filters or other type of ungranted permissions.
  • The url is accessible but the process that has to be completed once receiving the IPN is not being successfully executed and the order is not being confirmed with an order reference.

My server is behind a firewal. What IPs do you use to send the IPN?

SeQura uses 3 static IPs for both sandbox and production environments:

  • 34.253.159.179
  • 34.252.147.155
  • 52.211.243.177

My physical multistore integration asks for a NIN control. What is the nin_control?

Physical multistore integrations requires an additional field to be sent in the step 1 of the checkout. This data is mandatory and it will be validated in order to prevent fraud.

This data is found in the back of the spanish DNI or in the bottom of a NIE. See the image to find it out. You can also use this image in your software. Sequence Overview

My server doesn’t have an up to date SSL certificate. How can I bypass this validation while testing?

The IPN expects to notify a HTTPS url. It is mandatory that the notify_url is HTTPS. If the server doesn’t have an up-to-date SSL certificate the IPN won’t proceed. However, there is a way to bypass this limitation in the sandbox environment. Important: This won’t work in production / live environment.

To use a non secure url in the notify_url field, you can prefix the url with the protocol “unverified-https://”. For instance: unverified-https://my.shop.tld/checkout/sequra-ipn/8765432

How can I get in Sandbox an order that goes through the on hold state?

When testing in Sandbox, if you get and order approved, SeQura will send you an IPN requesting the confirmation of the order. You can test t get confirmed directly, receiving only one IPN.

If you want SeQura to tell you to put the order on hold first, and a few moments later, to confirm it, make sure the shopper name you enter in the identification form includes the text Review Test Approve–don’t worry about capitalization.

If you want SeQura to tell you to put the order on hold first, and then cancel the order, make sure the shopper name you enter in the identification form includes the text Review Test Cancel–don’t worry aboyut capitalization.

This will help you fully test the IPN processing.