Nafath Signing

During merchant onboarding the Nafath signing URL will be returned in the merchant response object as following:

{
    "id": "a4cc5d53-3f5c-4f6f-bc2e-de03454a45e9",
    "type": "company",
      ...other fields,
    "signature": {
        "status": "initiated",
        "url": "CONTRACT_URL"
    }
}

However, in order for signing to be available, owner_id or signatory_id document is required:

{
  "type": "owner_id",
  "info": {
    "id": "1111111111",
    "date_of_birth": "1990-01-01",
    "mobile": "0555555555"
  },
  "file": "data:text/plain;base64,SGlpaWkg8J+RiyE="
}

Or

{
  "type": "signatory_id",
  "info": {
    "id": "1111111111",
    "date_of_birth": "1990-01-01",
    "mobile": "0555555555"
  },
  "file": "data:text/plain;base64,SGlpaWkg8J+RiyE="
}

Note: Signatory ID is used when the contract is signed by a person other than the owner. This requires an authorization letter by uploading power_of_atteroney document or other.

Summary

1. X platform must submit accurate information when uploading the merchant's owner_id or signatory_id documents:

   • ID number
   • Date of birth
   • Mobile number

2. The field signature will be available in the merchant object to communicate the signature state:

   • status: It will contain the signature status. (one of unsigned, initiated, signed)
   • url: When the status is initiated, it will contain the contract to be signed through Nafath.

3. Merchant's status will automatically change based on the workflow state:

   • Once the contract is signed, the merchant will be active.
   • Once the contract is rejected, the merchant will be disabled.