PerfectSolution
Forum Replies Created
-
Forum: Plugins
In reply to: [Quickpay for WooCommerce] Onsite payment / iframe / embedHi @ktraving2
First of all thank you for your positive feedback – it is highly appreciated.
As of right not, the plugin does not support embedded payment. This is on our long term roadmap though 🙂 Unfortunately I have no ETA on this right now.
Forum: Plugins
In reply to: [Quickpay for WooCommerce] Default order status after paymentHi there,
No, according to my knowledge there is no way to easily change this. If this is a matter of stream lining the communication to the customers, I would suggest you to modify the email template used to customers when an order is set to processing. This email can be found and copied to your child theme in /wp-content/plugins/woocommerce/emails/customer-processing-order.php
I hope this helps you a bit. 🙂
Hi,
The plugin checks any captured amount and compares it to the order total. In case you have changed an order from 400DKK to 300DKK and captures 300DKK manually, it will not capture any further funds when completing the order.
Hi @skafte,
The proper approach in this case is to change the order total on the order. This can be done by switching the order status back to i.e. “Pending”. After that, you are allowed to edit the product prices and the order totals. Change them and save the order. When this has been done, you may complete the order and the correct amount will automatically be captured. By following this procedure, you will also ensure that the WooCommerce Reports (and other plugins) relying on the order totals, are getting the correct amounts.
Forum: Plugins
In reply to: [Quickpay for WooCommerce] Payment method updateHi Toktor,
The card is not updated on the old subscription transaction. This is simply not possible with QuickPay. Instead we are creating a new subscription with QuickPay with the new credit card. When the credit card is updated, you may find the transaction ID in your WooCommerce store and track it down in your QuickPay manager as well.
Forum: Plugins
In reply to: [Quickpay for WooCommerce] Payment method updateYes, that is correct. It will not pay any outstanding amounts automatically, but it will update the card on the subscription 🙂
Forum: Plugins
In reply to: [Quickpay for WooCommerce] Payment method updateHi Robert,
No, the subscription is not updated. The outstanding order is paid via a regular payment, but the credit card on the subscription is still the same. In this case, the customer would need to update the credit card separately afterwards.
Forum: Plugins
In reply to: [Quickpay for WooCommerce] Only “Dankort” comes up as payment option.No, you cannot use it for free. You must have an agreement with the respective acquirers to use it in production.
I suggest you direct these questions to the QuickPay support who are very competent in handling these requests 🙂Forum: Plugins
In reply to: [Quickpay for WooCommerce] Only “Dankort” comes up as payment option.Hi Carsten,
The error you are getting is because “Dankort” is the only available payment method on your merchant account. You might need to add further acquirer details to your manager.
Using ‘creditcard’ as payment method will automatically add all the supported payment methods (based on your account) to the payment window.
If you are having problems with setting up the acquirer data in your manager, please contact support@quickpay.net.
Hi @skafte
It is difficult for me to say exactly what the problem is here. Is this a problem that occurs every single time you bulk complete orders?
Is it always a problem after the first order being completed? Or is it random? Also, in order for me to get the most out of the logs, could you please let me know if the timestamps in the logs matches an incident?
Forum: Plugins
In reply to: [Quickpay for WooCommerce] Compatibility issues with WooCommerce 3.4.0?As of right now we do not have any knowledge of issues with incompatibility with WooCommerce 3.4+ – we have not experienced any issues ourselves nor received any reports from merchants using the plugin yet.
Hi Skafte,
Thank you for you report.
It sounds like a fatal- or a parse error occurs when you are processing multiple orders. Could you please attach your woocommerce-quickpay logs and error logs?
Forum: Plugins
In reply to: [Quickpay for WooCommerce] Status mismatchHi Katrine,
The payment data in the orders overview is a cached view. This means that the data might or might not be the current data. This is also why each order has the “CACHED” tag shown on it. A cached transaction can be updated by viewing the single order, as you clearly already found out 🙂
The cache was implemented to avoid excessive load when loading large order tables. Disabling the cache will require API requests for each order shown in the order overview.
If you do want to disable caching, you may add the following snippet to your theme’s functions.php file
add_filter('woocommerce_quickpay_transaction_cache_enabled', '__return_false');Forum: Plugins
In reply to: [Quickpay for WooCommerce] TLS 1.1 or TlS 1.2?Hi,
The plugin relies on the TLS protocol set in the server configuration. The plugin is not enforcing any specific version of TLS. If in doubt you should contact your hosting provider.
Forum: Plugins
In reply to: [Quickpay for WooCommerce] order_id: already exists on another paymentHi,
This error is returned by the QuickPay API when duplicated order IDs are used. There may be several reasons why this error occur, but it is usually caused by either:
- A staging/test environment creating the same order numbers as your production website
- Test transactions made before site launch
You may take a look in your QuickPay manager to look up the transactions with the order IDs mentioned in the error message. By taking a look at the transaction date and data, you should be able to identify when and how the specific transactions were created.
It is not possible to delete existing transactions in QuickPay, so the easiest and fastest way to fix this is by prefixing the your webshop’s order numbers. QuickPay has made a guide for that on this page.