Design Team

Good morning @archflirt

The plugin does support refunds & voiding transactions. We had this issue pop up a little while ago and we’d suggest checking the user access settings in your NMI account. Please confirm that the user you are connecting with via the API Key has refunds or voids turned on. You can check this under: My Settings > User Accounts, and then select the user account tied to your API Key.

[ Signature deleted ]

• This reply was modified 5 years, 10 months ago by Jan Dembowski.

@scottking

At the moment, the differences are minor. The free version allows you to accept transactions using the three step redirect process, which is a secure way to collect credit card information so that it is never stored on your server.

The paid/premium version does that as well and allows your users to save their payment methods for future transactions. This data is also collected and stored securely, but is never stored on your server. Currently, this is the only difference between the paid and free versions. In the future, we are hoping to add support for subscriptions to the premium version.

[ Signature deleted ]

• This reply was modified 5 years, 10 months ago by Jan Dembowski.

@sam1001

Thanks for the update! I was researching it this morning and could not recreate the problem. Every transaction I submitted came up as Three Step, so that is good information to have.

[ Signature deleted ]

• This reply was modified 5 years, 10 months ago by Jan Dembowski.

@basicmatrix

Thanks for the note! I will log this and make sure we confirm payment methods are legit before they are created in WooCommerce.

Nate

This option is not currently available with our plugin, but I will add it to our list of to-do’s. Thanks for the input!

Nate

We are currently working on a new version that will move everything to the checkout page. For the first release, we had to move it to the second page but realize that it is not as convenient and easy to use as it should be. We don’t have a release date for this at the moment, but we are making progress and hope to have it ready soon.

Nate

Sorry about that. I did a little digging and found that mobile browsers might force their own css styles on your buttons. Try adding this to the css definitions for those elements:
-webkit-appearance: none;

I found that here, but am not positive it will be the fix you need:
https://drupal.stackexchange.com/questions/171952/styling-submit-form-button-for-mobile

@kmgreek

There shouldn’t be different id’s for mobile. I did check out your shop on Chrome and it was doing the same thing, so I picked apart your css a little bit and came up with the following. Please try plugging this in and let me know how it goes. I just grabbed the styles from your buttons on the previous page and assigned them to the id’s of the two buttons from our plugin.

#backbutton, #submitbutton {
color:#ffffff;

font-family: Karla, Arial, Helvetica, sans-serif;
font-weight: 700;
letter-spacing: 1px;

padding: 11px 23px;
line-height: 16px;
font-size: 13px;

background: #32a242;
text-transform: uppercase;
color: #ffffff;
transition: all .2s;
border-width: 0px;
border-style: solid;
border-color: #ffffff;
border-radius: 25px;
-webkit-transition: all .2s;
-moz-transition: all .2s;
-ms-transition: all .2s;
-o-transition: all .2s;
-webkit-border-radius: 25px;

display: inline-block;
position: relative;
outline: 0;
zoom: 1;
border: 1px solid transparent;
text-align: center;
text-transform: uppercase;
text-decoration: none;
font-weight: 700;
cursor: pointer;
box-sizing: border-box;
-webkit-transition: all .2s;
transition: all .2s;
}

#backbutton:after, #backbutton:before, #submitbutton:after, #submitbutton:before {
transition-property: color,background-color,border-color;
transition-duration: .2s;
transition-timing-function: linear;
}

#backbutton:hover, #submitbutton:hover {
background-color:#EBAD37;
}

@kmgreek

At the moment, I do not have any styles on the buttons. You should be able to access them using the following element ids:
#backbutton
#submitbutton

I believe modifying the styles for those id’s will do what you want. If not, please be sure to let me know and I’ll take a closer look.

[ Signature deleted ]

• This reply was modified 5 years, 10 months ago by Jan Dembowski.

@thademorrow

Hi Tyler

Technically, the customer does leave your site. For the three step redirect process, the credit card information is submitted directly to the gateway url from the checkout form. It is then returned to the site and validated, then the order is completed and the user is redirected to the confirmation page.

We have not had a situation like this come up yet, but we believe it will not interfere with the checkout process as the transaction with the gateway and the changes to the order have been completed by the time the redirect is used. Our best suggestion would be to set it up as you suggested (/checkout/order-received?utm_nooverride=1) and run a test transaction. You can also try it without the ?utm_nooverride=1 and see if that shows up in your analytics correctly.

Please let me know how this goes. It is an interesting use case and I’d like to find out more about how it works.

Thanks!

Nate

@joelpeterson

Hi Joel
At the moment, our plugin does not support the WooCommerce Subscriptions plugin. We will be working on it for a future release, but don’t have a scheduled release date yet.

Thanks for checking in!

[ Signature deleted ]

• This reply was modified 5 years, 10 months ago by Jan Dembowski.

@johnthetech

I’ve made some updates to the plugin already to deal with the recent WooCommerce updates and have a few more yet to finish before the next release, but this request will be definitely be included. I should have it ready later this month, after I finish dev and testing.

Nate

@ddsystems

Thanks for the note! I will look into it and reply to this thread once I have a fix published and ready to go.

Nate

@kylearena07
I took a closer look at your cart page and it looks like there is a Javascript error that might be interfering with the way we handle the checkout process. This error could be coming from another plugin or the WP theme you are using.

I’d be happy to try and help troubleshoot. Please let me know what I can do.

Nate

Hi Travis,

You can upgrade to the Pro version directly in your WordPress admin after you download and install the free version.

You can find the upgrade page in the admin under WooCommerce > Settings > Upgrade

Thanks.