Version: 2.0 | Last Updated: October 1, 2026

Overview

Yativo provides a comprehensive identity verification system for both individuals (KYC) and businesses (KYB). You can verify your customers using either:

• API Submission — programmatically submit all customer data and documents
• Hosted KYC/KYB Links — redirect your customers to a Yativo-hosted verification page

Every customer must complete verification before they can use Yativo payment services (virtual accounts, payouts, deposits, etc.). After successful KYC/KYB, customers receive endorsements that unlock specific payment rails (e.g., SEPA, SPEI, USD Base).

Verification Flow

1. Create a Customer  →  POST /customer
2. Submit KYC or KYB  →  POST individual-kyc/submit  OR  POST business-kyc/submit
3. Check Status        →  GET /customer/kyc/{customer_id}
4. Customer Approved   →  Endorsements activated, payment rails available

Authentication

All API requests require an API key. Send both headers on every request. There's no login call and no token to refresh.

X-Api-Key: yativo_pk_...
X-Api-Secret: yativo_sk_...

Create keys in the dashboard under Developers → API Keys. The secret is shown only once. Each key only works from the server IPs listed on it (enforced from midnight on 14 October 2026). See Getting Started for details.

⚠️ Legacy API keys (Account ID + App Secret with POST /auth/login) are deprecated. From 15 October 2026, login tokens only work in the Yativo dashboard and server requests must use an API key.

Idempotency

To prevent duplicate operations, include an Idempotency-Key header in all POST, PUT, and PATCH requests.

Idempotency-Key: unique-request-identifier-string