Linux 软件免费装
Banner图

Virtuaria PagBank / PagSeguro for WooCommerce

开发者 tecnologiavirtuaria
更新时间 2026年6月20日 04:44

标签

boleto pagseguro pix cartão pagbank

下载

3.6.0 3.3.3 3.5.3 3.6.5 2.3.3 2.4.0 2.0.1 2.2.7 2.2.8 2.3.0 2.3.1 1.1.3 1.1.2 2.0.2 2.2.2 2.2.6 2.3.4 3.6.6 3.6.3 2.0.0 2.1.0 2.2.1 2.3.2 2.5.0 2.7.0 3.1.0 3.3.4 2.2.3 3.3.0 2.0.4 3.0.0 3.0.1 3.2.0 3.3.2 1.1.0 1.2.0 1.0 1.0.1 2.2.0 2.6.0 3.3.1 3.3.5 3.3.6 1.0.2 1.1.1 2.0.3 2.2.5 3.5.2 3.6.4 3.4.1 3.4.4 3.4.5 3.5.0 3.3.7 3.4.2 2.2.4 3.5.1 3.6.1 3.6.2

详情介绍:

Easy to install and configure, allows for extra charges, full and partial refunds, discounts on Pix and Boleto, 3DS authentication, payment splitting, storing payment methods, automatic payment confirmation for credit, Pix, and Boleto, among many others. Now featuring Mixed Payment, a payment method that combines Credit and Pix to bring more flexibility and convenience to online shopping. ✅ Main Features: ⭐ PREMIUM 💎 Exclusive features for those who want maximum performance and control. Get the Premium version at: https://virtuaria.com.br/loja/virtuaria-pagbank-pagseguro-para-woocommerce/ Mixed Payment (Credit + Pix) Elevate your online store's shopping experience by offering customers the option of mixed payment, partly by credit and partly by Pix, in a single order, with automatic confirmation of both payment methods. Individual, partial, or total refund options are also available directly in your store's dashboard. Configure minimum and maximum values ​​for credit and Pix, ensuring total control over transactions. Furthermore, enhanced security with 3DS technology is maintained, providing advanced protection for you and your customers. Increase your e-commerce conversion rate, purchase the premium license and activate Mixed Payment in your store (link)( https://virtuaria.com.br/loja/virtuaria-pagbank-pagseguro-para-woocommerce/ ) 📹 Plugin Playlist on YouTube 📹 ✨ Initial Connection with PagBank This plugin uses the most modern Order/Connect billing API provided by PagSeguro, allowing for much simpler and more secure configuration and activation, without the need to generate keys via the PagSeguro panel or open support tickets. 👨🏾‍🎓 Questions & Support 💌 Interested in something else? Contact us directly at tecnologia@virtuaria.com.br and guarantee a solution tailored to your needs. Features 🚀 Pix 🖥️ How ​​it works Starting with version 3.0, our plugin offers a new configuration that allows you to treat Credit, Pix, and Boleto as independent payment methods in the WooCommerce and Checkout panel. This feature facilitates the identification of payment methods in integrations with external systems (CRM, ERP, etc.), making financial management easier. Furthermore, separate methods allow third-party plugins to perform specific actions on each payment method, such as applying discounts. We continue to offer the option to operate with unified payment methods for the simplicity and convenience of users who prefer this format. This ensures full compatibility for those using previous versions of the plugin who wish to update. 💳 Save Payment Method For faster future purchases, the plugin allows you to configure the "Save Payment Method" feature. This feature does not store the buyer's credit card data, but rather a purchase code (token) for the card, which is sufficient for the customer to make future purchases without having to enter their card details again. 💰 Extra Charge The plugin has an "Extra Charge" functionality that allows you to charge an extra amount on orders made with a credit card. This function can be useful, for example, for sales of products by weight, as in this case the final value is almost always different from the initially requested amount, something very common in supermarkets. It is also useful in cases where the customer requests the inclusion of new items in the order. To make extra charges, the function to store payment data must be active. ⚡ Checkout Optimization The plugin has a setting to activate asynchronous order processing mode. This allows some of the status updates that occur during checkout to be done in the background and asynchronously, significantly speeding up checkout. We recommend activating this only if your customers usually buy many items at once and this is slowing down your checkout. ⚡ 3DS Authentication The 3D Secure (3DS) protocol is an authentication mechanism for e-commerce transactions that seeks to increase security and reliability, benefiting both sellers and consumers, reducing fraud and chargebacks. Upon completing the purchase, 3DS authentication is automatically activated, and can be direct or require additional validation, such as SMS or bank/card app. The main advantage of 3DS is the reduction of chargebacks, because when authenticating a transaction, the responsibility for chargebacks is transferred to the card issuer bank. The plugin allows configuration to enable or disable 3DS, and it's also possible to specify a minimum order value for its application. It also allows purchases even via cards without 3DS support, guaranteeing a higher conversion rate. 🌟 NEW FEATURE 01: PagBank Payment Split for WooCommerce 🌟 Ideal for online stores with multiple sellers, this FREE solution allows the total value of a purchase to be automatically split between several PagBank accounts. An easy-to-adopt solution that, in most cases, does not require any theme changes to enable an effective multi-store checkout. Compatible with payments via Credit Card, Pix, or Boleto, this functionality offers flexibility and efficiency. Perfect for a variety of business models such as marketplaces, dropshipping, and franchises, Virtuaria PagBank Split is the ideal solution to optimize your sales and multi-seller payments. 📥 More Information and Download of the Virtuaria Split Plugin 📥 📹 Watch the video about Payment Splitting 📹 🌟 NEW FEATURE 02: Correios Integration – Shipping, Labels and Tracking 🌟 Connect your WooCommerce online store to Correios efficiently and reliably. The plugin offers for free: Notes: Compatibility This plugin requires a plugin that adds Brazilian fields to the checkout to function correctly. Examples of compatible plugins: Discounts on PagBank Fees:Virtuaria Special 01: Credit 3.79% (receipt in 30 days) | Pix 0.99% | Boleto R$ 2.99; – Virtuaria Special 02: Credit 4.39% (receipt in 14 days) | Pix 0.99% | Boleto R$ 2.99; – Negotiated PagSeguro Rate: If you have already negotiated a better personalized rate with PagSeguro; – PagSeguro Standard Rate: Standard rates of the PagSeguro platform. Note: If you are already using the plugin, you need to re-establish the connection to activate the discount. Contribution If you wish to contribute to the plugin's development, please send us a pull request on Github.

安装:

Plugin Installation: With just this, it's already possible to receive payments and automatically return data. Requirements: 1- Account on PagSeguro and have WooCommerce installed; 2- Plugin [WooCommerce Extra Checkout Fields for Brazil] (http://wordpress.org/plugins/woocommerce-extra-checkout-fields-for-brazil/).
Attention: It is not necessary to configure any URL in "Redirect page" or "Transaction notification", as the plugin works directly with the PagSeguro API.
Plugin configuration screen: With the plugin installed, access the WordPress admin and go to "WooCommerce" > "Settings" > "Payments" > "PagSeguro".

升级注意事项:

No updates available

常见问题:

1 - What is the plugin's license?

This plugin is licensed under GPLv3. The code is 100% open source. We do not offer PRO versions with extra features.

2 - What do I need to use this plugin?

  • Have a current version of the WooCommerce plugin installed.
  • Have a current version of the WooCommerce Extra Checkout Fields for Brazil plugin installed.
  • Have a PagSeguro account.
  • If you wish to use Pix payments, you need to register a random key in your PagSeguro seller panel.

3 - From which countries does PagSeguro accept payments?

Currently, PagSeguro only accepts payments from Brazil and uses the Real as currency. We have configured the plugin to only accept payments from users who selected Brazil in their payment information during checkout. = 4 - What payment methods does the plugin accept? Credit card, Pix, and bank slip payments are accepted; however, you need to activate them in your account. Check the payment and installment methods.

5 - How does the plugin integrate with PagSeguro?

We integrate based on the official PagSeguro documentation, which can be found in the "integration guides" using the latest version of the payment API.

6 - Is it possible to send the "Number", "Neighborhood", and "CPF" data to PagSeguro?

Yes, it is possible, just use the plugin "WooCommerce Extra Checkout Fields for Brazil".

7 - The order was paid and the status is "processing" instead of "completed", is this correct?

Yes, by default, in paid purchases the order status automatically changes to processing, meaning you can ship your order. However, setting the status to "completed" is the merchant's responsibility at the end of the sales and delivery process. For downloadable products, the default WooCommerce setting is to allow access only when the order has the status "Completed". However, in the WooCommerce settings, under the Products tab, it's possible to enable the option "Grant access to download the product after payment", thus allowing the download when the order status is "processing". If the data is correct, you should access the "WooCommerce > System Status" page and check if fsockopen and cURL are active. You need to seek help from your hosting provider if you have fsockopen and/or cURL disabled. Finally, you can enable the Debug Log option in the plugin settings and try closing an order again (you must try closing an order for the log to record the error). With the log, you can find out exactly what is going wrong with your installation. If you don't understand the log content, that's okay, you can open a "topic in the plugin forum" with the log link (use pastebin.com.

8 - Is there automatic payment confirmation? Is the order status changed automatically?

Yes, the status is changed automatically using the PagSeguro status change notification API.

9 - Common situations for blocking PagSeguro notifications received by the plugin

The most common reason is a security plugin, firewall, or tool on the server where the store is running that is blocking notifications. In this case, simply disable the blocking or add an exception to not block notifications originating from PagSeguro. Examples:

  • Site with CloudFlare, as by default any communication from other servers to yours will be blocked. This can be resolved by unblocking the IP list. Regarding PagSeguro.
  • Security plugin like "iThemes Security" with the option to add the HackRepair.com list to the site's .htaccess file. The problem is that the PagSeguro user-agent is in the middle of the list and will block any communication. You can remove it from the list; just find where it blocks the "jakarta" user-agent and delete it, or create a rule to accept PagSeguro IPs.
  • mod_security enabled; in this case, the same thing will happen as with CloudFlare, blocking any communication from other servers to yours. As a solution, you can disable or allow PagSeguro IPs.

10 - Does it work with the PagSeguro Sandbox?

Yes, it works, and you just need to activate it in the plugin options, in addition to configuring your "test email" Remember that, if you are testing in the Sandbox, instability is common, and this may cause PagSeguro not to send status updates to the plugin.

11 - Which URLs should I use to configure "Transaction Notification" and "Redirect Page"?

It is not necessary to configure any URL for "Transaction Notification" or "Redirect Page," the plugin already tells PagSeguro which URLs will be used.

12 - Difficulties using the Sandbox

In conversation with the PagSeguro integration team, we were informed that the Orders API is not 100% updated with the Sandbox. Therefore, it is possible that some of the problems below may occur:

  • Transaction does not appear in the sandbox panel despite correct API return;
  • Status change notifications do not reach the store;
  • Refund failure;
  • Difficulties logging into the sandbox panel;
  • Internal Server Error;
  • Transaction is not found;
  • Operation timed out;
  • Bad Gateway;
  • External service error.
= 13 - What values ​​can my customers pay with this plugin? = There are no maximum values ​​for sales, however there are minimum values ​​to be transacted with PagSeguro, as listed below: Method | Card Brand | Minimum Value (R$) | Minimum Installment (R$) Credit | Visa | 1.00 | 5.00 Credit | Mastercard | 0.20 | 5.00 Credit | American Express | 0.20 | 5.00 Credit | Other brands | 0.20 | 5.00 Bank slip | - | 0.20 | - Pix | - | 1.00 | -

14 - Does this plugin allow full and partial refunds?

Yes, you can refund orders with a processing status by going directly to the order page in WooCommerce and clicking on Refund -> Refund via PagSeguro and setting the amount, whether full or partial.

15 - Is there a minimum refund amount?

Yes, the minimum refund amount via the online store is R$ 1.00. = 16 - Where can I find the plugin log? = In the menu “WooCommerce > Status > Logs”. It is also possible to generate a detailed system report in the "WooCommerce > Status" menu, via the "Get System Report" button.

17 - What is the correct format for the "Name on Invoice" field on the card?

PagSeguro does not allow the "Name on Invoice" field to have more than 17 characters. It also does not allow the use of special characters or spaces. This may generate the message "PagSeguro: Check the data entered and try again". From version 2.3.0 onwards, the plugin configuration does not allow the character limit to be exceeded, so if you filled in this field in an older version and the name is out of standard, simply adjust the field and save the configuration.

18 - Pix Orders Being Cancelled

When a purchase is made via Pix payment, an order with the status "Awaiting" is created in the panel, however, if the Pix payment is not identified by the time limit, the order will automatically change to the status "Cancelled". The time limit is defined in the “PIX Code Validity” field on the plugin settings screen (there is a 30-minute tolerance beyond the time limit). If the payment was made but not identified by the plugin, some guidance can be found in topic 9 of this FAQ. = 19 - How to activate special rates? From version 2.5.0 onwards, Virtuaria, in partnership with PagSeguro, offers special conditions related to the rate charged to merchants using the plugin. To enable these new rates, it is necessary to disconnect the plugin and reconnect it using one of the special rates provided on the plugin settings screen. Currently we have the following options:

  • Virtuaria Special 01: Credit 3.79% (receipt in 30 days) | Pix 0.99% | Boleto R$ 2.99;
  • Virtuaria Special 02: Credit 4.39% (receipt in 14 days) | Pix 0.99% | Bank slip R$ 2.99;
  • Negotiated PagSeguro (if you have negotiated a personalized rate with PagSeguro);
  • PagSeguro standard.
Note: Rates may be changed at PagSeguro's discretion. = 20 - By using 3DS, will my store be free from disputes on PagBank? The use of 3DS authentication does not guarantee the prevention of disputes in your online store. The buyer protection program remains active, requiring you to maintain delivery records in the cardholder's name to contest possible claims. However, when a transaction is authenticated, the issuing bank assumes responsibility for fraudulent chargebacks (Liability shift), providing greater security. In addition, 3DS authentication increases the approval rate, reducing suspicions of unauthorized purchases. It is important to note that 3DS only addresses cases of fraud, not issues related to delivery or consumer rights, such as product/service quality. = 21 = Problems with Pix Payment Confirmation Your online store is configured to receive automatic payment confirmations from PagSeguro/PagBank through the Virtuaria PagSeguro plugin, but these notifications are being blocked by the hosting server before they even reach your website. This happens because: The server identifies the notifications as "not secure" PagSeguro sends notifications using a technical identifier (Go-http-client/2.0), which some servers automatically block. Security firewalls are interfering Many hosting providers use protection systems (such as ModSecurity or CDN) that can block requests of specific formats. How to Solve? Step 1: Contact Your Hosting Support Explain that the server is blocking PagSeguro notifications and request: Add to the whitelist: ✅ /wc-api/WC_Virtuaria_PagSeguro_Gateway ✅ Go-http-client/2.0 Disable temporary blocks: Ask them to check if the firewall or CDN is blocking requests to the endpoint: /wc-api/WC_Virtuaria_PagSeguro_Gateway What to Write to Support? Use this template: Subject: PagSeguro Notification Blocking Hello, I am having problems receiving payment notifications from PagSeguro in my store through the Virtuaria PagSeguro plugin. Technical Details: Blocked endpoint: /wc-api/WC_Virtuaria_PagSeguro_Gateway Server error code: HTTP 406 Used: Go-http-client/2.0 Request that: Add to firewall whitelist Verify if the above endpoint is allowed Example of the error log: 15.229.10.19 - - [29/Apr/2025:16:45:06 -0300] "POST /wc-api/WC_Virtuaria_PagSeguro_Gateway HTTP/2.0" 406 226 "-" "Go-http-client/2.0" Sincerely, [Your Name] Important! If you use Cloudflare or a CDN: Temporarily disable or configure rules to not block the Go-http-client/2.0 User-Agent. The Virtuaria PagSeguro plugin is working correctly: The problem is not with the plugin, but with external security settings.

Screenshots

  1. Plugin settings;
  2. Credit card settings - separate;
  3. Pix settings - separate;
  4. Bank slip settings - separate;
  5. Credit card, Pix, and bank slip settings - unified;
  6. Transparent checkout with credit;
  7. Transparent checkout with bank slip;
  8. Transparent checkout with Pix;
  9. Refund;
  10. Successful refund;
  11. Storage of payment data;
  12. Additional charge;
  13. Bank slip;
  14. Bank slip in the new order email;
  15. Payment with Pix;
  16. Second copy of Pix in the new order email;
  17. Payment status inquiry;
  18. Installment payment on the product page;
  19. Checkout layout in lines - Credit;
  20. Checkout layout in lines - Pix;
  21. Checkout layout with separate methods;
  22. Transactions (Virtuaria PagBank Split);
  23. Sellers (Virtuaria PagBank Split);
  24. 3DS Authentication in action;
  25. Payment with Credit + Pix.

更新日志:

3.6.5 2026-06-19 3.6.5 2026-06-18 3.6.4 2025-12-15 3.6.3 2025-10-20 3.6.2 2025-08-12 3.6.1 2025-07-07 3.6.0 2025-07-02 3.5.3 2025-05-29 3.5.2 2025-05-20 3.5.1 2025-05-15 3.5.0 2025-05-14 3.4.5 2025-05-08 3.4.4 2025-02-18 3.4.2 2025-02-14 3.4.1 2025-02-10 3.4.0 2024-12-23 3.3.7 2024-10-22 3.3.6 2024-09-24 3.3.5 2024-08-07 3.3.4 2024-04-09 3.3.3 2024-03-15 3.3.2 2024-02-29 3.3.1 2024-02-29 3.3.0 2024-02-27 3.2.0 2024-02-20 3.1.0 2024-02-05 3.0.1 2024-01-16 3.0.0 2023-12-14 2.7.0 2023-11-10 2.6.0 2023-10-19 2.5.0 2023-09-05 2.4.0 2023-07-13 2.3.4 2023-06-22 2.3.3 2023-06-19 2.3.2 2023-06-14 2.3.1 2023-06-07 2.3.0 2023-05-30 2.2.8 2023-05-25 2.2.7 2023-05-05 2.2.6 2023-05-02 2.2.5 2023-03-27 2.2.4 2023-03-23 ​​ 2.2.3 2023-03-22 2.2.2 2023-03-22 2.2.1 2023-03-21 2.2.0 2023-03-10 2.1.0 2023-02-14 2.0.4 2023-02-07 2.0.3 2023-02-01 2.0.2 2023-01-26 2.0.1 2023-01-24 2.0.0 2023-01-23 1.2.0 2022-11-10 1.1.3 2022-09-15 1.1.2 2022-09-13 1.1.1 2022-09-08 1.1.0 2022-09-02 1.0.2 2022-08-04 1.0.1 2022-07-29 1.0 2022-07-28