Tashqi tizimlar bilan integratsiya
Mijoz Payme orqali 1 500 000 so‘m to‘ladi. OmborPro dagi hisob-faktura “to‘langan” bo‘lishi uchun nima sodir bo‘lishi kerak?
Bizning server Payme ga “to‘ladimi?” deb so‘raydimi yoki Payme bizga xabar beradimi? Taxmin qiling.
Bu ma’ruza oxirida siz quyidagilarni bajara olasiz...
REST klientlar: Laravel HTTP klienti
Tizimlar bir-biri bilan qanday gaplashadi?
Usul tanlash — kim tashabbuskor, qanchalik tez va qanday ishonchlilik kerakligiga bog‘liq.
1REST / JSON
2SOAP / XML
SoapClient.3Webhook
4Fayl almashinuvi
5Xabar brokeri
GET, POST va javob bilan ishlash
$response = Http::acceptJson() ->connectTimeout(3) ->timeout(10) ->get('https://cbu.uz/uz/arkhiv-kursov-valyut/json/'); $response->status(); // 200 $response->successful(); // true — 2xx $usd = $response->collect()->firstWhere('Ccy', 'USD'); // tokenli JSON POST (masalan, SMS provayderi) Http::withToken(config('services.sms.token')) ->post(config('services.sms.url') . '/send', [ 'phone' => '998901234567', 'text' => 'Buyurtma BY-2026-000123 tasdiqlandi', ]) ->throw();
200 true ['Ccy' => 'USD', 'Nominal' => '1', 'Rate' => '12850.45', 'Date' => '27.10.2026', ...]
Authorization: Bearer ... sarlavhasiRequestException — usiz xato jim o‘tadiretry callback va zaxira yo‘l
try { $rows = Http::connectTimeout(3)->timeout(10) ->retry(3, 200, function (Exception $e) { return $e instanceof ConnectionException || ($e instanceof RequestException && $e->response->serverError()); }) ->get(config('services.cbu.url')) ->json(); } catch (ConnectionException|RequestException $e) { Log::warning('CBU javob bermadi', ['error' => $e->getMessage()]); $rows = null; // oxirgi saqlangan kurs ishlatiladi }
[2026-10-27 09:30:12] local.WARNING: CBU javob bermadi
{"error":"cURL error 28: Operation timed out after 10001 milliseconds"}Tashqi so‘rov uchun tavsiyalar
| Parametr | Tavsiya | Sabab |
|---|---|---|
connectTimeout | 2–5 s | Server javob bermasa tez voz kechish |
timeout | 5–15 s (veb), ≤ job timeout (worker) | Standart 30 s — php-fpm ni band qiladi |
retry | 2–3 marta, oshib boruvchi oraliq | Vaqtinchalik xatolar o‘tib ketadi |
| Qayta urinish sharti | Ulanish xatosi, 5xx, 429 | 4xx — so‘rovning o‘zi noto‘g‘ri |
| POST takrori | Faqat Idempotency-Key bilan | To‘lov yoki SMS ikki marta ketmasin |
| Kesh / zaxira | Kurslar — kuniga bir marta, bazada | Tashqi tizim ishlamasa ham ilova ishlaydi |
1-bo‘lim yakuni: REST klientlar: Laravel HTTP klienti
connectTimeout va timeout farqi nimada?1-topshiriq: Javobga qarab qaror: ok, retry yoki fail
Tashqi API ga so‘rov natijasi bo‘yicha keyingi qadamni aniqlang. $status — HTTP kod, 0 — ulanish xatosi yoki timeout. $urinish — hozirgi urinish raqami (1 dan), $maxUrinish — ruxsat etilgan jami urinishlar. 2xx — ok. Vaqtinchalik xatolar (0, 408, 429, 500–599) — urinishlar tugamagan bo‘lsa ($urinish < $maxUrinish) retry, aks holda fail. Qolgan barcha kodlar (3xx, boshqa 4xx) — fail. $status 0 yoki 100–599 oralig‘ida bo‘lmasa yoki $urinish/$maxUrinish < 1 bo‘lsa — InvalidArgumentException.
Imzo: function http_qaror(int $status, int $urinish, int $maxUrinish): string
Qaytaradi: 'ok', 'retry' yoki 'fail'.
http_qaror(200, 1, 3)
"ok"
Webhooklar: imzo va idempotentlik
To‘lov holatini qanday bilamiz?
✗ Polling: biz so‘raymiz
- Har daqiqada har bir ochiq hisob-faktura uchun so‘rov
- 1000 faktura → soatiga 60 000 ta keraksiz so‘rov
- To‘lov 59 soniyagacha kechikib ko‘rinadi
- Provayder limitiga tushish xavfi (429)
✓ Webhook: bizga xabar beriladi
- Hodisa bo‘lganda bitta POST
- Holat bir necha soniyada yangilanadi
- Lekin endpoint ommaviy — imzo shart
- Dublikatlar keladi — idempotentlik shart
VerifyTestPaySignature
public function handle(Request $request, Closure $next): Response { $ts = (string) $request->header('X-TestPay-Timestamp'); $sig = (string) $request->header('X-TestPay-Signature'); $expected = hash_hmac( 'sha256', $ts . '.' . $request->getContent(), // xom tana! config('services.testpay.secret'), ); if (! ctype_digit($ts) || abs(time() - (int) $ts) > 300 || ! hash_equals($expected, $sig)) { return response()->json(['error' => 'invalid signature'], 401); } return $next($request); }
POST /api/v1/webhooks/testpay (imzosiz)
HTTP/1.1 401 Unauthorized
{"error":"invalid signature"}Imzo qanday tekshiriladi
function verify(string $ts, string $body, string $sig, int $now): string { if (abs($now - (int) $ts) > 300) { return 'expired'; } $expected = hash_hmac('sha256', "$ts.$body", 'test-secret'); return hash_equals($expected, $sig) ? 'ok' : 'bad_signature'; } $ts = '1793088000'; $body = '{"id":"tp_9f2c","invoice":"HF-2026-000045","amount":15000000}'; $sig = hash_hmac('sha256', "$ts.$body", 'test-secret'); // provayder $now = 1793088060; $fake = str_replace('15000000', '1', $body); echo verify($ts, $body, $sig, $now) . PHP_EOL; echo verify($ts, $fake, $sig, $now) . PHP_EOL; echo verify($ts, $body, $sig, $now + 940) . PHP_EOL; echo verify($ts, json_encode(json_decode($body)), $sig, $now);
ok bad_signature expired ok
ok/ bo‘lsa — farq qiladiInvoiceService::applyPayment()
return DB::transaction(function () use ($extId, $number, $tiyin) { $invoice = Invoice::where('number', $number) ->lockForUpdate()->firstOrFail(); if (Payment::where('external_id', $extId)->exists()) { return 'duplicate'; // 200 bilan javob beramiz } $amount = bcdiv((string) $tiyin, '100', 2); // tiyin → so‘m $invoice->payments()->create([ 'amount' => $amount, 'method' => 'card', 'external_id' => $extId, 'paid_at' => now(), ]); $invoice->paid_amount = bcadd($invoice->paid_amount, $amount, 2); $invoice->status = bccomp($invoice->paid_amount, $invoice->total, 2) >= 0 ? 'paid' : 'partial'; $invoice->save(); return 'processed'; });
1-so‘rov: {"status":"processed"} paid_amount = 1500000.00, status = paid
2-so‘rov: {"status":"duplicate"} hech narsa o‘zgarmadi2-bo‘lim yakuni: Webhooklar: imzo va idempotentlik
json_encode($request->all()) bo‘yicha hisoblab bo‘lmaydi?2-topshiriq: Webhook imzosini tekshirish
TestPay webhook so‘rovini tekshiring. Imzo — "$timestamp.$body" satrining $secret bilan HMAC-SHA256 qiymati (kichik harfli hex). Sarlavhadagi imzo sha256= prefiksi bilan kelishi ham mumkin — prefiksni olib tashlang. Tartib: $timestamp faqat raqamlardan iborat bo‘lmasa — bad_request; |$now − $timestamp| > 300 — expired; imzo mos kelmasa — bad_signature; aks holda — ok. Solishtirish faqat hash_equals bilan.
Imzo: function imzo_tekshir(string $body, string $timestamp, string $signature, string $secret, int $now): string
Qaytaradi: 'ok', 'bad_request', 'expired' yoki 'bad_signature'.
imzo_tekshir('tp_1:1500', '1000', hash_hmac('sha256', '1000.tp_1:1500', 'k'), 'k', 1100)"ok"
To‘lov tizimlari: Payme va Click
To‘lov qanday o‘tadi
Hisob-faktura
HF-2026-000045 ni yaratadi va to‘lov havolasini beradiTekshiruv so‘rovi
Mijoz to‘laydi
Tasdiq so‘rovi
payments ga yozamizJavob
Solishtirish
payments taqqoslanadiPayme va Click integratsiyasi
| Jihat | Payme (Merchant API) | Click (SHOP API) |
|---|---|---|
| Protokol | JSON-RPC 2.0, bitta URL | Prepare va Complete so‘rovlari |
| Autentifikatsiya | Basic auth sarlavhasi (kassa kaliti) | sign_string — MD5 imzo (maxfiy kalit bilan) |
| Summa | Tiyinda (butun son) | So‘mda |
| Tranzaksiya id | params dagi Payme id → external_id | click_trans_id → external_id |
| Hisob | params.account dagi maydon (masalan, faktura raqami) | merchant_trans_id |
| Xato javobi | JSON-RPC error obyekti | Javobdagi xato kodi va izohi |
Bitta endpoint — metod bo‘yicha taqsimlash
public function __invoke(Request $req, PaymeService $s): JsonResponse { $id = $req->input('id'); $auth = (string) $req->header('Authorization'); if (! $s->checkAuth($auth)) { return $s->error($id, 'auth'); // hujjatdagi xato kodi } $p = (array) $req->input('params', []); return match ($req->input('method')) { 'CheckPerformTransaction' => $s->checkPerform($id, $p), 'CreateTransaction' => $s->create($id, $p), 'PerformTransaction' => $s->perform($id, $p), 'CancelTransaction' => $s->cancel($id, $p), 'CheckTransaction' => $s->check($id, $p), 'GetStatement' => $s->statement($id, $p), default => $s->error($id, 'method_not_found'), }; }
← {"method":"Foo","params":{},"id":1024}
→ {"jsonrpc":"2.0","error":{"code":-32601,"message":"Method not found"},"id":1024}3-bo‘lim yakuni: To‘lov tizimlari: Payme va Click
3-topshiriq: JSON-RPC 2.0 so‘rovini tahlil qilish
Payme kabi JSON-RPC endpoint uchun so‘rovni tahlil qiling va javob tuzing. JSON noto‘g‘ri — xato -32700 Parse error. Natija JSON obyekt emas (son, satr, null, massiv-ro‘yxat yoki bo‘sh) yoki method satr emas — -32600 Invalid Request. method $metodlar ro‘yxatida yo‘q — -32601 Method not found. params berilgan, lekin obyekt/massiv emas — -32602 Invalid params. Aks holda result = ['method' => ..., 'params' => params yoki []]. id — so‘rovdagi id (bo‘lmasa yoki JSON yaroqsiz bo‘lsa null).
Imzo: function jsonrpc_javob(string $json, array $metodlar): array
Qaytaradi: ['jsonrpc' => '2.0', 'result' => [...], 'id' => ...] yoki ['jsonrpc' => '2.0', 'error' => ['code' => int, 'message' => string], 'id' => ...] — kalitlar shu tartibda.
jsonrpc_javob('{"method":"CheckTransaction","params":{"id":"t1"},"id":5}', ['CheckTransaction']){"jsonrpc":"2.0","result":{"method":"CheckTransaction","params":{"id":"t1"}},"id":5}SMS shlyuzlari va 1C bilan ma’lumot almashish
SmsGateway interfeysi va bildirishnoma kanali
interface SmsGateway { public function send(string $phone, string $text): string; } final class SmsChannel { public function __construct(private SmsGateway $gateway) {} public function send(object $notifiable, Notification $n): void { $phone = $notifiable->routeNotificationFor('sms', $n); if ($phone) { $this->gateway->send($phone, $n->toSms($notifiable)); } } } // Notification::via(): return ['database', SmsChannel::class];
[2026-10-27 10:02:11] local.INFO: SMS → 998901234567: "Buyurtma BY-2026-000123 jo'natildi" (LogSmsGateway)
via() da sinf nomi qaytariladirouteNotificationForSms() metodini chaqiradiNima uchun ‘ belgisi SMS narxini oshiradi
| Kodlash | Bitta SMS | Ko‘p qismli (har qism) | Qachon |
|---|---|---|---|
| GSM-7 | 160 belgi | 153 belgi | Faqat lotin harflari, raqamlar, oddiy belgilar |
| UCS-2 | 70 belgi | 67 belgi | Kirill, ‘ ’ “ ” kabi belgilar, emoji |
Buyurtma jo'natildi (19) | GSM-7: 1 SMS | — | Oddiy apostrof GSM-7 da bor |
| “Buyurtma jo‘natildi” + 60 belgi | UCS-2: 2 SMS | 67 + 12 | Bitta ‘ butun xabarni UCS-2 ga o‘tkazadi |
CommerceML (soddalashtirilgan) dan tovarlarni o‘qish
$xml = <<<XML <КоммерческаяИнформация ВерсияСхемы="2.05"> <Каталог><Товары> <Товар><Ид>8f1c-01</Ид><Артикул>UN-001</Артикул> <Наименование>Un 1-nav 50 kg</Наименование></Товар> <Товар><Ид>8f1c-02</Ид><Артикул>SH-002</Артикул> <Наименование>Shakar 50 kg</Наименование></Товар> </Товары></Каталог> </КоммерческаяИнформация> XML; $doc = simplexml_load_string($xml); foreach ($doc->Каталог->Товары->Товар as $t) { printf("%s | %s | 1C:%s\n", $t->Артикул, $t->Наименование, $t->Ид); } echo 'Jami: ' . count($doc->Каталог->Товары->Товар);
UN-001 | Un 1-nav 50 kg | 1C:8f1c-01 SH-002 | Shakar 50 kg | 1C:8f1c-02 Jami: 2
products.sku ga mosimport.xml — XMLReader bilan oqimdaTo‘rt variant va ularning o‘rni
1CommerceML fayllari
import.xml (katalog), offers.xml (narx, qoldiq). Paketli, kuniga bir necha marta.2Sayt bilan almashinuv protokoli
3OData REST
4Maxsus HTTP-servis
5Excel / CSV
ProductsImport.6Qoida
4-bo‘lim yakuni: SMS shlyuzlari va 1C bilan ma’lumot almashish
Xabar brokerlari: RabbitMQ va Kafka
Laravel navbati, RabbitMQ va Kafka
| Jihat | Laravel navbati (Redis) | RabbitMQ | Kafka |
|---|---|---|---|
| Model | Vazifa navbati | Navbatli broker (AMQP) | Taqsimlangan jurnal |
| Iste’molchilar | Shu ilovaning workerlari | Turli servislar, turli tillar | Consumer group lar |
| O‘qilgandan keyin | Job o‘chiriladi | Ack dan keyin o‘chadi | Retention muddatigacha qoladi |
| Tartib | Navbat ichida FIFO (taxminan) | Navbat ichida | Partitsiya ichida qat’iy |
| Kuchli tomoni | Oddiy, Laravel ichida | Marshrutlash, ack, DLX | Oqim, replay, katta hajm |
| OmborPro misoli | Hisobot, e-mail | OrderConfirmed → 1C, SMS | POS hodisalari analitikasi |
RabbitMQ va Kafka lug‘ati
1Exchange (RabbitMQ)
2Ack / DLX
3Prefetch
4Topic / partition (Kafka)
5Offset
6Consumer group
OrderConfirmed hodisasini e’lon qilish (php-amqplib)
use PhpAmqpLib\Connection\AMQPStreamConnection; use PhpAmqpLib\Message\AMQPMessage; $conn = new AMQPStreamConnection('rabbitmq', 5672, 'app', 'secret'); $ch = $conn->channel(); $ch->exchange_declare('omborpro.events', 'topic', false, true, false); $message = new AMQPMessage(json_encode([ 'event' => 'order.confirmed', 'number' => 'BY-2026-000123', 'total' => '1500000.00', ]), [ 'content_type' => 'application/json', 'delivery_mode' => AMQPMessage::DELIVERY_MODE_PERSISTENT, ]); $ch->basic_publish($message, 'omborpro.events', 'order.confirmed'); $ch->close(); $conn->close();
RabbitMQ: exchange omborpro.events (topic) order.confirmed → queue 1c.orders (binding: order.*) order.confirmed → queue sms.notify (binding: order.confirmed)
order.confirmed — bog‘lanish andozalari bo‘yicha navbatlargaKalit bo‘yicha partitsiya: tartib qayerda saqlanadi
function partition(string $key, int $count): int { return crc32($key) % $count; // Kafka aslida murmur2 ishlatadi } $events = [ ['key' => 'BY-2026-000123', 'type' => 'OrderConfirmed'], ['key' => 'BY-2026-000124', 'type' => 'OrderConfirmed'], ['key' => 'BY-2026-000123', 'type' => 'OrderShipped'], ]; $offsets = [0, 0, 0]; foreach ($events as $e) { $p = partition($e['key'], 3); $o = $offsets[$p]++; echo "{$e['type']} {$e['key']} -> p$p, offset $o" . PHP_EOL; }
OrderConfirmed BY-2026-000123 -> p1, offset 0 OrderConfirmed BY-2026-000124 -> p0, offset 0 OrderShipped BY-2026-000123 -> p1, offset 1
Hodisani yo‘qotmasdan e’lon qilish
Tranzaksiya
confirmed bo‘ladi va shu tranzaksiyada outbox ga hodisa qatori yoziladiCommit
Relay
sent_at IS NULL qatorlarni oladiE’lon
sent_at ni belgilaydiIste’molchi
sent_at ni yozishga ulgurmay yiqilsa — hodisa qayta yuboriladi. Shuning uchun iste’molchi idempotent.5-bo‘lim yakuni: Xabar brokerlari: RabbitMQ va Kafka
Asosiy xulosalar
1Servis sinfi + config
config/services.php va .env da.2Timeout, retry, throw
connectTimeout, timeout, faqat vaqtinchalik xatolarda retry, ->throw() va zaxira yo‘l.3Webhook = imzo + idempotentlik
hash_equals, timestamp, payments.external_id unique.4Payme va Click — merchant API
5SMS va 1C — kelishilgan qoidalar
6Broker — tizimlararo
Yakunlashdan oldin sakkizta savol
retry(3, 200, $fn) dagi $fn vazifasi?hash_equals?11-amaliy mashg‘ulot: 5 ta PHP topshiriq va loyiha bosqichi
CBU javobidan exchange_rates qatorlari
Narxni valyutada ko‘rsatish
Sanaga mos kurs (dam olish kunlari bilan)
TestPay webhook protsessori
1C katalogi bilan sinxronlash farqi
Darsni tark etishdan oldin
Javoblaringizni yozing (✎ Javob yozish) yoki qog‘ozga yozib topshiring.