An identity-verification bureau with an explainable verdict.

Upload a document and a selfie, run liveness and face match, screen against sanctions and PEP lists, and get back approved, review, or rejected — with the full evidence chain behind it. A code-level guard, not just a prompt, blocks auto-approval whenever required evidence is missing.

The use case

KYC as an asynchronous pipeline, not a black box.

Onboarding a Brazilian financial-services customer means proving a document is genuine, the person presenting it is who they claim, and they're not on a sanctions or PEP list — then being able to show your regulator exactly how you reached that conclusion.

The seven-step pipeline

What's in the box

Bureau-grade verification, evidence included.

From upload to verdict

Three calls: upload, submit, check the case.

Native KYC is asynchronous by design — a case moves through the pipeline in the background; poll `GET /v1/cases/{id}` or wait for the webhook.

1. 0. Request upload URLs and get the presigned S3 slots

   Ask for presigned S3 URLs for each image slot and upload directly to S3 — never multipart to the API itself.

   Requestbash

   curl -X POST https://api-kyc-hml.swepay.com.br/v1/cases/uploads \
     -H "Authorization: Bearer ${SWEPAY_JWT}" \
     -H "Content-Type: application/json" \
     -d '{ "slots": ["document_front", "document_back", "selfie"] }'

   Responsejson

   {
     "uploads": [
       { "slot": "document_front", "objectKey": "cases/tmp/8f3c.../front.jpg", "uploadUrl": "https://s3.sa-east-1.amazonaws.com/..." },
       { "slot": "document_back", "objectKey": "cases/tmp/8f3c.../back.jpg", "uploadUrl": "https://s3.sa-east-1.amazonaws.com/..." },
       { "slot": "selfie", "objectKey": "cases/tmp/8f3c.../selfie.jpg", "uploadUrl": "https://s3.sa-east-1.amazonaws.com/..." }
     ]
   }

2. 1. Start the liveness session, then submit the case

   Run the liveness capture against the returned `sessionId`, then submit the case with the uploaded object keys and that `livenessSessionId`. Returns `202 Accepted`.

   Requestbash

   curl -X POST https://api-kyc-hml.swepay.com.br/v1/cases \
     -H "Authorization: Bearer ${SWEPAY_JWT}" \
     -H "Content-Type: application/json" \
     -d '{
       "cpf": "***.***.***-**",
       "documentType": "CNH",
       "documentFrontKey": "cases/tmp/8f3c.../front.jpg",
       "documentBackKey": "cases/tmp/8f3c.../back.jpg",
       "selfieKey": "cases/tmp/8f3c.../selfie.jpg",
       "livenessSessionId": "sess_8f21..."
     }'

   Responsejson

   HTTP/1.1 202 Accepted
   {
     "caseId": "c4d9e2a1-3b7f-4c1a-9e2d-1f6a7b8c9d0e",
     "status": "received"
   }

3. 2. Check the case, or wait for the webhook

   Poll for status and evidence, or receive an HMAC-signed webhook when the case reaches a final status.

   Requestjson

   curl https://api-kyc-hml.swepay.com.br/v1/cases/c4d9e2a1-3b7f-4c1a-9e2d-1f6a7b8c9d0e \
     -H "Authorization: Bearer ${SWEPAY_JWT}"

   Responsejson

   {
     "caseId": "c4d9e2a1-3b7f-4c1a-9e2d-1f6a7b8c9d0e",
     "status": "approved",
     "verdict": {
       "decision": "approved",
       "reasonSummary": "Document and face-match evidence within threshold; no sanctions match."
     },
     "evidence": [
       { "step": "DocumentExtraction", "status": "passed" },
       { "step": "DocumentIntegrity", "status": "passed" },
       { "step": "Liveness", "status": "passed", "score": 98.1 },
       { "step": "FaceMatch", "status": "passed", "score": 95.6 },
       { "step": "SourceConnectors", "status": "passed" },
       { "step": "Verdict", "status": "passed" }
     ]
   }

`api-kyc-hml.swepay.com.br` above is illustrative — Native KYC has no deployed public host yet (the pipeline is implemented; onboarding onto the Marketplace Subscription Hub is pending). Full pipeline and policy reference on the developers page. Technical questions: engineering@swepay.com.br.

Security & compliance

Evidence without images.

Native KYC processes some of the most sensitive personal data a fintech handles — document, CPF, face. It's built to retain evidence, not the underlying images.

Pricing

Per-check dimensions, or a monthly plan with included volume.

Billed entirely through AWS Marketplace. `kyc_basic` covers the core pipeline; add `kyc_official` only for cases where you've configured Serpro.

Usage dimensions

Every plan below includes a bundle of `kyc_basic` checks; usage beyond the plan is billed per dimension.

Monthly plans

Priced by `kyc_basic` check volume.

Which one do I need?

Native Biometrics vs. Native KYC

Independent products (ADR-0003) that solve different problems and integrate well together. Most fintechs start with whichever matches the moment: onboarding a new customer, or re-verifying one they already know.

Need both? Subscribe to each independently on AWS Marketplace — there's no bundled SKU, and no requirement to run one to use the other.

Frequently asked

Before you integrate.

Straight answers to the questions that come up most before a compliance review.

Two ways to start.