Payment Gateway for Authorize.net for WooCommerce vs Simple PAY.JP Payment

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: Authorize.net API Used for processing payments, issuing refunds, storing payment profiles, and handling subscriptions. 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 Accept.js Used to tokenize credit card details in the browser before they reach your server. 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 Webhook Services Used to receive updates from Authorize.net about transaction status, subscription events, etc. Endpoints used: https://api.authorize.net/rest/v1/webhooks https://apitest.authorize.net/rest/v1/webhooks Merchant Signup Links Provides a link to register or log in to an Authorize.net merchant account. 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

This plugin provides payment form by PAY.JP with simple shortcode. Note: The supported currency is only JPY so far. Example of Shortcode: [simple-payjp-payment amount=50 form-id="id-string" name='no' result-ok="https://example.tokyo/?page_id=7" result-ng="https://example.tokyo/?page_id=8" ] amount (mandatory*): price in JPY plan-id (mandatory*): subscription plan ID form-id (mandatory): any ID of the form name: show/hide name field (‘yes’ => show (default), ‘no’ => hide) result-ok: page url to redirect after payment succeeded if you want to customize success message result-ng: page url to redirect after payment failed if you want to customize failure message prorate: disabled/enabled prorated for subscription payment (‘no’ => not prorated (default), ‘yes’ => prorated) (*) ‘amount’ is mandatory for single payment. ‘plan-id’ is mandatory for subscription payment. ‘amount’ and ‘plan-id’ should be exclusive. You can confirm these information of each payments in descripton property of Charge record on PAY.JP admin panel. Only one shoutcode can be placed in a page. API Action hook simplepayjppayment_result_ok: called after payment succeeded simplepayjppayment_result_ng: called after payment failed Localization English (default) – always included Japanese – always included Technical Details How to use is summalized in the following page: WordPressプラグイン Simple PAY.JP Payment About the 3D Secure Feature Depending on the default settings of the browser or user-specific configurations, the pop-up blocking feature might be enabled. If 3D Secure authentication is attempted in a subwindow format under such conditions, the subwindow launch may be blocked, making authentication impossible. Disclaimer Thank you for using the “Simple PAY.JP Payment” plugin (hereinafter referred to as “this plugin”). Please carefully read the following disclaimer before using this plugin. By using this plugin, you agree to the terms outlined below. User Responsibility This plugin is provided “as is” without warranties of any kind, either express or implied, including, but not limited to, implied warranties of merchantability, fitness for a particular purpose, or non-infringement. The developer assumes no responsibility for any issues or damages arising from the use of this plugin. Users are responsible for configuring and operating the plugin at their own risk. Responsibility for Financial Transactions The developer assumes no responsibility for any financial transactions conducted using this plugin. It is the user’s sole responsibility to verify the accuracy and security of transactions. We strongly recommend seeking legal advice as needed. Data Protection and Security While this plugin is designed with data protection and security in mind, complete safety cannot be guaranteed. Users are advised to implement appropriate security measures, such as installing SSL certificates and performing regular backups. Support and Updates This plugin is subject to ongoing improvement and may be updated or modified without prior notice. However, the developer does not guarantee compatibility with specific environments or the functionality of the plugin after updates. Use of Third-Party Services This plugin may utilize third-party payment services or APIs. The developer is not responsible for any issues arising from these services, including service interruptions, errors, or security risks. Please review the terms and conditions of any third-party services you use in conjunction with this plugin.