KYC & KYB API for Indonesia

Enterprise-grade KYC API, without enterprise pricing.

Verify people, businesses, bank accounts, documents and biometrics through one developer-first API platform built for Indonesia. Pay only for completed results.

Built for fintechs, lenders, marketplaces, payment platforms, e-commerce and other Indonesian digital businesses.

HMAC-signedReplay-protectedScoped keysEncrypted at restFully auditedPay per result
One API. Real verification results.
signed request · example values Live
POST /v1/kyc/verify
X-Api-Key: key_live_••••7c2e
X-Signature: v1=c07a51e2…a418
Approved200 OK
{
  "decision": "approved",
  "faceMatch": "PASS",
  "liveness": "PASS",
  "document": "PASS"
}
Built for
The verification suite

One integration standard for every check.

One signing scheme, one response format and one audit trail — use a single API or the complete KYC flow.

Registry checks

Data checks

Biometric & document

KYC Verify

One call. One decision you can act on.

Selfie and KTP in — approved, review or rejected out.

Instead of building four verification systems yourself, use one API.

  • The whole check, one price. Quality gate, face match, passive liveness and document checks in a single call.
  • Never approved on a guess. Approval requires every component to pass; anything inconclusive returns review.
  • Document checks included. Document integrity and data-consistency checks run on every card.
Explore KYC Verify API From Rp1.750 / verification
  1. 01Quality gate
  2. 02Face match
  3. 03Passive liveness
  4. 04Document checks
  5. 05Decision
Platform

More than verification APIs.

Run the verification operation, not just the verification request — fraud signals, policies, reviews, webhooks, batches, hosted verification, audit and certificates, all included.

No platform surcharge — included with your verification usage

Verify

Operate

Govern

Security, in depth

Every request has to earn its answer.

Built for sensitive identity data. An ordered chain of checks runs before a single field is returned — and sensitive data is encrypted at rest.

01
Authenticated key
Active keys only
02
Timestamp window
±5-minute freshness
03
Single-use nonce
Replays rejected
04
HMAC signature
Constant-time check
05
Rate budget
Per-key limits
06
Key scope
Granted capabilities only
07
Verified result
Encrypted & audited
Images never stored Embeddings never returned NIK masked in records Model version on every decision
Pricing

Simple pricing. No enterprise maze.

Know what you'll pay before you integrate — published per-result pricing, no annual commitment, volume pricing when you scale.

  • Don't pay for failed inputsInvalid input, rate limits, provider errors and rejected photos are never billed.
  • No annual commitmentNo monthly minimum on pay-as-you-go.
  • Volume pricingFrom 1,000 verifications a month, custom from 50,000.

Launch pricing Temporary launch prices from Rp70 per check.

FAQ

Common questions

Anything else? Our team answers technical and commercial questions.

How does pricing work?

You pay per completed result, and each product has its own price. Invalid input, rate limits, provider errors and photos rejected by the quality gate are not billed.

Is there a minimum commitment?

No annual commitment or monthly minimum on pay-as-you-go pricing. Volume pricing is available from 1,000 verifications a month.

Can I use a single API, like Face Match only?

Yes. Every API works on its own. KYC Verify combines them into one call when you want a single decision.

How do I get access?

Request access and we activate your dashboard account. You then create API keys with only the scopes you need.

How is personal data handled?

Photos are processed in memory and not stored. Face embeddings are never stored or returned. OCR values go only to the caller; our records keep a masked NIK.

Do you offer webhooks, batch processing or a no-code option?

Yes. Signed webhooks, batches of up to 1,000 checks, and a hosted verification link you can send to users without building any screens.

Ready to verify your first customer?

Start with one API. Add complete KYC when you need it.