Add key performance and processing advantages to your payment environment with this powerful web-service API. After a customer’s card is read, a transaction token is created to replace sensitive card data. The token is used throughout the rest of the payment process, enabling secondary transactions to be completed without the card being swiped a second time. Adjust tips or capture an authorization anytime before the batch is closed. Thanks to our direct in-house processor integration, we're able to serve numerous POS software and terminal combinations.
Accept payments at your retail store, restaurant, and more.
Any Payment Type
Accept various payment types including VISA, Mastercard, American Express, Discover, JCB, and Diners Club credit cards.
Any Payment Method
Accept credit, debit and EBT cards (keyed, swiped, tapped, or dipped), cash, and mobile wallets.
Easy Integration
Submit a request using the contact form and installation files will be sent to your email address.
EMV Pre-Certified
This payment system utilizes EMV pre-certified software. Your application communicates with the pre-certified software, which collects transaction and card data and passes it to North, keeping it out of your server environment.
Tokenized Transactions
Custom tokens allow you to link to transactions for voids, refunds, tip adjustments, and more. They help mitigate the risk and expense involved with storing sensitive card data.
1/5
Advanced Payment Functionality
Unlock a range of payment functions including tip adjustments, voids, batch settlements, create authorization codes in offline mode, and more.
Cardholder data typically only needs to be accessed one time. When the terminal initially reads the credit card information, a transaction token is created and used throughout the rest of the payment process. Any subsequent parts of the transaction are handled directly with our in-house processor using the token, meaning terminals will not access cardholder data again unless a new token is required — for example, if a different card will be used for payment or if a new check is started.
Subsequent transaction data can be passed directly to our in-house processor at any time prior to batch settlement. This means tips can be added and authorizations can be captured without cards being read more than once. To start a tab, simply read the card to authorize it and return it to the customer. When it’s time to finish the transaction, the customer can add a tip, and the tab can be closed without reading the card again.
Compatible with Oracle Payment Interface
Use with Oracle Payment Interface (OPI) specifications to communicate via OPI/SPI requests or use with a standard Swagger Consumable Interface to communicate via REST requests generated by third-party POS systems via JSON. Simply going to the Swagger endpoint started by the web service allows developers to begin processing CAEDC within hours.
Customizable for your Business Model
Our development team can quickly and easily add support for most terminal lines. With a terminal market that’s constantly evolving, you will never need to worry that your devices will become obsolete. The Hospitality POS API is consumed by our internal software, so its performance is constantly validated.
