Sends a sale transaction to the payment terminal. This is the most basic operation, in its simplest form you only need to send the amount and currency to the payment terminal for the transaction to start.

A sale operation which also returns a card token. Tokens keep your software out of PCI scope and can be used for tracking customer behavior ,keep a card on file as well as initiating recurring payments.

Returns a card token without withdrawing funds from the card. This functionality is useful for all kinds of custom scenarios, for example when a card needs to be kept on file but no funds should be charged.

A tokenize and modify operation allows you to start a financial operation for an initial amount, tokenize the card being dipped/tapped/swiped and modify the amount before the transaction is sent for processing. This feature allows you to bring your own loyalty engine and apply for example an instant discount at the point of sale for loyal customers.

A pre-auth initiates a pre-authorization operation to the card reader. It's used to verify that the account is valid and has sufficient funds to cover a pending transaction, without actually debiting the cardholder's account upfront.

This function returns the full PAN of the card being swiped, dipped or tapped. Only the PANs of whitelisted card ranges will be returned by the Handpoint systems. This operation is most often used to be able to process funds or points from loyalty cards.

Sends a refund operation to the payment terminal. This transaction type moves funds from the merchant account to the cardholder´s card. In its simplest form you only need to send the amount and currency to the payment terminal for the transaction to start.

A reversal operation allows the merchant to reverse a previous sale or refund operation. A reversal is different from a refund, it does not require a card to be inserted and can only be completed until the acquirer settles the batch of transactions at night.

MOTO (Mail Order / Telephone Order) also called manual card entry is a type of transaction used by merchants to get services paid via telephone, mail, fax, or internet communication. Triggering this function will prompt a card input form on the terminal for the merchant to enter the card number, expiry date and CVV of the card to be charged.

Several terminals provided by Handpoint have an integrated printer which can be used to print any HTML formatted receipt, including printing images, bitmaps or barcodes. The printer can also be used prior to taking a payment, for example it can be used to print the itemized receipt provided by your software.

This function allows the merchant to stop a transaction after it was sent to the payment terminal. This is very useful in case the amount to be charged is incorrect and the merchant needs to send another transaction request to the card reader.

This operation allows your software to fund separate merchant accounts from a single terminal. It is particularly useful if a terminal is shared between multiple merchants, for example at an Hair Salon or a Doctor's office.

With on-reader tipping, you can display suggested tip amounts on the reader before the customer presents their payment method. The reader shows the customer suggestions based on the tipping option that you set up.

Pin bypass can be enabled to allow disabled or visually impaired cardholders to skip the PIN entry step. Signature bypass can be enabled to prevent the terminal from asking the cardholder to sign on the digital screen.

The payment application can be set in kiosk mode to prevent navigation between the different menus of the terminal. In order to get out of kiosk mode a password is required from the merchant. This merchant password is defined during onboarding the first time the payment application is launched.

The payment terminal can automatically print merchant and/or customer receipts by changing a configuration parameter in the settings of the application. With this easy solution you can rely on Handpoint to print receipts instead of integrating to the print receipt function.

For some types of merchants (e.g gambling categories) it is important to only be able to accept debit cards. Therefore, Handpoint offers to their partners the possibility to filter and decline specific card types based on custom rules.

Android based terminals allow you to remotely log into the terminals to help troubleshoot any issues that may arise on merchant location. From fetching logs remotely to taking full control over the terminal we give you tools to make the merchant experience as smooth as possible.

Software updates can be pushed automatically to the payment terminals. If you are using the Handpoint payment application or building your own application on top of the Handpoint Android SDK you can easily manage distribution of new updates to payment terminals in the field.

Payment terminals are secure devices and it is required to inject the terminal with an encryption key to protect the card number and PIN during a transaction. Most terminal distributors inject keys manually via cable before shipping devices to the merchant. With the Handpoint solution the encryption key can be downloaded over the air which improves the overall setup experience.

A transaction report can be printed with the list of transactions that happened during a specific period. The report shows the transaction split by card brands and transaction types (sales, refunds and reversals).

The Handpoint payment application and SDK messages are available in multiple languages. Thanks to the Handpoint modular architecture it is also very easy to add a new language if currently not supported by simply translating a couple of files.