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 theClientReferencein both reports. - Keep each Datanamix response exactly as received, together with the
X-Signatureheader returned with it. The signature only matches the original bytes.
Request
Subject: svc.user.<partner_id>.submit_kyc_reference
| Field | Type | Required | Description |
|---|---|---|---|
user_id | string | required | The SAVA user being verified (UUID) |
provider | string | required | Must be "datanamix" |
data.job_id | string | required | The client reference you used for both Datanamix requests. Must equal ClientReference in both reports |
data.payload.idVerificationPlusPhoto.xSignature | string | required | The X-Signature header returned with the ID verification with photo response (base64url) |
data.payload.idVerificationPlusPhoto.payload | string | required | The exact original ID verification with photo response body, as text |
data.payload.amlVerification.xSignature | string | required | The X-Signature header returned with the AML response (base64url) |
data.payload.amlVerification.payload | string | required | The exact original AML response body, as text |
data.payload.faceMatchVerification.payload | object | optional | The 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:
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.
| Check | Requirement |
|---|---|
| Signatures | Both reports carry an X-Signature that verifies against Datanamix's published signing keys for their exact payload |
| Client reference | ClientReference in both reports equals job_id |
| ID report result | Success is true and ResponseCode is 0 |
| ID record | ID number Matched, person Alive, ID not blocked, a valid 13-digit ID number, names and date of birth present |
| Photo | A photograph is returned and the HANIS ID is Matched |
| AML report result | Success is true and ResponseCode is 200 |
| AML search inputs | The searched name matches the verified identity, country is ZA, and any ID number or date of birth searched matches |
| AML outcome | A clear no-match: nothing found, zero records, no possible matches, and no further result pages |
| Live data | Sandbox reports never approve a real user |
| SAVA profile | The verified ID number, date of birth, first name and last name match the user's SAVA profile |
Outcome
kyc_status | When | kyc_rejection_reason example |
|---|---|---|
approved | Every check passes | — |
rejected | A signature is missing or invalid | idVerificationPlusPhoto: payload signature verification failed |
rejected | An ID or photo check fails | ID number did not match |
rejected | The AML screening isn't a clear no-match | AML screening did not return a clear no-match outcome (…) |
rejected | The verified identity doesn't match the SAVA profile | provider identity does not match user profile: date of birth mismatch |
pending | The 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.