Payment Gateway for Authorize.net for WooCommerce

Registo de alterações

1.0.23

• Fixed – Payments that Authorize.net accepted but held for review (Advanced Fraud Detection Suite) were marked as Failed orders with the misleading reason “Error I00001: Successful”, so customers who had already been charged were told the payment failed and paid again. These orders now go On hold with the transaction ID and a note telling you to approve or decline the transaction in the Authorize.net Merchant Interface. Approvals and ordinary declines are unchanged.
• Added – Order status now follows the outcome of a fraud review automatically: approving a held transaction in Authorize.net completes the order, declining it cancels the order and restores stock. Existing stores are updated on their own after this release – no settings need to be re-saved, no webhook is replaced, and any extra event types you added to the webhook yourself are kept.
• Improved – Card, eCheck and Google Pay orders held for review are never flipped to Failed by a later error during checkout, and “Capture Authorized Payment” is hidden while a transaction is still under review.
• Improved – Refunding an order whose payment is still under review now tells you to approve or decline the review in Authorize.net first, instead of returning a gateway error. Authorize.net does not allow these transactions to be refunded or voided until the review is settled.
• Fixed – With the transaction type set to “Authorize only”, a post-purchase order bump or upsell charge (CheckoutWC, FunnelKit) moved the original order back to On hold and replaced its transaction ID with the bump’s. The order now keeps its own status and transaction reference, and the extra authorization is recorded in an order note so you can capture it in the Authorize.net Merchant Interface.
• Added – Developers: the duplicate-transaction window sent to Authorize.net can now be set with the easyauthnet_authorizenet_duplicate_window filter, which turns on Authorize.net’s own protection against a customer submitting the same payment twice. The default is unchanged.

1.0.22

• Fixed – In rare cases checkout could fail at the final step with “There was an error processing your order.” and no explanation, because an unexpected PHP error during payment stopped WooCommerce from returning a valid response. The gateway now reports a proper error message and records the cause in WooCommerce > Status > Logs. Successful payments and ordinary card declines are unaffected.
• Improved – Tested with WooCommerce 11.0.

1.0.21

• Added – Accounting integration support: every order now carries its Authorize.Net transaction reference, including pre-authorized card payments and eCheck (ACH). QuickBooks connectors and similar bookkeeping tools can reconcile these orders against the gateway automatically.
• Improved – eCheck orders keep their transaction reference through settlement, so your books stay in step with the payment as it clears. Your configured eCheck order status is unchanged.
• Improved – Streamlined payment gateway registration for smoother compatibility with third-party plugins that list your store’s payment methods.

1.0.20

• Added – Google reCAPTCHA v3 fraud protection for card and eCheck checkout, blocking card-testing attacks. Optional and off by default; enable it under the Credit Card settings tab with your own v3 keys.
• Added – CheckoutWC compatibility: post-purchase one-click order bumps are charged to the card saved during checkout, with refund support.
• Added – WooCommerce Subscriptions: admins can now change or repair a subscription’s payment method from the subscription edit screen, and a recovered failing payment method is applied to future renewals automatically.
• Fixed – Changing a subscription’s payment method from My Account charged the customer immediately; the new card is now saved without any charge.
• Fixed – WooCommerce Pre-Orders “charge upon release” now works end-to-end: the card is saved at checkout and charged automatically when the pre-order is released.
• Fixed – FunnelKit upsells: guest checkout upsells are now supported and a declined upsell charge shows the real decline reason instead of failing silently.
• Improved – Safer detection of third-party plugins to prevent rare fatal errors caused by other plugins’ autoloaders, and stricter saved-card validation so a payment can only use cards saved by this gateway.

1.0.19

• Fixed – “Missing or invalid card token” still occurred on the Pay for Order page for stores using the block-based Checkout. The Pay for Order handler now binds reliably regardless of checkout type, so admin-created orders can be paid with card or eCheck.

1.0.18

• Fixed – “Missing or invalid card token” error when customers paid for admin-created orders (e.g. draft orders) from the Pay for Order page. Card and eCheck details are now tokenized correctly on that page, so these orders can be completed.

1.0.17

• Fixed – Card Logos selection could not be cleared; removing all card logos and saving reverted to showing every logo. An empty selection is now saved and respected, while fresh installs still default to all logos.

1.0.16

• Added – Google Pay Express button in the block-based Cart and Checkout, matching the existing classic checkout express experience.
• Fixed – Google Pay Express now captures the buyer’s billing address from the Google Pay sheet, so orders always record a billing address even when the cart needs no shipping (virtual products, or no shipping methods configured). Classic and block express now share identical address logic.
• Fixed – Checkout could break when the Authorize.Net Public Client Key was missing; it is now detected and stored automatically.

1.0.15

• Added – Support for additional currencies: AUD, CAD, DKK, EUR, GBP, NOK, NZD, PLN, SEK, USD.
• Fixed – Orders rejected when an address or other billing field exceeded Authorize.Net’s character limits; values are now truncated to the API maximum lengths.

1.0.14

• Fixed – American Express (and other valid cards) being declined at checkout by the plugin’s own client-side card-type check. Card brand acceptance is now governed entirely by your Authorize.Net merchant account, which returns the real decline reason when a brand is not enabled.
• Changed – The “Accepted Cards” setting is now “Card Logos” and controls only which card icons are displayed at checkout.

1.0.13

• Fixed – Google Pay live OR_BIBED_11 error by adding a “Google Pay Merchant ID” setting for production transactions.

1.0.12

• Fixed – capture webhook forcing physical orders to Completed.

1.0.11

• Improved – PHP 8.5 compatibility: defensive type coercion in payment, refund, and XML request flows (Authorize.Net API, Google Pay, eCheck).

1.0.10

• Improved – Synchronization between Authorize.net CIM and WooCommerce saved payment methods.

1.0.9

• Added – FunnelKit compatible for upsell and cross-sell flows.

1.0.8

• Fixed – Intermittent checkout failures (E00114 Invalid OTS Token) and improved CIM card-saving flow stability.

1.0.7

• Added – Support for eCheck (ACH) payments.
• Added – Support for Google Pay payments.
• Fixed – Issue preventing new card details from being saved in Authorize.Net for customers with existing saved cards.

1.0.6

• Enhanced – Improved gateway settings panel text.

1.0.5

• Added – Compatibility with WordPress 6.9.

1.0.4

• Improved Gateway Settings UI.

1.0.3

• Enhancement – Improved credit card form for a smoother checkout experience.

1.0.2

• Enhanced – Display actual API error messages instead of generic error messages.

1.0.1

• Enhancement: Display specific Authorize.Net decline reasons in the Checkout block (WooCommerce Blocks) instead of a generic error message.

1.0.0

• Initial stable release
• Accept.js integration for secure card tokenization
• Support for WooCommerce Subscriptions
• Support for WooCommerce Checkout Blocks
• Refunds, voids, saved cards, and authorization capture support