e-signatures

One API call in, one certified document out.

Built for companies that need signatures on real commercial contracts — loan agreements, settlement offers, mandates — without adopting a whole e-signature platform.

Talk to us See all products

how it works

Four steps, one API.

Send the document

POST a PDF and signer details to the APFIN API. Get back a signing link.

Signer opens the link

They see the document and a signature pad — no account, no app download.

They sign

Finger on a phone, mouse on a laptop. Both are captured identically.

You get it back, sealed

A webhook fires and the signed PDF, with its audit certificate, is ready to pull.

POST /api/v1/envelopes

Signed

try it

It's just an API.

Real requests, real responses.

$ curl -X POST https://api.apfin.co.za/v1/envelopes \
  -H "Authorization: Bearer sk_live_..." \
  -F document=@loan-agreement.pdf \
  -F signer[name]="T. Nkosi" \
  -F signer[email]="t.nkosi@example.co.za"
Response
{
  "id": "env_21533f46",
  "status": "sent",
  "signUrl": "https://apfin.co.za/sign/8ad2f1"
}

$ curl -X POST https://api.apfin.co.za/v1/kyc/verify \
  -H "Authorization: Bearer sk_live_..." \
  -F document=@id_front.jpg \
  -F selfie=@selfie.jpg
Response
{
  "id": "kyc_7f1a90",
  "status": "verified",
  "matchScore": 0.98,
  "documentType": "za_id"
}

$ curl -X POST https://api.apfin.co.za/v1/aml/screen \
  -H "Authorization: Bearer sk_live_..." \
  -d name="T. Nkosi" \
  -d idNumber="8501015800083"
Response
{
  "id": "scr_c92e01",
  "status": "clear",
  "matches": []
}

legal basis

Under section 13 of the Electronic Communications and Transactions Act 25 of 2002, a hand-drawn electronic signature is valid for ordinary commercial contracts, provided intent and reliability can be shown. Every signed document gets an audit certificate page recording exactly what a court would look for if a signature is ever disputed.