To’lov provayderlari bilan SLA

TL; DR

Kuchli SLA = biznes effektiga bog’langan o’lchanadigan KPI (AR, TtW, TtR, latency, webhook SLA, settlement timeliness), shuningdek protsessual majburiyatlar (eskalatsiyalar, RFO/RCA, o’zgarishlar) va moliyaviy rag’batlantirish (service credits). Biz o’z metriklarimiz va provayderimiz ma’lumotlarini kuzatib boramiz, kundalik tsiklda solishtiramiz va fayloverning tayyor pleybuklarini saqlaymiz.

1) Atamalar va amal qilish sohasi

SLA (Service Level Agreement) - xizmat ko’rsatish sifati bo’yicha shartnoma majburiyatlari.
SLO (Service Level Objective) - metriklar bo’yicha aniq maqsadli darajalar (soat/kun/oy).
PSP/Acquirer/APM/Bank/RTP - provayder turlari; SLA relslari boʻyicha farq qilishi mumkin.
Usullar/harakatlar:’deposit/auth/capture’,’refund’,’payout/withdrawal’,’webhooks’,’settlement’.

SLA hajmi: API/panel, to’lovlarni qayta ishlash, notifikatsiyalar, hisobotlar/reyestrlar, qo’llab-quvvatlash, o’zgartirish (change management), xavfsizlik va komplayens.

2) SLA metrik lug’ati

2. 1 Foydalanish imkoniyati va unumdorligi

API Uptime% (daqiqalik/besh daqiqalik granulyarlik)

Auth/Capture Latency p95/p99 (сек)

Webhook Delivery p95 (сек) и Success % (≥99. 9%)

Settlement Timeliness: ariza berilgan T + N ga kiritilgan batchalar ulushi (99% ≥)

2. 2 Konvertatsiya va sifat

Approval Rate (AR) quyidagi segmentlar bo’yicha: ’country × BIN × method × device’(variativ ravishda, istisnolar bilan «referens koridor» sifatida)

Soft Decline Recovery Support (retraylarni, yo’nalishlarni qo’llab-quvvatlash)

Refund Success % и TtR p95

Payout Success % и TtW p95

Duplicate/Idempotency Incidents = 0

2. 3. Ma’lumotlar va hisobotlarning ishonchliligi

Report Delivery SLA: реестры `transactions/settlements/fees` до `HH:MM UTC` (≥99. 5%)

Schema Stability/Change Notice: 30 kun ≥ xabarnoma

Webhooks vs Reports Consistency: tafovutlar ≤ 0. 05%

2. 4 Hodisalar va qo’llab-quvvatlash

Ustuvor darajalar bo’yicha MTTA/MTTR (javob/tiklashgacha bo’lgan vaqt)

RFO/RCA (Reason For Outage/Root Cause Analysis) ≤ 5 ish kuni

Planned Maintenance Notice ≥ 7 kun (kritik - ≥ 14)

3) Tavsiya etiladigan maqsadli qiymatlar (mo’ljallar)

(Usulga/bozorga moslashtiriladi; kartochka/instant/APM farqlanadi.)

Uptime API (oylik): ≥ 99. 95% (kritik kontur)

Latency p95: Auth ≤ 1. 0 s, Capture ≤ 1. 5 s, Webhooks ≤ 3 s

AR Corridor (referens): matritsangizdagi bozor/BIN medianidan past emas - 2-3 p.p. (hisoblash usulini belgilash)

Refund TtR p95: kartalar ≤ T + 1 b.d., instant rails ≤ 60 s

Payout TtW p95 (instant): ≤ 120 s; (T + 1) - talabnoma berilgan kunda 100%

Settlement Timeliness: ≥ 99% da T + N

Report Delivery: ≥ 99. kelishilgan vaqtgacha 5%

4) O’lchash va dalillar bazasi

Savdo tomoni: telemetriya API (app-level timers), loging’request _ id’, vebxuk loglari, ichki eventlar’auth/capture/refund/payout’, xususiy Uptime/Latency dashbord.
Provayder tomoni: status-sahifa, hodisalar bo’yicha texnik hisobotlar, SLA bo’yicha hisobotlar, AR/latency, settlement-statement bo’yicha yuklar.
Taqqoslash: kundalik voqealaringizni PSP hisobotlari bilan reconcile («Taqqoslash»... ga qarang), AR/latency statistik nazorati (yoʻlaklar).
Yagona vaqt: UTC, ntp sinxronizatsiyasi.

5) Moliyaviy rag’batlantirish va kreditlar

• Uptime/Latency/Webhook → aniqlangan% fee-kreditlar degradatsiyasi.
• Settlement → kreditni kechiktirish, kechiktirilgan summa/komissiya foizida.
• AR-koridorning surunkali buzilishi → routing/komissiyani qayta ko’rib chiqish/qo’shma reja.
• Cap/Collar: kreditlarning yuqori limiti/oy, istisnolar (fors-major, tartibga solish harakatlari).
• Non-performance Exit: N ketma-ket qoidabuzarliklarda bekor qilish huquqi.

6) Hodisalar va eskalatsiyalar jarayoni

P0-P3 sinflari (P0 - to’liq kirish/ommaviy rad etish).
MTTA/MTTR maqsadlari: masalan, P0 MTTA ≤ 15 min, MTTR ≤ 2 soat.
Kanallar: navbatchi chat/telefon, tiket-tizim, maqom-sahifa.
RCA (≤ 5 r.d.) profilaktika rejasi bilan: texnik, protsessual, marshrutizatsiya chora-tadbirlari.
Sapport uchun kommunikatsiya: oʻyinchilar uchun xabarlar shablonlari (kechikishlar/muqobillar).

7) O’zgarishlarni boshqarish (Change Management)

Notice ≥ 30 kun: API/reyestrlar sxemasi, 3DS parametrlari, marshrutlar, settlement-kalendar, vositachilik modellari.
Qo’shma testlar Sandbox + 5-10% trafik uchuvchisi.
Rollback rejasi va «feature-flag» sizning tomoningizda.

8) Xavfsizlik va SLAdagi komplayens

Tranzit/tinchlikda shifrlash, sertifikatlash (PCI DSS/SOC), zaifliklar va ularni bartaraf etish muddatlari.
Sanksiya/AML-skrining, PEP, SoF/SoW - provayder tomonidan qo’llab-quvvatlanadigan funksiyalar va ularning SLA.
Data Processing Addendum (DPA), retention и DSAR.
Breach Notification: Xavfsizlik hodisasida 24 soatdan ≤.

9) Monitoring va dashbordlar

1. Uptime/Latency (p50/p95/p99) usullari va mintaqalari bo’yicha.

2. Webhook SLA: yetkazib berish vaqti, muvaffaqiyatli ulushi, drebezg/dublikatlar.

3. AR/Soft Declines’BIN × country × provider’kesimida.

4. Refund/Payout Health: Success %, TtR/TtW p95.

5. Settlement Timeliness va Aging bo’lmagan batchlar.

6. Incident Panel: MTTA/MTTR, ochiq RCA, kredit-memo.

10) SLA-tahlillar uchun ma’lumotlar modeli (minimal)

ts_utc, provider, method_code, action(auth/capture/refund/payout/webhook/settlement),
latency_ms, status, is_success,
bin, country, device_os,
webhook_delivery_sec, webhook_retry_count,
settlement_date, settlement_status,
incident_id, severity, mtta_sec, mttr_sec

11) SQL-kesmalar (misol)

11. 1 Uptime/Latency

sql
SELECT
DATE_TRUNC('hour', ts_utc) AS h,
provider, method_code, action,
COUNT() FILTER (WHERE is_success)=1. 0 / COUNT() AS success_rate,
PERCENTILE_CONT(0. 95) WITHIN GROUP (ORDER BY latency_ms) AS p95_ms
FROM sla_events
WHERE action IN ('auth','capture')
GROUP BY 1,2,3,4;

11. 2 Webhook SLA

sql
SELECT
DATE_TRUNC('hour', ts_utc) h, provider,
PERCENTILE_CONT(0. 95) WITHIN GROUP (ORDER BY webhook_delivery_sec) AS wb_p95,
AVG(CASE WHEN webhook_retry_count=0 THEN 1 ELSE 0 END) AS wb_success
FROM sla_events
WHERE action='webhook'
GROUP BY 1,2;

11. 3 Settlement Timeliness

sql
SELECT settlement_date, provider,
AVG(CASE WHEN settlement_status='ON_TIME' THEN 1 ELSE 0 END) AS on_time_share
FROM sla_events
WHERE action='settlement'
GROUP BY 1,2;

12) SLA bandlari namunasi (namunasi)

text
1. Availability
- Monthly API Uptime ≥ 99. 95% (5-min granularity).
- Exclusions: Planned Maintenance (≤ 2h/month, 00:00–06:00 UTC, 7d notice).

2. Performance
- Auth p95 latency ≤ 1. 0 s; Capture p95 ≤ 1. 5 s.
- Webhook delivery p95 ≤ 3 s, success ≥ 99. 9%, no duplicates.

3. Financial Operations
- Settlement T+N on-time ≥ 99%; reports delivered by 07:00 UTC D+1 (≥ 99. 5%).

4. Incident Management
- P0: MTTA ≤ 15 min, MTTR ≤ 2 h; P1: 30 min / 4 h.
- RCA within 5 business days with preventive actions.

5. Data & Changes
- 30-day advance notice for API/report schema changes.
- Backward compatibility window ≥ 60 days.

6. Remedies
- Service credits per breach (tiered), cap 25% monthly fees.
- Termination right upon 3 consecutive P0 breaches.

13) Feylover pleybuklari

Auth/Latency degradatsiyasi

Amallar: smart-routingni muqobil PSPga kiritish, zaif BINlarga 3DS-challenge oshirish, soft-decline retrajlarini backoffli qilish.

Webhook kechikishlar/dublikatlar

Harakatlar: pollingga o’tish, qayta ishlovchilarda idempotentlikni yoqish, avto-refandlarni vaqtincha muzlatish.

Settlement ushlandi

Harakatlar: G’aznachilik StressRes-ni ishga tushirish, tezkor to’lovlar limitini vaqtincha pasaytirish, PSPda eskalatsiya, kredit-memo.

Payouts muammolari

Harakatlar: zaxira relsiga (SEPA/RTP/boshqa PSP) oʻtish, high-risk uchun’payout-lock’ni yoqish, VIPni ustuvorlashtirish.

14) Provayderlar va QBRni boshqarish

QBR (quarterly business review): AR/Latency/Webhook/Settlement/KPI-kreditlar, yaxshilash rejasi, yo’l xaritasi fich.
Benchmarking: SLO, hodisalar, qiymat (Cost/GGR), hisobot sifati bo’yicha provayderlarning qiyosiy jadvali.
Scorecard: SLAning har bir boʻlimi boʻyicha 0-5.

15) SLAni joriy etish chek-varaqasi

• Metrika, formula va segmentatsiya aniqlangan (UTC, p95/p99, hisob-kitob bazalari).
• Yigʻish/dashbordlar va har kuni PSP hisobotlari bilan solishtirish oʻrnatilgan.
• MTTA/MTTR, eskalatsiyalar, kontaktlar 24/7, maqom sahifasi yozilgan.
• Surunkali buzilishlarda service credits va bekor qilish huquqi mustahkamlangan.
• Change-notice ≥ 30 kun, sandbox testlari va rollback rejasi.
• Xavfsizlik/komplayens: PCI/SOC, breach ≤ 24h, DPA/retention.
• Feylover pleybuklari va marshrut orkestratori bilan integratsiya.
• QBR/scorecard, AR-koridorlarni muntazam kalibrlash.

16) Tez-tez xatolar

Tushunarsiz ta’riflar («muvaffaqiyat» deb hisoblash kerak) → nizolar va «qog’oz» SLA.
O’z metrikalarining yo’qligi → provayderning hisobotlariga bog’liqligi.
Moliyaviy rag’batlantirish yo’q → SLA ishlamaydi.
AR ni antifrod effekti bilan aralashtirish → hisob-kitob bazasida nima borligini aniqlang.
Ignor settlement-kalendar va taymzon → tikilmagan va kassa uzilishlari.

Xulosa

Ishchi SLA - bu umumiy iboralar to’plami emas, balki raqamlar va jarayonlar bilan tikilgan kontrakt: sizning telemetriyangiz bilan tasdiqlangan ochiq/tezlik/konversiya/xulosalar/hisobotlar bo’yicha aniq SLO, qoidabuzarlik uchun kredit-memo va feyloverning tayyor pleybuklari. Bunday SLA umidlarni tenglashtiradi, reaktsiya vaqtini qisqartiradi va monetizatsiya maqsadlarini to’g’ridan-to’g’ri qo’llab-quvvatlaydi: AR yuqori, TtW/TtR past, kassa kechikishlari kamdan-kam uchraydi va hodisalar boshqariladi.