CLICK's Shop API lets suppliers expose their services through the payment platform. A supplier's billing system implements Prepare and Complete requests, connecting its services with acceptance through CLICK SuperApp, web, USSD and Telegram interfaces under its integration model.
TL;DR:
- CLICK Shop API connects merchant billing with CLICK payment acceptance.
- Prepare and Complete use separate action values and related transaction identifiers.
- CLICK’s PHP integration distinguishes Shop API methods from Merchant API operations.
Summary
Purpose and Scope
CLICK Shop API connects a merchant’s billing system with CLICK payment acceptance. CLICK’s public PHP integration requires the merchant to be connected through the Shop API scheme, linking its payment model to the supplier’s own application.
Supplier Role
The integration configuration identifies the merchant, service and user and includes a secret key. Its payment model can be used directly or extended by the merchant’s application, so the billing integration sits within the merchant’s server-side software.
Prepare and Complete
Prepare uses action 0 and Complete uses action 1. Both examples carry CLICK and merchant transaction identifiers, the amount, error information, signature time and signature string. Complete additionally carries the merchant preparation identifier, linking the later stage to its earlier billing step.
Interface Boundary
The same library documents Merchant API operations separately, including invoice creation, status checks and card-token methods. Those operations should not be treated as the Prepare/Complete contract.
Keywords
- CLICK
- Shop API
- Uzbekistan
- Billing Integration
- Prepare Callback
- Complete Callback
- Payment Validation
- Order Fulfilment
- USSD
- Merchant Integration