mercadopago

A seller said Mercado Pago Secure Fields froze for iPhone buyers, causing lost revenue and leaving no usable support ticket path.

A Mercado Pago user says recurring update regressions break credit card installments, hurt sales, and pushed them to migrate to PagBank.

Users report that Mercado Pago setup is confusing, unreliable between test and production, and now causes serious integration and notification problems for payments.

Pluggin Mercado Pago Oficial no puedo acceder: users show bugs, support pain that may indicate a product gap.

Mercado Pago webhook processing intermittently crashes with a division-by-zero error, preventing order notification emails for a notable share of paid orders.

The user reports that card fields fail to load on iPhone checkout when scripts are deferred, and support confirms the WebKit timing bug prevents payment fields from being injected.

A paid PIX order never appeared in WooCommerce, leaving the merchant to verify payment manually and open a separate support ticket.

An update to Mercado Pago hid card entry fields in Checkout API, forcing a rollback until a later update fixed it.

After Mercado Pago 8.7.8, card payment pages for manually created WooCommerce orders stopped loading, and support confirmed a reproduced bug awaiting a fix.

Mercado Pago v8.7.17 breaks clean WooCommerce sites on activation because gateway properties are accessed before initialization, with a user-supplied workaround.

Mercado Pago dynamic card fields failed on iPhone, preventing payments and frustrating the seller with an unhelpful support route.

Mercado Pago users report configured card installments not appearing in WooCommerce checkout, causing lost sales and plugin switching.

Mercado Pago charged the full WooCommerce order amount instead of respecting Smart Coupons store credit at checkout.

Lento y le faltan funciones: users show compatibility, support pain that may indicate a product gap.

Mercado Pago 8.7.23 omitted checkout assets, leaving the credit-card form blank until users update or manually copy files.

After a likely update, the Mercado Pago plugin caused HTTP 500 errors that prevented creating a new order.

Mercado Pago payments completed successfully but WooCommerce orders stayed pending until manually synchronized.

The reviewer alleges Mercado Pago injects invasive checkout tracking that shares transaction data with related marketplace companies.

A Mercado Pago update hides or prevents selection of credit-card installments and document fields, causing shoppers to abandon purchases.

Mercado Pago 8.7.16 hit a fatal order metabox error that prevented navigating sales, and the user rejected being sent through a poor support channel.

Mercado Pago Checkout API causes the WooCommerce order summary to reload endlessly, blocking checkout while Checkout Pro works normally.

De mal en peor: users show bugs pain that may indicate a product gap.

After an update, Mercado Pago checkout repeatedly rejected cardholder names and some browsers could not select installments until fixes were released.

Mercado Pago payments were credited but WooCommerce orders were still cancelled as unpaid after the pending-payment timeout.

Mercado Pago PIX payments were not automatically updating WooCommerce order status, forcing manual receipt checks and status changes.

Mercado Pago's manual pay-for-order links fail because credit-card and related payment options do not work in that flow.

A Mercado Pago update produced an undefined array key warning that affected checkout and other payment methods, with support offering workarounds.

Mercado Pago checkout showed a cardholder name error in version 8.7.5, and support said version 8.7.6 fixed it.

The user paused Mercado Pago because card autofill and previously entered customer tax details were not reused at checkout.

Dúvidas: users show compatibility, support pain that may indicate a product gap.