Datanamix

Reference KYC with Datanamix. Send the signed ID, photo and AML reports, and SAVA verifies them and makes the KYC decision automatically.

Overview

Datanamix uses the signed payload model of Reference KYC. You run the Datanamix checks in your own app, then send SAVA the original Datanamix responses together with their signatures. SAVA verifies each signature against Datanamix's published signing keys, checks the results, and approves or rejects the user's KYC automatically.

You send two signed reports:

  • ID verification with photo (idVerificationPlusPhoto): SAVA verifies the signature of Datanamix's ID/photo report and checks its returned results. Approval requires a matched ID number, a matched HANIS ID result, and a returned photograph, alongside the other identity checks.
  • AML screening (amlVerification): screens the verified person against sanctions and watch lists.

SAVA does not perform a selfie comparison or liveness check in this flow. The optional faceMatchVerification payload is retained for audit and is not used in the automatic approval decision.

South African ID holders

Automatic approval with Datanamix requires a valid 13-digit South African ID number and an AML search with country ZA.

Before you start

  • Your partner account must be configured for Datanamix during onboarding.
  • Use one client reference for both Datanamix requests (the ID and the AML search) and send it as job_id. SAVA checks it against the ClientReference in both reports.
  • Keep each Datanamix response exactly as received, together with the X-Signature header returned with it. The signature only matches the original bytes.

Request

Subject: svc.user.<partner_id>.submit_kyc_reference

Request
{
  "user_id": "<SAVA-user-uuid>",
  "provider": "datanamix",
  "data": {
    "job_id": "<shared-client-reference>",
    "payload": {
      "idVerificationPlusPhoto": {
        "xSignature": "<ID-report-signature>",
        "payload": "<exact original ID response text>"
      },
      "amlVerification": {
        "xSignature": "<AML-report-signature>",
        "payload": "<exact original AML response text>"
      },
      "faceMatchVerification": {
        "payload": {
          "...": "complete face-match response"
        }
      }
    }
  }
}
FieldTypeRequiredDescription
user_idstringrequiredThe SAVA user being verified (UUID)
providerstringrequiredMust be "datanamix"
data.job_idstringrequiredThe client reference you used for both Datanamix requests. Must equal ClientReference in both reports
data.payload.idVerificationPlusPhoto.xSignaturestringrequiredThe X-Signature header returned with the ID verification with photo response (base64url)
data.payload.idVerificationPlusPhoto.payloadstringrequiredThe exact original ID verification with photo response body, as text
data.payload.amlVerification.xSignaturestringrequiredThe X-Signature header returned with the AML response (base64url)
data.payload.amlVerification.payloadstringrequiredThe exact original AML response body, as text
data.payload.faceMatchVerification.payloadobjectoptionalThe complete face-match response. Stored for audit; not used in the decision

Send the exact original response text

SAVA verifies each signature against the exact bytes Datanamix returned. Send each payload as the original response text, unchanged. Parsing and re-serializing the JSON (reordering keys, changing spacing or escaping) breaks the signature, and the submission is rejected.

Response

You receive the standard acknowledgment. It confirms receipt and is not the decision:

Response
{
  "accepted": true,
  "user_id": "<SAVA-user-uuid>",
  "job_id": "<shared-client-reference>",
  "received_at": "2026-08-13T12:00:06.300Z",
  "status": "RECEIVED"
}

Then check the result with List Users or Get User. For Datanamix the decision is usually made straight away, so the first poll normally shows approved or rejected.

What SAVA checks

The user is approved only when every check passes.

CheckRequirement
SignaturesBoth reports carry an X-Signature that verifies against Datanamix's published signing keys for their exact payload
Client referenceClientReference in both reports equals job_id
ID report resultSuccess is true and ResponseCode is 0
ID recordID number Matched, person Alive, ID not blocked, a valid 13-digit ID number, names and date of birth present
PhotoA photograph is returned and the HANIS ID is Matched
AML report resultSuccess is true and ResponseCode is 200
AML search inputsThe searched name matches the verified identity, country is ZA, and any ID number or date of birth searched matches
AML outcomeA clear no-match: nothing found, zero records, no possible matches, and no further result pages
Live dataSandbox reports never approve a real user
SAVA profileThe verified ID number, date of birth, first name and last name match the user's SAVA profile

Outcome

kyc_statusWhenkyc_rejection_reason example
approvedEvery check passes—
rejectedA signature is missing or invalididVerificationPlusPhoto: payload signature verification failed
rejectedAn ID or photo check failsID number did not match
rejectedThe AML screening isn't a clear no-matchAML screening did not return a clear no-match outcome (…)
rejectedThe verified identity doesn't match the SAVA profileprovider identity does not match user profile: date of birth mismatch
pendingThe user's SAVA profile is missing an ID number, date of birth or name, so SAVA compliance reviews it manually—

After a rejection, fix the cause (for example, resend the untouched original responses, or correct the user's profile) and submit again.

On this page