Multiple Stores with NCR Secure Pay

NCR Secure Pay uses tokenized card numbers and reusable transaction IDs to track credit card transactions in NCR Counterpoint. However, each transaction ID can only be associated with the merchant account assigned to the store that originally created the transaction. This means that activity associated with a particular transaction will be applied to the store at which the original payment data was processed, as follows:

If you switch processors, you will be unable to release any order to which a deposit has been applied prior to the processor change. Make sure you release all pending orders with deposits before you configure NCR Secure Pay to use a different processor.

Accounting distributions for these transactions are created for the original store, which may result in apparent discrepancies between reports generated in NCR Counterpoint and your General Ledger. To reconcile these discrepancies, you should make corrective distributions for these transactions in your accounting software.

Further, card number tokens that are generated for NCR Secure Pay transactions processed in one store cannot be accessed by a different store. Thus, if you process a validated return for a sale that occurred at another store (i.e., a "cross-store" validated return), NCR Counterpoint cannot automatically refund the account associated with the original sale. You must re-swipe the original card or enter payment information manually to complete the refund.

Similarly, NCR Counterpoint cannot retrieve card number tokens for transactions that have not been settled, which means you must re-swipe the original card or enter payment information manually to complete a "same day" validated return at a single store.