Configuring NCR Secure Pay in Counterpoint, for NCR Retail Online only
Configuring NCR Secure Pay in NCR Counterpoint likely will require the assistance of your NCR Counterpoint partner. This article will attempt to guide you through the highlights of configuring NCR Secure Pay in NCR Counterpoint. However, if you aren't able to complete any of the NCR Counterpoint specific tasks outlined in this article, you'll need to contact your NCR Counterpoint partner for assistance.
Prerequisites for Implementing NCR Secure Pay within Counterpoint
This article assumes you've already completed the task of obtaining an ecommerce credit card processing account through your bank. If this step has not been completed, please review our "NCR Secure Pay Setup
" article. You will not be able to implement NCR Secure Pay in NCR Counterpoint, without first completing that step.
Prerequisite 2: Another important aspect of configuring NCR Secure Pay in Counterpoint is that a separate store, station and drawer has been set up for ecommerce. If you do not have a separate store, station and drawer configured for ecommerce, you'll need to contact your NCR Counterpoint partner to set that up. The Counterpoint partner should also make sure the store being used for ecommerce has the appropriate credit card pay codes available for use. Additionally, it's assumed there are NO open orders in the store being used for ecommerce for tickets or orders that did not originate online. If there are open documents that must process payment by means of CPGateway, those transactions will need to be closed out before NCR Secure Pay can be implemented in the store being used for ecommerce.
This article assumes you've already placed some test orders in your NRO storefront and have already successfully imported those orders into Counterpoint. If this step has not been completed, please review our "Testing Your NRO Store
" and our "Processing NRO Orders
" articles linked within our "Getting Started Overview
Implementing NCR Secure Pay in NCR Counterpoint
Step 1: Obtain the NCR Secure Pay Login ID and the NCR Secure Pay POS password.
Step 2: In NCR Counterpoint, go to Setup > Point of Sale > Stores. Open the store being used for ecommerce. NOTE: If you do not have access to this menu, you'll need to speak with your store administrator or your NCR Counterpoint partner.
Step 3: On the Credit Cards tab of the ecommerce store, select NCR Secure Pay as the payment gateway. In the Merchant Number field, enter the Merchant number provided by your credit card processor. *TIP: If you don't have that setup information handy, you can obtain the value by logging into your NCR Secure Pay portal and accessing the Settings link. Next, in the Secure Pay Merchant ID field, enter your NCR Secure Pay Login ID. Lastly, enter the NCR Secure Pay POS password. After all of this information is configured, click the "Test Connection" button.
If all of this was configured correctly, you'll see a success message.
If you get an error and you're absolutely certain the information is correct, there likely is a network configuration that is preventing your NCR Counterpoint system from connecting to your NCR Secure Pay account. If an error occurs, you'll need to contact your NCR Counterpoint partner for assistance.
Step 4: After confirming NCR Secure Pay is connecting to NCR Secure Pay, it's time to configure the credit card pay codes into the ecommerce control file. To do this, in Counterpoint, go to Setup > Ecommerce > Control. On the Payment tab, map the credit card pay codes for the payment methods that you accept. If you click on a lookup next to your credit card payments and nothing is in the box, your store being used for ecommerce likely does not have credit card pay code types allowed. You will need to contact your NCR Counterpoint partner for assistance with configuring credit card pay codes for your ecommerce store. After mapping the credit card pay codes, save your changes.
Enabling NCR Retail Online to send payment information to NCR Counterpoint
Retail Hosted Apps Support strongly encourages that a few test orders be placed in NCR Counterpoint to ensure that NCR Secure Pay is working properly. Once that is confirmed, you can enable NRO to send payment information to NCR Counterpoint. Keep in mind that NRO will NEVER send complete credit card numbers or CVV codes to NCR Counterpoint. NRO will send partial information simply for the purpose of verifying the last four digits of the payment method used to pay for an ecommerce order. Instead of the actual payment method, NRO will send the Transaction ID token information and that will be used to tie the payment to the order. This token will allow you to make order edits that change the total order amount and will authorize the correct amount to charge the customer. It will also allow you to perform a validated return to the payment method, if merchandise is returned by the customer.
Once NRO is enabled to send payment information to NCR Counterpoint, orders will import into NCR Counterpoint with pay codes, as opposed to coming in as cash transactions. When an order is sent to NCR Counterpoint with pay codes, every action against that order must be taken on the NCR Counterpoint side. For example, you will no longer create credit memos through the NRO admin panel for the purpose of returning money to the customer. You can certainly continue to create "offline" credit memos, but the purpose of the credit memo will be purely cosmetic. Instead, the Validated Return performed in NCR Counterpoint will return the money to the customer's payment method. Additionally, the Integration Agent will continue to go through the motions of invoicing and shipping orders and sending tracking information. But, invoices will be "captured offline" because the actual payment is captured in NCR Counterpoint. Basically, all that was learned from our "Processing Orders the Automated Way
" article is still true with one exception; no money is captured by the Integration Agent any longer. But, the information we provided in our training videos and in our addendum article, "Editing Orders That Originated In Your NRO Store
" still applies.
Step 1: Make a note of the last order sent to NCR Counterpoint that did not utilize pay codes. The reason you're doing this is to help you determine when NCR Counterpoint began capturing payment, should you have any older open NRO orders in NCR Counterpoint or should you need to issue a return against an NRO order sent to NCR Counterpoint before NCR Secure Pay was implemented in NCR Counterpoint.
Rest assured, you can still process refunds and payments on orders prior to this change. That's because the IA is smart enough to know for which orders credit card pay codes were sent. It knows which orders should still be processed the "old" way, in regards to refunds and payments.
If you can't remember where a payment was processed, there are tricks to figuring this out. In NRO, you can open the order details under Sales > Orders. The Comments History tab will provide the original TTID to you. After obtaining this TTID, you can use it to search for the transaction in the NCR Secure Pay portal. After finding the transaction, the Ticket Number will inform you where the payment was captured. If the payment was captured by NRO, the "ticket number" will reflect the NRO order number. If it was captured by Counterpoint, the ticket number will reflect the NCR Counterpoint ticket number.
Step 2: Now, it's time to enable pay codes be sent to NCR Counterpoint! To do this, in the NRO admin panel, go to System > Configuration > Sales Section > Payment Methods tab > NCR Secure Pay panel. For the setting, "Where should payments be captured?," set this to NCR Counterpoint. Now, click the Save Config button in the upper right portion of your screen.
That's it! Congratulations! You will now reap the many benefits of processing payments through NCR Counterpoint.
Article ID: 556
Created On: Wed, Jun 3, 2015 at 2:33 PM
Last Updated On: Wed, Sep 30, 2015 at 10:25 AM
Online URL: http://help.ncrretailonline.com/article/configuring-ncr-secure-pay-in-counterpoint-for-ncr-retail-online-only.html