Those Details Dont Match Our Records. Double-check and Try Again Istock

article.post .entry li img.aligncenter { margin: 15px auto; }

Overview ↑ Dorsum to top

WooCommerce Authorize.Cyberspace Gateway integrates with Authorize.Net payment services to provide secure and powerful payment processing for your store. With this gateway, you can take credit cards and eChecks and let customers salvage 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 you plan to use this plugin with Subscriptions, Pre-Orders, or desire to allow customers to save their payment details, the Customer Information Manager (CIM) feature must exist enabled on your Authorize.Net account (additional monthly costs may apply).

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

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

Requirements ↑ Back to top

• An Authorize.Net account
• An SSL certificate. An SSL certificate is besides required on local exam environments.
• WooCommerce 3.5+
• WordPress v.ii+
• PHP 7.0+ (yous tin can run into this under WooCommerce > Status)

Installation ↑ Back to top

1. Ensure your store meets the plugin requirements.
2. Download the extension from your WooCommerce dashboard.
3. Go to Plugins > Add New > Upload and select the Cypher file you just downloaded.
4. Click Install Now and and then Activate.
5. Click Configure and read the next section to acquire how to setup the plugin.

Getting Started ↑ Back to top

To begin using Qualify.Net, you must commencement connect the plugin to your Authorize.Net account. Follow the steps beneath to find your API credentials on Authorize.Net and setup the plugin:

1. Login to your Authorize.Net business relationship.
2. Get to Accounts > Settings > API Credentials & Keys.

3. Copy your API Login ID.
4. Select the New Transaction Key radio button and click Submit. Re-create the Transaction Fundamental.
5. If yous want to setup webhooks, select the New Signature Key radio button and click Submit to generate the Signature Key.

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

That's information technology! You are now ready to start accepting credit cards via Authorize.Net! Keep reading if you desire to tweak settings and customize the checkout procedure.

Credit Carte du jour Settings ↑ Dorsum to top

You tin configure the post-obit settings for the Authorize.Net credit card gateway:

• Enable / Disable: Allow customers to use this gateway to checkout.
• Title: The text shown for the payment during checkout and on the Order Received page.
• Description: The text shown nether the gateway's title during checkout. Limited HTML is allowed. If y'all enable test mode, this section will also display a notice along with test credit card numbers.
• Bill of fare Verification (CSC): Crave customers to enter their card security codes when checking out. This tin can exist useful if you have requirements in your Authorize.Net account for CV2 verification.
• Transaction Blazon: Controls how transactions are submitted to Authorize.Net. Select "Accuse" to automatically capture payments. If you select "Authorization", you must manually capture and settle payments in your Authorize.Cyberspace command console or on the WooCommerce orders screen after the transaction has been submitted. This defaults to "Charge".
• Accuse Virtual-Only Orders: If Transaction Type is gear up to "Authority", enable this to automatically capture charges for orders with only virtual products. For downloadable products, this will grant downloads access right away.
• 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 menu logos are displayed during checkout. This has no affect on which cards are accepted by your merchant account.
• Tokenization: Let customers save their payment methods for future use at checkout. This is required for Subscriptions or Pre-Orders.
• Detailed Decline Letters: Display detailed messages to customers to provide reasoning for declines instead of a generic error bulletin when possible. Click here to read more about detailed decline messages.
• Debug Mode: Enable when you're having issues processing transactions. Y'all can choose to log API requests directly on the checkout page, relieve them to the WooCommerce > Status > Logs page, or both. As a all-time practice, please do not enable this setting unless y'all're having problems with the plugin.
• Environment: Switch between "Examination" and "Production" credentials. Enable "Test" to send transactions to your Authorize.Internet Examination Account. Note: This is not the "test mode" that is listed nether your account. This is an entirely split sandbox environment that requires a separate login and split up API credentials. Do non place your Examination Account (or regular account) into "Test Mode" within the Qualify.Net control panel every bit transactions will non process at all if that fashion is fix.
• Share connectedness settings: If using the credit card and eCheck gateways, select this setting to share credentials between the gateways and then y'all don't take to enter them twice.
• API Login ID: Follow the steps to a higher place to recall your API Login ID.
• API Transaction Fundamental: Follow the steps higher up to generate your API Transaction Key.
• API Signature Cardinal: Optional. Simply required if you want to enable webhooks for Authorize.Internet account updates. Follow the steps to a higher place to generate your API Signature Primal.
• Payment Class Blazon: Y'all tin can choose how yous'd like to display the payment form. The Inline option meets SAQ-A EP PCI requirements while the Lightbox selection supports SAQ A standards.

eCheck Settings ↑ Back to top

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

• Enable / Disable: Let customers to use this gateway to checkout. You must enable eChecks on your Qualify.Net account to employ the eCheck gateway. Follow the procedure below under eCheck Issues to get eChecks setup and enabled.
• Championship: The text shown for the payment during checkout and on the Order Received page.
• Clarification: The text shown under the gateway'southward title during checkout. Limited HTML is allowed. If you enable test mode, this section will also display a notice along with a test bank account number.
• Tokenization: Permit customers salve their payment methods for hereafter utilize at checkout. This is required for Subscriptions or Pre-Orders.
• Authorisation: Display an dominance message during the checkout process.
• Authorization Message: If Authority is enabled, enter the message yous want to show to your customers. Y'all can employ the following merge tags:
  • {merchant_name}: Your store name
  • {order_date}: Appointment of purchase
  • {order_total}: Total order value
• Recurring Dominance Bulletin: If Authorization is enabled and WooCommerce Subscriptions is agile on your site, you tin enter the message you desire to show your customers for recurring payments.
• Detailed Reject Letters: Display detailed letters to customers to provide reasoning for declines instead of a generic error message when possible. Click hither to read more most detailed pass up messages.
• Debug Mode: Enable when you're having issues processing transactions. You lot tin can choose to log API requests direct on the checkout folio, relieve them to the WooCommerce > Status > Logs page, or both. Equally a all-time practice, please do non 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 Examination Account. Note: This is non the "test mode" that is listed under your account. This is an entirely separate sandbox environment that requires a separate login and separate API credentials. Do non place your Test Account (or regular account) into "Test Mode" inside the Authorize.Net control panel as transactions will non process at all if that mode is set.
• Share connection settings: If using the credit carte and eCheck gateways, select this setting to share credentials betwixt the gateways so yous don't have to enter them twice.
• API Login ID: Follow the steps in a higher place to retrieve your API Login ID.
• API Transaction Key: Follow the steps to a higher place to generate your API Transaction Key.
• API Signature Cardinal: Optional. Only required if you want to enable webhooks for Qualify.Net business relationship updates. Follow the steps higher up to generate your API Signature Key.
• Payment Course Type: Choose to brandish the payment form inline or in a lightbox. Select "Inline" to back up PCI-DSS SAQ A-EP compliance.

eCheck Setup with Qualify.Net

To enable eCheck processing on your Authorize.Cyberspace account:

1. Setup an eTicket and enquire for the "WEB" eCheck type to be enabled. Be certain you are an account owner and know your gateway ID.
2. Web transactions are usually enabled within two business days, only there is a funding hold automatically placed on your account – y'all tin can take funds in, just tin can't have them out until y'all pass another security check with the underwriting section.
3. To expedite this procedure, call the Authorize.Internet underwriting section so they tin 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 will be removed.

Webhook Setup ↑ Dorsum to top

Webhooks notify your WooCommerce site when customer profiles and payment profiles are deleted from your Authorize.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 above to generate your API Signature Key, which you can enter in the plugin settings to enable webhooks. So, click the link in the settings notice to enable webhooks. This will push button the required information into your Qualify.Net account. Authorize.Internet will now notify your site when the customer or payment profiles are deleted from your account. Nosotros do, however, recommend avoiding changes within your business relationship when possible.

Managing Orders ↑ Back to top

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

Capture Charges ↑ Back to top

If y'all are using version 2.0+ of the Authorize.Net gateway and the Transaction Blazon setting is ready to "Authorization", you can manually capture these payments from the WooCommerce Orders page. Click hither to read more about capturing charges.

Note: If your Transaction Type setting is set to "Accuse", you cannot use the Capture button. Attempting to practise and then will result in the following error message: 3 (E00027) - The transaction was unsuccessful. Mistake Code: 33 - A valid referenced transaction ID is required.

Automated Refunds ↑ Back to top

If you are using version 2.0+ of the Authorize.Cyberspace gateway and version 2.two+ of WooCommerce, yous can process refunds for Credit Card transactions directly in WooCommerce without needing to log into your Authorize.Internet account. Click here to read more than well-nigh issuing automatic refunds from WooCommerce.

Void Transactions ↑ Back to height

You can void transactions straight in WooCommerce in the following circumstances:

• If your Transaction Type setting is set to "Dominance", y'all can void when the transaction has been authorized only non yet captured.
• If your Transaction Blazon setting is set to "Accuse", you can void when the transaction has non yet been settled (e.m. funds oasis't been transferred from the client's business relationship to your Authorize.Internet business relationship).

Qualify.Net does non take partial voids. If a transaction is no longer eligible to be voided, you must refund the order. Click here to read more about voiding transactions in WooCommerce.

Gateway Features ↑ Dorsum to top

Your customers can have advantage of the post-obit features when your site uses WooCommerce Authorize.Net.

Saving Payment Methods ↑ Back to meridian

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

Client Saved Payment Methods

Subscriptions / Pre-Orders Back up

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

Accept.js ↑ Dorsum to top

Version 3.0+ of WooCommerce Authorize.Net includes automated back up for Have.js. Once you have configured the gateway, nosotros can retrieve the information required to utilize Take.js from your Authorize.Net account – no actress configuration steps required! This feature means that customer payment information is handled directly by Authorize.Net, meeting the lower level PCI SAQ A-EP compliance level. Take.js is handled behind the scenes, so your customers won't detect any change to their checkout process. Click here to learn more about Accept.js.

Enhanced Checkout Form ↑ Dorsum to top

Qualify.Net supports an enhanced checkout form that improves the checkout experience on mobile and desktop devices. Click hither to read nearly the enhanced payment form.

Notation: The advent of your checkout form may vary based on your site'due south theme.

Authorize.Internet Emulation ↑ Back to top

Nosotros are in the process of deprecating support from Qualify.Cyberspace emulation. Newer users of the WooCommerce Authorize.Internet plugin may not have access to these settings. Please contact our back up team with any questions about Qualify.Net Emulation support.

Note: Authorize.Net Emulation does not support advanced features such as 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, you need to enable the Qualify.Net emulator nether Plugins > Installed Plugins — click "Enable emulation gateway":

Enable Emulation Gateway

This allows y'all to use Qualify.Net's emulation protocol for other gateways. The Authorize.Net emulator settings will at present be bachelor under WooCommerce > Settings > Payments. To utilize Qualify.Cyberspace emulation, you must enable the gateway and enter the Gateway URL and API credentials provided to y'all by your payment processor.

Emulator settings

Authorize.Internet Emulation Settings ↑ Back to top

• Enable / Disable – This will enable the gateway to exist used by customers to checkout.
• Championship – This is the text shown for the payment during checkout and on the Order Received page.
• Description – This is the text shown under the championship during checkout. Limited HTML is allowed. If you enable test way, this section volition also display a notice along with test credit card numbers.
• Card Verification (CSC) – Enable this to crave customers to enter their CVV / CV2 (Bill of fare Security Code) when checking out. This can be useful if you have requirements in your Authorize.Net account for CV2 verification.
• Transaction Type – This controls how transactions are submitted to Authorize.Net. You may choose either "Accuse" or "Authority". If you select "Say-so", you must manually capture and settle payments in your Qualify.Net control panel or on the WooCommerce orders screen after the transaction has been submitted. This defaults to "Charge".
• Accepted Card Logos – This controls the card logos that display during checkout. This is purely cosmetic and has no upshot on the cards actually accepted by your merchant account.
• Debug Way – Enable this is you are having issues correctly processing transactions. Yous tin can either log API requests / responses straight to the checkout / thank you page, save them to the WooCommerce Mistake Log (found under WooCommerce > System Status > Logs) or both. All debugging letters are cleaned of sensitive information earlier display, simply every bit a best practice, please do not enable this unless you are having issues with the plugin.
• Environment – Switch between "Test" and "Production" credentials. Enable "Test" to send transactions to your Authorize.Internet Exam Account. Note: This is not the "examination way" that is listed under your Authorize.Net account. This is an entirely carve up sandbox environment that requires a dissever login. Y'all tin sign up for a test account here. Once you have washed this, you tin enter a separate API Login ID and API Transaction Primal for your test business relationship. Practise not identify your Test Business relationship (or regular account) into "Test Style" within the Qualify.Internet control panel as transactions volition not process at all if that mode is set.
• 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.Internet account (Test or Production). Follow the steps to a higher place to get this. If you're using this gateway for Qualify.Net emulation, then this will be the API Login provided to you lot by your payment processor.
• API Transaction Key – This is the API Transaction Key for your Authorize.Cyberspace account (Test or Production). Follow the steps above to get this. If you're using this gateway for Authorize.Cyberspace emulation, and then this will be the API Transaction Key provided to you by your payment processor.

Oftentimes Asked Questions ↑ Back to top

Q: Why am I receiving an mistake message on subscription renewals maxim that Carte Code is required? It's not required in my plugin settings! A: If you're seeing an fault like "Authorize.Internet Payment Failed (iii E00027): Card Lawmaking is Required…", information technology'southward likely that Card Lawmaking is required on your Authorize.Net account. For PCI compliance and security reasons, Authorize.Net cannot store CSCs for subscription renewals, and so card codes are unavailable for renewal orders. If your Authorize.Cyberspace account requires these, the orders volition fail. Click here to learn how to disable this requirement.

---

Q: Why don't Subscriptions display inside the Qualify.Cyberspace control panel? A: Subscriptions aren't shown in Authorize.Cyberspace because the gateway doesn't use ARB (automated recurring billing). Information technology tokenizes the client'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 every bit irresolute payment dates and amounts, that ARB can't handle.

---

Q: Why did I receive a "examination transaction successful" electronic mail? A: During checkout, the extension validates the payment data entered by the customer (i.eastward. confirms that the menu number, expiration date, etc. are right). This "test transaction" does not charge the customer, but generates an email to the merchant. You can electronic mail support@authorize.cyberspace to have them disable this email notification to you lot.

---

Q: Tin can I process automated refunds with eChecks? A: No – automatic refunds from WooCommerce tin simply be processed for credit card transactions.

---

Q: I'm migrating sites – can I import customer IDs and payment contour IDs to my new site? A: The Authorize.Net plugin stores the customer ID, payment profile ID, and shipping profile ID every bit meta fields, then y'all could use an consign plugin like Customer/Lodge CSV Export to pull down the IDs from your erstwhile site and use an import plugin like Customer/Guild/Coupon CSV Import Suite to import these IDs to yous new site! Other export/import plugins might work well here, too, so long as they are capable of exporting and importing customer/user meta.

---

Q: My customers get email receipts from WooCommerce and Authorize.Internet. How do I get rid of Authorize.Net receipts? A: You tin can disable these emails in your Authorize.Internet account. Click here for instructions on disabling customer email receipts.

---

Q: How do I capture a higher amount than what is authorized (like a gas station or restaurant)? A: Authorize.Net (along with most any eCommerce payment processor) cannot practice this with carte-not-nowadays transactions, such as online payments. For these payments, you can only capture up to the value of the authority: "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, so this isn't possible on your WooCommerce site or with the Qualify.Cyberspace plugin.

---

Q: Authorize.Net supports Apple tree Pay for web payments. Can I use this in my store? A: Qualify.Net CIM contains a framework for Apple tree Pay, merely information technology can only be enabled by developers, as the certification process requires programmer-only tools. If you lot work with a developer and would like to add together Apple tree Pay to your store, delight click here to review the setup instructions and requirements. Please note that configuring Apple Pay support for this plugin is considered a customization and is not covered by our support policy.

---

Q: Does this plugin support 3D Secure? I need to meet Stiff Customer Authentication (SCA) requirements. A: WooCommerce Authorize.Net does not back up 3D Secure at this time — Authorize.Net'southward API does not support accepting the client data required to run across 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 inquire your Authorize.Internet representative about migrating you to CyberSource. You can read more about PSD2 and Authorize.Internet here, and see updates on 3D Secure with WooCommerce CyberSource here.

---

Q: I take a local exam environment, do I need to have an SSL certificate installed? A: Yeah, an SSL certificate is besides required on local test environments. In club to obtain an SSL Certificate for your local site, yous can generate a self-signed certificate, or install a exam certificate with a service such as the complimentary Permit's Encrypt. Q: When I delete a user on WordPress, is their saved payment method deleted on Authorize.Cyberspace? A: When a user is deleted on WordPress, their payment profile will exist deleted from their Authorize.Net customer profile too. Their Customer Contour would still exist in the Customer Information Manager (CIM), and the payment profile section volition brandish: "This Customer Profile does not have any associated Payment Profiles".

Troubleshooting ↑ Back to top

Authorize.Net Test Credentials ↑ Back to top

To run tests with this plugin, you lot will need a set of dedicated examination credentials from Authorize.Cyberspace. Your alive credentials cannot be used in "Test" fashion. When yous modify the Environment setting to "Test", the Connection Settings fields will remove your live credentials and let you enter your test credentials. When you switch dorsum to "Production", the plugin will restore your live credentials.

Annotation: Practise not fix your production accounts into test mode from within your Authorize.Net account – this returns dummy information for live transactions, but does non work with the plugin's test style, since you're still using production credentials.

Qualify.Net Error Codes ↑ Dorsum to top

Qualify.Net provides many different mistake/response codes that tin can provide helpful information almost what caused an fault during payment processing. Click here to review Authorize.Net's Response Code Reference. Yous can enter the lawmaking in this reference tool to see the cause of the error. In some cases, such as a transaction existence held for review or declined, the plugin can't resolve the issue. In those cases, you lot must prepare the trouble from your Authorize.Cyberspace account. Notes:

• Orders with Response Code = iv will exist approved, only can be cancelled manually in the WooCommerce admin and Authorize.Net Merchant Expanse expanse afterwards if they neglect review.
• Be sure to have "Partial Authorization" turned off in your Authorize.Internet Merchant Surface area. This will restrict orders with Response Code = 4 and Response Code = 295 from being approved. "Allow Partial Payments" is off by default, but to verify it is off, follow these steps:
  • Login to your Authorize.Net merchant surface area.
  • Go to Account > Partial Dominance.
  • Ensure that Let Partial Payments is unchecked and click Submit to salve your changes, if applicable.

Required Field Errors ↑ Back to height

If you receive an error like (E00027) - The transaction was unsuccessful. Error Code: 33 - [Field Name] is required., your Authorize.Net account is probable setup to crave a field that our plugin cannot transport. These errors can occur on orders, refunds, and void transactions. To resolve this issue, you should remove all field requirements from your Qualify.Net account by following the steps below:

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

Accept.js Errors ↑ Back to height

If you receive an error like Take.js Error: payment nonce is missing, your checkout page is probable 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 crusade this error. A few conflicting plugins to wait for are:

• Autoptimize
• SG Optimizer
• Hummingbird Pro

If you lot 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 Issues ↑ Back to elevation

If yous enabled eChecks in the Authorize.Net gateway plugin just have not enabled Spider web eCheck enabled on your Authorize.Net account, yous may run across errors like [Code 246] - This eCheck.Net type is not allowed. Click here for instructions on setting up eChecks on your Qualify.Internet business relationship.

Refund Issues ↑ Dorsum to top

When attempting to procedure an automatic refund, you may see the following error bulletin: Oops, you cannot partially void this order. Please use the full society amount. This means that you're trying to perform a partial refund, but the charge hasn't been settled still. This can happen when you try to refund inside a twenty-four hour period of purchase. The Qualify.Net plugin tries to void this order since the funds haven't been transferred however, but Authorize.Net doesn't permit partial voids. To resolve this, please wait until the accuse has settled (nearly 24 hours after the order was charged) before trying the refund again.

Failed Subscription Renewals ↑ Back to top

The well-nigh frequent cause of failed subscription renewals is the "Payment token is missing or invalid" error. This occurs when payment information has changed on your site or within Qualify.Net for this user, simply the subscription tape hasn't been updated. For a renewal to procedure successfully, a few conditions must exist 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 contour must match data on the subscription record. Click here to learn more than most finding this information in the subscription record.
• The payment must be accepted past Authorize.Net. Our plugin has no control over declined transactions.

If the customer profile ID and payment profile ID (payment token) don't match betwixt the user and subscription records, whatever automatic renewal orders will fail until you update the subscription record IDs to match the user tape IDs. We have a few recommendations for preventing mismatches betwixt user and subscription records:

• Don't use the same Qualify.Net API credentials on multiple sites. If client payment information is inverse on one site but not some other site, your payment contour data may no longer sync with your Authorize.Net account properly.
• If you take customer information over the telephone, exist 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 Qualify.Net, and so information technology can't update your site'due south subscription records.
• If you make any changes to client or payment profile information from your Authorize.Internet business relationship, be sure to also update the subscription records on your site. You should double-check customer profile ID and payment profile ID for the subscription whatsoever fourth dimension y'all make changes in Qualify.Internet.
• If your customers want to update a subscription payment method, they must utilise the subscription "Change Payment" procedure. Simply adding a new payment method to their site business relationship won't alter the subscription's payment method. If you're doing this for them, we recommend using the gratuitous User Switching plugin to impersonate their account.

Other Issues ↑ Back to top

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

• 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 Key are correct.
• Enable Debug Style and review the errors codes/messages provided by Qualify.Net. Click here to learn more about Qualify.Cyberspace error/response codes. In some cases, such as a transaction being held for review or declined, the plugin cannot alter the issue and information technology must exist resolved in your Authorize.Net account. If the error code indicates an issue with the plugin, please submit a support ticket and include the logs to assistance us troubleshoot.

For Developers ↑ Dorsum to top

Hither is a couple of example snippets for some of the Qualify.Internet CIM filters in place: Default the "Securely Save to Business relationship?" checkbox on the payment class 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 ) || $form->tokenization_forced() ) {
	render $html;
	}
	return str_replace( 'type="checkbox"', 'blazon="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', 10, 2 );

Conform authorize-but transaction order condition from "On concur" to something else

	<?php
	office sv_wc_auth_net_cim_tweak_held_order_status( $order_status, $guild, $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', ten, 3 );

Questions & Back up ↑ Back to top

Accept a question before you buy? Please make full out this pre-sales course. Already purchased and need some assistance? Please check out our troubleshooting tips and frequently asked questions for common problems or contact back up via the help desk if you need more help.

greerustract.blogspot.com

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

Share this post