Confirm order (POS - legacy)

Once seQura has approved the order, the shop must confirm that the order is actually being placed. Since the POS software is working from an isolated environment where seQura cannot make requests to send an IPN, the process has to be started manually.

Please, ask seQura to activate this option since it isn't available in the default configuration.

Overview

When the shopper notifies the merchant the credit has been approved, the store operator must preceed with the confirmation process.

Configuration

In order to use the manual IPN workflow, the payload cannot include any url: notify_url, return_url or approved_url.

The Shop completes the confirmation

To proceed with the comfirmation completely, the shop needs to

1. send the order data to seQura for verification,
2. mark the order as completed in the shop's database,
3. send the order reference to seQura (if this has not been done already),

In step 1, the merchant will make a PUT request to the URL returned in the Location header field of the initial solicitation. The merchant will send again all the order data and also will include the field state="confirmed".

SeQura will usually respond with a 200 OK status in which case the shop should proceed with steps 2-3. But if the order cart, delivery address, customer data or other details have changed in an unacceptable way, seQura will respond to the confirmation request with a 409 Conflict status and a JSON body detailing the problems. In this case, the shop must not complete the order in the shop's database or send the order reference to SeQura.

Once the steps 1 and 3 has been done and got 200 OK responses, the order is successfully confirmed in seQura and the merchant can proceed now with the delivery of the goods and the payment receipt. seQura will send to the shopper the credit conditions by email.

Problem: Order reference missing

Until the shop informs seQura of the order's order_ref_1, seQura will not be able to perform any work on the order and the merchant will not be paid for the order. seQura will follow up at least weekly on confirmed orders that don't have order_ref_1, but if the shop has recurring problems of this kind, seQura will consider this a broken integration and disconnect the service.

Problem: Order reference not unique

SeQura expects the combination (merchant.id, merchant_reference.order_ref_1) to be unique for confirmed orders. The merchant must be aware that errors in the shop might mean that an order reference is reused and that seQura will not process these orders. The error can occur in two places:

• During step 1 above, when the shop requests seQura to confirm the order. If the shop provided the order_ref_1 at the beginning of the checkout, seQura will now check to see that the reference is unique among confirmed orders. If it isn't, seQura will respond with a 409 Conflict.
• During step 3 above, when the shop updated the confirmed order with its order reference. Again, seQura will respond with 409 Conflict if the order_ref_1 is not unique. This case is more complicated than the former since (a) the order is confirmed in the shop with seQura as the payment method and (b) seQura is not able to process the order further.