New Proof of Delivery Feature: Pincode Verification

Announcements
1

:new: What’s new?

We have released a new feature within the delivery option object for our API to empower our clients to activate end-customer verifications using pin-codes.

We have enabled two different method for the new pin-code feature:
Static - Which is a simple 2 digit code using the last 2 digits of the end-customers phone number.
Dynamic- Which is a more secure pin-code as a random 4 digit code is dynamically created.

:magic_wand: What’s the impact?

In order to improve the security of your deliveries and reduce resources time taken up on customer support claims of lost orders or deliveries provided to the wrong customer, we encourage the use of either the static or dynamic pin-code verification to ensure a secure verification step is in place.

:bulb: How does it work?

When creating a job using our job creation endpoint, you are now able to use the delivery_options object which contains the pin_code object to inform us if you would like to enable the feature and also the type of pin-code verification you would like to use.

You would also need to confirm at which delivery status you would like your end-customers to receive the SMS message with the pin code, this can be found in our What are Stuart’s SMS and Email notification options? FAQ post.

By default, end-customers would receive the below generic message including their pin-code at a specified status trigger but this message can also be customised.

“Courier Name”, your Stuart courier is on their way to pick up your order which can be followed here: “Stuart tracking link”. To receive your order, provide the code “Static/Dynamic pin-code”.

Optionally, we can also include the pin-code generated in the job creation API response, allowing you to employ your own method to provide visibility of the pin-code e.g push notifications, UX portal.

"proof": {
   "signature_url": null,
   "pin_code": "38" 
},

Example static pin code request:

{
    "job": {
        "pickups": [
          ...
        ],
        "dropoffs": [
            {
              ... ,
              "delivery_options":{
               "pin_code":{
                  "enabled":true,
                  "type":"static"
               }
            }
         ]
    }
}

Example of dynamic pin code request:

{
    "job": {
        "pickups": [
          ...
        ],
        "dropoffs": [
            {
              ... ,
              "delivery_options":{
               "pin_code":{
                  "enabled":true,
                  "type":"dynamic"
               }
            }
         ]
    }
}

Currently, this feature is only available on request. Please speak to your account manager or your Stuart CSE representative to discuss using this feature.

Please note, if you attempt to use this feature without contacting Stuart first you will see the below error message:

{
    "error": "RECORD_INVALID",
    "message": "Unable to save record",
    "data": {
        "job.dropoffs.delivery_options": [
            "Pin_code type not allowed"
        ]
    }
}

Additionally, due to the use of SMS messages for the communication, we need to ensure a valid mobile number is provided for the end customer.

:date: When will this change take place?

Live now!

:eyes: What’s next?

Currently, this feature is only available on request but we aim for a more public release soon!

Subscribe to Announcement notifications to keep up to date! :face_with_monocle: