hesabpaygateway
HPOS and Block Checkout compatibility
Last Updated: October 14, 2026HPOS Back up the store and check extension compatibility on staging. WooCommerce configures order storage under Settings → Advanced → Features. For an existing store, complete the required synchronization before switching storage. Follow the official HPOS migration guide. Block Checkout Block Checkout is page content, not a general “Enable Block Checkout” switch in Advanced Features....
Getting support and escalating an issue
Last Updated: October 14, 2026Start with the relevant details Use the support portal or contact sales@hesabpaygateway.com. Include the order number where appropriate, plugin version, selected environment, time and a clear description of the expected and actual result. Attach only redacted logs or screenshots. Never send a merchant PIN, API key, full card details or permanent administrator password. If access...
Troubleshooting webhook connectivity
Last Updated: October 14, 2026Read the receiver response HTTP 503 with “Authentication service unavailable” means the receiver could not complete its authentication check. Check the selected environment, outbound provider access and provider availability. HTTP 404 may indicate a missing route or a missing transaction; the response detail matters. Redirects, HTML error pages and HTTP 405 can prevent the provider...
Interpreting Lite and Pro logs
Last Updated: October 14, 2026Read the operation and result together Session creation, signature verification, transaction lookup and vendor payout are different operations. Record the environment, HTTP status, response format and redacted reference for the failing step. A success-looking browser page is not payment evidence. HTTP 503 indicates unavailability; a timeout can leave a transfer outcome unknown. Use the provider...
Identifying common errors
Last Updated: October 14, 2026Separate the failing step License activation: check expiry, purchase eligibility, site allowance and the license server response. Session creation: check the gateway environment, provider HTTP status and redacted response format. Payment confirmation: compare provider evidence with the order and review webhook verification. Vendor payout: inspect the existing ledger before any retry. HTTP 503 is service...
Preparing for more traffic
Last Updated: October 14, 2026Use measured capacity Measure checkout response time, provider latency, scheduled-task backlog and database behavior with a representative staging workload. A compatibility declaration does not establish capacity for thousands of orders. Keep private account and payment endpoints outside public page caches. Review worker capacity, provider limits and recovery procedures before increasing traffic. Roll out one significant...
Aligning payments and fulfillment
Last Updated: October 14, 2026Confirm before delivering Match the provider payment to the correct WooCommerce order before releasing paid downloads or dispatching goods. A customer return, manual status change or webhook reachability check is not sufficient evidence. Choose Processing or Completed according to the work remaining. Check the resulting emails, stock and account access. Handle unpaid, refunded and reversed...
Training staff to troubleshoot safely
Last Updated: October 14, 2026Give staff a clear sequence Identify whether the issue concerns a license, checkout session, payment confirmation or vendor payout. Record the time, version, environment and redacted reference. Compare provider evidence with the order and ledger. Escalate an unknown outcome before retrying a transfer or changing fulfillment status. Limit permissions to the staff role’s needs. Never...
Updating the plugin safely
Last Updated: October 14, 2026Before updating Read the release notes and requirements. Back up the database, files and private licensing material where applicable. Test the exact ZIP on staging with your theme, checkout and active extensions. For Lite, use the WordPress.org update channel. For Pro, keep an eligible license activated and use the official update or account-download workflow. Do...
Testing transactions after changes
Last Updated: October 14, 2026Use a repeatable checklist On staging, test session creation, an authorized provider payment, verified notification handling, the WooCommerce order status and the expected customer download or fulfillment step. Include failure and cancellation paths. For vendor payouts, confirm recipients, allocations, ledger entries and duplicate protection without making unauthorized transfers. Record the plugin version, environment and redacted...
What data goes to external services
Last Updated: October 14, 2026Payment and licensing have different flows The payment integration sends the data needed to create and verify provider sessions and transactions. The licensing service handles the Pro key, installation identity and activation state. Routine license activation does not require a copy of your shoppers’ order database. HTTPS protects transport; it does not mean every JSON...
Privacy and merchant responsibilities
Last Updated: October 14, 2026Describe actual processing Your privacy notice should describe the account, billing, support, payment and licensing data your business actually uses, along with its providers and retention practices. A gateway installation is not automatic GDPR compliance or a complete consent-management system. WordPress and WooCommerce include privacy tools, but decide what can be exported or erased against...
HTTPS and server access
Last Updated: October 14, 2026Protect the store and receiver Use a valid HTTPS certificate for the public site and webhook receiver. Keep administrator access limited, use strong authentication and protect private backups and server-side credentials. Do not bypass certificate verification or signature checks to make checkout work. Keep public cart, account and payment URLs separate from private release storage....
Hosted payments and PCI responsibilities
Last Updated: October 14, 2026A plugin is not a compliance certificate Redirecting shoppers to a hosted payment provider can change the card-data flow. It does not automatically remove your website from PCI DSS responsibilities, certify your business, or establish your eligible Self-Assessment Questionnaire. Confirm scope, provider validation and required assessment with your acquirer or a qualified assessor. Keep the...
How webhook verification works
Last Updated: October 14, 2026Provider verification The integration verifies incoming signatures and timestamps using HesabPay’s server-side verification endpoint and the API key for the matching environment. Do not invent a local HMAC formula, derive a signature from the merchant PIN, or disable verification to clear a dashboard warning. Order evidence Verified signatures authenticate a notification; payment processing also needs...
Checking prices, currencies and rounding
Last Updated: October 14, 2026Compare each amount Start with the WooCommerce order total, including the configured discounts, tax, shipping and fees. Compare the gateway’s recorded conversion and provider-session amount. Check decimal formatting and rounding with known examples. Language and currency are separate settings. A translated label must not change the numeric value. Do not promise arbitrary currency support or...
Translating checkout labels
Last Updated: October 14, 2026Keep presentation separate from transaction data Translate visible labels and instructions using the tools supported by your checkout type and theme. Confirm product names, validation errors, totals and return-page messages in each language. Classic WooCommerce field hooks do not automatically register fields in Block Checkout. Use the appropriate WooCommerce integration for the chosen checkout. Do...
Payment language options in Pro
Last Updated: October 14, 2026Choose an available language WordPress and WooCommerce provide site-language and translation facilities. Pro’s language selector controls the available payment-interface option described in the installed settings. It does not automatically translate your entire store or guarantee compatibility with every translation plugin. Select a supported option, then check checkout instructions, provider redirects and return pages in the...
Manual exchange rates in Pro
Last Updated: October 14, 2026Set an explicit conversion rate Activate Pro, choose the Manual exchange-rate method and enter the positive USD-to-AFN rate described by the installed field. Confirm the direction and supported currency before saving. Use a known order total to check conversion and rounding. A manual rate is an administrative choice, not a live quote, automatic profit strategy...
Automatic exchange rates
Last Updated: October 14, 2026Gateway conversion Automatic conversion is available in Lite and Pro for supported currencies. The gateway uses its configured rate source and conversion workflow when preparing payment amounts; this is not a guarantee of live market pricing or hourly catalog-price synchronization. Check the rate and converted amount recorded for the payment session against the WooCommerce total....
Avoiding duplicate and uncertain transfers
Last Updated: October 14, 2026Before any retry Keep the order, session and transaction references together. Compare the existing payout ledger with the provider dashboard. A timeout or temporary service error can occur after the provider has received a transfer. Do not create a new session, change a reference or resubmit money merely because the browser did not show success....
Pro payment and payout controls
Last Updated: October 14, 2026Controls available in Pro Pro provides manual currency conversion, supported vendor payout controls, custom success and failure destinations, language options and advanced diagnostics. Availability depends on the installed release and license status. Lite does not provide the Pro manual vendor payout workflow. The fixed vendor allocation uses a percentage share; it is not a built-in...
Setting up WC Vendors payouts
Last Updated: October 14, 2026Check the supported integration Vendor payout controls require Pro, a valid license and the supported WC Vendors integration. Do not assume compatibility with every marketplace plugin. Enable the intended multi-vendor mode and review vendor recipient details, the allocation percentage and the merchant remainder. Use known product totals, discounts, fees, taxes and shipping when checking a...
Configuring vendor shares
Last Updated: October 14, 2026Review the installed version The fixed Pro settings use Vendor Share Percentage: the portion of eligible discounted product line totals allocated to vendors. The label and meaning in an older release can differ. Read the installed field description before changing existing settings. In the fixed allocation, shipping, fees and taxes are excluded from the vendor...
Automatic and manual vendor payouts
Last Updated: October 14, 2026Choose one payout mode Vendor payouts are a Pro feature for supported WC Vendors integrations. Manual Vendor API Mode overrides automatic distribution. A customer payment and a later vendor transfer are separate events. In the fixed payout workflow, automatic processing depends on a verified paid order, the configured eligible order status, valid vendor allocation and...
Physical and digital fulfillment
Last Updated: October 14, 2026Payment and delivery are separate checks For digital products, verify that an eligible paid order grants the expected account download. For physical products, confirm payment before shipping and keep the order in the appropriate fulfillment status. Choosing Completed can trigger downstream actions; it does not prove that a parcel was delivered. Test order emails, downloads,...
Keeping checkout clear
Last Updated: October 14, 2026Match the purchase information Show the same price, license term and site allowance on the pricing page, product and checkout. Explain the required customer account and where paid downloads appear. Keep payment method descriptions accurate for digital products. Use clear labels and required-field messages, accessible controls and layouts that work on a narrow screen. Retain...
Choosing the paid order status
Last Updated: October 14, 2026Processing or Completed Use the gateway’s Order Status After Payment setting for the intended fulfillment workflow. Processing usually leaves fulfillment work outstanding; Completed indicates that the merchant considers the order fulfilled. A status label alone is not provider evidence. Only a verified successful payment should trigger the gateway’s paid transition. A manual status change does...
Configuring payment webhooks
Last Updated: October 14, 2026Register the receiver Copy the webhook URL from WooCommerce → Settings → Payments → HesabPay and register it in the matching HesabPay dashboard. Use the actual store URL and HTTPS for a public production receiver. Reachability and payment confirmation A dashboard reachability check only establishes that the receiver responded. It does not prove signature verification...
The payment lifecycle
Last Updated: October 14, 2026From checkout to confirmation WooCommerce creates the order and the gateway requests a provider payment session. The shopper follows the approved provider payment URL. The provider processes the payment. The receiver verifies the notification and matches the transaction evidence to the order. The order moves to the configured paid status only when confirmation succeeds. A...
Improving checkout performance
Last Updated: October 14, 2026Measure before changing settings Measure page loading, session creation and webhook processing separately. The provider’s response time is not the same as page-render time. Use appropriately sized images, keep supported dependencies and test caching on staging. Exclude cart, checkout, account, webhook and protected-download responses from public page caching. Do not cache one customer’s account or...
Keeping useful and private transaction logs
Last Updated: October 14, 2026Review the right record Use WooCommerce order notes, gateway logs and the Pro payout ledger where available. Compare references with the provider dashboard. A logged request or HTTP response does not by itself prove a successful payment. Restrict log access, redact exports and retain only what is needed for support and operations. Do not publish...
Using debug mode in Lite and Pro
Last Updated: October 14, 2026Collect the smallest useful evidence Open the installed gateway’s settings and use the available debug option when investigating a reproducible problem. Lite provides basic diagnostics; advanced transaction tools require Pro and an eligible license. Record the time, plugin version, selected environment, operation and HTTP response status. Keep API keys, merchant PINs, license keys and customer...
Moving from sandbox to production
Last Updated: October 14, 2026Production checklist Back up the store and confirm merchant approval with HesabPay. Select Production and enter the production API key privately. Register the live store’s webhook in the production dashboard. Review currency, totals, payout settings and the verified-payment order status. Arrange an authorized payment test, then compare the provider transaction and WooCommerce order before fulfilling...
Sandbox and production environments
Last Updated: October 14, 2026Keep environments separate Sandbox and Production use separate API keys and provider dashboards. A working production key does not validate a sandbox configuration, and sandbox failure does not establish a production outage. Use a staging store for tests. Check the request environment and HTTP status in redacted gateway logs. HTTP 503 means the requested service...
First-time store setup checklist
Last Updated: October 14, 2026Prepare Back up files and the database. Confirm the ZIP’s WordPress, WooCommerce and PHP requirements. Check merchant approval and obtain the correct environment’s API key privately. Keep only one HesabPay edition active; activate a valid license for Pro. Verify Review currency conversion, the webhook URL and the order status after verified payment. Test the intended...
Deploying plugin updates with Git or SVN
Last Updated: October 14, 2026Separate source control from deployment Use Git for your private source history and review changes before packaging a release. WordPress.org SVN distributes the public Lite edition; it is not a place for Pro packages, customer keys or merchant credentials. Build a ZIP containing only the intended plugin directory and reviewed runtime files. Exclude credentials, database...
Initial configuration and secure setup
Last Updated: October 14, 2026Configure the gateway Open WooCommerce → Settings → Payments → HesabPay. Choose Sandbox or Production and use the API key issued for that same environment. Set the checkout title, description and order status after verified payment. Register the displayed webhook URL in the same provider environment. Check currency conversion, checkout, provider payment and WooCommerce order...
Installing Lite or Pro
Last Updated: October 14, 2026Before installation Back up files and the database. Read the requirements declared by the ZIP you are installing and verify every extension on a staging copy. Keep only one HesabPay gateway edition active. Lite Install HesabPay Gateway for WooCommerce from WordPress.org, activate it, then open WooCommerce → Settings → Payments → HesabPay. Pro Sign in...
HesabPay for WooCommerce: start here
Last Updated: October 14, 2026What the plugin does HesabPay connects WooCommerce checkout to the provider’s payment service. Available methods and merchant eligibility are controlled by HesabPay. Lite includes standard payments and automatic conversion. Pro adds licensed controls for manual conversion, custom redirects, supported WC Vendors payouts and diagnostics. Check the installed version and current pricing before choosing a feature....
