Synchronization pitfalls in PDP Mobile with 1C:ERP for accounting and meters
How PDP Mobile linked personal accounts, charges, meter readings, and PDF receipts with 1C:ERP — and where the data model is easy to get wrong.
How SellerHub Found Revenue Discrepancies in Large Catalogs
In SellerHub, revenue reconciliation with marketplaces started failing for large sellers: commissions, penalties, and logistics were calculated differently, and reports required batch processing.
How PDP Keeps Deleted Deals for Loss Analysis
PDP now uses soft delete for deals: a manager picks one of 13 loss reasons, and the sales team gets data for analyzing the funnel.
How CryptoScope Protected Paid Plans from Cannibalization
We break down part of CryptoScope’s plan configuration: base access, webhook events, grace period, downgrade, and P2P trading risk warnings.
Why PDP Moved Away from Manual Holdbacks for Defects
In PDP, instead of a manually entered hold amount, we added `hold_percentage`: the system calculates a percentage of the work value based on the scope and contract, and the money stays with the platform until the defects are resolved.
How PDP Mobile Pays Utilities with Cards and SBP
PDP Mobile now supports two utility payment flows: cards via redirect and SBP via QR/deep link. Separate TTLs handle expired links.
How PDP prevented duplicate booking payments
PDP added duplicate-payment protection at two levels: in the application business logic and in the database. Discrepancies between the bank and the system were handled separately.
How PDP reserves apartments through bank payment links
In PDP, we connected an acquiring bank for online apartment reservations: payment links with TTL, a redirect to the bank page, and a callback with digital signature verification.
How MedConnect keeps a medical consultation going after a connection drop
In MedConnect, we added consultation context autosave, reconnect, and real-time connection status so the doctor and patient return to the same session.