Title: Payment Gateway for Authorize.net for WooCommerce Author: Easy Payment Published: 2025 年 8 月 11 日 Last modified: 2026 年 9 月 23 日 --- 搜索插件 ![](https://ps.w.org/payment-gateway-for-authorize-net-for-woocommerce/assets/icon- 256x256.png?rev=3342779) # Payment Gateway for Authorize.net for WooCommerce 作者：[Easy Payment](https://profiles.wordpress.org/easypayment/) [下载](https://downloads.wordpress.org/plugin/payment-gateway-for-authorize-net-for-woocommerce.1.0.25.zip) * [详情](https://cn.wordpress.org/plugins/payment-gateway-for-authorize-net-for-woocommerce/#description) * [评价](https://cn.wordpress.org/plugins/payment-gateway-for-authorize-net-for-woocommerce/#reviews) * [安装](https://cn.wordpress.org/plugins/payment-gateway-for-authorize-net-for-woocommerce/#installation) * [开发进展](https://cn.wordpress.org/plugins/payment-gateway-for-authorize-net-for-woocommerce/#developers) [支持](https://wordpress.org/support/plugin/payment-gateway-for-authorize-net-for-woocommerce/) ## 描述 **Payment Gateway for Authorize.net for WooCommerce** by Easy Payment is a secure and feature-rich solution for accepting credit card payments via Authorize.net. Customers stay on your website during checkout, creating a seamless experience. This plugin uses **Authorize.net Accept.js** to tokenize credit card details before they reach your server—ensuring full **PCI-DSS SAQ A-EP compliance**. It supports one-time and recurring payments with full integration for **WooCommerce Subscriptions** and the modern **Checkout Block** system. Developed by an Official Authorize.net Partner, this plugin ensures high performance and reliability. ### Payment Methods * Credit & Debit Card Payments * eCheck (ACH) * Google Pay ### Features * Accept credit card payments using Authorize.net Accept.js * Process refunds and voids from the WooCommerce order screen * Pre-authorization and capture later (“Authorize Only”) supported * Save cards for future purchases with secure tokenization * Works with WooCommerce Subscriptions for recurring billing * FunnelKit compatible for upsell and cross-sell flows * Fully compatible with WooCommerce Checkout Blocks * PCI compliant using tokenization (SAQ A-EP) * Responsive credit card form for all devices * Logging and debug tools for development and troubleshooting ### Supported Card Types * Visa * MasterCard * American Express * Discover * JCB * Diners Club ### Integration Compatibility * WooCommerce Subscriptions * WooCommerce Checkout Blocks * WooCommerce Pre-Orders * FunnelKit Checkout / FunnelKit Upsell ### External Services This plugin connects to several Authorize.net services to process payments securely and provide related functionality: 1. **Authorize.net API** Used for processing payments, issuing refunds, storing payment profiles, and handling subscriptions. 2. * Data sent: transaction amount, customer name, address, and tokenized card data * Endpoints used: - https://api.authorize.net/xml/v1/request.api - https://apitest.authorize.net/xml/v1/request.api 3. **Accept.js** Used to tokenize credit card details in the browser before they reach your server. 4. * Data sent: raw card number, expiry, CVV (sent directly to Authorize.net via JavaScript SDK) * Endpoints used: - https://js.authorize.net/v1/Accept.js - https://jstest.authorize.net/v1/Accept.js 5. **Webhook Services** Used to receive updates from Authorize.net about transaction status, subscription events, etc. 6. * Endpoints used: - https://api.authorize.net/rest/v1/webhooks - https://apitest.authorize.net/rest/v1/webhooks 7. **Merchant Signup Links** Provides a link to register or log in to an Authorize. net merchant account. 8. * Endpoints: - https://account.authorize.net/ - https://sandbox.authorize.net/ - https://account.authorize.net/signUpNow?resellerId=27457 * No personal data is sent by the plugin automatically. **Terms of Service:** https://www.authorize.net/about-us/terms.html **Privacy Policy:** https://www.authorize.net/about-us/privacy.html ## 屏幕截图 [⌊Payment settings in the WooCommerce admin panel⌉⌊Payment settings in the WooCommerce admin panel⌉[ Payment settings in the WooCommerce admin panel [⌊Secure credit card fields powered by Accept.js⌉⌊Secure credit card fields powered by Accept.js⌉[ Secure credit card fields powered by Accept.js ## 安装 1. Upload the plugin to the `/wp-content/plugins/` directory. 2. Activate it via **Plugins > Installed Plugins**. 3. Go to **WooCommerce > Settings > Payments > Authorize.net Credit Card**. 4. Enter your Authorize.net credentials: **API Login ID**, **Transaction Key**, and** Signature Key**. The **Public Client Key** required by Accept.js is detected and stored automatically. 5. Enable the gateway and configure optional settings. ## 常见问题 ### Does this plugin support subscriptions? Yes. It fully supports WooCommerce Subscriptions using saved cards via tokenization. ### Why is Accept.js required? Accept.js is used to tokenize card data in the browser before it’s sent to your server, making the integration PCI compliant. ### Can I issue refunds directly from WooCommerce? Yes. You can process refunds and voids from the WooCommerce order admin. ### Will customers leave my site to complete the payment? No. All payment processing happens inline using Accept.js—customers stay on your checkout page. ### Does it support WooCommerce Checkout Blocks? Yes. This plugin is fully compatible with the block-based Cart and Checkout experience. ## 评价 ![](https://secure.gravatar.com/avatar/1d8faaeaf16e85dde1c0dcb657f9053765d8e87b5fb74f0bfd2852ea51c686c5? s=60&d=retro&r=g) ### 󠀁[Excellent Plugin, Excellent Customer Service](https://wordpress.org/support/topic/excellent-plugin-excellent-customer-service-9/)󠁿 [nworbdier](https://profiles.wordpress.org/nworbdier/) 2026 年 7 月 16 日 We were having issues on our store and reached out to the team and it was resolved in one day. Their slack support is also amazing and they act like they really care about your issue on a personal level.Would HIGHLY recommend to anyone on the fence for this plugin. It's actually better than the official Authorize.net plugin I installed. The reason I switched to this one is because the official plugin was blocking a function and wouldn't work for our store at all. EasyPayment all the way! ![](https://secure.gravatar.com/avatar/db0bb4c4e7b3258f0a5c71f2b5a86d304fec2053be3d1d50fbcaff127bd21576? s=60&d=retro&r=g) ### 󠀁[Top tier support!](https://wordpress.org/support/topic/top-tier-support-7/)󠁿 [meroving](https://profiles.wordpress.org/meroving/) 2026 年 5 月 9 日 2 回复 I'm really impressed with the team's fast support. Communication was smooth, they reacted quickly to every request, and the plugin is working well too! Very satisfied. Thanks! ![](https://secure.gravatar.com/avatar/104be22e835758e4805d9f4d3af096597222ba16d6515d624dbe2bb0c9facb34? s=60&d=retro&r=g) ### 󠀁[The ONLY one that works!](https://wordpress.org/support/topic/the-only-one-that-works-14/)󠁿 [alienjackhammer](https://profiles.wordpress.org/alienjackhammer/) 2025 年 9 月 17 日 1 回复 I've tried EVERY authorize.net plugin. I even paid for two of them. None of them worked. The biggest problem with most of the plugins; is that they do not work with woocommerce blocks. And the ones that do; don't show correct response codes and do not allow saved credit card info. I'm very pleased with the product AND the support. I had an issue and the developer responded right away. If you are looking for an authorize.net plugin that actually works; this is the one. Can't recommend enough! [ 阅读所有3条评价 ](https://wordpress.org/support/plugin/payment-gateway-for-authorize-net-for-woocommerce/reviews/) ## 贡献者及开发者 「Payment Gateway for Authorize.net for WooCommerce」是开源软件。 以下人员对此插 件做出了贡献。 贡献者 * [ Easy Payment ](https://profiles.wordpress.org/easypayment/) [帮助将「Payment Gateway for Authorize.net for WooCommerce」翻译成简体中文。](https://translate.wordpress.org/projects/wp-plugins/payment-gateway-for-authorize-net-for-woocommerce) ### 对开发感兴趣吗? 您可以[浏览代码](https://plugins.trac.wordpress.org/browser/payment-gateway-for-authorize-net-for-woocommerce/)， 查看[SVN仓库](https://plugins.svn.wordpress.org/payment-gateway-for-authorize-net-for-woocommerce/)， 或通过[RSS](https://plugins.trac.wordpress.org/log/payment-gateway-for-authorize-net-for-woocommerce/?limit=100&mode=stop_on_copy&format=rss) 订阅[开发日志](https://plugins.trac.wordpress.org/log/payment-gateway-for-authorize-net-for-woocommerce/)。 ## 更新日志 #### 1.0.25 * Improved – Tested with WordPress 7.1.2. #### 1.0.24 * Fixed – WooCommerce Subscriptions: every automatic renewal was charged twice in the same scheduled run. The gateway’s renewal handler was registered once by WooCommerce and a second time by the Checkout Blocks integration, so each renewal charge was submitted twice: Authorize.net rejected the duplicate (“Error 11: A duplicate transaction has been submitted.”), and that rejection then marked the already-paid renewal order as Failed and put the subscription On hold – so the customer was charged, yet received a renewal invoice asking them to pay again. Renewal handlers now run exactly once per renewal. If this affected your store: those Failed renewal orders were in fact paid – verify the charge in the Authorize. net Merchant Interface, then set the order back to Processing and reactivate the subscription. Thanks to @gordonium for the precise report. * Fixed – As a permanent safeguard, a renewal order that already has a completed payment can never be charged again or flipped to Failed by a duplicate attempt, whatever triggers it: the duplicate is skipped and recorded as an order note instead, and Authorize.net’s own 120-second duplicate-transaction window remains active on all renewal and saved-card charges. * Fixed – The Checkout Blocks integration created its own private copies of the card, eCheck and Google Pay gateways on every page load; it now reuses the gateways WooCommerce has already loaded. This also stops the same duplication elsewhere: saving the gateway settings no longer validates credentials and re-registers the Authorize.net webhook twice, “Capture Authorized Payment” no longer submits the capture twice (which left a stray “Capture failed” note on a successfully captured order), and removing a saved card no longer sends the profile deletion to Authorize.net twice. #### 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 ## 额外信息 * 版本 **1.0.25** * 最后更新：**3 周前** * 活跃安装数量 **800+** * WordPress 版本 ** 5.6 或更高版本 ** * 已测试的最高版本为 **7.1.3** * PHP 版本 ** 7.4 或更高版本 ** * 语言 * [English (US)](https://wordpress.org/plugins/payment-gateway-for-authorize-net-for-woocommerce/) * 标签 * [authorize.net](https://cn.wordpress.org/plugins/tags/authorize-net/)[credit card](https://cn.wordpress.org/plugins/tags/credit-card/) [visa](https://cn.wordpress.org/plugins/tags/visa/) * [高级视图](https://cn.wordpress.org/plugins/payment-gateway-for-authorize-net-for-woocommerce/advanced/) ## 评级 5 星（最高 5 星）。 * [ 3 条 5 星评价 ](https://wordpress.org/support/plugin/payment-gateway-for-authorize-net-for-woocommerce/reviews/?filter=5) * [ 0 条 4 星评价 ](https://wordpress.org/support/plugin/payment-gateway-for-authorize-net-for-woocommerce/reviews/?filter=4) * [ 0 条 3 星评价 ](https://wordpress.org/support/plugin/payment-gateway-for-authorize-net-for-woocommerce/reviews/?filter=3) * [ 0 条 2 星评价 ](https://wordpress.org/support/plugin/payment-gateway-for-authorize-net-for-woocommerce/reviews/?filter=2) * [ 0 条 1 星评价 ](https://wordpress.org/support/plugin/payment-gateway-for-authorize-net-for-woocommerce/reviews/?filter=1) [您的评价](https://wordpress.org/support/plugin/payment-gateway-for-authorize-net-for-woocommerce/reviews/#new-post) [查看全部评论](https://wordpress.org/support/plugin/payment-gateway-for-authorize-net-for-woocommerce/reviews/) ## 贡献者 * [ Easy Payment ](https://profiles.wordpress.org/easypayment/) ## 支持 最近两个月解决的问题： 总计 2，已解决 1 [查看支持论坛](https://wordpress.org/support/plugin/payment-gateway-for-authorize-net-for-woocommerce/)