Complete order - client mode

Only the client needs to be logged in to use this endpoint. The user does not need to be logged in, click here to read more.

The API is used only to fulfill a previously registered order with orderId. Currently this API is possible to use on orders with mobile payment or for prepaid orders. You can only use this API to fulfill the order if paymentMethod on the order is sms, invoice, free, kco (Klarna), creditcardPayex or other (own integration with payment provider).

This API previously exposed functionality to create and link a ConnectID user to the order, and possibly send a sms/email notification. This functionality is removed from this API. To use these features, you need to use the new API named Assign user.

Request

Authorization

OAuth 2.0

Client Credentials

Add the parameter

Authorization

to Headers，whose value is to concatenate the Token after the Bearer.

Example:

Authorization: Bearer ********************

Token URL: https://connectid.no/user/oauth/token

Refresh URL: https://connectid.no/user/oauth/token

Scopes:

read-For all access

Body Params application/json

orderId

integer

required

Fullfill order with this id.

callbackUrl

string

optional

Callback URL (absolute) used when payment is fulfilled. Parameter fulfillmentStatus is added to url and method GET is used. Parameter will have one of the following values:

success

failed

Examples

Responses

🟢200OK

application/json

Body

fulfillmentStatus

enum<string>

optional

Possible values are:

OK: A message is sent to user and a callback is done (if callbackUrl is given in request) when payment is done.

ERROR:

Allowed values:

OKERROR

orderId

integer

optional

Something went wrong calling fullfilment API, e.g mobile phone number not accepted. Is null if status OK.

errorMessage

string

optional

Descriptiv error message if error status.

🟠400Bad Request

🟠429Too Many Requests

🔴500Server Error