The site does not work can be quite different in several ways: the payment method is not seen at all in the Checkout, the order registration button is incorrect, the request to make a transaction is rejected, the transfer to the bank page is not made or the user returns to the site after paying but the order is not confirmed. Until the failure stage is determined, the payment gatewayway plug-in removes most of the evidence.
Quick answer:Before attempting again, check the order and transaction section of the payment gatewayway panel to ensure that the previous payment is not repeated. Then enter the transaction with a controlled order, timestamp, order number, status and non-sensitive ID. Put the network browser, the WooCommerce/PHP log and the payment gatewayway panel report together in the same space.
What is the exact stage of the breakdown?
| The sign. | Possible layer | A witness. |
|---|---|---|
| Payment method not displayed | Activation, currency, country, method of sending or betting | Settings and checkout message |
| Order registration will be suspended before transfer. | validation, JavaScript, PHP or order building | Ajax response and log |
| The API is running out of doors. | Credential, amount, callback, network or TLS | Official error code and request ID |
| The bank opens, but the return is ruined. | Callback, route, WAF or DNS | Redirect chain and access log |
| Successful payment, failed order. | Verify/webhook or status mapping | Transaction ID and log verification |
When the payment method is not visible
Activating the plugin is not enough. Many portals determine availability based on currency, country of billing, minimum/maximum amount, product type, subscription, or method of sending. Check Console and Checkout messages and match settings with the same version of the plugin.
Checkout and JavaScript
If the request does not click on the request record, see the first Console error, field authentication, and form interference. If the request is created, its status and response are important; the response 200 may also have an error payload. Multiple clicks or refresh during Pending may create another order or payment attempt.
Credits and testing environment
The acceptor, API key, or secret key must be relevant to the same production/sandbox environment and domain. Do not include the secret in a screenshot, public ticket, repository, or log. Check for gaps, newlines, cancelled credentials, or IP restrictions from the official panel. After possible disclosure, rotate the key from the official path; hiding text in the interface does not neutralize disclosure.
Money, unit of money and round.
Compare the order amount in WooCommerce, the amount sent to the API and the amount registered in the payment gatewayway panel. The error of converting real/domain, percentage, discount, shipping fee or tax can disqualify verification. Test the correction with several checked amountsincluding coupons and shipping and do not repeat the amount logic in multiple plugins.
Connecting the server to the port API
Transaction creation is usually done from a store server. Check DNS, TCP connection, TLS, timeout, output proxy, and HTTP response. Turning off TLS certificate checks is not the solution and increases the possibility of a mid-range attack. If the output IP needs to be whitelisted, specify the actual NAT IP from the valid path.
A timeout error does not mean a complete failure of the transaction; it may have been accepted when the request was made but the response to the store has not been received. Before retry, request the status with a single ID or API inquiry.
Callback and Webhook
The portal must be able to call a return URL or webhook from the Internet and with valid HTTPS. Language redirect, forced login, maintenance mode, Basic Auth, WAF, Geo-block and cache can stop the callback. Compare the exact URL sent to the portal to the URL registered in the panel; domains with/without www and scheme are different.
System time, certification and signature of the application
Ports with signed requests or limited timestamps depend on the exact server time. Check the time synchronization status and expiration date of the certificate chain; the store's display timezone is not the same as the system clock. Do not set the time to go back to pass manual validation. Fix the root of the NTP, container, or host discrepancy, and then create a new request.
If the error relates to the signature, check the canonical string, encoding, field order and credential of the same environment as the official plug-in/output documentation. Do not delete the signature algorithm for poor acceptance or secure comparison.
Which logs should we use?
- WooCommerce Status → Logs for the source associated with the portal
- PHP error log for fatal/exception on the same timestamp
- access/error log Web server for callback and upstream status
- Network browser to request order registration and redirect
- Gateway panel for status and official transaction error code
Enable the plug-in identification log only as needed and turn off or restrict it after the test. Card numbers, CVVs, passwords, secrets, full tokens, cookies and personal data should not be registered or published.
WAF, Cache and security plugins.
For false positive, find a specific rule ID and request and create a limit exception. Complete disabling of WAF, CSRF protection or rate limit is not acceptable. Cart, Checkout and callback pages should not have public cached responses, but excessive bypass will also remove the entire store from the cache for no reason.
The inconsistency of the version and the Hooks.
After updating WooCommerce, PHP, a template, or a plugin, the signature, Checkout Block, or HPOS may become incompatible with the plugin. Check the official changelog and requirement.
Management of incidents when a gate is shut down or unstable
If the error rate is suddenly high for all users, record an incident with start time, last deployment version, and request ID sample. Check the official status of the provider and the output network errors separately. Display the alternative gateway only when its configuration, settlement, callback, and refund experience have already been tested; adding an unknown payment add-on in a hurry creates more risk in the middle of the final.
The checkout message should be transparent and not encourage the customer to click-by-click. If there is a possibility of accepting the request, tell the user to check the order and account status before trying again. Reconcile the error after the event, Pending orders and clear transactions; returning service alone does not close previous payment records.
The safe detection process.
- Do not stop selling; first, identify the scope and status of the current transactions.
- Provide backup, staging and a validated trial method/quantity.
- Record the failure stage and the unresponsive request/response.
- Interpret the error code in the official documents at the same gate.
- Check the currency settings, callback, credential and availability.
- Comply with network, TLS, WAF and server logs with timestamp.
- After modification, test the entire cycle of creation, payment, verification and change of status.
Smoke test after the correction.
- Guest and user logged in.
- Physical product and virtual product if there is.
- Delivery, discounts and taxes
- The payment was successful and cancelled.
- Returns browser and independent webhook
- Order status, inventory, email and trial refund
If after payment, the order remains Failed or Pending, the guideSuccessful payment with a failed order.If the transfer doesn't start and the spinner stays,He's got the check-out tracking system.It's more appropriate.
Common Mistakes
- Repeated payment for re-exams without prior transaction review
- Switching port, template and cache simultaneously
- Secret release in log or support message
- Disable TLS verification or WAF
- Interpreting timeout as a definite failure
- Manual change of order status without financial reconciliation
- Testing just redirect and ignore the verify/webhook
When do you need special assistance?
If the money is cut from the customer, the transactions are conflicting or callback is recurring, the test is more on financial risk production.Support for the WooCommerce storeIt can order store logs, web servers and gateway panels with reconcile transaction IDs and point of failure without blind manipulation.
Common Questions
Does clearing the cache solve the payment gateway problem?
Only if the response or asset is old is a factor, the error credential, API, amount or callback will not be resolved with purge.
Why is the payment gatewayway for the manager, but not for the client?
Compare the availability conditions, country, currency, method of sending, cache and session of two users.
Is it safe to enable Debug?
If limited, temporary and redacted, error display to the user or secret registration and payment data is not secure.
Did he have to re-pay the order at the timeout?
No, check the order status and the payment gatewayway panel or inquiry first so that there are no repeat payments.