Skip to main content

Release Notes

tip

Don't miss any updates on our latest releases. Contact your Handpoint relationship manager to subscribe to the Handpoint Newsletter!

Select your integration path to see the relevant changelog. Selecting a path here also filters all code examples across the docs.

REST API​

Cloud Integration — your server sends HTTP requests to Handpoint Cloud, which relays payment commands to the PAX terminal

Your server connects to a PAX SmartPOS terminal through the Handpoint Cloud — no Android development required. Send an HTTP request to start a transaction; receive the result in real time.

2.30.0​

Features:

Added Address Verification Service (AVS) support for MOTO and card-present transactions.

  • moToSaleRequest now accepts a billing object containing zipCode (required) and address (optional) fields. Providing a billing object triggers an AVS check on the acquirer.
  • transactionRequest (card-present Sale / Keyed Entry) also accepts the same billing object for AVS on card-present transactions.

AVS must be enabled on the merchant's acquirer agreement. The billing object is optional; omit it for transactions where AVS is not required.

info

The AVS result code is currently returned on the Android SDK TransactionResult.addressVerification field (SDK 7.1014.0+) for direct MoTo operations. Support for the AVS result in the Cloud API poll response (GET /transaction-result) is planned for a future release.

2.29.0​

Features:

New NoTransactionToCancel error (error code 1005) is now returned from POST /transactions when a stopCurrentTransaction operation is attempted but there is no transaction currently in progress to cancel. Previously this case was reported as the generic CancelOperationNotAllowed error (1003).

2.27.0​

Features

New endpoints for Pre-Authorization operations that do not require the card to be present, allowing Pre-Auth Increase/Decrease and Capture to be performed server-side without routing through the payment terminal:

  • POST /preauthorization/increase — increase or decrease a pre-authorization hold amount.
  • POST /preauthorization/capture — capture a pre-authorization without a terminal.

2.26.0​

Features:

New Deferred Tokenization Endpoint is now available, allowing a deferred tokenization on the following operations: sale, refund, preAuthorizationCapture, moToSale and moToRefund. This ensures that if a SaleAndTokenize operation fails due to issues with the token provider, the integrator can choose to de-couple these operations into 2, allowing authorizations to be processed and tokenizing using the transactionId (guid) of the original operation later on.

2.25.0​

Features:

New MOTO Operations (no reader) endpoints are now available, allowing MOTO (Mail Order / Telephone Order) transactions to be processed without a payment reader, using a card token retrieved from the gateway:

  • POST /moto/sale — performs a MOTO sale using a previously generated card token.
  • POST /moto/refund — performs a refund of a previous operation using its original identifier.
  • POST /moto/reversal — performs a reversal (void) of a previous operation using its original identifier. Deprecated in favor of POST /reversal — use POST /reversal instead, which works for all transaction types (card-present, MOTO, pre-auth) with no additional requirements.

New Batch Operations endpoints are now available, allowing you to remotely manage batches on a specific payment terminal using the Cloud API:

  • POST /batch/close — requests the closure of a batch for a given terminal and batch number.
  • POST /batch/summary — retrieves a summary of a batch for a given terminal and batch number.
  • POST /batch/detail — retrieves the full detail of a batch, including a list of transactions.
info

Batch Operations are currently in Beta and are not available for all acquirers. Contact your Handpoint relationship manager to find out if this feature is supported for your acquirer.

2.23.1​

Features:

The batch number is returned in the Transaction Result object now as batchNumber, provided the acquirer returns it.

2.23.0​

Bug fixes:

Support for MOTO operations in the Get Transaction Status service has been added.

2.22.4​

Bug fixes:

Internal performance issues have been solved.

2.22.3​

Bug fixes:

An external vulnerability has been addressed.

2.22.2​

Features:

A new cardPresent parameter is available under Optional Transaction Parameters. Used for Elavon card-present reversals.

2.20.0​

Features:

  • Added a selector to the /{transactionReference}/status endpoint which improves greatly on reporting.
  • Added "commands" to allow greater device control options.
  • A new tokenize parameter is available under Optional Transaction Parameters.

2.17.0​

Features:

Mastercard MoneySend fields for money remittance merchants. Supported operations: Sale, Sale & Tokenize, Refund, Linked Refunds, Reversals, MoTo Sale, MoTo Refund.

2.15.0​

Features:

New transaction type: Pre-Authorization. A pre-authorization charge is a temporary hold placed on a customer's payment card. A pre-authorized transaction can be increased (Pre-Auth Increase), captured (Pre-Auth Capture), or fully released (Pre-Auth Reversal).

2.14.0​

Features:

New Get Transaction Status endpoint. Query the Handpoint Gateway for the status of a transaction at any given time using the transactionReference provided at the start of a financial operation.