An Error Occurred Please Try Again or Try an Alternate Form of Payment Woocommerce Authorize net

Overview ↑ Dorsum to elevation

WooCommerce Authorize.Net Gateway integrates with Authorize.Cyberspace payment services to provide secure and powerful payment processing for your shop. With this gateway, you tin have credit cards and eChecks and let customers save their payment details to your site for fast and easy checkouts. This payment gateway includes full support for WooCommerce Subscriptions and WooCommerce Pre-Orders!

If yous program to use this plugin with Subscriptions, Pre-Orders, or want to allow customers to save their payment details, the Client Information Managing director (CIM) feature must exist enabled on your Authorize.Cyberspace account (additional monthly costs may apply).

This plugin also includes Accept.js from Authorize.Internet for improved security and decreased PCI compliance responsibleness. Customer credit card data is handled directly by Authorize.Net to offload some security concerns. Click here to learn more nearly Accept.js

Looking for details on 3D Secure? See this FAQ entry.

Requirements ↑ Dorsum to acme

• An Authorize.Net account
• An SSL certificate. An SSL certificate is also required on local test environments.
• WooCommerce 3.five+
• WordPress v.2+
• PHP seven.0+ (you can see this nether WooCommerce > Condition)

Installation ↑ Back to top

1. Ensure your store meets the plugin requirements.
2. Download the extension from your WooCommerce dashboard.
3. Become to Plugins > Add New > Upload and select the ZIP file you just downloaded.
4. Click Install Now and then Actuate.
5. Click Configure and read the side by side department to larn how to setup the plugin.

Getting Started ↑ Back to top

To brainstorm using Authorize.Net, you lot must first connect the plugin to your Qualify.Internet account. Follow the steps below to notice your API credentials on Authorize.Cyberspace and setup the plugin:

1. Login to your Authorize.Net account.
2. Become to Accounts > Settings > API Credentials & Keys.

3. Copy your API Login ID.
4. Select the New Transaction Key radio button and click Submit. Copy the Transaction Key.
5. If you lot want to setup webhooks, select the New Signature Cardinal radio push button and click Submit to generate the Signature Cardinal.

6. Now, log into your site and become to WooCommerce > Settings > Payments and select WooCommerce Authorize.Net.
7. Paste the API Login ID, API Transaction Fundamental, and API Signature Key, if applicable.
8. Click Save Changes.

That's it! You are now set to kickoff accepting credit cards via Authorize.Cyberspace! Keep reading if you lot want to tweak settings and customize the checkout process.

Credit Carte Settings ↑ Dorsum to top

You lot tin can configure the following settings for the Authorize.Net credit card gateway:

• Enable / Disable: Allow customers to employ this gateway to checkout.
• Championship: The text shown for the payment during checkout and on the Order Received folio.
• Description: The text shown under the gateway'south title during checkout. Limited HTML is allowed. If you enable test mode, this section will likewise brandish a notice along with exam credit card numbers.
• Bill of fare Verification (CSC): Require customers to enter their carte du jour security codes when checking out. This can be useful if you have requirements in your Qualify.Net account for CV2 verification.
• Transaction Type: Controls how transactions are submitted to Authorize.Net. Select "Charge" to automatically capture payments. If yous select "Say-so", you must manually capture and settle payments in your Qualify.Net control panel or on the WooCommerce orders screen subsequently the transaction has been submitted. This defaults to "Charge".
• Accuse Virtual-Only Orders: If Transaction Type is set to "Authorization", enable this to automatically capture charges for orders with merely virtual products. For downloadable products, this will grant downloads access right abroad.
• Capture Paid Orders: If Transaction Type is set to "Authorization", enable this to automatically capture charges when orders move to a paid status.
• Accepted Cards: Determines which card logos are displayed during checkout. This has no impact on which cards are accepted by your merchant account.
• Tokenization: Let customers salve their payment methods for future use at checkout. This is required for Subscriptions or Pre-Orders.
• Detailed Pass up Letters: Brandish detailed messages to customers to provide reasoning for declines instead of a generic error message when possible. Click here to read more virtually detailed decline messages.
• Debug Mode: Enable when yous're having problems processing transactions. You tin cull to log API requests direct on the checkout page, save them to the WooCommerce > Condition > Logs page, or both. As a best practice, please practise not enable this setting unless you're having issues with the plugin.
• Environment: Switch between "Test" and "Production" credentials. Enable "Examination" to send transactions to your Qualify.Net Exam Account. Note: This is not the "test way" that is listed under your account. This is an entirely separate sandbox environment that requires a carve up login and divide API credentials. Do not place your Test Business relationship (or regular account) into "Test Mode" within the Authorize.Net control panel as transactions will not process at all if that manner is set up.
• Share connexion settings: If using the credit carte du jour and eCheck gateways, select this setting to share credentials between the gateways and so y'all don't take to enter them twice.
• API Login ID: Follow the steps in a higher place to call up your API Login ID.
• API Transaction Key: Follow the steps to a higher place to generate your API Transaction Key.
• API Signature Key: Optional. Just required if you desire to enable webhooks for Authorize.Cyberspace account updates. Follow the steps above to generate your API Signature Key.
• Payment Form Type: You lot tin choose how you lot'd like to display the payment form. The Inline option meets SAQ-A EP PCI requirements while the Lightbox choice supports SAQ A standards.

eCheck Settings ↑ Back to acme

You tin can configure the following settings for the Authorize.Net eCheck gateway:

• Enable / Disable: Allow customers to utilise this gateway to checkout. You lot must enable eChecks on your Authorize.Net account to use the eCheck gateway. Follow the procedure below under eCheck Issues to get eChecks setup and enabled.
• Title: The text shown for the payment during checkout and on the Order Received page.
• Description: The text shown under the gateway'due south title during checkout. Limited HTML is allowed. If you enable test mode, this section will also display a notice along with a test bank business relationship number.
• Tokenization: Allow customers salvage their payment methods for future use at checkout. This is required for Subscriptions or Pre-Orders.
• Potency: Display an authorisation message during the checkout process.
• Authorization Message: If Authorisation is enabled, enter the bulletin yous desire to show to your customers. You can use the post-obit merge tags:
  • {merchant_name}: Your shop name
  • {order_date}: Appointment of purchase
  • {order_total}: Total order value
• Recurring Authorization Bulletin: If Authorization is enabled and WooCommerce Subscriptions is active on your site, yous can enter the bulletin you desire to show your customers for recurring payments.
• Detailed Pass up Letters: Display detailed messages to customers to provide reasoning for declines instead of a generic mistake bulletin when possible. Click hither to read more than about detailed reject messages.
• Debug Mode: Enable when yous're having bug processing transactions. Yous can choose to log API requests directly on the checkout page, save them to the WooCommerce > Condition > Logs page, or both. As a best exercise, please do not enable this setting unless yous're having issues with the plugin.
• Environment: Switch between "Exam" and "Production" credentials. Enable "Test" to send transactions to your Qualify.Net Examination Business relationship. Note: This is not the "test fashion" that is listed nether your account. This is an entirely split sandbox environs that requires a separate login and separate API credentials. Practice non place your Test Account (or regular account) into "Test Mode" within the Authorize.Net control console as transactions will not process at all if that style is set.
• Share connectedness settings: If using the credit carte du jour and eCheck gateways, select this setting to share credentials betwixt the gateways and so you don't have to enter them twice.
• API Login ID: Follow the steps to a higher place to retrieve your API Login ID.
• API Transaction Key: Follow the steps above to generate your API Transaction Key.
• API Signature Key: Optional. Just required if you want to enable webhooks for Authorize.Cyberspace account updates. Follow the steps above to generate your API Signature Central.
• Payment Form Type: Choose to display the payment class inline or in a lightbox. Select "Inline" to support PCI-DSS SAQ A-EP compliance.

eCheck Setup with Qualify.Net

To enable eCheck processing on your Authorize.Net account:

1. Setup an eTicket and enquire for the "WEB" eCheck type to exist enabled. Exist certain you are an business relationship possessor and know your gateway ID.
2. WEB transactions are usually enabled within 2 business days, merely there is a funding hold automatically placed on your account – y'all can take funds in, but tin can't accept them out until yous pass some other security check with the underwriting department.
3. To expedite this process, phone call the Authorize.Net underwriting department so they can check your website while on the phone with you. They'll ensure you have a valid SSL on cart/checkout and prominently placed terms of use and privacy policy pages.
4. Once you've met these requirements, the funding hold volition be removed.

Webhook Setup ↑ Dorsum to elevation

Webhooks notify your WooCommerce site when customer profiles and payment profiles are deleted from your Qualify.Net account. This is helpful when using WooCommerce Subscriptions to ensure that payment token removals are logged on your site for troubleshooting purposes. Follow the steps to a higher place to generate your API Signature Fundamental, which you can enter in the plugin settings to enable webhooks. Then, click the link in the settings notice to enable webhooks. This will push the required information into your Authorize.Net account. Authorize.Net will now notify your site when the customer or payment profiles are deleted from your business relationship. We do, however, recommend avoiding changes within your account when possible.

Managing Orders ↑ Dorsum to top

As a site ambassador, you lot can utilize the WooCommerce Authorize.Net gateway to manually capture charges and automatically refund/void transactions as needed.

Capture Charges ↑ Back to peak

If you are using version ii.0+ of the Authorize.Net gateway and the Transaction Blazon setting is prepare to "Say-so", you can manually capture these payments from the WooCommerce Orders folio. Click here to read more nigh capturing charges.

Note: If your Transaction Type setting is set to "Charge", you lot cannot utilise the Capture button. Attempting to do so volition consequence in the following error message: 3 (E00027) - The transaction was unsuccessful. Mistake Code: 33 - A valid referenced transaction ID is required.

Automatic Refunds ↑ Back to top

If you are using version 2.0+ of the Authorize.Net gateway and version 2.2+ of WooCommerce, you can procedure refunds for Credit Card transactions straight in WooCommerce without needing to log into your Authorize.Net account. Click here to read more about issuing automatic refunds from WooCommerce.

Void Transactions ↑ Back to top

Y'all tin can void transactions directly in WooCommerce in the post-obit circumstances:

• If your Transaction Type setting is set up to "Authorization", you can void when the transaction has been authorized simply not still captured.
• If your Transaction Blazon setting is ready to "Accuse", you tin can void when the transaction has not yet been settled (e.g. funds haven't been transferred from the customer's account to your Authorize.Internet account).

Authorize.Internet does not accept partial voids. If a transaction is no longer eligible to be voided, yous must refund the lodge. Click here to read more well-nigh voiding transactions in WooCommerce.

Gateway Features ↑ Back to top

Your customers can accept reward of the following features when your site uses WooCommerce Authorize.Net.

Saving Payment Methods ↑ Back to top

Customers can save payment methods during the checkout procedure or from their My Business relationship area. This lets them quickly select payment details during future checkouts and also lets your site support Subscriptions and Pre-Orders. To manage their saved payment methods, customers can get to My Account > My Payment Methods. From here, they can add together new payment methods (credit cards or eChecks), fix their default method, and delete any old or expired methods. Click here to read more nearly managing saved payment methods.

Customer Saved Payment Methods

Subscriptions / Pre-Orders Support

WooCommerce Authorize.Net supports all features of WooCommerce Subscriptions and WooCommerce Pre-Orders for both credit cards and eChecks (if enabled).

Accept.js ↑ Back to top

Version iii.0+ of WooCommerce Authorize.Internet includes automated support for Accept.js. Once you lot have configured the gateway, nosotros can remember the information required to use Accept.js from your Authorize.Net account – no extra configuration steps required! This characteristic means that customer payment data is handled direct by Authorize.Net, meeting the lower level PCI SAQ A-EP compliance level. Have.js is handled behind the scenes, then your customers won't notice any alter to their checkout process. Click hither to learn more about Accept.js.

Enhanced Checkout Form ↑ Back to top

Authorize.Net supports an enhanced checkout grade that improves the checkout experience on mobile and desktop devices. Click here to read about the enhanced payment course.

Note: The appearance of your checkout form may vary based on your site's theme.

Authorize.Net Emulation ↑ Back to peak

Nosotros are in the process of deprecating back up from Authorize.Net emulation. Newer users of the WooCommerce Authorize.Net plugin may not have access to these settings. Delight contact our support squad with any questions well-nigh Authorize.Net Emulation support.

Annotation: Authorize.Net Emulation does not support advanced features such equally refunds, voids, and capturing charges from within WooCommerce. Merely payment processing is supported.

To use Authorize.Net with a gateway that supports Authorize.Cyberspace emulation, yous demand to enable the Authorize.Internet emulator under Plugins > Installed Plugins — click "Enable emulation gateway":

Enable Emulation Gateway

This allows you to apply Qualify.Net'south emulation protocol for other gateways. The Authorize.Net emulator settings will now be available under WooCommerce > Settings > Payments. To use Authorize.Net emulation, you must enable the gateway and enter the Gateway URL and API credentials provided to yous by your payment processor.

Emulator settings

Qualify.Net Emulation Settings ↑ Back to top

• Enable / Disable – This will enable the gateway to be used by customers to checkout.
• Title – This is the text shown for the payment during checkout and on the Order Received page.
• Description – This is the text shown nether the title during checkout. Express HTML is allowed. If you enable test fashion, this department will also brandish a notice forth with examination credit carte numbers.
• Bill of fare Verification (CSC) – Enable this to crave customers to enter their CVV / CV2 (Carte Security Code) when checking out. This can be useful if you have requirements in your Authorize.Net business relationship for CV2 verification.
• Transaction Type – This controls how transactions are submitted to Authorize.Net. You may choose either "Charge" or "Authorization". If yous select "Authority", y'all must manually capture and settle payments in your Authorize.Net control panel or on the WooCommerce orders screen afterwards the transaction has been submitted. This defaults to "Charge".
• Accepted Card Logos – This controls the carte logos that display during checkout. This is purely cosmetic and has no effect on the cards actually accustomed past your merchant account.
• Debug Mode – Enable this is y'all are having bug correctly processing transactions. Y'all can either log API requests / responses directly to the checkout / cheers page, relieve them to the WooCommerce Error Log (found under WooCommerce > System Status > Logs) or both. All debugging letters are cleaned of sensitive information before display, but as a best practice, please do non enable this unless yous are having issues with the plugin.
• Environs – Switch between "Test" and "Production" credentials. Enable "Test" to transport transactions to your Qualify.Net Exam Account. Note: This is not the "test mode" that is listed under your Authorize.Net account. This is an entirely dissever sandbox environment that requires a separate login. You can sign upward for a test account here. One time yous have done this, y'all tin can enter a separate API Login ID and API Transaction Key for your test business relationship. Do not place your Test Business relationship (or regular account) into "Test Mode" inside the Authorize.Net command panel every bit transactions will not process at all if that mode is fix.
• Payment Gateway URL – The Gateway URL for the Authorize.Net gateway processor. Optionally, this URL can be changed to a different processor that allows Authorize.Net emulation.
• API Login ID – This is the API Login for your Authorize.Net account (Examination or Production). Follow the steps in a higher place to become this. If you're using this gateway for Authorize.Net emulation, then this will be the API Login provided to yous by your payment processor.
• API Transaction Key – This is the API Transaction Key for your Authorize.Cyberspace account (Test or Product). Follow the steps above to get this. If you're using this gateway for Authorize.Cyberspace emulation, then this will be the API Transaction Cardinal provided to you by your payment processor.

Frequently Asked Questions ↑ Dorsum to meridian

Q: Why am I receiving an fault message on subscription renewals saying that Bill of fare Lawmaking is required? Information technology'southward not required in my plugin settings! A: If you're seeing an mistake like "Authorize.Net Payment Failed (3 E00027): Carte Code is Required…", it's likely that Bill of fare Code is required on your Qualify.Net account. For PCI compliance and security reasons, Authorize.Net cannot store CSCs for subscription renewals, and so carte du jour codes are unavailable for renewal orders. If your Authorize.Net business relationship requires these, the orders will fail. Click here to learn how to disable this requirement.

---

Q: Why don't Subscriptions display inside the Authorize.Net control panel? A: Subscriptions aren't shown in Authorize.Internet considering the gateway doesn't utilise ARB (automatic recurring billing). Information technology tokenizes the customer's payment method so the Subscriptions plugin handles charging the payment method. This is far more flexible than ARB and thus supports a lot of features, such as changing payment dates and amounts, that ARB tin can't handle.

---

Q: Why did I receive a "test transaction successful" email? A: During checkout, the extension validates the payment data entered past the client (i.e. confirms that the carte number, expiration engagement, etc. are correct). This "test transaction" does not charge the client, only generates an electronic mail to the merchant. You lot can email support@qualify.net to have them disable this email notification to you.

---

Q: Can I process automatic refunds with eChecks? A: No – automated refunds from WooCommerce can merely exist processed for credit card transactions.

---

Q: I'm migrating sites – tin I import client IDs and payment profile IDs to my new site? A: The Qualify.Net plugin stores the customer ID, payment contour ID, and shipping profile ID as meta fields, and so you could employ an export plugin like Client/Order CSV Export to pull down the IDs from your old site and use an import plugin like Customer/Order/Coupon CSV Import Suite to import these IDs to you new site! Other export/import plugins might work well here, too, and so long as they are capable of exporting and importing customer/user meta.

---

Q: My customers get e-mail receipts from WooCommerce and Authorize.Net. How exercise I become rid of Authorize.Net receipts? A: You lot can disable these emails in your Authorize.Net business relationship. Click here for instructions on disabling customer electronic mail receipts.

---

Q: How do I capture a higher amount than what is authorized (similar a gas station or restaurant)? A: Authorize.Net (along with nigh whatsoever eCommerce payment processor) cannot practice this with bill of fare-non-nowadays transactions, such as online payments. For these payments, y'all can only capture up to the value of the authorization: "The amount being requested for capture is less than or equal to the original authorized amount." When gas stations and restaurants do this, they're using a particular POS system that gives them a certification to capture a certain percentage over the authorized amount. This functionality isn't available for eCommerce systems, then this isn't possible on your WooCommerce site or with the Authorize.Internet plugin.

---

Q: Authorize.Net supports Apple Pay for spider web payments. Can I utilise this in my store? A: Authorize.Net CIM contains a framework for Apple Pay, but it can only be enabled past developers, equally the certification process requires developer-only tools. If yous piece of work with a developer and would similar to add Apple Pay to your store, please click here to review the setup instructions and requirements. Please note that configuring Apple Pay back up for this plugin is considered a customization and is non covered by our support policy.

---

Q: Does this plugin support 3D Secure? I need to run across Strong Customer Hallmark (SCA) requirements. A: WooCommerce Authorize.Net does not back up 3D Secure at this fourth dimension — Authorize.Net'southward API does not support accepting the customer data required to meet 3D Secure v2.0 requirements (which is required for folks seeking to comply with PDS2 regulations / SCA requirements). If you need to enable SCA, please ask your Authorize.Net representative nigh migrating yous to CyberSource. You can read more about PSD2 and Authorize.Net here, and meet updates on 3D Secure with WooCommerce CyberSource here.

---

Q: I have a local exam environs, practice I need to have an SSL certificate installed? A: Yes, an SSL certificate is as well required on local test environments. In order to obtain an SSL Certificate for your local site, you can generate a self-signed certificate, or install a test certificate with a service such as the gratis Let'southward Encrypt. Q: When I delete a user on WordPress, is their saved payment method deleted on Qualify.Net? A: When a user is deleted on WordPress, their payment profile volition be deleted from their Authorize.Net customer profile also. Their Customer Profile would still exist in the Client Information Manager (CIM), and the payment profile section will display: "This Customer Profile does non accept any associated Payment Profiles".

Troubleshooting ↑ Back to top

Authorize.Net Test Credentials ↑ Dorsum to top

To run tests with this plugin, you lot volition demand a set of dedicated test credentials from Authorize.Net. Your alive credentials cannot be used in "Test" mode. When you change the Environment setting to "Examination", the Connection Settings fields will remove your alive credentials and let you enter your test credentials. When yous switch back to "Production", the plugin volition restore your live credentials.

Notation: Practise not gear up your production accounts into test fashion from within your Authorize.Net account – this returns dummy data for alive transactions, but does not work with the plugin's test mode, since you're still using production credentials.

Authorize.Cyberspace Error Codes ↑ Back to tiptop

Authorize.Cyberspace provides many different error/response codes that tin provide helpful information about what caused an mistake during payment processing. Click here to review Authorize.Net's Response Lawmaking Reference. You lot can enter the code in this reference tool to see the crusade of the error. In some cases, such every bit a transaction being held for review or declined, the plugin can't resolve the issue. In those cases, you must set up the trouble from your Authorize.Net business relationship. Notes:

• Orders with Response Code = 4 will be approved, just can be cancelled manually in the WooCommerce admin and Authorize.Net Merchant Area area afterwards if they neglect review.
• Be sure to accept "Partial Say-so" turned off in your Qualify.Net Merchant Area. This will restrict orders with Response Lawmaking = 4 and Response Lawmaking = 295 from existence approved. "Permit Partial Payments" is off past default, merely to verify it is off, follow these steps:
  • Login to your Authorize.Internet merchant area.
  • Go to Account > Fractional Authority.
  • Ensure that Allow Fractional Payments is unchecked and click Submit to salvage your changes, if applicative.

Required Field Errors ↑ Back to top

If you lot receive an mistake like (E00027) - The transaction was unsuccessful. Mistake Lawmaking: 33 - [Field Name] is required., your Authorize.Net business relationship is likely setup to require a field that our plugin cannot send. These errors can occur on orders, refunds, and void transactions. To resolve this issue, you lot should remove all field requirements from your Authorize.Net account by post-obit the steps below:

1. Login to your Authorize.Internet Account.
2. Go to Business relationship > Payment Form > Form Fields.
3. Uncheck the Required boxes for all fields.
4. Click Submit.

Have.js Errors ↑ Back to top

If you receive an error like Accept.js Error: payment nonce is missing, your checkout page is likely not loading the Accept.js file when our plugin expects it to. This is usually caused by a JavaScript conflict of some kind, typically with your theme or another plugin. Optimization plugins can interfere with how JavaScript loads on your checkout page and cause this fault. A few conflicting plugins to expect for are:

• Autoptimize
• SG Optimizer
• Hummingbird Pro

If y'all are using 1 of these plugins, disabling the plugin completely or adjusting its settings so they don't optimize your checkout folio should resolve the error.

eCheck Problems ↑ Back to superlative

If you enabled eChecks in the Authorize.Net gateway plugin but accept not enabled WEB eCheck enabled on your Authorize.Net account, you may see errors similar [Code 246] - This eCheck.Net type is not allowed. Click hither for instructions on setting upwardly eChecks on your Authorize.Net account.

Refund Issues ↑ Back to peak

When attempting to process an automatic refund, yous may see the following fault message: Oops, you cannot partially void this social club. Delight use the full order amount. This means that you're trying to perform a partial refund, but the charge hasn't been settled yet. This can happen when y'all try to refund inside a day of buy. The Authorize.Net plugin tries to void this order since the funds haven't been transferred yet, but Authorize.Net doesn't permit fractional voids. To resolve this, please await until the charge has settled (about 24 hours after the order was charged) earlier trying the refund over again.

Failed Subscription Renewals ↑ Back to height

The most frequent crusade of failed subscription renewals is the "Payment token is missing or invalid" mistake. This occurs when payment information has changed on your site or inside Authorize.Cyberspace for this user, just the subscription tape hasn't been updated. For a renewal to procedure successfully, a few atmospheric condition must be met:

• The customer must have a payment token on your site. Click here for information on viewing user payment tokens.
• The payment token data in the user profile must lucifer data on the subscription tape. Click here to learn more about finding this information in the subscription record.
• The payment must exist accustomed past Authorize.Cyberspace. Our plugin has no command over declined transactions.

If the customer contour ID and payment profile ID (payment token) don't match between the user and subscription records, any automated renewal orders volition fail until you lot update the subscription record IDs to lucifer the user tape IDs. We accept a few recommendations for preventing mismatches betwixt user and subscription records:

• Don't employ the aforementioned Qualify.Net API credentials on multiple sites. If customer payment information is changed on one site simply not another site, your payment contour data may no longer sync with your Qualify.Cyberspace account properly.
• If you accept customer information over the phone, be sure to update the payment information on your site instead of on Authorize.Net. Our plugin will push changes from your site to your Authorize.Net account, but won't be notified of payment information changes in Authorize.Net, so it can't update your site'south subscription records.
• If you make any changes to client or payment profile information from your Qualify.Net account, be sure to also update the subscription records on your site. You should double-cheque customer profile ID and payment profile ID for the subscription any time yous brand changes in Authorize.Internet.
• If your customers want to update a subscription payment method, they must employ the subscription "Change Payment" process. But adding a new payment method to their site account won't alter the subscription's payment method. If you're doing this for them, we recommend using the complimentary User Switching plugin to impersonate their business relationship.

Other Bug ↑ Back to peak

Having a different problem? Follow these steps to make certain everything is setup correctly before posting a support asking:

• Please ensure that your site meets the plugin requirements.
• Check the FAQs to see if they address your question.
• Ostend that your API Login ID and API Transaction Fundamental are right.
• Enable Debug Fashion and review the errors codes/messages provided by Qualify.Internet. Click here to learn more about Authorize.Cyberspace error/response codes. In some cases, such equally a transaction being held for review or declined, the plugin cannot change the issue and it must be resolved in your Authorize.Net account. If the error code indicates an issue with the plugin, delight submit a support ticket and include the logs to help the states troubleshoot.

For Developers ↑ Back to top

Here is a couple of example snippets for some of the Authorize.Cyberspace CIM filters in place: Default the "Securely Save to Account?" checkbox on the payment form to checked

	<?php
	// force the "securely save to account" checkbox to default to checked
	function wc_auth_net_cim_save_payment_method_default_checked( $html, $class ) {
	if ( empty( $html ) || $class->tokenization_forced() ) {
	return $html;
	}
	return str_replace( 'type="checkbox"', 'type="checkbox" checked="checked"', $html );
	}
	add_filter( 'wc_authorize_net_cim_credit_card_payment_form_save_payment_method_checkbox_html', 'wc_auth_net_cim_save_payment_method_default_checked', ten, 2 );

Adjust qualify-only transaction order status from "On hold" to something else

	<?php
	function sv_wc_auth_net_cim_tweak_held_order_status( $order_status, $order, $response ) {
	if ( 'on-hold' === $order_status && $response instanceof SV_WC_Payment_Gateway_API_Response && $response->transaction_approved() ) {
	$order_status = 'processing';
	}
	return $order_status;
	}
	add_filter( 'wc_payment_gateway_authorize_net_cim_credit_card_held_order_status', 'sv_wc_auth_net_cim_tweak_held_order_status', x, 3 );

Questions & Support ↑ Back to top

Have a question before y'all buy? Delight make full out this pre-sales grade. Already purchased and need some help? Please bank check out our troubleshooting tips and frequently asked questions for mutual issues or contact support via the help desk if y'all need more help.

nolenmustent.blogspot.com

Source: https://woocommerce.com/document/authorize-net/

Share this post