We use cookies to try and give you a better experience in Freshdesk.
You can learn more about what kind of cookies we use, why, and how from our Privacy policy. If you hate cookies, or are just on a diet, you can disable them altogether too. Just note that the Freshdesk service is pretty big on some cookies (we love the choco-chip ones), and some portions of Freshdesk may not work properly if you disable cookies.
We’ll also assume you agree to the way we use cookies and are ok with it as described in our Privacy policy, unless you choose to disable them altogether through your browser.
Overview
GraceSoft has identified unexpected one-cent authorizations between September 29 and October 19 on a small number of Authorize.net gateway accounts where address verification checks were disabled.
We’re contacting our Authorize.Net customers to help review their payment security settings. To be sure your Authorize.net payment gateway is secure and prevent fraud transactions, we recommend the following security updates.
1. Regenerate the Transaction Key
As a precautionary security measure, we recommend regenerating your Authorize.Net Transaction Key and updating the corresponding configuration in GraceSoft.
Log in to your production Authorize.Net Merchant Interface.
Navigate to Account → Account and API Settings → API Credentials & Keys.
Under Transaction Key, select the option to generate a new Transaction Key.
Choose when the existing key should expire: immediately or after 24 hours, depending on the options presented.
Coordinate the change with GraceSoft technical team to minimize the risk of payment processing interruptions.
Submit the request and complete any required PIN or one-time passcode verification.
Copy and securely store the new Transaction Key. Ensure it is accessible only to authorized personnel.
Provide the new key to your authorized technical team through an approved secure channel.
Update the payment gateway configuration in GraceSoft under Setup → Account → Credit Card.
Test the payment workflow and confirm that transactions are processing successfully before considering the change complete.
2. Review Recent Transactions
Review your Authorize.Net transaction history for the period covering September 29 through October 19, 2026, and check for $0.01 authorizations.
If you identify unfamiliar transactions:
Record the transaction IDs, dates, amounts, and other relevant references.
Contact GraceSoft to update Authorize.Net AVS Fraud settings.
Important security precautions
Never send your Transaction Key through ordinary email or include it in screenshots, support tickets, or application logs.
Do not share your merchant account password, Transaction Key, or full payment card details with unauthorized personnel.
Do not expire the existing key immediately unless the replacement configuration is ready or immediate revocation is necessary to address a suspected compromise.
If you suspect that your merchant account credentials have been compromised, contact Authorize.Net and GraceSoft Support promptly for assistance.
3. Verify Payment Processing
After completing the recommended security actions, verify that your payment gateway configuration is correct and that payment processing continues to function as expected.
4. Contact Support
If you need assistance reviewing your payment gateway configuration, updating your Transaction Key, or investigating unusual authorization activity, contact GraceSoft Support and provide the relevant transaction references.
For your security, do not send passwords, Transaction Keys, or full payment card details by email or through support tickets.
Recommendation
We recommend completing these security checks promptly to help reduce the risk of further suspicious activity and protect your payment processing operations.
0 Votes
0 Comments
Login or Sign up to post a comment