mufassall

Konspekt · Biznes jarayonlar

Pulni qaytarish va chargeback

14 daq · O'rta · mufassall.dtwin.uz/uz/l/refunds-and-chargebacks/

← Darsni ochish

Muammo

Do'kon pulni ikki yo'l bilan qaytaradi: o'zi to'liq yoki qisman refund qiladi, yoki karta egasining banki pulni chargeback orqali majburan qaytarib oladi. Ikkalasi ham "qandaydir summani ayirish"dek ko'rinadi va ikkalasi bir xil joylarda sinadi: tahrirlangan to'lov qatori, ikki marta yuborilgan bosish, bir vaqtda qaytarayotgan ikki xodim, faqat keyinroq webhook bilan keladigan status va hech kim kuzatmagan dispute muddati.

Nimani o'rganasiz

  • Nega refund alohida yozuv va alohida buxgalteriya provodkasi bo'ladi, asl to'lov esa hech qachon tahrirlanmaydi
  • Idempotency kaliti va shartli update refund'ni ikki marta yoki olingan summadan ortiq to'lanishidan qanday saqlaydi
  • Asinxron tugaydigan refund statuslari: pending, succeeded, failed va ikki marta yoki noto'g'ri tartibda keladigan webhook'lar
  • Chargeback hayot sikli: dispute ochilishi, pulni ushlab turish, muddatgacha dalil yuborish, yutish yoki yutqazish va provayder hisoboti bilan kunlik solishtirish
Yakuniy sahna

Diagramma kod sifatida

Darsdagi yakuniy sxemani matn ko'rinishida oling va Jira, GitLab, GitHub, Notion yoki hujjatga qo'ying: Mermaid u yerlarda o'zi chiziladi. D2 va PlantUML (Confluence, IntelliJ) uchun alohida variantlar bor.

Mermaid: sxema

flowchart LR
  n_support(["Support xodimi"])
  n_api["Refund servisi"]
  n_db[("To'lovlar bazasi")]
  n_provider>"Karta provayderi"]
  n_support2(["Ikkinchi xodim"])
  n_issuer>"Emitent bank"]
  n_recon("Kunlik solishtirish")
  n_support -->|"chaqiruv"| n_api
  n_api --> n_db
  n_api -->|"chaqiruv"| n_provider
  n_support2 -->|"chaqiruv"| n_api
  n_provider -.->|"asinxron"| n_api
  n_issuer -->|"asinxron"| n_provider
  n_recon --> n_provider
  n_recon --> n_db

Mermaid: so'rovlar ketma-ketligi

sequenceDiagram
  participant n_api as Refund servisi
  participant n_db as To'lovlar bazasi
  participant n_provider as Karta provayderi
  participant n_issuer as Emitent bank
  participant n_recon as Kunlik solishtirish
  Note over n_api,n_db: To'langan buyurtma va qaytarilgan tovar
  n_api->>n_db: SELECT id, status, captured_minor FROM payments WHERE id = 'pay_7731'#59;
  n_db-->>n_api: pay_7731 #124; captured #124; 450000
  Note over n_api,n_db: Refund to'lovning ustidan yoziladi
  n_api->>n_db: UPDATE payments
  Note over n_api,n_db: Refund yangi yozuv va yangi provodka
  n_api->>n_db: BEGIN#59;
  Note over n_api,n_provider: Timeout va ikkinchi bosish
  n_api->>n_provider: 14:02:10.0 POST /v1/refunds payment=pay_7731 amount=150000
  Note over n_api,n_provider: Refund id'si idempotency kaliti bo'ladi
  n_api->>n_provider: POST /v1/refunds HTTP/1.1
  n_provider-->>n_api: HTTP/1.1 200 OK
  Note over n_api,n_db: Ikki xodim bir vaqtda qaytaradi
  n_api->>n_db: captured 450000, already refunded 150000, left 300000
  Note over n_api,n_db: Tekshirish va band qilish bitta buyruqda
  n_api->>n_db: UPDATE payments
  n_db-->>n_api: agent A: UPDATE 1 refunded_minor = 350000
  Note over n_provider,n_api: Provayder keyinroq javob beradi
  n_provider->>n_api: POST /webhooks/provider HTTP/1.1
  n_api-->>n_provider: HTTP/1.1 200 OK (stored, applied in 40 ms)
  Note over n_issuer,n_provider: Mijozning banki pulni qaytarib oladi
  n_issuer->>n_provider: dispute.created dp_3307
  Note over n_api,n_db: Pulni ushlab tur, muddatgacha javob ber
  n_api->>n_db: BEGIN#59; -- dispute.created dp_3307
  Note over n_recon,n_db: Har kuni provayder hisoboti bilan solishtir
  n_recon->>n_db: 06:00 provider report 2026-11-18: 412 refunds, 9 disputes

D2

direction: right

n_support: "Support xodimi" {
  shape: rectangle
}
n_api: "Refund servisi" {
  shape: rectangle
}
n_db: "To'lovlar bazasi" {
  shape: cylinder
}
n_provider: "Karta provayderi" {
  shape: cloud
}
n_support2: "Ikkinchi xodim" {
  shape: rectangle
}
n_issuer: "Emitent bank" {
  shape: cloud
}
n_recon: "Kunlik solishtirish" {
  shape: rectangle
  style.multiple: true
}

n_support -> n_api: "chaqiruv"
n_api -> n_db
n_api -> n_provider: "chaqiruv"
n_support2 -> n_api: "chaqiruv"
n_provider -> n_api: "asinxron" {
  style.stroke-dash: 3
}
n_issuer -> n_provider: "asinxron"
n_recon -> n_provider
n_recon -> n_db

PlantUML: so'rovlar ketma-ketligi

@startuml
participant "Refund servisi" as n_api
database "To'lovlar bazasi" as n_db
boundary "Karta provayderi" as n_provider
boundary "Emitent bank" as n_issuer
participant "Kunlik solishtirish" as n_recon
note over n_api, n_db : To'langan buyurtma va qaytarilgan tovar
n_api -> n_db : SELECT id, status, captured_minor FROM payments WHERE id = 'pay_7731';
n_db --> n_api : pay_7731 | captured | 450000
note over n_api, n_db : Refund to'lovning ustidan yoziladi
n_api -> n_db : UPDATE payments
note over n_api, n_db : Refund yangi yozuv va yangi provodka
n_api -> n_db : BEGIN;
note over n_api, n_provider : Timeout va ikkinchi bosish
n_api -> n_provider : [dublikat] 14:02:10.0 POST /v1/refunds payment=pay_7731 amount=150000
note over n_api, n_provider : Refund id'si idempotency kaliti bo'ladi
n_api -> n_provider : POST /v1/refunds HTTP/1.1
n_provider --> n_api : HTTP/1.1 200 OK
note over n_api, n_db : Ikki xodim bir vaqtda qaytaradi
n_api -> n_db : captured 450000, already refunded 150000, left 300000
note over n_api, n_db : Tekshirish va band qilish bitta buyruqda
n_api -> n_db : UPDATE payments
n_db --> n_api : agent A: UPDATE 1 refunded_minor = 350000
note over n_provider, n_api : Provayder keyinroq javob beradi
n_provider ->> n_api : POST /webhooks/provider HTTP/1.1
n_api -->> n_provider : HTTP/1.1 200 OK (stored, applied in 40 ms)
note over n_issuer, n_provider : Mijozning banki pulni qaytarib oladi
n_issuer ->> n_provider : dispute.created dp_3307
note over n_api, n_db : Pulni ushlab tur, muddatgacha javob ber
n_api -> n_db : BEGIN; -- dispute.created dp_3307
note over n_recon, n_db : Har kuni provayder hisoboti bilan solishtir
n_recon -> n_db : 06:00 provider report 2026-11-18: 412 refunds, 9 disputes
@enduml

PlantUML: komponentlar

@startuml
left to right direction
agent "Support xodimi" as n_support
component "Refund servisi" as n_api
database "To'lovlar bazasi" as n_db
cloud "Karta provayderi" as n_provider
agent "Ikkinchi xodim" as n_support2
cloud "Emitent bank" as n_issuer
collections "Kunlik solishtirish" as n_recon
n_support --> n_api : chaqiruv
n_api --> n_db
n_api --> n_provider : chaqiruv
n_support2 --> n_api : chaqiruv
n_provider ..> n_api : asinxron
n_issuer --> n_provider : asinxron
n_recon --> n_provider
n_recon --> n_db
@enduml

Xulosa

Pulni qaytarishning olti qoidasi.

1) Refund yangi qator va yangi provodka; bo'lib o'tgan to'lov hech qachon tahrirlanmaydi. 2) Refund qatorining id'si provayderga har bir chaqiruv uchun idempotency kaliti. 3) Limitni tekshirish va summani band qilish bitta shartli update'da yoki qator lock'i ostida: pending va succeeded jami hech qachon yechilgan summadan oshmasin. 4) Refund'lar asinxron tugaydi; yakuniy statusni imzolangan webhook'lardan, faqat oldinga qarab oling, pending'da qolib ketganlarini provayderdan so'rang. 5) Chargeback'ning muddati bor: pulni ushlab turing, vaqtida dalil bilan javob bering va dispute'dagi to'lovni refund qilmang. 6) Refund va dispute'larni har kuni provayder hisoboti bilan solishtiring.

Ko'rsatkichlar: boshida va oxirida

Ko'rsatkichBoshidaOxirida
Ikki marta to'langan refund0/mo0/mo
Olingandan ortiq refund0/mo0/mo
Statusi noto'g'ri refund00
Yutqazilgan chargeback0%24%
Mos kelmagan hisobot qatorlari00

Qadamlar

  1. Holat To'langan buyurtma va qaytarilgan tovar

    ord_5120 buyurtmasi karta bilan to'langan: 4 500.00, bazada 450000 minor birlik.

  2. Muammo Refund to'lovning ustidan yoziladi

    Birinchi versiya shunchaki yechilgan summani kamaytiradi va statusni o'zgartiradi.

  3. Yechim Refund yangi yozuv va yangi provodka

    Refund o'z id'si, summasi, sababi va statusi bilan alohida qator oladi, unga ishora qiluvchi teskari ishorali provodka ham yoziladi.

  4. Muammo Timeout va ikkinchi bosish

    Provayder sekin, so'rov 10 s dan keyin timeout bilan tugaydi.

  5. Yechim Refund id'si idempotency kaliti bo'ladi

    Servis avval rf_2208 refund qatorini saqlaydi, keyin provayderni Idempotency-Key: rf_2208 bilan chaqiradi.

  6. Muammo Ikki xodim bir vaqtda qaytaradi

    Birinchi refund'dan keyin 300000 qoldi.

  7. Yechim Tekshirish va band qilish bitta buyruqda

    To'lov refunded_minor hisoblagichini saqlaydi.

  8. Yechim Provayder keyinroq javob beradi

    Provayder re_51A ni pending sifatida qabul qildi.

  9. Muammo Mijozning banki pulni qaytarib oladi

    Boshqa mijoz bankiga tovar kelmadi deb yozadi.

  10. Yechim Pulni ushlab tur, muddatgacha javob ber

    Dispute o'z qatori va statusini oladi: needs_response, under_review, keyin won yoki lost.

  11. Yechim Har kuni provayder hisoboti bilan solishtir

    Har tong fon ishi provayderning refund va dispute'lar hisobotini yuklaydi va har bir qatorni provayder id'si bo'yicha moslaydi.

  12. Xulosa Xulosa

    Pulni qaytarishning olti qoidasi.

Atamalar

Qisman refund
Yechilgan summaning bir qismini qaytarish. U asl to'lovni tahrirlamaydi: alohida qator va alohida provodka bo'ladi, jami refund'lar esa yechilgan summadan oshmasligi kerak.
Chargeback
Karta egasining banki to'lovni e'tiroz bilan qaytarib olishi. Pul do'kondan darhol yechiladi, do'kon esa uni faqat muddatgacha dalil yuborib qaytarishi mumkin.
Dalil muddati
Do'kon chargeback'ga javob berishi kerak bo'lgan oxirgi payt. Undan keyin dispute javobsiz yutqazilgan hisoblanadi.
Refund summasini band qilish
Refund summasi provayder chaqirilishidan oldin, limit tekshiruvi bilan bitta shartli update'da to'lovning qaytarilgan hisoblagichiga qo'shiladi. Refund failed bo'lsa, summa bo'shatiladi.