search

Document Signature verification Process

UAE PASS document signature verification API offers for the signer’s identity verification through UAE PASS digital signature feature. On integrating the UAE PASS Document signature verification feature SP can validate the document singed time, signer details up to 3 years.

hashtag
SOAP Gateway Endpoint

Staging

Production

https://stg-id.uaepass.ae/trustedx-gw/SoapGatewayarrow-up-right

https://id.uaepass.ae/trustedx-gw/SoapGatewayarrow-up-right

hashtag
Transport Headers to invoke SOAP Service

POST https://stg-id.uaepass.ae/trusted-gw/SoapGateway

hashtag
Headers

Name
Type
Description

TwsAuthN

string

urn:safelayer:tws:policies:authentication:oauth:clients

SOAPAction

string

Verify

Content-Type

string

text/xml

hashtag
Request

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <soapenv:Header>
      <wsse:Security soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
         <wsse:UsernameToken>
            <wsse:Username>{client_id}</wsse:Username>
            <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">{client_secret}</wsse:Password>
         </wsse:UsernameToken>
      </wsse:Security>
   </soapenv:Header>
   <soapenv:Body>
      <VerifyRequest Profile="urn:safelayer:tws:dss:1.0:profiles:pdf:1.0:verify" RequestID="ba3810598a90af56a7e8" xmlns="http://www.docs.oasis-open.org/dss/2004/06/oasis-dss-1.0-core-schema-wd-27.xsd">
         <OptionalInputs>
            <ns1:AddCertificateValues binary="true" xsi:type="ns1:AddCertificateValuesType" xmlns:ns1="http://www.safelayer.com/TWS"/>
            <ns2:AddSignatureForm/>
            <css:AddRevocationValues binary="true"/>
            <css:AddTimeStampValues binary="true"/>
         </OptionalInputs>
         <InputDocuments>
            <Document>
            <Base64Data MimeType="application/pdf">JVBERi0xLjcKJeLjz9MKMSAwIG9iago8PC9DcmVhdGlvbkRhdGUoRDoyMDIxMDgwNjEwMjcwMSkvQ3JlYXRvcihQREZpdW0pL1Byb2R1Y2VyKFBERml1bTsgbW9kaWZpZWQgdXNpbmcgaVRleHRTaGFycJIgNS41LjEzLjEgqTIwMDAtMjAxOSBpVGV4dCBHcm91cCBOViBcKEFHUEwtdmVyc2lvblwpKS9Nb2REYXRlKEQ6MjAyMTA5MjMwNjI2MTYrMDAnMDAnKT4</Base64Data>
          </Document>
         </InputDocuments>
      </VerifyRequest>
   </soapenv:Body>
</soapenv:Envelope>

hashtag
Request Parameter

Name
Description
Required

Username

client_id of the SP. To be shared by the respective onboarding team.

Mandatory

PasswordText

Client_secret of the SP. To be shared by the respective onboarding team.

Mandatory

RequestID

SP can pass the unique ID for tracking the request for one particular transaction.

Optional

Base64Data

Base64 encoded data of the document which is to be verified

Mandatory

hashtag
Sample Request

hashtag
Sample Response

Previous7. Deleting DocumentNextPostman Collection for Multiple Document Signing.

Last updated

Was this helpful?