How abolfazlabdollahii/opencart works
This is an OpenCart Zibal payment extension. Shoppers see the payment option when its configuration and checkout constraints allow it, initiate a Zibal payment, then return for verification and order-status update. Administrators configure credentials and payment settings. The sampled code shows the admin settings save, storefront eligibility checks, payment request, fallback gateway calls, and callback verification; checkout dispatch and template interactions are inferred only where OpenCart’s extension structure supports them.
Main entry points: payment/zibal.php Payment Flow · payment/zibal.php Payment Settings · payment/zibal.php Method Eligibility · zibal.twig Settings Form
Components 14
Administration
- Payment Settings
admin/controller/payment/zibal.php - Settings Form
admin/view/template/payment/zibal.twig - Admin Text
admin/language
Checkout
- Method Eligibility
catalog/model/payment/zibal.php - Payment Button
catalog/view/template/payment/zibal.twig - Payment Confirmation
catalog/view/template/payment/zibal_confirm.twig - Storefront Text
catalog/language
Payment Processing
- Payment Flow
catalog/controller/payment/zibal.php
OpenCart Services
- Settings Model
- Order Service
- Order State
Other components
- Administrator
- Shopper
- Zibal Gateway
Connections 15
- Administrator → Payment Settings: configures
- Payment Settings → Settings Model: saves settings
- Payment Settings → Settings Form: renders form
- Payment Settings → Admin Text: loads text
- Shopper → Method Eligibility: requests options
- Method Eligibility → Order State: checks geo-zone data
- Shopper → Payment Flow: confirms payment
- Payment Flow → Order Service: loads order
- Payment Flow → Payment Button: renders option
- Payment Flow → Storefront Text: loads text
- Payment Flow → Zibal Gateway: requests payment
- Payment Flow → Zibal Gateway: verifies payment
- Zibal Gateway → Payment Flow: returns callback
- Payment Flow → Order Service: adds history
- Order Service → Order State: updates status