Counterpoint allows you to use NCR Secure Pay and CPGateway at different stores simultaneously. However, because encrypted card numbers are not stored in the Counterpoint database for stores that are using NCR Secure Pay, stores that are configured to use CPGateway cannot access payment data for transactions that originated in NCR Secure Pay stores.
This limitation imposes certain restrictions on how NCR Secure Pay stores and CPGateway stores can interact. Specifically, you cannot perform the following actions at a store that is configured to use CPGateway:
Automatically process a validated return for a ticket with a credit card payment that originated at an NCR Secure Pay store.
To complete a validated return
at a CPGateway store for a sale that originated at an NCR Secure Pay store,
you must re-swipe the original card or manually enter payment information
for the refund.
Release an order or layaway for which final payment was specified at an NCR Secure Pay store.
Automatically accept a deposit for an order or layaway using the account for which final payment was specified at an NCR Secure Pay store.
You can accept a deposit for
an order or layaway by re-swiping the original card or manually entering
payment information for the deposit.
Use the Credit card # on file for a customer record that was created at an NCR Secure Pay store.
Payment data for transactions
that originated at a CPGateway store can be accessed at NCR Secure Pay
stores that share the same company database, so these restrictions do
not apply to tickets, orders, or layaways created at stores using CPGateway.