- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Credit Card buttons do not become enabled or disabled
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
08-26-2010 12:26 PM
We are using BHE Credit card module and in a process of testing the Sage Credit card module on 7.3 May. However we have run into an issue with the Sage Credit Card module.
When we charge the card by clicking on the “Pre-Auth” or “Sale” button these two buttons do not become disabled and the other three (“Process Pmt”, “Credit”, “Void”) buttons do not become enabled. We do receive response code, message and reference ID but the transaction grid is not populated. We can also see the transactions in the Virtual Terminal website.
So, not only we cannot process the preauthorized credit card payment but we can also click on “Pre-Auth” or “Sale” many times creating multiple pre-authorizations or sales.
Has anybody had a similar experience while testing Sage Credit Card module? If so, what was the solution?
Solved! Go to Solution.
Re: Credit Card buttons do not become enabled or disabled
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
08-27-2010 03:30 PM
Oyama,
This should work without any problem, there must be something unique about your situation. What dollar amount were you trying to pre-auth? Perhaps there is an error condition being returned from SPS that is not being handled properly.
MAS500, Principal Designer
Irvine, CA
Re: Credit Card buttons do not become enabled or disabled
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
08-30-2010 05:55 AM
I tried pre-authorize between $10 and $1,500. I also contacted with Sage and I uploaded our database for them to work with.
Re: Credit Card buttons do not become enabled or disabled
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
09-09-2010 01:18 PM
Well after further testing, this is what I found:
If I login to windows with Pevonia\balint and log in to MAS with windows authentication then the CC buttons do not work.
If I login to windows with Pevonia\balint and log in to MAS with SQL authentication using the login name “balint” then the CC buttons do not work.
If I login to windows with Pevonia\balint and log in to MAS with SQL authentication using the any login name (we tried a couple) then the CC buttons do not work.
If I login to windows with any domain user name but “balint” and log in to MAS with windows authentication (we tried about 5 logins) then the CC buttons do work.
If I login to windows with any domain user name but “balint” and log in to MAS with SQL authentication using the login name “balint” then the CC buttons do work.
So, now I am really curious what is so special about my windows domain login.
Re: Credit Card buttons do not become enabled or disabled
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
09-10-2010 08:46 AM
All right. The issue has been fixed but I do not know what exactly was wrong. At the end, it turned out that there is something wrong with my local windows profile. Once I deleted and recreated my profile the CC buttons started to work the way they were supposed to work.
What was wrong with my profile you might ask? I have no idea. I just know recreating my local windows profile has fixed this issue.


