Effectively Monitor Transaction Processing in OrangeCRM

Regularly monitoring transaction processing is critical to the success of your business. While OrangeCRM automates transaction processing with its batch jobs, it is still necessary to review the results, so that you can identify any areas that may need attention.

To get a bird’s-eye view of each bank batch’s results, simply go to the Bank menu and click on one of the three Deposit options: Deposits by Date, Deposits by Bank or Deposits by Group.


Each of the three deposit options provides a list of transaction batches, along with a breakdown of the following key details for each batch: the number of transactions in error status, decline percentages for both sales and retried transactions, as well as the sale, refund, decline and net deposit dollar amounts.


Frequently analyzing the results of your daily bank batches will allow you to quickly identify any processing errors or negative trends that require action.

From the view pictured above, each batch can be opened to access its individual transactions. Shortcut links to the customer record are also provided with each transaction. This enables you to conveniently take any necessary actions on the transaction and/or customer record.


For additional instructions, please refer to the OrangeCRM Help Guide at

Speed Up Transaction Processing Times in OrangeCRM

OrangeCRM Batch Jobs are operations that are scheduled to run behind the scenes to accomplish a multitude of functions in an automated fashion.

Among the various types of Batch Jobs are Merchant Bank jobs, which batch together all qualifying transactions and sends them to the selected Gateway for processing. Merchants with a high number of banks and/or transactions may find that their batch jobs are taking too long to process.

A simple way to minimize transaction processing times is to schedule Merchant Bank jobs to run at night, when other CRM activity is very low. Additionally, you can free up your job queues during that time frame by using the Blackout Time feature to temporarily suspend any Batch Jobs that run frequently throughout the day, such as every hour or more often.

Blackout Time settings can be configured within the Advanced Scheduling tab of a Batch Job.


For further assistance with managing batch processing times, feel free to contact our support team at (770) 227-0036 Ext 1.


Does Your Online Business Need to Collect Sales Tax?

Collection of sales tax on internet sales has been a matter of ongoing debate both within individual states and at the federal level.

The current default rule throughout the United States is that you must collect sales tax on internet sales from customers in those states where your business has a physical presence. Generally speaking, a physical presence means having:

  • a warehouse in the state
  • a store in the state
  • an office in the state, or
  • a sales representative in the state.

Typically, if you do not have a physical presence in the state, you are not required to collect sales tax for an internet-based sale to someone in that state. However, many states have used the term “Nexus” rather than “Physical Presence” in their sales tax laws, regulations or other official documents. In the process, these states have sometimes defined nexus in ways that could go beyond physical presence.

For that reason, it’s important for online sellers to be aware of the internet sales tax laws in each of the states where their customers are located. Learn the current rules for all 50 states with this handy guide, provided by legal advisory company Nolo: Internet Sales Tax: A 50-State Guide to State Laws.

MasterCard’s New 2 Series BIN Initiative – Why It’s Important to be Compliant

Back in March we alerted merchants accepting MasterCard of the changes that are necessary to support the new 2 series Bank Identification Numbers (BINs) being released on October 14, 2016.

(To read that post, click the following link: Important Change for Merchants Accepting MasterCard – Don’t Get Slapped with Fines up to $25,000 Per Month!)

As a MasterCard mandated initiative, the credit card company will be monitoring 2 BIN acceptance rates and may impose non-compliance assessments to businesses that are unable to accept 2 BIN cards by the October deadline.

This BIN series will help to support the expanding payment industry and growing number of cardholders globally. Which means non-compliance can also result in a disruption to your business, along with the dissatisfaction of cardholders with a 2 series BIN who wish to do business with you, whose payments you are unable to accept.

With only 3 months remaining, it’s important for all industry stakeholders to take the needed actions to ensure your payment solution is equipped to recognize and process MasterCard 2 series BIN cards, if you haven’t already done so.

If you’re using OrangeCRM, you’ll have one less thing to worry about. Our software is already programmed to support the new MasterCard BINs.

Other systems that should be tested for compliance include point-of-sale (POS) terminals and payment processors/gateways used in both card present and card-not-present environments, such as web applications and online stores.

Manage Lead Payouts Based on Customer Billing Activity

Clear, accurate data is crucial in managing lead payouts. This is especially true since a number of factors can cause a lead’s status to change during the customer’s life cycle. OrangeCRM makes it easy to determine whether or not a lead is payable by giving you full control over when, why and how lead statuses are updated.

Manage when a lead’s status should be updated at the Fee Schedule level. This gives you the freedom to customize when a lead is to be considered payable or non-payable based on the payment cycle,  e.g. at the end of a trial period or during the first  continuity billing after the initial purchase.

Choose why a lead’s status is to be changed in the Fee Schedule Responses tab. Options include: Transaction Accepted, Transaction Declined, Transaction Error, Transaction Retry.

Finally, define how the lead will be updated by selecting the desired status for each of the options mentioned above.

Fee Schedule Responses - Set Lead Status

For more details, please visit our online help guide at


Customize How Transactions Are Handled In OrangeCRM

Did you know you can control which transactions OrangeCRM recognizes as Approved, Declined, Error, Retried or Chargeback? That’s right, OrangeCRM allows you to dictate how it handles each response code from your payment gateway and which transaction status is triggered.

A gateway response code is the message your payment processor sends back to the CRM for each transaction. Although the Merchant Bank form automatically populates the response codes for the selected gateway and assigns them to a default transaction status, you can choose to either keep the CRM’s default settings or customize them as needed.


Using the transaction pictured above as an example, let’s say your gateway uses response code 258 for “invalid cards” and the CRM default transaction status is Error. Well, you may wish to treat “invalid cards” as declines instead of errors. In that case you would simply go to the Gateway Response Codes section in the Merchant Bank Setup tab (see image below), remove response code 258 from the Error Codes list and insert it in the Decline Codes list. You could also add it to the list of Retry Codes if you want the CRM to automatically retry all “invalid card” transactions.


This is just one example of numerous ways in which you can customize how OrangeCRM handles transactions based on your gateway’s response codes. If you have any questions, please feel free to contact support at (770) 227-0036 Ext 1.

AVS Transaction Processing Management

If you use multiple merchant banks, OrangeCRM gives you the ability to use the bank with the lowest fee per transaction, based on the AVS response. You can choose which bank to route verified AVS transactions to, and which bank to route invalid AVS transactions to.

To manage these settings, go to the Merchant Bank >Setup Tab >Processing Options > AVS Trans Filter >Select from All Trans, Verified, Invalid or Unknown.

If you have any questions, please feel free to call our support line at 770-227-0036.

Time to Ditch your Wallet?

According to a recent survey by PayPal, in five major global markets, “at least 3 of 4 respondents said they wished they didn’t have to carry their wallets around with them.” This survey shows that nearly one in three Americans (29%) would choose a smartphone over a wallet if they could only bring one item when going out.”

So many consumers ‘are ready for the day when the notion of carrying around a bulky wallet to pay for things will seem antiquated’. Are we on the cusp of a transformational moment as to how consumers will make every day financial transactions?

Some businesses are seeing ‘a real opportunity to make people’s lives easier … and the opportunity to make their shopping experiences more seamless, connected, friction-free and intuitive.’ What do you think? Is it time to ditch your wallet? Please share your comment with us.

For more details on this PayPal survey, please go to their blog site at:

Load Balancing in OrangeCRM

Load balancing allows you to distribute your high transaction volume between multiple merchant banks so that all merchant banks are used in a balanced way.

OrangeCRM has two kinds of load balancing options available:

  1. Load balancing within OrangeCRM
  2. And load balancing by customer sticky routes.

Option 1 – Load Balancing within OrangeCRM

You can limit the dollar amount of transactions that a merchant bank can receive in a:

  • Day
  • Month
  • Or by the batch.

Next, you can set the priority levels for when your merchant bank batches will run.
Then OrangeCRM will load balance your merchant bank limits starting with the lowest merchant limit to the highest.

Option 2 – Customer Sticky Routing

At the point of origin, on the web site, a different bank route will be assigned to each customer progressively.  Each customer will be assigned to the next merchant bank in an even pattern. This routing at the point of acquisition will be stamped onto the customer’s record in OrangeCRM and maintained for all recurring billings.

OrangeCRM offers several detailed reports to show the results of your load balancing. Here are few examples of these reports:

  • The Unrealized Billing report
  • The Summary by Bank report
  • And the Program Rate of Attrition report

These flexible load balancing options are extremely helpful for our customers who have several merchant banks that they are working with.

What is PCI DSS compliance?

PCI DSS stands for Payment Card Industry Data Security Standard (PCI DSS). It is a proprietary information security standard for business organizations who handle cardholder information for the major credit cards whether they are: prepaid, debit, POS or credit cards. The purpose of this standard is to reduce credit fraud by creating some strong, consistent controls around the cardholder’s data.

There are four levels of PCI compliance. Merchants typically fall into one of the four levels of PCI that are based on their transaction volumes during a 12 month review by a credit card company. Click on the image below for the four tiers of PCI compliance on Visa’s web site.

Merchant levels and compliance validation requirements defined

Would you like to find out more information about PCI Data Security Standards? Go to the PCI SSC’s Website at:

© 2018 OrangeCRM Blog

Theme by Anders NorénUp ↑