Mulai

Langkah awal untuk partner yang ingin mengintegrasikan dengan Kesles Merchant.

1. Daftar Partner

Hubungi tim Kesles Merchant di partner@kesles.com untuk mendapatkan:

• partner_id (UUID)
• credential_key (identifier publik — aman di-log)
• credential_secret (dikirim via channel terenkripsi — bukan email)

Detail lengkap alur onboarding → Partner Onboarding.

2. URL Dasar

Lingkungan	URL Dasar
Production	https://api-merchant.kesles.com
Staging	https://api-merchant-staging.kesles.com

Semua endpoint partner publik berada di prefix /partner/v1. Endpoint internal / administratif tidak di-host di domain ini dan tidak di-expose ke partner.

3. Tukar Credential menjadi Access Token

curl -X POST "https://api-merchant-staging.kesles.com/partner/v1/auth/token" \
  -H "Content-Type: application/json" \
  -d '{
    "credential_key": "'$KESLES_CREDENTIAL_KEY'",
    "credential_secret": "'$KESLES_CREDENTIAL_SECRET'"
  }'

Response:

{
  "token_type": "Bearer",
  "access_token": "eyJhbGc...",
  "expires_in": 3600,
  "scopes": ["merchant.read", "transaction.read"],
  "partner_id": "uuid",
  "partner_code": "PTR-DEMO-001",
  "partner_name": "Partner Demo"
}

scopes (array) menentukan endpoint mana yang boleh dipanggil — partner referral umumnya merchant.read + transaction.read; partner finance/scoring dapat tambahan scoring.read atau risk-summary.read. Token berlaku selama expires_in detik (default 3600).

4. Request Pertama

Contoh request list merchant referral:

curl -X GET "https://api-merchant-staging.kesles.com/partner/v1/partners/{partner_id}/referral-merchants" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "X-Request-ID: $(uuidgen)"

Response sukses:

{
  "partner_id": "uuid",
  "partner_code": "PTR-DEMO-001",
  "items": [
    {
      "merchant_id": "uuid",
      "merchant_code": "MRC-000123",
      "merchant_name": "Toko Contoh",
      "merchant_status": "active",
      "referral_code": "KESLES-PARTNER-XXX",
      "access_type": "referral",
      "granted_at": "2026-01-15T08:30:00Z"
    }
  ]
}

5. Langkah Berikutnya

• Onboarding Partner — alur lengkap kickoff → go-live
• Referensi API Partner — spec endpoint lengkap
• Autentikasi HMAC — pattern signature untuk endpoint yang signed (partner-specific flows yang memerlukan HMAC)