Complete order by fulfillment URL

In this article we are focusing on how to complete a order by using the fulfillment URL. You may use fulfillment URL if the order is not prepaid and for all payment methods that requires user involvement for processing the payment. This includes all payment methods excluding other and sms (Link mobility).

Step 6: Complete your order by fulfillment URL

To fulfill an order, you need to have an orderId. You received the orderId when you registered the order in step 4. In addition to this, you need to specify a returnUrlfor redirecting the user after processing the payment. Read more about the fulfillment URL.

A detailed description of processing the payment is described below:

1. Redirect the user to fulfillment URL.
2. Send orderId and absolute returnUrl as query parameters in the URL.

The next step depends on if the order is prepaid or not. Step 7 describes the process for paying the order and this is only required if the order is not prepaid (prepaid = false). Please skip step 7 if the order is prepaid. The system will redirect the user to the returnUrlif the order is prepaid.

Step 7: Paying the order

In this step we describe how to pay the order. Please skip this step if the order is prepaid (prepaid = true).

We are continuing the payment process from step 6:

3. Redirecting the user to the payment provider. The user may pay the order.
4. After the payment process is done. The user will be redirected to the returnUrland a fulfillmentStatus parameter is added. The value of this parameter is

• success if the order was paid.
• cancel if the user canceled the payment process.
• error if an error occured.
• unknown is only used when something goes wrong and we may not get end status of transaction.

If the fulfillmentStatus is not success, further processing of the order will be stopped. This means that the order will not be transferred to the backend system.

Step 8: Handle the order in Connect

After the user has been redirected to returnUrl:

• The user will be granted a temporary access if the order has followed the process described for how to grant temporary access.
• The system will update the order with userId if the user was logged in with ConnectID.
• The order will be marked as "fulfilled" in the system.

Step 9: Assign the user to the order

You can skip this step if the user was logged into the system before order registration.

You need to connect the user to the order if the user was not logged into the system before order registration, and the order specifies products with digital content that requires access. In this case you have used Register order – client mode for order registration. This means you used for example (Register order - client mode) for order registration.

The API will check if the user has an account. A user account will be created if the user does not have an account. If the user has an account, it will inform if the password is set or not. The user account will be connected to the order with the specified orderId.

Please see the Assign user - client mode in our API documentation for a detailed description of this endpoint.