Errors and Solutions

This guide contains the most common errors when using the WPify Woo GP webpay plugin and steps to resolve them.

Payment Errors

Verification failed — invalid signature

Cause: The response signature from GP webpay could not be verified. This usually means the public key does not match the GP webpay environment, or the key file is corrupted.

Solution:

1. Verify that the Public key path in WooCommerce → Settings → Payments → GP webpay points to the correct file
2. Make sure you are using the public key that matches the selected environment (Test vs. Production) — test and production environments use different public keys
3. Re-download the public key from GP webpay and replace the file on your server
4. Check that the key file has not been modified or corrupted during upload (use binary/FTP transfer mode)

Payment failed — transaction rejected by GP webpay

Cause: GP webpay rejected the payment. This can happen for various reasons including insufficient funds, expired card, or 3D Secure failure.

Solution:

1. Check the order notes in WooCommerce for the specific error code returned by GP webpay
2. Ask the customer to try a different card or contact their bank
3. Verify that the Merchant number is correct
4. If the issue persists across multiple customers, contact GP webpay support

Order stays in "Pending payment" after payment

Cause: The callback from GP webpay did not reach your website, or the response verification failed.

Solution:

1. Check that your website is publicly accessible (not behind a password or IP restriction)
2. Verify that no security plugin or firewall is blocking requests to /wp-json/wpify-woo/v1/gpwebpay
3. If using a caching plugin, make sure it does not cache REST API endpoints
4. Check the logs at WPify → WPify Logs for the wpify-woo-gpwebpay plugin — look for callback entries and possible errors
5. Ensure your SSL certificate is valid — GP webpay may not redirect to sites with invalid certificates

Configuration Errors

GP webpay gateway does not appear in WooCommerce Payments

Cause: The plugin is not activated or the license is not valid.

Solution:

1. Go to Plugins and verify that WPify Woo GP webpay is activated
2. Go to WPify → WPify Woo GP webpay and check the license status
3. Go to WooCommerce → Settings → Payments and enable the GP webpay gateway

Private key not found

Cause: The path to the private key file is incorrect, or the file does not exist at the specified location.

Solution:

1. Verify the Private key path in the gateway settings — the path must be relative to the document root (e.g. wp-content/uploads/private/mykey.key)
2. Check that the file actually exists on the server at the specified path
3. Ensure the web server has read permissions for the key file
4. If you uploaded the key via FTP, make sure it was transferred in binary mode

Frequently Asked Questions (FAQ)

What is the deposit flag?

The deposit flag controls when the payment amount is charged from the customer’s card:

• Deposit immediately — the full amount is charged right away when the customer completes the payment
• Authorize — only a hold (authorization) is placed on the customer’s card. The actual charge must be captured later through the GP webpay merchant admin portal. This is useful when you need to verify the order before charging.

If you use authorization mode, remember to capture the payment in the GP webpay admin before the authorization expires (typically 7–30 days depending on the card issuer).

Where do I get the private and public keys?

The keys are obtained from GP webpay as part of the merchant onboarding process:

1. Private key — you generate a private key and a certificate signing request (CSR). The private key stays on your server and is never shared.
2. Public key — GP webpay provides their public key for verifying payment responses. This key is different for the test and production environments.

Contact GP webpay support or your account manager for detailed instructions on key generation. They typically provide documentation and tools for creating the key pair.

Does the plugin support refunds?

No, the plugin does not support automatic refunds through WooCommerce. Refunds must be processed manually in the GP webpay merchant admin portal.

Does the plugin support recurring payments?

No, the plugin does not support recurring or subscription payments. It is designed for one-time card payments only.

Can I use the plugin with the block checkout?

Currently, the plugin supports the classic WooCommerce checkout only. Block-based checkout (WooCommerce Checkout Block) is not supported at this time.