A digital signature is a secure digital code attached to an electronic document that verifies the identity of the signer and confirms that the document content has not been changed after signing.

In South Africa, digital signatures are recognised under the Electronic Communications and Transactions Act (ECTA). The signing process in Fabric demonstrates:

• A clear intention to sign through an explicit signing action
• That the agreement content and reference documents were shown to the user before signing and embedded into the signature at the time of signing
• Identity verified via an OTP sent to the signatory's email address

Standard cryptographic methods protect the record: SHA-256 hashing, AES 256 encryption, and RSA 2048-bit asymmetric encryption.

ⓘ Note: Some agreement types still require a wet (physical) signature and cannot be signed digitally — including sale/transfer of immovable property, wills, bills of exchange, long-term leases (>20 years), surety agreements, and certain IP transfers.

Navigate to the Confirmations and Agreements section in the application workflow and copy the Digital Signature Verification link. You can also scan the QR code shown on the page.

CONFIRMATIONS AND AGREEMENTS SECTION

ⓘ Tip: The QR code on the Confirmations and Agreements page links directly to the same verification page — you can scan it from any device.

When you open the verification link, the Fabric Digital Signing page loads. This page independently re-checks the signed content and referenced files to confirm the signature is still valid.

Confirm the following:

• The verification page shows a valid signature status
• The signing record reflects that the application was signed successfully
• The signed content has not been tampered with after signing (a tampered document would show an invalid signature)

FABRIC DIGITAL SIGNING — VERIFICATION PAGE

ⓘ Tip: This page is independent evidence. Use it as proof during dispute resolution — it confirms the signing event and that signed content was not altered.

The verification page shows:

• Signatory Selection — the name selected from a dropdown (linked to CIPC data)
• Signing Email Address — the email address used to complete the OTP and sign
• Last Re-assignment — who the application was last re-assigned to

Use these details as supporting evidence if the applicant disputes who signed the application.

⚠ Note: If the wrong director was selected during signing, the digital signature record still reflects who completed the signing action. Any internal authority dispute is the applicant's own governance matter — the signature itself remains valid.

1. Copy the POPI Consent link from the workflow record.
2. Open the link in your browser.
3. Confirm that the page shows the consent was accepted as part of the workflow.

ⓘ What this proves: POPI consent confirmation shows that the user accepted the POPI consent clause as part of the application workflow — it does not prove identity, but it does confirm the acceptance event.

1. Save screenshots of the verification page(s), or export to PDF if needed.
2. Attach the evidence to the support ticket or dispute response.
3. Summarise the findings clearly using the outcome statement below.

The applicant says they did not sign

Cause: The signer may have been a different internal user within the applicant's organisation, or they may be disputing authority after signing.

Resolution: Provide the digital signature verification link and POPI consent link as independent evidence of the signing event and consent acceptance.

The verification link does not load

Cause: The link may be incomplete, expired, or copied incorrectly.

Resolution: Re-copy the link directly from the workflow record and try again.

Application Validation Issue: "The signature on the digital application does not match the selected signatory"

Cause: The person who completed the OTP and signed differs from the signatory selected in the application form dropdown.

Resolution: Open the verification link to check the signing email address. The digital signature record still captures the actual signing event — use the verification page as evidence and escalate to the applicant to resolve the internal authority discrepancy.

Can terms and conditions be changed after signing without detection?

No. If signed content is changed after signing, the digital signature validation will fail or reflect an invalid signature status.

What does POPI consent confirmation prove?

It confirms that the user accepted the POPI consent clause as part of the workflow.

What if the wrong director was selected during signing?

The digital signature record still reflects who completed the signing action. Any internal authority dispute is the applicant's internal governance matter.

Supporting Document

Digital Signature Technical Overview