Dynamics AX Credit Card Processing Alternatives 2017

Need a solution to process credit cards for Microsoft Dynamics AX 2012? Whether replacing Microsoft Dynamics ERP Payment Services due to end of life announcement, or looking for an alternative to Red Maple Advanced Credit Cards, Christine Speedy has a solution to delight your customers and make your business more profitable virtually overnight. It’s wrong to thing big name gateways are compliant with your B2B payment processing needs. If that were true, our solutions would not exist.

Dynamics AX Credit Card Processing Critical Features Checklist:

  • Customer managed wallet from the very first sale, including before payment is needed. Must eliminate need for paper or digital credit card authorization forms with card data in the clear!
  • No 3rd party applications needed to get paid from invoice; automate journal entry updates. (Eliminate BillTrust and similar.)
  • Communicate the way your customers want, both text and email.
  • Automate rate qualification. A payment gateway with Level 3 processing is not enough; merchants can only qualify for level 3 (corporate, purchasing, business card) interchange rates if all the rules are met. The two most common rules B2B businesses struggle with are “Settlement within 72 hours” for card not present sales, and “Authorization amount and settlement amount must be equal”. CenPOS automates compliance, most gateways cannot.

    interchange rate qualification

    The same transaction can process at different rates, depending on which rules you follow.

  • Compliance with Visa Stored Credential Transaction framework and mandates effective October 14, 2017. Merchants need record of customers opt-in to storing and use of the stored card terms and conditions, among other items. For example, a checkbox. There are many nuances including identifying merchant initiated vs customer initiated. CenPOS automates compliance, most gateways cannot.
  • 3-D Secure cardholder authentication- increase approvals, shift fraud liability risk, and for some card types qualify for reduced interchange rates.
  • Virtual Encrypted Keypad – segment your network, software and devices from payment processing for reduced PCI Compliance scope and burden.
  • Accept payments wherever you need in AX- free text, sales orders, payment journals and more.

Improve Efficiencies, Cash Flow, Customer Experience:

  • Invoice delivery via text and email
  • 2-clicks to pay for repeat customers
  • Customer managed wallet for payment methods.
  • Invoice portal – on demand access 24/7 to view and pay invoices
  • Automated collections reminders to pay

AX Solution for all payment types:

  • ACH and check, with and without guarantee.
  • Wire- eliminate inefficiencies matching deposits to invoices and returning unidentified wires.
  • Credit card
  • Paypal and more

Depending on your current AX set up, businesses can be live in less than 2 days.

Christine Speedy, CenPOS authorized reseller, 954-942-0483. B2B cloud payments solutions and CenPOS enterprise cloud payment solutions expert. CenPOS is a merchant-centric, end-to-end payments engine that drives enterprise-class solutions for businesses, saving them time and money, while improving their customer engagement. CenPOS secure, cloud-based solution optimizes acceptance for all payment types across multiple channels without disrupting the merchant’s banking relationships.

First Data level 3 processing solutions

Need a solution for level 3 processing with your First Data merchant account? A payment gateway that supports level 3 processing is required, but that’s not enough. Payment gateway selection and implementation impact whether a transaction actually qualifies for level 3 rates.

The main requirements to qualify for level III interchange rates are:

  1. Submit required extra order detail. This varies by card brand; for example Ship to/from ZIP code, Destination country code,VA/ tax amount, invoice number, order reference number, Discount amount, Freight/shipping amount, Duty amount, Order date, unit of measure and more.
  2. Valid authorization. For example, the authorization and settlement amount must be the same.
  3. Interchange Rate Special Requirements, which may vary by card, industry etc. For example, here are requirements to qualify for MasterCard Data Rate III
    1. U.S. Merchant
    2. Applicable Electronic Authorization Data must be included and match Settlement Data
    3. Valid Banknet Reference Number and Banknet Date in valid date format MMDD
    4. Settlement within 2 days of transaction
    5. Level II & Level III Corporate Card data (Level II Data includes the entry of customer code, card acceptor type, tax ID and sales tax. Level III Data includes Level II data, line item detail, item description, item quantity, item unit of measure, extended item amount, product code, and debit or credit indicator.)
    6. Non-T&E MCC
    7. Card Acceptor Type and Tax ID must be provided

Visa Stored Credential Framework Impacts Authorization Validity

For business, corporate and purchasing card transactions to qualify for Level 3 interchange rates, a valid authorization is required. New rules change requirements for card not present transactions using stored cards. US businesses must comply with Visa Stored Credential Transaction framework effective October 14, 2017. Without getting into too much detail, payment gateways must update to comply, and merchants will also need to make some changes going forward.

Merchant requirements include:

  • When capturing a stored credential for the first time, complete special requirements, including cardholder authentication as applicable (Managed by payment gateway or integrated solution.)
  • Send correct transaction type on subsequent transactions: Installment Payments, Recurring Payments, or Unscheduled Credential On File. (Managed by payment gateway or integrated solution.)
  • Authorization and settlement amount must match. (Managed by payment gateway or integrated solution.)
  • Obtain cardholder consent and disclosure agreement. (Most likely managed by payment gateway or merchant.)

For years, authorization and settlement amount mismatch has been a common problem for merchants to qualify for level III rates. Even if a gateway solves this problem, an integration may limit the capability. This is easily identified by EIRF, STD/ standard, level I and level II rates present in the “pending interchange” section on merchant statements.

To solve all of the above problems, merchants can use a third party payment gateway with their merchant account, that manages authorization validity and continual changes within the gateway, including integrated solutions. Below image shows before and after interchange rates from actual merchant statements; same merchant account, just changed the payment gateway.level 3 gatewayContact Christine for a level 3 payment gateway that works with your First Data Merchant Account, as well as other acquirers.

Christine Speedy, CenPOS authorized reseller, 954-942-0483 is based out of South Florida and NY. CenPOS is a merchant-centric, end-to-end payments engine that drives enterprise-class solutions for businesses, saving them time and money, while improving their customer engagement. CenPOS secure, cloud-based solution optimizes acceptance for all payment types across multiple channels without disrupting the merchant’s banking relationships.

Volusion for B2B? No way!

Volusion for B2B ecommerce shopping cart is unacceptable. B2B companies are going omnichannel, yet Volusion lacks critical tools distribution companies need to maximize profits, security, and efficiency.

  1. Payment gateways and level III data– Wholesalers average 30% premium in merchant fees because NO Volusion payment gateways help businesses properly qualify for level 3 interchange rates across ALL sales channels, from ecommerce to retail. They have continually ignored requests to support, instead adding dozens and dozens of ‘me too’  gateways that are pretty much all alike.
  2. Retail – B2B retailers need US EMV options that support their needs. Whether it’s signature capture terminals like the Verifone MX915, or mobile terminals. None of their gateways has ever supported level 3 processing for retail, and is there even an US EMV terminal with P2P encryption certified for any processor today that works with Volusion?
  3. Omnichannel flexibility and PCI Compliance – How many business to business companies have a sales force taking phone orders? What is Volusion doing to help secure that transaction and help prevent fraud? Not nearly enough.

Over the decade that I owned a Volusion B2B ecommerce store, I recommended them over and over again. So much that their product development reached out to me to ask if there was anything I needed. It’s been seven years and the one thing I wanted, a modern payment gateway that meets business to business needs, they still haven’t done, even though the work is minimal. Why not? Well I’m tired of waiting and if someone finds my positive reviews online, I want everyone to know, there are many compelling reasons why I do not recommend Volusion for B2B ecommerce.

Steps to Reduce Credit Card Fraud For Distribution Industry

dealer fraud credit card processingCredit card fraud is still rampant in the US, even after US EMV liability shift convinced many merchants to purchase terminals to support chip cards. Marine, auto, and other high value parts dealers have long had a problem mitigating fraud risk with local and international parts.

  1. For card not present orders, require self-pay with cardholder authentication. Taking cards over the phone, and or requiring a credit card authorization form, will not protect against all forms of counterfeit card fraud. However, consumer authentication shifts liability back to the issuer; the issuer guarantees payment, and because it’s lower risk, dealers can qualify for lower interchange rates, the bulk of merchant fees. Online payment, ecommerce payment, and electronic bill presentment and payment are the 3 methods dealers can use to enable self-payment.
  2. For retail orders, EMV is mandatory. Not by regulation, but by necessity. If a chip card is presented, and merchant supports, they’re 100% protected from counterfeit card fraud, and sometimes lost or stolen cards; if not supported by the merchant, the merchant can be automatically charged back at the issuers discretion and there’s no dispute process for merchants.
  3. Check guarantee. Whether in person or via echeck, check guarantee services are only good if they don’t reject your checks later on. Surprisingly (or maybe not), some services seem to look for ways not to approve your claim, such as information is missing from checks. This can be avoided with technology that forces users to collect the right data, including for remote self-payers.

If all of the above are implemented, dealers are protected from virtually any type of credit card fraud. The following tips will help prevent other types of lost disputes, or serve as supporting documentation if not all the above are implemented.

  1. Get a signed sales order. This can reduce non-fraud claims related to disputes about what was expected. The sales order should clearly state what was sold, refund policy, and cancellation policy, or refer to another document that specifies the information, but is initialed acceptance on the sales order.
  2. Ship to cardholder billing address. If not possible, then get cardholder approval that states bill to and ship to address are different, and they’re approval.
  3. Require all communications to cardholder business email address if selling wholesale. Free email like gmail is not OK.
  4. Require cardholder respond from business email address approving transaction receipt. This is a strong document in the case of a dispute for “I didn’t approve it”, especially when a third party is picking up the part from the dealer.
  5. The marine, automotive and other distribution companies are hit particularly hard with non-qualified transaction penalties when shifting between retail, key entered, and online payments. It’s critical that transactions are presented properly not only to qualify for lower rates, but to protect against lost disputes that require specific evidence for each type of transaction.

Not related to security, but critical for interchange rate qualification, the bulk of credit card processing fees, all services (retail, MOTO, ecommerce) should support level III processing.

In summary, dealers need US EMV and cardholder authentication to maximize risk mitigation from credit card fraud. US EMV requires terminal certification, and gateway certification* to your merchant account provider. Cardholder authentication requires a payment gateway certified for the service.  There are very few companies that meet all these requirements so if your credit card processing salesperson gives you a blank stare when you ask, it’s time to explore other options.

*A payment gateway certified for level III retail to your acquirer is required; countertop terminals are incapable of sending level III data.

Magento B2B Payment Gateway Developer Selection – CenPOS vs Authorize.net vs

Which is the best payment gateway for Magento developers B2B clients?

The answer lies in Magento top user concerns, which are security & PCI Compliance, cost, customer experience and flexibility with other systems including ERP and accounting.

Security and PCI Compliance: PCI should be a non-issue as any payment gateway being suggested for a B2B company should be level 1 PCI Compliant. However, developers can help merchants reduce PCI Compliance burden by partnering with a B2B payment gateway specialist who can recommend payment gateway solutions compatible with all business needs, not just Magento. For example, does the business also send invoices from an ERP? Do salesmen or credit managers get credit card numbers via fax or phone? Magento developers are not experts in payments and cannot be expected to ask the right questions to help solve unrelated compliance problems.

Internal and external fraud protection are critical. At a minimum, the payment gateway must support 3-D Secure, including Verified by Visa and MasterCard SecureCode to shift liability for certain types of fraud from merchant to card issuer.

Payment Gateway Cost: The worst mistake is recommending or selection a payment gateway based on per transaction cost. The payment gateway plays a critical role in interchange rate qualification, which comprises over 95% of merchant fees. Gateway capabilities, and lack thereof, can literally double the cost of credit card acceptance for B2B. The most important base criteria is it must support Level 3 processing. There are many nuances to qualifying transactions correctly, that most credit card processor salesmen don’t understand, so there’s little expectation a developer would have the global financial expertise to recommend the best choice.

Treasury Management: Where are your customers? Where are your offices? What currency do you want to collect and bill in? Authorize.net has virtually nothing to help manage cross-border sales. CenPOS has a multitude of treasury solutions that can be customized.

For example, a company bills everything from the US, but also has operations in Canada and the European Union. Authorize.net will process every transaction in USD. The company pays cross-border fees on foreign issued cards, which now exceed 1% in some cases, and then pays again to repatriate revenue back to the EU or Canadian operations. CenPOS automatically identifies and processes the transaction in the local issuer currency, avoiding costly cross-border fees and more expensive US interchange rates, and deposits in the regional account. It does this seamlessly with no special developer programming.

Customer Experience: Will the gateway enhance or detract? In most cases, there’s very little difference in the checkout experience, but for B2B, there’s a bigger picture. What if the customer buys via multiple channels? Sharing tokens across multiple channels, including for emailed invoices may be important. A holistic look at all sales channels and payment methods is essential, but it’s not a good use of a developers time, thus deferring to payment expert will yield a better ROI for developer and better result for the business.

Flexibility: Payment acceptance types, global availability, omnichannel integrations, flexibility and scalability are all factors in choosing not only the best B2B payment gateway for Magento, but also for the entire organization. For example, if there’s also a retail component, US businesses also need an EMV solution that supports level 3 processing for retail. If the distributor is global, how many countries is the gateway available in?

Back Office Efficiency: If you’ve ever done research in Authorize.net reports, and then in CenPOS, you’ll appreciate the massive difference between download and search vs dynamic drill down within CenPOS online reports. CenPOS reports were designed with input from today’s businesses, not those of over a decade ago. Too many differences to mention here.

There’s a plethora of misinformation across multiple industries ranging from consultants to developers. Defaulting to Authorize.net or Payflow Pro because they’re two of the oldest payment gateways, is an injustice to the end user. Payment gateway selection plays a crucial role in business profits, security and efficiency. By partnering with a payments expert, clients are provided the best solution, and Magento developers can grow revenues with specialty implementation and add-on services the expert recommends.  

“I have some knowledge of Magento, including as a developer in it’s early years, but I’m not a Magento expert,” says Christine Speedy, owner of 3D Merchant Services and B2B payment gateway expert. “Likewise, there are great B2B Magento developers, that are not payment gateway experts. By partnering, we can offer businesses more appropriate solutions to maximize profits and security, while also mutually benefiting. “