Newest KB Articles in Credit Cards

Payrix Integration

Fri, 25 Aug 2017 20:07:44 GMT

Announcing Payrix Integration with new low flat processing rates!

We are excited to announce that CMS has now completed it's integration with Payrix and will be passing along the low flat rates savings to you!

Payrix processing is available whether you're using CMS Classic (desktop) or CMS Cloud,

With this new integration, there are...

No Monthly fees.
No Regulatory fees.
No PCI Compliance fees.
No Gateway fees.
No Non-compliance fees.
No Annual fees.
No Hidden fees.

There really is no catch.

Credit Cards: Just a simple fixed rate of 2.92% and .20/transaction
eCheck is just 1.02% and .30/transaction.

Even if you are already using the CC module, you can now add additional accounts with no fees and with the new low rates.

CMS Classic Users

To get started, please make sure that you are running CMS version 20.3.25 or later.

Setup of your Payrix account is instant and completely automated. It can be done by you, you alone in just 2 minutes.
Click Program Setup > Options > Credit Cards. Then click Add and choose Yes to create your Payrix account.

CMS Cloud Users
Please create a support ticket requesting Payrix Integration.

CCPI Module Features:

Instantly charge cards directly in CMS.
Create multiple no-fee accounts to direct different projects charges to be funded to their own bank account.
Schedule cards to be charged on a recurring basis (monthly pledges or tuition).
Same with eCheck (ACH). One time charges or recurring.
Setup special forms on your website that automatically charge the card and auto-enter the data into your CMS.

If you have any questions, please email us at support@chabadms.com.

The fine print

Account Setup $18. This includes the account setup and banking verification.
Next Day funding is $1.25. 2 day funding is $0.25.
There are a few exceptions to the 2.92% flat rate for high risk amounts. >=$3000 for Amex is +.55%, and $7,500 for Visa/MC/Discover is +.35%
At this time, Payrix is only available for merchants in the USA. International cards for merchants in the USA are of course accepted. If you are located outside the US but have a US Tax ID number and bank account, you can use this feature.

Fees are subject to change

Updated March 2023.

Authorize.net Advanced Fraud Protection Suite (AFPS)

Fri, 07 Oct 2016 00:14:37 GMT

Below we will cover the most important filters in AFPS that we believe will give you the most protection. These are the Transaction IP Velocity filter, the Amount filter, the Daily Velocity filter and the Hourly Velocity filter.

Login to your Authorize.net account and click Fraud Protection Suite. This can be found in the Tools menu on the left column, or in the center under Products & Services. The first time you use this, you may need to confirm your agreement to the terms and conditions.
There are various filters that you can enable and configure. The examples below are our recommendations only. Your needs may be different. You have the option to configure them as you choose.
1. Transaction IP Velocity filter
  Although credit card thieves have the ability to use different IP addresses, it is unlikely that they will use a different IP for each card number attempt. It's not worth their while. Enabling and configuring this filter should be all it takes to thwart their attempt to use your form to test their stolen credit cards.
  
  We recommend that this filter be enabled and set to allow a maximum of five (5) or maybe ten (10) transactions, but no more. (The screenshot below has it set to three (3). Be sure to set the Filter Action as "Decline the transaction."
  
  (It is not necessary to add your own IP address to the exclusion list, as in the screenshot above, because the CMS Program does not presently submit any IP address when processing cards. So this filter will not affect the CMS Program).
2. Amount filter
  Often, credit card thieves will use a very small amount ($1, or $0.01) to test the cards. Their rational is that they hope that if the card does go through, the card owner will not be bothered to report such a small charge. Setting a filter for the amount will further thwart their efforts. Setting an upper limit will also protect you from innocent errors where a person making a donation may forget to put in a period and you can end up charging the person $18,000 instead of $180.00 (!) -- and then have to deal with refunds and hope that the processor will refund you the fees...
3. Daily and Hourly Velocity filters
  If, for whatever reason, the first two filters did not stop the hackers (perhaps they are changing their IP addresses dynamically and using regular amounts), the Daily and Hourly Velocity filters add an additional layer of protection. You can set them to be above the highest number you would ever expect on a given hour/day. Keep in mind though, to remove these filters (temporarily) if your running a campaign (e.g. End of Year) where your hourly and daily velocity will be much higher than usual.
4. Regional IP Address Filter
  This filter allows you to block entire regions from being able to process to your account. For example, you can block Africa, Asia and South America. You can also go into each Region and specific which countries to allow or block. For example, for the Middle East, you can allow Israel and the "West Bank" but block the rest.

Note that in all filters, I chose to "Decline the transaction." If you were to chose "Authorize and hold for review," while it may disrupt the card thieves somewhat, you will still be charged Authorization fees.

Other filters that you may consider enabling are

Suspicious Transaction Filter
Enhanced AVS and CVV Handling Filters
And more...

In summary: We want to be able to charge cards online; it is convenient, efficient and makes running our organization smooth. At the same time, it is the responsibility of the merchant account owner (that would be you), to do all he can to prevent fraud on his site, if for no other reason than for his own protection.
Will hackers fine a way around these extensive and powerful filters? Perhaps. But if that happens we will take further action and implement additional protection.

Once Authorize.net's Fraud Protection is enabled and configured on your account, you can safely turn on (check) Instant Charge, otherwise, we recommend that you leave Instant Charge turned off (unchecked).

In CMS Connected, click Online Form Setup or click Form Designer on the CMS Connected Dashboard.

(If you are using an older version of the Form Designer, click the Previous Version at the top right. There you can select your form, click Edit and then enable or disable (check or uncheck) the Instant Charge feature (Credit Cards tab).

Credit Card Field Moved to Bottom of Payment Page

Thu, 07 Jan 2016 20:18:24 GMT

The Credit Card field has been moved to the bottom of the Payment window, just below the Organization field.

We recommend that you turn off the "Hide Details..." option so that you won't have to click the Show Details button in order to access the Credit Card field.
To do this, click Program Setup > Options > Invoice tab and un-check the "Hide Details for Bills/Payments" check box.

This change was implemented in preparation to the upcoming integration with Authorize.net's Customer Information Manager.

Multiple Merchant Accounts

Thu, 25 Nov 2010 16:57:29 GMT

It is possible to use more than one Merchant Account and Gateway with CMS. For example, you may have a separate merchant account for Hebrew School or Camp that deposits directly into the School/Camp bank account.

For assistance in the initial setup in creating your merchant account and adding it to CMS, please contact tech support.

It is imperative that you understand how the program directs credit card charges to the correct merchant account. This is done based on the Organization field in the Transaction.

To associate an Organization with a Merchant Account, click Program Setup > Custom List Setup > Organizations. For each Organization, select a Merchant Account.

Note: If your Merchant Account is not listed, please call tech support to add it.

When entering the payment or a bill (one time charge, or recurring), select the Organization (from the Organization field) that is associated with the Merchant Account you want the Charge to be directed to.

(If you don't see the Organization field in the Payment or Bill screen, click the Show Details button. You can have the Details shown by default by clicking Program Setup > Options > Invoices tab and uncheck the "Hide Details from Bills/Payments" check box.)

If no organization is selected in the Payment/Bill, the default merchant account, listed in Program Setup > Options > Credit Cards tab, will be used.

You can associate an organization with a Category.

Click Program Setup > Category Manager. Select a Category and click Modify. Choose the Default Organization.
By doing this, the Organization field is entered automatically after selecting a Category in the Payment/Bill screen or when scheduling a recurring pledge. You can still modify the Organization field after selecting the Category if need be.

Refund a Credit Card Payment

Mon, 29 Dec 2008 03:27:36 GMT

In order to refund a credit card charge made in CMS you will need to go to Authorize.net's website.

If the charge did not settle yet, you can VOID the charge (it will not appear on the donor's cc statement).
If it already settled, you need to post a credit.

After voiding/crediting the charge, you can delete the payment in CMS.

The following was taken from a Authorize.net Guide.
To issue a credit using the Virtual Terminal:

Log into the Merchant Interface.
Click Virtual Terminal in the Main Menu.
From among the choices displayed in the category Select Payment Method, select Refund a Credit Card or Refund a Bank Account.
Provide payment and customer information as required on the Virtual Terminal screen.
Provide the Customer’s Credit Card/Bank Account Information.

Credit Card Security

Thu, 11 Dec 2008 15:47:52 GMT

You should enable Security so that the credit cards you enter are more secure.

Click Tools > Security to set this up.

At minimum, you should assign write permission to the Default Group and create one user in the Default group. This will force your to log in with a user name and password when starting the program. If more than one user is using the program, you can create various groups with different permission levels. Each user will only have permission based on the group he or she is in. Only the users who are in a group with permission to the credit card domain will be able to view and charge cards.

Click here for more information on Form Level Security.

Be sure that your computer is secure. You have updated virus protection, a firewall spyware protection and have the latest updates and service packs for Windows.