triPOS Direct now automatically updates to the latest BIN File.
Updated EMV CAPK certificates to latest versions.
Added support for portable processing with Ingenico Move 5000 with printer (non-barcode) device. Supports WiFi and Bluetooth communications.
Removed the ability to install/configure Vx devices.
Added support for unattended processing with Verifone Ux300/Ux100/Ux400.
Enhanced processing of FSA/HSA to support EMV Contact/Contactless cards.
Enhanced Mx9xx family to support XPI5400L and OS1400. triPOS will automatically upload Mx devices to new software. Expect to leave device uninterrupted for 15-20 min. till device has completed upload.
Enhanced Ingenico Lane 3000/Lane 5000/Lane 7000/Link 2500 devices to support Display endpoint.
Enhanced Ingenico Lane 5000/Lane 7000 devices to support scrolling display.
Bug Fixes & Other Changes
Corrected signature status code to reflect correct value for Gift Sale and Gift Refund transactions for iUC285 devices.
Corrected issue that prevented loading a custom Idle image when Windows FIPS was enabled.
Corrected issue that was flagging “Empty response on read” error when obtaining a signature on Mx915/Mx925 devices.
Updated null lane test card used in LaneID 9999 for triPOS Direct and triPOS Cloud testing.
Enhanced logging for system reversals for Auth, Sale, Refund and Force Credit transactions.
Corrected issue for forwarding stored transactions to the wrong host.
Eliminated the flashing of triPOS logo when a technical fallback swipe is performed.
Deprecated Features
As of triPOS Direct v5.21, Verifone Vx805 and Verifone Vx690 support has been deprecated. Performance testing of the Verifone Vx805 and Vx690 devices has been discontinued due to manufacturer end of life notifications. Recommend remaining on older version of triPOS Direct to continue to use existing Vx805 and Vx690 devices, or upgrade to a new device model such as Ingenico Lane 3000.
As of triPOS Direct v6.0.0 the Ingenico iCMP device support has been deprecated.
As of triPOS Direct v6.0.0 the Windows 7 operating system family has been deprecated.
Supported Operating Systems
triPOS Direct Supported Operating Systems
Windows 8.1 Pro (32 and 64 bit)
Windows 8.1 Enterprise (32 and 64 bit)
Windows 10 Pro (32 and 64 bit)
Windows 10 Enterprise (32 and 64 bit)
Linux CentOS Rel 7 (32 bit)
NOTE: Any variation of the operating system edition name i.e. Windows 10 Pro Education or Windows 10 IoT Core, are not supported operating systems. If you have any questions regarding a supported operating system, please contact Developers Integration team.
EMV Certified Devices
Worldpay
EMV Contact/Contactless/Quickchip for Verifone Mx915, Mx925
EMV Contact/Contactless/Quickchip for Ingenico iSC250, iSC480, iPP320, iPP350, iSMP4, iUC285
EMV Contact/Contactless/Quickchip for Ingenico Tetra Lane 3000, Lane 5000, Lane 7000, Link 2500 devices.
Fiserv (formerly First Data)
EMV Contact for Verifone Mx915, Mx925
EMV Contact for Ingenico iSC250, iSC480, iPP320, iPP350, iSMP4
EMV Contact/Contactless/Quickchip for Ingenico Lane 3000, Lane 5000, Lane 7000, Link 2500, Move 5000 devices
Paymentech
EMV Contact for Verifone Mx915, Mx925
NEW EMV Contact for Verifone Mx915, Mx925
EMV Contact for Ingenico iSC250, iSC480, iPP320, iPP350, iSMP4
NEW EMV Contact/Contactless/QuickChip for Ingenico Lane 3000, Lane 5000, Lane 7000, Link 2500, Move 5000
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP, iSMP4) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
Verifone Mx9xx and Vx devices display a "CARD READ ERR" when a card containing only track 3 data is swiped. Transactions not canceled will time-out and return a PinPadException and "VerifoneXPI S20 timeout response" message. This issue is pending resolution from Verifone.
MasterCard contactless MSD for NFC Card and ApplePay issues on Mx devices
Back-to-back pre-reads are an invalid sequence.
Cashback is not supported for EMV Contactless transactions.
NOTE: Any variation of the operating system edition name i.e. Windows 10 Pro Education or Windows 10 IoT Core, are not supported operating systems. If you have any questions regarding a supported operating system, please contact Developers Integration team.
New Features & Improvements
triPOS Direct now automatically updates to the latest BIN File.
Updated EMV CAPK certificates to latest versions.
Added support for portable processing with Ingenico Move 5000 with printer (non-barcode) device. Supports WiFi and Bluetooth communications.
Removed the ability to install/configure Vx devices.
Added support for unattended processing with Verifone Ux300/Ux100/Ux400.
Enhanced processing of FSA/HSA to support EMV Contact/Contactless cards.
Enhanced Mx9xx family to support XPI5400L and OS1400. triPOS will automatically upload Mx devices to new software. Expect to leave device uninterrupted for 15-20 min. till device has completed upload.
Enhanced Ingenico Lane 3000/Lane 5000/Lane 7000/Link 2500 devices to support Display endpoint.
Enhanced Ingenico Lane 5000/Lane 7000 devices to support scrolling display.
Bug Fixes & Other Changes
Corrected signature status code to reflect correct value for Gift Sale and Gift Refund transactions for iUC285 devices.
Corrected issue that prevented loading a custom Idle image when Windows FIPS was enabled.
Corrected issue that was flagging “Empty response on read” error when obtaining a signature on Mx915/Mx925 devices.
Updated null lane test card used in LaneID 9999 for triPOS Direct and triPOS Cloud testing.
Enhanced logging for system reversals for Auth, Sale, Refund and Force Credit transactions.
Corrected issue for forwarding stored transactions to the wrong host.
Eliminated the flashing of triPOS logo when a technical fallback swipe is performed.
Deprecated Features
As of triPOS Direct v5.21, Verifone Vx805 and Verifone Vx690 support has been deprecated. Performance testing of the Verifone Vx805 and Vx690 devices has been discontinued due to manufacturer end of life notifications. Recommend remaining on older version of triPOS Direct to continue to use existing Vx805 and Vx690 devices, or upgrade to a new device model such as Ingenico Lane 3000.
As of triPOS Direct v6.0.0 the Ingenico iCMP device support has been deprecated.
As of triPOS Direct v6.0.0 the Windows 7 operating system family has been deprecated.
EMV Certified Devices
Worldpay
EMV Contact/Contactless/Quickchip for Verifone Mx915, Mx925
EMV Contact/Contactless/Quickchip for Ingenico iSC250, iSC480, iPP320, iPP350, iSMP4, iUC285
EMV Contact/Contactless/Quickchip for Ingenico Tetra Lane 3000, Lane 5000, Lane 7000, Link 2500 devices.
NEW EMV Contact/Contactless/QuickChip for Verifone Ux300, Ux400, Ux100.
NEW EMV Contact/Contactless/QuickChip for Ingenico Move 5000.
Fiserv (formerly First Data)
EMV Contact for Verifone Mx915, Mx925
EMV Contact for Ingenico iSC250, iSC480, iPP320, iPP350, iSMP4
NEW EMV Contactless/QuickChip for Verifone Mx915, Mx925 devices.
NEW EMV Contact/Contactless/Quickchip for Ingenico Lane 3000, Lane 5000, Lane 7000, Link 2500, Move 5000 devices
Paymentech
EMV Contact for Verifone Mx915, Mx925
EMV Contact for Ingenico iSC250, iSC480, iPP320, iPP350, iSMP4
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP, iSMP4) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
Verifone Mx9xx and Vx devices display a "CARD READ ERR" when a card containing only track 3 data is swiped. Transactions not canceled will time-out and return a PinPadException and "VerifoneXPI S20 timeout response" message. This issue is pending resolution from Verifone.
MasterCard contactless MSD for NFC Card and ApplePay issues on Mx devices
Back-to-back pre-reads are an invalid sequence.
Cashback is not supported for EMV Contactless transactions.
Ingenico devices sometime is showing the triPOS logo instead of the Idle message/logo set in triPOS.config file
NOTE: Any variation of the operating system edition name i.e. Windows 10 Pro Education or Windows 10 IoT Core, are not supported operating systems. If you have any questions regarding a supported operating system, please contact Developers Integration team.
New Features & Improvements
Includes BIN Table dated May 9th, 2021
Tetra devices now using 6.81.08 version of UPP.
Support for Lane 7000 devices on triPOS Direct.
Support for Pre-Read, Quickchip and EMV Contactless for Lane 7000 devices on Worldpay processor.
Support for ValuTec Gift card. triPOS supported gift transactions:
/api/v1/gift/activate, /api/v1/sale, /api/v1/gift/reload, /api/vi/balance, /api/v1/reversal/{transactionId}/gift, /api/v1/return/{transactionId}/gift, /api/v1/refund, /api/v1/gift/unload, /api/v1/gift/balanceTransfer, /api/v1/gift/close.
Support for ValuTec Loyalty. triPOS supported Loyalty transactions:
/api/v1/gift/activate, /api/v1/sale, /api/v1/gift/reload, /api/vi/balance, /api/v1/reversal/{transactionId}/gift, /api/v1/return/{transactionId}/gift, /api/v1/refund, /api/v1/gift/balanceTransfer, /api/v1/gift/close
Support for EMV Quickchip using standard flow, as opposed to using pre-read flow.
Support for automatically updating the BIN table from Worldpay weekly. This allows for triPOS Direct to automatically update the BIN file without any intervention by ISV/Merchant. – NOTE: Pre-requisite is that triPOS Cloud 2.2.0 and triPOS Cloud 2.3.1 are deployed in ACTUAL as they contain provisions to enable the BIN table microservice.
Support for Deferred Auth Indicator for Store and Forward transactions.
Support for P2PE OnGuard SDE encryption Tetra devices. Devices supported Lane 3000, Lane 5000, and Link 2500.
Enhanced the lane locking time when returnResponseBeforeCardRemoval flag is set.
Bug Fixes & Other Changes
Corrected issue that was preventing certain swiped Valutec gift cards.
Corrected issue where This Lane Closed was flashing on display when performing a Pre-Read swipe transaction.
Corrected issue where iUC285 was cancelling transaction and freezing the device when performing pre-read transactions.
Corrected issue where isCardInserted returned incorrect value FALSE, while card is still inserted.
Corrected issue where "Card Removed Transaction Cancelled" was incorrectly displayed after Remove Card screen.
Corrected issue where “Please Remove Card” prompt in a Mx device was timing out before 60 seconds standard timeout.
Enhanced Tip selection prompt to display Original Transaction Amount.
Corrected issue where TerminalID was missing from request message on /sale/token transaction. We now send TerminalID with request message.
Corrected issue that Card numbers were being truncated at 14 digits when manually entering on Link 2500 device. Now the device can display up to 16 digits.
Deprecated Features
As of triPOS Direct v5.21, Verifone Vx805 and Verifone Vx690 support has been deprecated. Performance testing of the Verifone Vx805 and Vx690 devices has been discontinued due to manufacturer end of life notifications. Recommend remaining on older version of triPOS Direct to continue to use existing Vx805 and Vx690 devices, or upgrade to a new device model such as Ingenico Lane 3000.
EMV Certified Devices
Worldpay
EMV Contact for Ingenico iCMP.
EMV Contact/Contactless/Quickchip for Verifone Mx915, Mx925
EMV Contact/Contactless/Quickchip for Ingenico iSC250, iSC480, iPP320, iPP350, iSMP4, iUC285
EMV Contact/Contactless/Quickchip for Ingenico Tetra Lane 3000 device.
EMV Contact/Contactless/Quickchip for Ingenico Tetra Link 2500 device.
EMV Contact/Contactless/Quickchip for Ingenico Tetra Lane 5000 device.
NEW EMV Contact/Contactless/Quickchip for Ingenico Lane 7000 devices.
Fiserv (formerly First Data)
EMV Contact for Verifone Mx915, Mx925.
EMV Contact for Ingenico iSC250, iSC480, iPP320, iPP350, iCMP, iSMP4.
Paymentech
EMV Contact for Verifone Mx915, Mx925
EMV Contact for Ingenico iSC250, iSC480, iPP320, iPP350, iCMP, iSMP4
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP, iSMP4) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
Verifone Mx9xx and Vx devices display a "CARD READ ERR" when a card containing only track 3 data is swiped. Transactions not canceled will time-out and return a PinPadException and "VerifoneXPI S20 timeout response" message. This issue is pending resolution from Verifone.
MasterCard contactless MSD for NFC Card and ApplePay issues on Mx devices
Back-to-back pre-reads are an invalid sequence.
Cashback is not supported for EMV Contactless transactions.
Ingenico devices sometime is showing the triPOS logo instead of the Idle message/logo set in triPOS.config file
NOTE: Any variation of the operating system edition name i.e. Windows 10 Pro Education or Windows 10 IoT Core, are not supported operating systems. If you have any questions regarding a supported operating system, please contact Developers Integration team.
New Features & Improvements
Includes BIN Table dated January 4, 2021.
Integrated the support for the Ingenico Tetra Lane 5000 device, certified for EMV Contact, EMV Contactless and Quickchip on the Worldpay processor. New Tetra devices require to set the driver to <driver>IngenicoUpp</driver> in triPOS.config. New Tetra device requires the same Ingenico USB driver used for Telium devices to be installed on the host PC. Telium/Tetra Ingenico USB driver is located at https://developer.vantiv.com/docs/DOC-2643
Support for EMV Contactless and QuickChip for iUC285 with RBA 23.02.46 certified on the Worldpay processor.
Ability to toggle on and off CVV security code support for triPOS Direct via transaction request for manually keyed transactions.
Sample Sale Request:
{
"laneId": "{{laneId}}",
"transactionAmount": "1.70", "IsCscSupported" : "true",
"configuration":{ "checkForDuplicateTransactions":"false", "allowPartialApprovals": "false"}
}
Bug Fixes & Other Changes
Corrected issue where “cashback amount not confirmed†was showing three times on the triPOS transaction response.
Corrected issue of prompting for Payment selection, even when the requested cashback amount is being sent in the transaction request on Verifone devices. Now we do not prompt for Payment selection.
Added support for EMV cards to Omnitoken, so it corrected issue for not prompting to “remove card†when using EMV card for Omnitoken transactions.
Corrected issue where triPOS was defaulting to logo in idle screen when Idle Image was set in the config file on Ingenico devices.
Corrected issue with creditSaleSignatureThresholdAmount where the threshold amount was not working properly.
Corrected issue for configuration parameters displaying NULL in configuration endpoints.
Corrected issue that was prompting for signature on a non-signature capable device Lane 3000.
Corrected typo in swagger documentation for AutoRental.
Corrected the http response when device is disconnected/pinpad is not found. We now display the response as http 200 instead of http 500.
Corrected connectivity issue that was reporting “This lane closed†on iPP320 and Lane 3000 devices.
Corrected issue where StoreCard gift manually keyed transactions were getting declined with "EncryptedCardData exceeds max length " response for Tetra devices.
Deprecated Features
In triPOS Direct v5.21, Verifone Vx805 and Verifone Vx690 support has been deprecated. Performance testing of the Verifone Vx805 and Vx690 devices has been discontinued due to manufacturer end of life notifications. Recommend remaining on older version of triPOS Direct to continue to use existing Vx805 and Vx690 devices, or upgrade to a new device model such as Ingenico Lane 3000.
EMV Certified Devices
Worldpay
Verifone Vx805*, Vx690* (*refer to Deprecated Features)
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP, iSMP4) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
Verifone Mx9xx and Vx devices display a "CARD READ ERR" when a card containing only track 3 data is swiped. Transactions not canceled will time-out and return a PinPadException and "VerifoneXPI S20 timeout response" message. This issue is pending resolution from Verifone.
MasterCard contactless MSD for NFC Card and ApplePay issues on Mx devices
Back-to-back pre-reads are an invalid sequence.
Cashback is not supported for EMV Contactless transactions.
Ingenico devices sometime is showing the triPOS logo instead of the Idle message/logo set in triPOS.config file
NOTE: Any variation of the operating system edition name i.e. Windows 10 Pro Education or Windows 10 IoT Core, are not supported operating systems. If you have any questions regarding a supported operating system, please contact Developers Integration team.
New Features & Improvements
Includes BIN Table dated October 4, 2020.
Added new parameter setting “GetToken†in the POS application transaction request so triPOS now can return an OmniToken on a response of a transaction from Express. Transactions impacted are: CreditCardSale, CreditCardAuthorization, CreditCardIncrementalAuthorization, CreditCardReversal, DebitCardSale and DebitCardReturn.
triPOS now can create OmniToken/PASS/Paymetric tokens from EMV Contact and EMV Contactless/eWallets.
Added new variable “returnResponseBeforeCardRemoval†in tripos.config file triPOS to send transaction response to POS application, before/while EMV card is prompted to be removed.
Integrated the support for the Ingenico Tetra Link 2500 device, certified for EMV Contact, EMV Contactless and Quickchip on the Worldpay processor. Link 2500 devices support Bluetooth and WiFi communication modes. Tetra Link 2500 device require to set the driver to IngenicoUpp in triPOS.config.
Bug Fixes & Other Changes
Corrected issue where “Confirm Amount†prompt was being presented before card read prompt when EMV contactless is enabled. “Confirm Amount†prompt now is presented after payment selection prompt.
Corrected “entryMode†to show “ContactIcc†when EMV transaction times out.
Corrected issue with error message when invokeManualEntry is set in transaction request for iUC285. triPOS now returns “Manual entry not supported for this deviceâ€.
Corrected USB communications issues for Mx915 devices.
Corrected issue for iUC285 device displaying "This Lane Closed" after overnight reboot. iUC285 now goes to Idle screen after overnight reboot.
Corrected issue of triPOS intermittently displaying triPOS logo before displaying Idle screen.
Deprecated Features
NEW Vx805 XPI 8.42B is no longer a supported device.
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 PIN pad. To avoid this failure, do not make a request to a Vx805 PIN pad until the PIN pad is fully configured.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP, iSMP4) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
Verifone Mx9xx and Vx devices display a "CARD READ ERR" when a card containing only track 3 data is swiped. Transactions not canceled will time-out and return a PinPadException and "VerifoneXPI S20 timeout response" message. This issue is pending resolution from Verifone.
MasterCard contactless MSD for NFC Card and ApplePay issues on Mx devices.
Back-to-back pre-reads are an invalid sequence.
“Vx805 devices with XPI 8.42b would not be able to support any contactless transactions. Please refer to https://developer.vantiv.com/docs/DOC-4459. This workaround has some limitations, it would work well for installations with ONLY Vx805 XPI 8.42b in this triPOS instance. If you require to combine Vx805 XPI 8.42 with MSD Contactless and Ingenico devices with EMV Contactless in the same triPOS instance, this would be an invalid configuration.
Cashback is not supported for EMV Contactless transactions.
Ingenico devices sometime is showing the triPOS logo instead of the Idle message/logo set in triPOS.config file.
StoreCard gift manually keyed transactions are getting declined with "EncryptedCardData exceeds max length " response for Tetra device.
NOTE: Any variation of the operating system edition name i.e. Windows 10 Pro Education or Windows 10 IoT Core, are not supported operating systems. If you have any questions regarding a supported operating system, please contact Developers Integration team.
New Features & Improvements
Includes BIN Table dated August 3, 2020.
For credit only endpoints as (Credit, Authorization, Force and Payment Account Create, Payment Account Update) when presented with a dual AID card, triPOS will not present the Credit vs Debit prompt, and will automatically select the credit AID. This same behavior also applies when using these credit only endpoints in Store And Forward mode.
If isDebitSupported parameter is set to FALSE in triPOS.config and a debit only card is presented, triPOS cancels the transaction and now also displays “Debit is Not Supported†on the PIN pad.
Integrated support for the Ingenico Tetra Lane 3000, certified for EMV contact, EMV contactless and quickchip on the Worldpay processor. New Tetra devices require the driver set to <driver>IngenicoUpp</driver> in triPOS.config. New Tetra device requires the same Ingenico USB driver used for Telium devices to be installed on the host PC. Telium/Tetra Ingenico USB driver is located at https://developer.vantiv.com/docs/DOC-2643
Bug Fixes & Other Changes
Corrected issue where the card read prompt was not showing contactless symbol when triPOS.config has Storecard credentials enabled.
Corrected issue to have triPOS validate credentials for all transaction requests. triPOS now returns “401 Unauthorized†with the error and with the exception message.
Corrected issue that was causing the PIN pad device to lock up for 2-5 minutes after a timeout occurred at the PIN entry prompt. Now triPOS displays transaction cancelled on display and returns a “statusCodeâ€: “Cancelled†in the transaction response and "VerifoneXPI Z62. response is cancelled. Cancelled by cardholder\r\n" in the processor logs the Mx device to the Idle screen after a PIN entry prompt times out.
Corrected issue where triPOS was processing an automatic reversal for a partial approval with an incorrect value for the amount.
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 PIN pad. To avoid this failure, do not make a request to a Vx805 PIN pad until the PIN pad is fully configured.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
Some numeric-only strings (e.g. "123") are reserved as prompt IDs in RBA/UPP and will not be displayed as raw text for the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP, iSMP4) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
Verifone Mx9xx and Vx devices display a "CARD READ ERR" when a card containing only track 3 data is swiped. Transactions not canceled will time-out and return a PinPadException and "VerifoneXPI S20 timeout response" message. This issue is pending resolution from Verifone.
MasterCard contactless MSD for NFC Card and ApplePay issues on Mx devices.
Back-to-back pre-reads are an invalid sequence.
“Vx805 devices with XPI 8.42b are not be able to support any contactless transactions. Please refer to https://developer.vantiv.com/docs/DOC-4459. This workaround has some limitations, it would work well for installations with ONLY Vx805 XPI 8.42b in this triPOS instance. If you require to combine Vx805 XPI 8.42 with MSD Contactless and Ingenico devices with EMV Contactless in the same triPOS instance, this would be an invalid configuration.
Cashback is not supported for EMV contactless transactions.
Ingenico devices sometime show triPOS logo instead of the idle message/logo set in triPOS.config file.
For token payment account create and payment account update transactions (Pass/Paymetric/Omnitoken) when prompting for card read on Mx9xx XPI 5400D devices, we display a contactless symbol, however contactless is not supported yet for Tokenization.
NOTE: Any variation of the operating system edition name i.e. Windows 10 Pro Education or Windows 10 IoT Core, are not supported operating systems. If you have any questions regarding a supported operating system, please contact Developers Integration team.
New Features & Improvements
Support for EMV Contactless and preread/Quick Chip transactions on Verifone Mx9xx family devices.
To enable/disable EMV Contactless, you set isContactlessEmvEntryAllowed and isEmvSupported flags to true
<isContactlessEmvEntryAllowed>true</isContactlessEmvEntryAllowed> will be true by default
<isEmvSupported>true</isEmvSupported> will be true by default.
Support for preread/QuickChip for swipe, contact and contactless transactions on Verifone Mx9xx family devices.
To enable/disable QuickChip you set the flag quickChip
<quickChip>false</quickChip> is set to false by default.
To configure the life (in seconds) of the pre-read data, you set it in the quickChipDataLifetime flag
<quickChipDataLifetime>30</quickChipDataLifetime> is set to 30 seconds by default.
When quickChip flag is set to true, the following must be done to successfully request preRead/QuickChip for a given transaction (Ex:/ sale). It entails a two (2) step request. 1st, the preRead request, followed immediately (before the life of the pre-read data expires) by the finalization (quickChip) request.
preRead true; this is a required field and must be set to true for pre-read
provisionalAmount; this is an optional field, is used to trigger CVM behavior (PIN/Signature, etc…) when above CVM limit for various card brands (Limits are in config file defined at startup). If this field is not specified, it defaults to $1.00.
Corrected issue for iUC285 Unattended that was locking up device when contactless card/wallet was presented to the iUC285 and the nonFinancialExpected flag was set
Corrected issue with Tip processing for percent tip options
Corrected issue of missing GUID in verbose logs
Corrected issue where pinpad was freezing after EMV Refund transaction and card was removed on Signature Capture prompt
Corrected issue for Receipt Printing endpoint to correct the laneId value set in the triPOS transaction response
Corrected issue to show the correct Signature StatusCode for Vx805 Devices
Corrected error received when MSD and EMV Contactless are set to false in triPOS.config file
Duplicate json/xml links are removed from metadata page
Corrected error on VX805 XPI 12.x where signature status code was being displayed as Unknown instead of SignatureRequiredNotSupportedByPinPad
Corrected error with requested Cashback option not working in Preread/QC sale
Corrected error where PIN pad does not return to Idle after Timeout on signature screen
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 PIN pad. To avoid this failure, do not make a request to a Vx805 PIN pad until the PIN pad is fully configured.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP, iSMP4) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
Verifone Mx9xx and Vx devices display a "CARD READ ERR" when a card containing only track 3 data is swiped. Transactions not canceled will time-out and return a PinPadException and "VerifoneXPI S20 timeout response" message. This issue is pending resolution from Verifone.
MasterCard contactless MSD for NFC Card and ApplePay issues on Mx devices
Back-to-back pre-reads are an invalid sequence.
Vx805 devices with XPI 8.42b would not be able to support any contactless transactions. Please refer to https://developer.vantiv.com/docs/DOC-4459. This workaround has some limitations, it would work well for installations with ONLY Vx805 XPI 8.42b in this triPOS instance. If you require to combine Vx805 XPI 8.42 with MSD Contactless and Ingenico devices with EMV Contactless in the same triPOS instance, this would be an invalid configuration.
NOTE: Any variation of the operating system edition name i.e. Windows 10 Pro Education or Windows 10 IoT Core, are not supported operating systems. If you have any questions regarding a supported operating system, please contact Developers Integration team.
New Features & Improvements
Support for EMV Contactless and Quick Chip transactions on Ingenico Telium family devices iSC250, iSC480, iPP320, iPP350 and iSMP4
To enable/disable EMV Contactless, you set “isContactlessEmvEntryAllowed†and isEmvSupported flags to true.
<isContactlessEmvEntryAllowed>true </isContactlessEmvEntryAllowed> will be true by default.
<isEmvSupported>true </isEmvSupported> will be true by default
Support for pre-read for swipe, contact and contactless transactions on Ingenico Telium family devices iSC250, iSC480, iPP320, iPP350 and iSMP4. Support for QuickChip (contact) transactions on Ingenico Telium family devices
To enable/disable QuickChip you set the flag “quickChip†<quickChip>false</quickChip> is set to false by default.
To configure the life (in seconds) of the pre-read data, you set it in the quickChipDataLifetime flag. <quickChipDataLifetime>30</quickChipDataLifetime> is set to 30 seconds by default.
When “quickChip†flag is set to true, the following must be done to successfully request preRead/QuickChip for a given transaction (Ex:/ sale). It entails a two (2) step request. 1st, the preRead request, followed immediately (before the life of the pre-read data expires) by the finalization (quickChip) request.
i) "preRead": true; this is a required field and must be set to true for pre-read.
ii) "provisionalAmount"; this is an optional field, is used to trigger CVM behavior (PIN/Signature, etc…) when above CVM limit for various card brands (Limits are in config file defined at startup). If this field is not specified, it defaults to $1.00.
Notice, the final transaction amount is specified in the 2nd step (QuickChip) and not in the 1st step (preRead).
Update Ingenico devices to RBA 23.0.44 for iSC250, iSC480, iPP320, iPP350 and iSMP4 with the exception of iUC285 device. The RBA 23.0.44 upgrade is to support EMV Contactless on Ingenico devices and the new iSMP4 hardware.
Enhance display to notify cardholder for a successful Gift Card read, displaying “Processing†instead of “Approvedâ€.
Updated signature status code values returned to “Unknown†for declined transaction and to “SignatureNotRequiredByUnattendedPINpad†for the Unattended iUC285 device.
Enhanced documentation related to Visa recurring payments.
Updated to latest BIN table dated Mar/9/2020.
Updated triPOS to load Ingenico devices to RBA 23.0.44.
Bug Fixes & Other Changes
Corrected issue that was allowing PIN bypass on Debit transactions.
Corrected empty currency code field in triPOS.config file.
Corrected issue that was allowing Fallback on Unattended merchants. No fallback would be allowed in Unattended.
Updated Tip Selection documentation to show the None/Other examples.
Corrected issue with contactless reads on iUC285 unattended devices.
Corrected issue in XML for namespace error.
Corrected issue for expired CAPK notification on Vx805 XPI 8.42b devices.
Corrected issue where “approvedAmount†displayed on device and in triPOS response to POS application was incorrectly calculated.
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 PIN pad. To avoid this failure, do not make a request to a Vx805 PIN pad until the PIN pad is fully configured.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP, iSMP4) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
Verifone Mx9xx and Vx devices display a "CARD READ ERR" when a card containing only track 3 data is swiped. Transactions not canceled will time-out and return a PinPadException and "VerifoneXPI S20 timeout response" message. This issue is pending resolution from Verifone.
MasterCard contactless MSD for NFC Card and ApplePay issues on Mx devices
Back-to-back pre-reads are an invalid sequence.
Vx805 devices with XPI 8.42b would not be able to support any contactless transactions. Please reach out to DI team to provide a workaround configuration for Rel 5.17 that will allow to support MSD Contactless on Vx805 XPI 8.42b equivalent to the Rel 5.16.1 supported MSD contactless. This workaround has some limitations, it would work well for installations with ONLY Vx805 XPI 8.42b in this triPOS instance. If you require to combine Vx805 XPI 8.42 with MSD Contactless and Ingenico devices with EMV Contactless in the same triPOS instance, this would be an invalid configuration.
UserInputTimeout is now configurable using request parameter "UserInputTimeout†for iUC285(Unattended) from minimum 10 sec to maximum 1 hr on Sale, Authorization and Refund endpoint.
triPOS Direct now supports Installation in Custom Directory.
EMV Support for iSC250 for TSYS.
triPOS will now allow "$0" tip in tipSelection.
triPOS will now send ticketNumber, ShiftId, ClerkNumber, MarketCode to Express via request.
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 PIN pad. To avoid this failure, do not make a request to a Vx805 PIN pad until the PIN pad is fully configured.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP, iSMP4) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
Verifone Mx9xx and Vx devices display a "CARD READ ERR" when a card containing only track 3 data is swiped. Transactions not canceled will time-out and return a PinPadException and "VerifoneXPI S20 timeout response" message. This issue is pending resolution from Verifone.
CXPI Vx690 devices may intermittently cancel a transaction. We are actively working with Verifone to identify the issue. Subsequent requests should behave as normal.
Payment Account creation using Manual entry fails for CXPI Vx690 devices.
Configurable CREDIT/DEBIT Prompts for Multi-AID EMV cards. This function can be enabled/disabled by isDisplayCustomAidScreen parameter in triPOS.config. On a new triPOS release 5.16 install, isDisplayCustomAidScreen defaults to TRUE in serial, IP and NULL Pinpad sample lanes. For upgrade installs, copy isDisplayCustomAidScreen parameter to each existing lane in triPOS.config and set to desired state.
Transaction flow progress indicator, GET /api/v1/status/lane/{laneId} has new values returned: PromptingForCardInput, PromptingToConfirmAmount, PromptingToConfirmCashBack, PromptingForCashBackAmount, PromptingToConfirmTipAmount, PromptingForPinEntry, PromptingFinishPreProcessing, PromptingProcessing, PromptingToRemoveCard that indicate what is being prompted on the Pinpad.
Support Visa Terminal Transaction Qualifiers (TTQ) for NFC read transactions (Contactless Cards, Apple Pay and Google Pay).
EBT Enhancements:
1. Populate BalanceAmount field when Express includes it in transaction response.
2. Add ability to define EBT Type in triPOS Sale request.
3. Add additional amount for Food Stamp benefit for EBT Sale transaction.
Enhanced Input Endpoint to support new promptType = idnumber to allow any numeric customer entry on Mx9xx and Ingenico devices. Use GET /api/v1/input endpoint. Please see Input Endpoint documentation for a list of prompts and formats currently supported for each device.
Updated triPOS Direct BIN file with latest Vantiv/Worldpay BIN file.
Tip Prompt now allows displaying Other and None on the same screen.
Enabled Credential on File functionality for Sale and Authorization transactions (initial transaction) in support of payment brand requirements.
Option to Display Amount during a Card Read on Ingenico devices, can be configured by displayTransactionAmount=True in the transaction request object.
Configurable display prompt timeout on iUC285 (Unattended), can be configured by userInputTimeout parameter in triPOS.Config.
Change to now send transaction response to POS App without waiting for cardholder to remove the EMV card on iUC285 for Unattended. In the past, we waited for card removal first, and then sent transaction response to POS App.
Updated triPOS application names to be “triPOS Cloud†and “triPOS Direct†to differentiate from which application is the transaction on Express Dashboard.
Bug Fixes & Other Changes
Corrected problem for No options for "Select Card Type" Mx USB device with Apple Pay and Google Pay.
Corrected EBT transaction routing issue for swiped/keyed Refunds and keyed Sales.
Reduced number of EMV tags returned on transaction response to POS App after EMV approval.
Resolved issue of Ingenico TCP/IP devices set to Static IP reverting back to DHCP during upgrade process.
Corrected issue where MasterCard PIN Bypass transactions were processing as Debit instead of Credit.
Corrected Contactless tap dynamic CVV issue for Apple Pay and Google Pay.
Corrected triPOS Gift Reload Response Class section of the POST /api/v1/gift/reload endpoint documentation misspelling, changed "ActivateGiftResponse" to "ReloadGiftResponse" (under Response Class).
Corrected misspelling in response value for “_type†in documentation, changed “relaodGiftResponse†to “reloadGiftResponseâ€.
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 PIN pad. To avoid this failure, do not make a request to a Vx805 PIN pad until the PIN pad is fully configured.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP, iSMP4) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
Verifone Mx9xx and Vx devices display a "CARD READ ERR" when a card containing only track 3 data is swiped. Transactions not canceled will time-out and return a PinPadException and "VerifoneXPI S20 timeout response" message. This issue is pending resolution from Verifone.
MasterCard contactless MSD for NFC Card and ApplePay issues on Mx devices.
Added support to process transactions using an EBT card (Food Stamp \ Cash Benefits). Please see EBT transactions for more details.
Added capability to configure the 24 hour reboot time for PIN pads. See PIN pad reboot for more info.
New POST /api/v1/reboot endpoint. Use this endpoint to reboot a specified PIN pad. See reboot documentation for more information.
Masked EasyPay code input for customer privacy.
Upgraded RBA versions for all Ingenico PIN pad models except iUC285 to 23.0.12.
Bug Fixes & Other Changes
Swiping non-standard cards, such as customer loyalty cards, no long result in a null reference exception being returned.
Fixed an issue with $0 Auth request in Store and Forward mode.
"Lane Closed" is now displayed on a PIN pad when it is replaced by another PIN pad on the same lane.
Ingenico PIN pads now display "Enter tip amount" instead of "Please enter new amount:" when prompting for tip entry.
Errors generated during one request no longer appear in the responses of other requests.
Firmware upgrades of Verifone Form Agent devices from the key injection facility (KIF) now complete successfully and no longer return a "VerifoneFA XDTX response len=0" exception.
"VerifoneFA failed to reboot" exception now longer occurs when upgrading a Verifone Form Agent PIN pad.
Ingenico iSC250s no longer sporadically "freeze" after the transaction is approved and prior to the signature prompt.
Ingenico iCM122, iPP320, iPP350, iSC250, iSC350, iSC480, and iSMP4 PIN pads now honor the canadaVisaDebitAllowed EMV config setting by accepting Canadian Visa debit cards when it is set to true.
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 PIN pad. To avoid this failure, do not make a request to a Vx805 PIN pad until the PIN pad is fully configured.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP, iSMP4) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
Verifone Mx9xx and Vx devices display a "CARD READ ERR" when a card containing only track 3 data is swiped. Transactions not canceled will time-out and return a PinPadException and "VerifoneXPI S20 timeout response" message. This issue is pending resolution from Verifone.
CXPI Vx690 devices may intermittently cancel a transaction. We are actively working with Verifone to identify the issue. Subsequent requests should behave as normal.
Payment Account creation using Manual entry fails for CXPI Vx690 devices.
Updated the Linux Mono installation script (mono_install.sh) to install the latest version of Mono (needed for TLS 1.2 support).
iUC285 devices support cancelling card input using the STOP button.
Updated triPOS installer to support TLS 1.2 in .NET framework.
Enhanced AutoRental transactions Sale, Auth Completion, Force, and OmniToken Sale to support AutoRentalDailyRentalRate, AutoRentalWeeklyRentalRate, AutoRentalInsuranceCharges data fields.
Updated triPOS BIN file with latest Vantiv BIN file.
Added support for non-barcode iSMP4 device.
Supports EMV recertification on First Data for Ingenico RBA 21.0.2 with EMV L2 Kernel rel 5.26.
Bug Fixes & Other Changes
Ingenico devices no longer become unresponsive if an EMV card is removed after the device has stopped beeping.
Removing an EMV card from Ingenico iUC285 devices the moment the screen turns green no longer causes triPOS to wait for card input for one minute.
Fixed a mapping exception on the GET /card/financial/{laneId} endpoint for devices running CXPI.
Initializing and ShuttingDown have been restored as possible values returned by the /api/v1/status/lane/{laneId} endpoint.
When an overnight reboot of an iUC285 occurs, triPOS now returns it to the idle screen instead of the "This Lane Closed" screen.
If a reboot of an Mx9xx device is required during a firmware upgrade, triPOS now picks up where it left off without needing to be restarted.
Fixed an issue in GET /api/v1/signature/{laneId}?form=contract where the PIN pad would display the signature screen for a split-second and then go to idle or reboot.
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 PIN pad. To avoid this failure, do not make a request to a Vx805 PIN pad until the PIN pad is fully configured.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP, iSMP4) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
Verifone Mx9xx and Vx devices display a "CARD READ ERR" when a card containing only track 3 data is swiped. Transactions not canceled will time-out and return a PinPadException and "VerifoneXPI S20 timeout response" message. This issue is pending resolution from Verifone.
CXPI Vx690 devices may intermittently cancel a transaction. We are actively working with Verifone to identify the issue. Subsequent requests should behave as normal.
Payment Account creation using Manual entry fails for CXPI Vx690 devices.
Added "smart initialization", which means devices may now be disconnected/connected, added/removed, and have their lanes changed without having to restart triPOS. Also, Idle messages may now be updated while triPOS is running. However, if it is done while triPOS is in the middle of obtaining card data, it will cause the card operation to fail.
Added important documentation regarding unattended devices and configuration for the iUC285.
Added support for the Vx690 CXPI OS 0500.
Removed card brand logos from the GET /api/v1/card/nonFinancial/ endpoint for CXPI Vx690 devices.
triPOS now supports the Scrolling Display feature (POST /api/v1/scrollingDisplay endpoint). See Scrolling Display documentation for more info.
Added support for the Ingenico RBA version 21.02. This update process takes a full 10-15 minutes to complete. Check the logs for information on the upgrade process and whether or not the initialization process is successful.
Added a Updating, Please Wait message when Ingenico devices are downloading newer RBA versions. Please note, the device will download additional forms but this message will display only for the RBA file which takes the longest.
Added ability to pass in requestedCashbackAmount in the request for Sale transactions. Note, this functionality requires that isCashbackAllowed is enabled in the triPOS.config.
Verifone Mx9xx devices are now able to accept PIN entry up to 12 digits.
Added isGiftSupported to the configuration request section for API requests.
Added isManualEntryAllowed to the configuration request section for API requests on the Sale, Authorization, and Refund endpoints only.
Added confirmOriginalAmount to the configuration request section for API requests.
Added invokeManualEntry, outside of the configuration request section, which allows the ability to skip the swipe screen and go directly to manual entry for card read endpoints.
Added displayTransactionAmount, outside of the configuration request section, which will display the transaction amount on the swipe screen for Verifone Mx9xx devices only.
Added support for the Ingenico iSMP4 device with Bluetooth and WiFi connectivity.
Bug Fixes & Other Changes
The /api/v1/status/lane/{laneId} endpoint has been repaired.
Fixed a bug where Verifone Mx9xx devices would enter a state of repeated initialization when updating the device's Form Agent, XPI and OS version. Devices containing Form Agent
versions of 3.0.4 or 4.3.5 will no longer trigger this initialization issue. Please note, once the device's OS has been updated you may need to restart triPOS to continue the upgrade
process.
Fixed an issue when pressing cancel on a PIN pad while on the Payment Type selection screen where the transaction continues on for processing.
Fixed an issue with the iUC285 when removing an EMV card on the Authorization screen caused the device to require a reboot.
Fixed a CXPI issue where manual entry was not working.
Fixed an issue where expiration months of 03 were not accepted on manual entry.
Fixed an issue where Mx9xx devices would not return to idle after a timeout.
Fixed an issue where Tip Options and/or Cashback Options would not display when confirmOriginalAmount was set to false.
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 PIN pad. To avoid this failure, do not make a request to a Vx805 PIN pad until the PIN pad is fully configured.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP, iSMP4) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for Verifone Mx9xx devices with triPOS running on Linux fails because the mono installation is missing a dependency.
Verifone Mx9xx and Vx devices display a "CARD READ ERR" when a card containing only track 3 data is swiped. Transactions not canceled will time-out and return a PinPadException and "VerifoneXPI S20 timeout response" message. This issue is pending resolution from Verifone.
CXPI Vx690 devices may intermittently cancel a transaction. We are actively working with Verifone to identify the issue. Subsequent requests should behave as normal.
If a TCPIP enabled Verifone Mx9xx device times out on the PIN entry screen, it is a known issue that the device will display an empty screen or remain on CANCELLED and then reinitialize within a minute. Subsequent requests will function as normal after reinitialization.
The below list of endpoints is temporarily not supported for any of the CXPI devices. If a request is sent to any of the listed endpoints and a card is swiped using a CXPI device, triPOS will return an error. Expected resolution for this issue is after our seasonal code freeze period.
POST /api/v1/paymentAccount
PUT /api/v1/paymentAccount/{paymentAccount}, only when updateCardData is true.
Added support for Verifone Vx805 and Vx690 devices that are loaded with the CXPI firmware. To use a Vx805/Vx690 that is loaded with the CXPI firmware, change the lanedriver type in the triPOS.config to VeriFoneCXpi. Vx805 devices loaded with regular XPI can still be used as normal. Please see CXPI Documentation for more details.
Added three new prompt types to the GET /api/v1/input endpoint. However, note that these new prompts are only supported on a Vx805 running CXPI. Please see the Input Endpoint documentation for a list of prompts and formats currently supported for each device.
Added the ability to support multi-line display using the POST /api/v1/display endpoint for Vx devices running CXPI. See Display Documentation for more details.
Added the ability to support multi-line prompts using the POST /api/v1/selection endpoint for Vx805 and Vx690 devices. See Selection Documentation for more details.
Added the storeCard field to the /api/v1/gift/activate /api/v1/balance /api/v1/refund /api/v1/return /api/v1/reversal /api/v1/sale endpoints to support the processing of StoreCard transactions.
AutoRental parameters are now supported on the following endpoints: POST api/v1/authorization, POST api/v1/authorization/{transactionId}/incremental, POST api/v1/authorization/{transactionId}/completion,
POST api/v1/sale, POST api/v1/authorization/force/credit, POST api/v1/sale/token, POST api/v1/authorization/token. AutoRental parameters should only be used in conjunction with the AutoRental market code.
Added the /api/v1/gift/reload endpoint. Please see the Gift Card Endpoint documentation for more information.
Added the /api/v1/barcode endpoint. Please see the Barcode Endpoint documentation for more information.
Added support for the Vx805 CXPI OS 0400 version which supports automatic ADE enablement.
Added the /api/v1/receipt endpoint. Please see the Receipt Endpoint documentation for more information.
Added support for the Verifone Vx690 CXPI device with WiFi connectivity only.
Added an isUnattended configurable value to indicate that a device is an unattended device. This is configurable in the pinpad section of the tripos.config file or in the api/v1/configuration/lanes request.
Ingenico devices now display "Updating, please wait..." while the device checks for updates during initialization. If RBA needs to be updated, the "Updating, please wait..." message will remain on the device's screen for the duration of the update, which can take up to 10-15 minutes.
triPOS now updates all Ingenico devices to the new version of RBA, 21.02. Please note, the update can take close to 10-15 minutes, and the device will reboot several times during the update process. Please see Bluetooth Connectivity for known issues about Bluetooth devices during software updates.
Bug Fixes & Other Changes
Removed the possible return value for cardholderAction "Skipped". For CXPI devices, when using the GET /api/v1/input endpoint, if the cardholder is able to skip the screen by pressing the ENTER button without inputting any data, the cardholderAction returned will be OK and the inputText returned will be empty.
Correct signature status code values are now returned on VeriFone Mx devices for all endpoints that return signature data if a signature entry timeout occurs or if there is an error with the PIN pad.
Fixed a bug where the transaction amount was not being sent to the processor for all reversals. The transaction amount value now appears in the totalAmount field of the triPOS response if the reversal is successful.
Fixed GET /card/nonfinancial/{laneId} for unencrypted cards returning PIN pad error.
Fixed a bug where the CommercialCardCustomerCode was not being sent to the processor.
Fixed a bug where SalesTax was not being sent to the processor.
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 PIN pad. To avoid this failure, do not make a request to a Vx805 PIN pad until the PIN pad is fully configured.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
The Ingenico RBA version 17.06 update process takes a full 10-15 minutes to complete. During that time, the PIN pad does not show any indication that the firmware files are being downloaded. Â Check the logs for information on the upgrade process and whether or not the initialization process is successful.
There is a connectivity issue with Ingenico Bluetooth devices when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
Verifone Mx9xx and Vx devices display a "CARD READ ERR" when a card containing only track 3 data is swiped. Transactions not canceled will time-out and return a PinPadException and "VerifoneXPI S20 timeout response" message. This issue is pending resolution from Verifone.
There is an issue with Verifone Mx9xx devices when upgrading from earlier versions of triPOS to release 5.12. If the PIN pad goes into a state of repeated initialization, please upgrade to release 5.9 prior to upgrading to release 5.12 or later.
There is an issue when pressing cancel on a PIN pad while on the Payment Type selection screen where the transaction continues on for processing and returns the paymentType as none.
Version 5.12.1 (Internal Release Only, Not for Field Distribution)
Added support for Vx805s that are loaded with the CXPI firmware. To use a Vx805 that is loaded with the CXPI firmware, change the lanedriver type in the triPOS.config to VeriFoneCXpi. Vx805 devices loaded with regular XPI can still be used as normal. Please see CXPI Documentation for more details.
Added three new prompt types to the GET /api/v1/input endpoint. However, note that these new prompts are only supported on a Vx805 running CXPI. Please see the Input Endpoint documentation for a list of prompts and formats currently supported for each device.
Bug Fixes & Other Changes
Removed the possible return value for cardholderAction "Skipped". For CXPI devices, when using the GET /api/v1/input endpoint, if the cardholder is able to skip the screen by pressing the ENTER button without inputting any data, the cardholderAction returned will be OK and the inputText returned will be empty.
Correct signature status code values are now returned on VeriFone Mx devices for all endpoints that return signature data if a signature entry timeout occurs or if there is an error with the PIN pad.
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 PIN pad. To avoid this failure, do not make a request to a Vx805 PIN pad until the PIN pad is fully configured.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
/api/v1/card/nonfinancial/{laneId} returns TransactionFlowException when the card only has track 3 data.
The Ingenico RBA version 17.06 update process takes a full 5 minutes to complete. During that time, the PIN pad does not show any indication that the firmware files are being downloaded. Â Check the logs for information on the upgrade process and whether or not the initialization process is successful.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP, iSMP4) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
Omni Token support has now been added and can be accessed through the POST /api/v1/token/omni and POST /api/v1/token/omni/{transactionId} endpoints.
Added support for the latest VeriFone software bundle: FormAgent 4.7.5/XPI 5300C2/OS 30250800. If your Mx915 or Mx925 are running a different software bundle, triPOS will automatically
update your PIN pad to this bundle. Please wait until the PIN pad has finished updating and rebooting before sending a request.
Added three new endpoints to support sale, authorization, and refund transactions using OmniToken: POST /api/v1/sale/token, POST /api/v1/authorization/token, POST /api/v1/refund/token. See OmniToken.
Added in Release 5.11: Added isCscSupported to the silent installer and also to the /api/v1/configuration/transactionendpoint.
Bug Fixes & Other Changes
Fixed a bug to return a more descriptive error when requests are sent to the /api/v1/selection endpoint with an invalid lane.
Logs have been updated to track requests by tp-request-id throughout the system. Logs will now roll based on size, configurable, and automatically delete the oldest copy based on the number of rolled backups. Please see triPOS Logs for detailed information.
Fixed a bug where the Learn More and View Details links were broken on the main triPOS help page.
Fixed in Release 5.11: Fixed bug where the checkForDuplicateTransactions flag was not working.
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
/api/v1/card/nonfinancial/{laneId} returns TransactionFlowException when the card only has track 3 data.
The Ingenico RBA version 17.06 update process takes a full 5 minutes to complete. During that time, the PIN pad does not show any indication that the firmware files are being downloaded. Â Check the logs for information on the upgrade process and whether or not the initialization process is successful.
There is a connectivity issue with Ingenico Bluetooth devices when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
/api/v1/card/nonfinancial/{laneId} returns TransactionFlowException when the card only has track 3 data.
The Ingenico RBA version 17.06 update process takes a full 5 minutes to complete. During that time, the PIN pad does not show any indication that the firmware files are being downloaded. Â Check the logs for information on the upgrade process and whether or not the initialization process is successful.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
This release of triPOS contains a significant amount of added and improved functionality around Store and Forward, API configuration options, new response values and automatic
PIN pad reconnection logic. We've also fixed several bugs, so please read the details below.
New Features & Improvements
The /api/v1/authorization and /api/v1/refund endpoints now support EMV Store and Forward transactions.
/api/v1/card/financial/{laneId} now returns CardHolderName and CardLogo. EncryptedCardData section inside of the response no longer contains CardHolderName.
triPOS will automatically attempt to reconnect PIN pads every 60 seconds, for more information please see the Integration Guide.
The /api/v1/sale endpoint now accepts cashback options through the API more».
The /api/v1/sale endpoint now accepts a configuration value that allows or disables debit through the API more».
The card read endpoints such as /api/v1/card/financial/{laneId}, /api/v1/card/financial/{laneId}, and /api/v1/card/financial/{laneId} now return CardEntryMode.
triPOS now supports automatic Store and Forward more».
IMPORTANT NOTE: Any client that uses either the existing manual Store and Forward, or is interested in integrating to the new
automatic Store and Forward, must delete the triPOS.db file before they will be able to store transactions with this version of triPOS.
Please make sure all stored transactions have been forwarded for online processing before deleting the triPOS.db file. Any stored transactions that have not been forwarded will be completely lost when deleting the triPOS.db file.
Bug Fixes & Other Changes
The selection endpoint used to default the form value to YesNoTextArea if the value was not provided. The validation is fixed so that it always requires a non-empty, valid form value.
The endpoints that accept a lodging section now require the marketCode to be HoteLodging if lodging fields are supplied. If the marketCode in the triPOS.config is not set to HotelLodging, then a marketCode of HotelLodging must be supplied in the configuration section of the request.
triPOS no longer allows the maximumCashbackAmount to be zero. If it is zero, the PIN pad will only accept $0 as a valid cashback amount. If the merchant does not want to allow cashback, it can be disabled using the isCashbackAllowed value in the triPOS.config, or through the new cashbackOptions request parameters.
Deprecated Features
Supported Devices
Verifone Vx805
Verifone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350, iCMP
EMV Devices
Verifone Vx805
Verifone Mx915
Ingenico iSC250, iSC480, iPP320, iPP350, iCMP
IP Devices
Verifone Mx915
Ingenico iSC250
Bluetooth Devices
Ingenico iCMP
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
The triPOS service may fail when disconnecting/reconnecting a Vx805 pin pad connected over USB. To avoid this failure, do not unplug a Vx805 pin pad without first stopping the triPOS service.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
/api/v1/card/nonfinancial/{laneId} returns TransactionFlowException when the card only has track 3 data.
The Ingenico RBA version 17.06 update process takes a full 5 minutes to complete. During that time, the PIN pad does not show any indication that the firmware files are being downloaded. Â Check the logs for information on the upgrade process and whether or not the initialization process is successful.
An Ingenico whitelist for clear non-financial card data is now supported on the /api/v1/pinpad/card/{laneId} and /api/v1/pinpad/card/nonfinancial/{laneId} endpoints. Only non-financial card ranges will be approved for the whitelist.
Financial card reads through the /api/v1/pinpad/card/{laneId} and /api/v1/pinpad/card/financial/{laneId} endpoints now support returning the encrypted card data using the isEncryptedCardDataNeeded flag.
Global debit Interlink and Maestro AIDs are now sent as debit transactions instead of credit.
Added a check for the header field tp-request-id. Check duplicate request for the last requests and returns error when same tp-request-id has found.
RBA version 17.06 is now supported on all Ingenico PIN pads.
Contactless and keyed card entry modes are now supported on all the card read endpoints (/api/v1/pinpad/card/{laneId}, /api/v1/pinpad/card/nonfinancial/{laneId} and /api/v1/pinpad/card/financial/{laneId}).
EMV is now supported on store and forward sale transactions.
Added new MultiOptionTextArea form for the /api/v1/selection endpoint on the Verifone Mx915 and Mx925. See Selection Endpoint.
Added a new endpoint /api/v1/display to support displaying text on the Mx915 or the Mx925. See Display Endpoint.
Added support for a custom idle screen image for the Mx915 and Mx925. See Idle Screen.Note: Currently NOT supported on Linux.
Healthcare is now supported on the /api/v1/sale/{paymentAccountId} and /api/v1/authorization/{paymentAccountId} endpoints.
Added fsaCard field to /api/v1/sale, /api/v1/authorization, /api/v1/paymentAccount, and /api/v1/paymentAccount{paymentAccountId} responses.
Added a new config section for store and forward on triPOS.config to control the level of liability when using store and forward functions.
Bug Fixes & Other Changes
Update logic to check for PIN entry through the Vx805 to correctly send PIN block when present.
Fixed Ingenico RBA devices show blank display after transaction.
Fixed iCMP not being able to Re-Pair after connecting to triPOS.
Fixed approvedAmount being set to a value other than zero for a Sale or Auth when EMV is declined in GENAC1(Offline).
Deprecated Features
Supported Devices
Verifone Vx805
Verifone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350, iCMP
EMV Devices
Verifone Vx805
Verifone Mx915
Ingenico iSC250, iSC480, iPP320, iPP350, iCMP
IP Devices
Verifone Mx915
Ingenico iSC250
Bluetooth Devices
Ingenico iCMP
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 PIN pad. To avoid this failure, do not make a request to a Vx805 PIN pad until the PIN pad is fully configured.
The triPOS service may fail when disconnecting/reconnecting a Vx805 PIN pad connected over USB. To avoid this failure, do not unplug a Vx805 PIN pad without first stopping the triPOS service.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
There is a connectivity issue with Ingenico Bluetooth devices (iCMP) when attempting to download files via Bluetooth connection. Please see Bluetooth Connectivity for workaround steps to download files to these devices.
Setting a custom idle screen image for the Verifone Mx915 and Mx925 with triPOS running on Linux fails because the mono installation is missing a dependency.
Added the ability to specify the installation path during a silent install of triPOS using the INSTALLFOLDER argument.
Added support for HTTPS calls to the triPOS Service. See the triPOS Integration Guide for details.
Added support for the /api/v1/signature/{laneId} endpoint on the Ingenico iSC250 and iSC480 devices.
Added support for the YesNoTextArea Form with the /api/v1/selection/{laneId} endpoint on the Ingenico iSC250 and iSC480 devices.
Added a new section in the triPOS.config on each lane to modify the idle message per device.
Added EasyPayCode type to the GET /api/v1/input endpoint so that it now allows input of a 4 digit code. See Input Endpoint.
Added on-screen cancel button to swipe and contactless swipe screens for the iPP320.
Added support for Level II fields for the following endpoints:
POST /api/v1/authorization
POST /api/v1/authorization/{transactionId}/completion
POST /api/v1/force/credit
POST /api/v1/refund
POST /api/v1/return/{transactionId}/{paymentType}
POST /api/v1/sale
Bug Fixes & Other Changes
Support for the InitializeOnStartup attribute for each lane in triPOS.config has been removed. All PIN pads will now initalize during the startup of the triPOS service.
Removed the healthcare section from the request model for the endpoint POST /api/v1/authorization/{transactionId}/completion as healthcare is not applicable to an authorization completion.
Edited misleading description of the request field referenceNumber for several endpoints. The description used to state that the referenceNumber is returned in the response, but that is not always the case.
Fixed validation logic for an authorization that contains healthcare values. The code is designed to return a warning if triPOS is not configured to support partial approvals when healthcare values are included in the request. triPOS was returning this warning even when partial approvals were supported.
Fixed the _type field of the GET /api/v1/selection endpoint so that it now returns the correct response type value.
Fixed a typo in the error message that is returned when a debit-only card is swiped for a refund when triPOS is not configured to allow debit refunds.
Updated the screenshot of the final screen of the GUI installer in the triPOS Integration Guide. The image was outdated and contained fields that no longer exist on the screen.
Updated the triPOS documentation by replacing all instances of ExpressPay with Express.
Added request validation to the DELETE /api/v1/configuration/lanes/ip/{laneId} and DELETE /api/v1/configuration/lanes/serial/{laneId}
endpoints to verify that the type of lane being deleted matches the type of lane in the request url.
Allowed Ingenico devices to display PIN pad idle text in triPOS config.
The endpoint GET /api/v1/card/nonfinancial{laneId} now returns track 3 data if present on the card. Track 3 data will also be returned by the endpoint GET /api/v1/card/{laneId} if the cardholder swipes a non-financial card and the card contains track 3 data.
Updated the comment for driver in the triPOS.config to list the correct casing for VeriFone.
Fixed a bug that caused triPOS to return HTTP Status Code "500" for a request to GET /api/v1/signature when a PIN pad was not fully initialized.
Updated documentation for GET /api/v1/selection to accurately reflect the behavior when the query parameter form is missing.
Deprecated Features
Supported Devices
Verifone Vx805
Verifone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
EMV Devices
Verifone Vx805
Verifone Mx915
Ingenico iSC250, iSC480, iPP320, iPP350
IP Devices
Verifone Mx915
Ingenico iSC250
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
The triPOS service may fail when disconnecting/reconnecting a Vx805 pin pad connected over USB. To avoid this failure, do not unplug a Vx805 pin pad without first stopping the triPOS service.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
The creditSaleSignatureThresholdAmount field has been added to the POST /api/v1/sale endpoint in the
configuration section that allows the creditSaleSignatureThresholdAmount field in the triPOS.config to be overridden.
Added /api/v1/input/{laneId} endpoint. This endpoint is a semi-custom screen that allows the client to display the given prompt on the PIN pad and accept cardholder input.
See Input Endpoint. IMPORTANT NOTE: triPOS will only return the raw input of the cardholder. If the amount entered is displayed on the PIN pad as $ 1.25,
triPOS will return only raw input of 125. No decimal point is returned, so for decimal amounts, apply decimal.
Bug Fixes and Other Changes
Fixed a bug in the documentation that misrepresented the name of the response from /api/v1/force/credit.
The GET /api/v1/signature/{laneId}?form=contract signature screen on the Mx915 now has a working scrollbar.
Deprecated Features
Supported Devices
Verifone Vx805
Verifone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
EMV Devices
Verifone Vx805
Verifone Mx915
Ingenico iSC250, iSC480, iPP320, iPP350
IP Devices
Verifone Mx915
Ingenico iSC250
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
The triPOS service may fail when disconnecting/reconnecting a Vx805 pin pad connected over USB. To avoid this failure, do not unplug a Vx805 pin pad without first stopping the triPOS service.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
Added binValue, cardHolderName, and entryMode to the POST /api/v1/token/paymetric response.
Added tp-express-acceptor-id, tp-express-account-id, and tp-express-account-token as optional header parameters. This sensitive data is only accepted by triPOS if the request is through localhost. If all three values are included, the supplied credentials will be used instead of the triPOS.config credentials for that request only.
Added support to the GET /api/v1/selection/{laneId}?form=MultiOption semi-custom screen for the iSC250. See "Known Issues" section below for limitations of this device.
Added support to the POST /api/v1/sale to accept tip prompt options. See TipOptions for more information.
Bug Fixes and Other Changes
The POST /api/v1/token/paymetric and POST /api/v1/token/paymetric/{transactionId} endpoints now return the expected status code of 500 when a token cannot be created.
The POST /api/v1/selection/{laneId}?form=YesNoTextArea endpoint now accepts an empty header or sub-header without returning an error.
The POST /api/v1/selection/{laneId}?form=YesNoTextArea and the POST /api/v1/selection/{laneId}?form=MultiOption endpoints can now accept a new request to the PIN pad after the PIN pad times out on one of the semi-custom forms.
The POST /api/v1/authorization/{paymentAccountId} endpoint now correctly populates the approvedAmount in the response.
triPOS now correctly sends the laneId to Express correctly for the following EMV scenarios:
1. When sending a Force as a result of the card's chip approving the transaction in GENAC1.
2. When sending a Reversal as a result of the card's chip declining the transaction in GENAC2 after it has already been approved online.
The documentation for tipSelections in the triPOS.config now more accurately describes how percentages are displayed on the PIN pad.
The logic that triPOS uses to establish a connection to an IP device now only attempts to connect twice, rather than continuously looping, if it cannot establish a connection to the PIN pad.
The Ingenico EMV configuration now correctly formats the RID's for the CA Public Keys.
Supported Devices
Verifone Vx805
Verifone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
EMV Devices
Verifone Vx805
Verifone Mx915
Ingenico iSC250, iSC480, iPP320, iPP350
IP Devices
Verifone Mx915
Ingenico iSC250
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
The triPOS service may fail when disconnecting/reconnecting a Vx805 pin pad connected over USB. To avoid this failure, do not unplug a Vx805 pin pad without first stopping the triPOS service.
The RBA software running on the iSC250 has the following limitations on the GET /api/v1/selection{laneId} endpoint:
1. Some numeric-only strings (e.g. "123") are reserved as Prompt IDs in RBA and will not be displayed as raw text on the prompt or buttons. If this occurs, please try to put a space at the beginning of the string for it to be displayed correctly.
2. RBA currently displays "Input Accepted" on the PIN pad after the cardholder makes a selection. The PIN pad will remain on the "Input Accepted" screen, rather than the semi-custom screen, until a new request is sent to the PIN pad.
Note: A bug found in this version causes an invalid CA Public Key configuration. Please upgrade to version 5.6.0 to use EMV with any Ingenico device.
IP Devices
Verifone Mx915
Ingenico iSC250
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
The triPOS service may fail when disconnecting/reconnecting a Vx805 pin pad connected over USB. To avoid this failure, do not unplug a Vx805 pin pad without first stopping the triPOS service.
Version 5.4.1 of triPOS disables the card reader of the Vx805 so that it does not allow a swipe when the PIN pad is in an idle state.
Bug Fixes and Other Changes
Vx805 no longer allows the cardholder to swipe a card when the PIN pad is in an idle state.
Supported Devices
Verifone Vx805
Verifone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
EMV Devices
Verifone Vx805
Verifone Mx915
Ingenico iSC250, iSC480, iPP320, iPP350
Note: A bug found in this version causes an invalid CA Public Key configuration. Please upgrade to version 5.6.0 to use EMV with any Ingenico device.
IP Devices
Verifone Mx915
Ingenico iSC250
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
The triPOS service may fail when disconnecting/reconnecting a Vx805 pin pad connected over USB. To avoid this failure, do not unplug a Vx805 pin pad without first stopping the triPOS service.
Version 5.4 of triPOS adds EMV support for the Ingenico iSC250 PIN pad.
New Features & Improvements
EMV support for the Ingenico iSC250 PIN pad.
Note: A bug found in this version causes an invalid CA Public Key configuration. Please upgrade to version 5.6.0 to use EMV with any Ingenico device.
Added support to triPOS for updating the iSC250's RBA firmware. If the PIN pad has an older version of RBA than the version included with the triPOS build,
triPOS will upgrade the PIN pad to the newer version of RBA upon initialization. If the lane that contains the iSC250 is configured to initialize on
startup, the upgrade will occur automatically when triPOS boots up and connects to the PIN pad. If not, it will take place upon the first request sent to the PIN pad.
The RBA upgrade process takes approximately 10-15 minutes and causes the PIN pad to reboot three times. During the upgrade, the PIN pad does not show any indication
that the firmware files are being downloaded. Check the trace logs for information on the upgrade process and whether or not the initialization process is successful.
This version of triPOS is released with RBA version 17.02. Note: To upgrade to a version of RBA newer than the version included with the given triPOS build,
place the RBA OGZ file in the executable directory of triPOS, with the naming convention iSC250.OGZ.version, where version is the 4 digit version without any
periods (i.e. 1702).
Bug Fixes and Other Changes
Added support to triPOS for updating the iSC250's date and time variables upon PIN pad initialization.
Added support to GET configuration/transaction and PUT configuration/transaction for isDebitRefundSupported.
Added silent installer support for isDebitRefundSupported.
Enabled the Ingenico family's physical cancel button to cancel the transaction while the PIN pad is displaying the swipe screen.
Added an on-screen cancel button to the Ingenico family's swipe screen.
Added the ability to update an expiration date on the PUT /api/v1/paymentAccount/{paymentAccountId} endpoint.
Fixed issue with non-signature supported PinPads on GET /api/v1/signature/{laneId} endpoint.
Deprecated Features
Supported Devices
Verifone Vx805
Verifone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
Note: A bug found in this version causes an invalid CA Public Key configuration. Please upgrade to version 5.6.0 to use EMV with any Ingenico device.
EMV Devices
Verifone Vx805
Verifone Mx915
Ingenico iSC250
IP Devices
Verifone Mx915
Ingenico iSC250
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
The triPOS service may fail when disconnecting/reconnecting a Vx805 pin pad connected over USB. To avoid this failure, do not unplug a Vx805 pin pad without first stopping the triPOS service.
Version 5.3 of triPOS enhances support for custom forms and flows. Notably, there is a new GET /api/v1/selection endpoint, a
new POST /api/v1/idle endpoint, and an enhanced GET /api/v1/signature endpoint. Using these endpoints in succession allows the creation of
powerful custom business flows.
New Features & Improvements
Upgrade support: triPOS now preserves the triPOS.config settings during an upgrade. See the triPOS Integration Guide for more details.
New GET /api/v1/selection endpoint. Use this endpoint to get cardholder selections via the pinpad. Available forms are YesNoTextArea and MultiOption. See selection documentation for more information.
New POST /api/v1/idle endpoint. Use this endpoint to return the Mx915 or Mx925 to the idle screen. See idle documentation for more information.
Enhanced GET /api/v1/signature endpoint. You can now use this endpoint to display text to the cardholder and require them to sign to indicate their acknowledgement of the provided text. See signature documentation for more information.
Added support to configure the corsAllowedOrigins triPOS.config value during silent install. See the triPOS Integration Guide for more details.
New POST /api/v1/token/paymetric endpoint for creating a Paymetric token with a card swipe.
Bug Fixes and Other Changes
The triPOS manual installer now only requires the user to enter Express credentials during install. All values removed from the installer's screens can be set in the triPOS.config via the configuration endpoints after install. Alternatively, these values can still be set through command-line arguments during a silent install.
Removed "Developer 2 Key" and "Developer 2 Secret" from the installer UI.
Removed "DEVKEY2" and "DEVSECRET2" from silent installer options. If provided, the silent installer will ignore these parameters.
currencyCode removed from configuration section of all applicable requests. Sending in this value will not cause an error, but the value will be ignored. Set the currencyCode for your account in the triPOS.config file.
The <emv> xml block has been moved out of triPOS.config and into it's own file triPOS.EMV.config. The tag itself has been changed from <emv> to <triposEmv>.
tripos now supports multiple domains for CORS Support.
The GET /api/v1/signature endpoint was erroneously returning hasErrors as true when a user pressed the cancel button. This has been corrected. triPOS will continue to return the signature { statusCode } as SignatureRequiredCancelledByCardholder in this case.
Replaced the triPOS.config value isConvenienceFeeAllowed with the more appropriate confirmConvenienceFeeAmount. See convenienceFeeAmount documentation for more details.
Deprecated Features
Deprecated Endpoints
(Note: Deprecated endpoints will remain available throughout v1 of the API, but may not be available in API v2)
[Deprecated] GET /api/v1/pinpad/card
Use GET /api/v1/card instead.
[Deprecated] GET /api/v1/pinpad/card/{laneId}
Use GET /api/v1/card/{laneId} instead.
[Deprecated] GET /api/v1/pinpad/card/financial
Use GET /api/v1/card/financial instead.
[Deprecated] GET /api/v1/pinpad/card/financial/{laneId}
Use GET /api/v1/card/financial/{laneId} instead.
[Deprecated] GET /api/v1/pinpad/card/nonfinancial
Use GET /api/v1/card/nonfinancial instead.
[Deprecated] GET /api/v1/pinpad/card/nonfinancial/{laneId}
Use GET /api/v1/card/nonfinancial instead.
[Deprecated] GET /api/v1/pinPadSelectionPrompt
Use GET /api/v1/selection?form=MultiOption instead.
Supported Devices
Verifone Vx805
Verifone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
The triPOS service may fail when disconnecting/reconnecting a Vx805 pin pad connected over USB. To avoid this failure, do not unplug a Vx805 pin pad without first stopping the triPOS service.
Version 5.2 of triPOS adds support for the Hotel and Lodging industry. The ability to do partial reversals, incremental authorizations, and to pass lodging parameters on the various
POST /sale, POST /authorization, and POST /force/credit endpoints is now supported.
New Features & Improvements
New GET /binQuery/{laneId} endpoint. Use this endpoint to determine if a card falls into a specific BIN range such as prepaid, healthcare, or debit.
New POST /authorization/{transactionId}/incremental endpoint added to the API.
Reversal endpoint now supports partial reversal. Use query string 'type=partial' to do a partial reversal.
Lodging parameters now supported on the following endpoints: POST api/v1/authorization, POST api/v1/authorization/{transactionId}/incremental, POST api/v1/authorization/{transactionId}/completion, POST api/v1/sale and POST api/v1/force/credit. Lodging parameters should only be used in conjunction with the HotelLodging market code.
Bug Fixes and Other Changes
Fixed POST /return/{transactionId}/{paymentType} endpoint to provide a clear error when payment type is debit. Debit is not allowed for the POST /return/{transactionId}/{paymentType} endpoint, use POST /refund instead.
Added configuration value named isDebitRefundSupported. Refund endpoint rejects debit card when isDebitRefundSupported is false. Please note that not all processors support debit refund.
POST /refund prompts cardholder to select payment type if card has multiple capabilities.
POST /refund no longer prompts for cashback during a debit refund.
POST /refund now maps to host request specific for debit refunds.
Supported Devices
Verifone Vx805
Verifone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
The triPOS service may fail when disconnecting/reconnecting a Vx805 pin pad connected over USB. To avoid this failure, do not unplug a Vx805 pin pad without first stopping the triPOS service.
triPOS version 5.1.1 fixes a number of small bugs.
Bug Fixes and Other Changes
An issue where in some cases an EMV transaction was being cancelled at GENAC2 after an online approval.
An issue where a time out on a TCP/IP Mx915 may have resulted in screen stuck on cancelled.
An issue with PIN Debit transactions on production Ingenico PIN Pads.
An issue with contactless MSD sales on Vx805 running XPI 8.30G.
An issue where, in some cases, the non-financial card read endpoint would not strip sentinels from track data.
An issue with time outs and/or rapid requests to the non-financial card read endpoint could result in an error.
Supported Devices
Verifone Vx805
Verifone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
The triPOS service may fail when disconneting/reconnecting a Vx805 pin pad connected over usb. To avoid this failure, do not unplug a Vx805 pin pad without first stoping the triPOS service.
triPOS version 5.1 adds support for TCP/IP pin pads, healthcare (FSA/HSA cards), and contactless MSD while EMV is enabled.
New Features & Improvements
Added TCP/IP support for Mx915. Note: A TCP/IP enabled PIN Pad is needed in order to communicate via TCP/IP.
Added contactless MSD support for Vx805 and Mx915 when EMV is enabled.
Added support for FSA/HSA cards on the POST /sale and POST /authorization endpoints.
Added accountNumber as part of the response for the POST /paymentAccount, POST /paymentAccount/{paymentAccountId}, POST /void,
POST /reversal, POST /return, POST /force/credit, and POST /authorization/{transactionId}/completion endpoints.
Added service recovery options that will cause the triPOS service to restart automatically if any exception causes the process to crash.
Bug Fixes and Other Changes
Only swipe is allowed on the POST /pinpad/card/financial, POST /pinpad/card/nonfinancial, and POST /paymentAccount endpoints even when EMV is enabled.
Removed FullyApproved from the triPOS statusCode response enumeration.
Supported Devices
Verifone Vx805
Verifone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
The triPOS service may fail when disconneting/reconnecting a Vx805 pin pad connected over usb. To avoid this failure, do not unplug a Vx805 pin pad without first stoping the triPOS service.
The EmvFallbackAllowed configuration setting was not properly allowing fallback in some situations, this has been corrected.
When double quotes(") are included in any api description they cause an exception when trying to generate models using the ServiceStack Visual Studio plugin, this has been corrected.
Supported Devices
VeriFone Vx805
VeriFone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
triPOS version 5.0 adds support for EMV. The POST /sale, POST /authorization, and POST /refund endpoints all support cardholders utilizing an EMV card when using a VeriFone Mx915.
The responses for these endpoints now contain an emv block with fields required to appear on an EMV receipt.
New Features & Improvements
convenienceFeeAmount is now an optional parameter used for reporting purposes on the POST /refund and POST /reversal/{transactionId}/{paymentType} endpoints.
triPOS now returns content-length with each response.
It is now possible to change a laneId using the lane configuration endpoints:
PUT /configuration/lanes/serial/
PUT /configuration/lanes/ip/
Added required EMV fields to SendRequestAndViewReceipt application: Application Label, Application Id, Cryptogram, and Declined Tags
Bug Fixes
In certain rare cases, the capabilities of a credit or debit card might have been misidentified.
All parameter values under the configuration section of a request are now properly mapped. Any value sent in under this section will override the corresponding value in the triPOS.config file.
When a signature is required, and the PIN pad does not support signature, it now returns SignatureRequiredNotSupportedByPinPad instead of Unknown.
Currency code is now sent up to the host for a reversal. This caused an error when processing with FDC Canada.
Fixed an issue with Ingenico PIN pads that did not allow $0.00 for tip amount entry.
Supported Devices
VeriFone Vx805
VeriFone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
This version of triPOS adds Cross-origin resource sharing (CORS) support, improvements to the binValue response field by always returning the first 6 digits of a
payment account number, and several enhancements to the responses of both stored and forwarded sale requests.
Breaking Changes
None
New Features / Improvements
triPOS now allows cross-origin requests by responding to Cross-origin resource sharing (CORS) preflight checks.
Updated Bin Value on responses to always be the first 6 of the card.
Added signature endpoint support for Ingenico iSC250, iSC250, and iSC480 (iPP3xx does not support signature).
The response from a successful "store" request now includes a HATEOS link to "forward" the request to the processor as well as the card logo.
The "forward" response now includes values for fields expirationMonth, expirationYear, cardHolderName, accountNumber and binValue.
Bug Fixes
Changed VeriFoneXpiPinPad to accept ENTER as the YES choice for YES/NO prompts.
Metadata documentation links have been fixed.
Better support for connect and disconnect events for VeriFone Vx and Mx pin pads.
A small memory leak that happened on each request was resolved.
In certain cases, it was possible for a card to match an incorrect bin entry and have its capabilities misidentified.
Deprecated Features
None
Removed Features
None
Supported Devices
VeriFone Vx805
VeriFone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
In certain cases, the reversal endpoint POST /api/v1/reversal/{transactionId}/{paymentType} may not work correclty with First Data Canada.
The triPOS service may fail when a request is sent during a specific phase of initialization of a Vx805 pin pad. To avoid this failure, do not make a request to a Vx805 pin pad until the pin pad is fully configured.
The highlight of triPOS version 4.2.206 is the implementation of Store and Forward for the sale endpoint.
It also introduces a request ID header that allows clients to track which response corresponds to each request.
Lastly, version 4.2.206 adds several additional fields to various API responses that facilitate both receipt building and determining transaction outcomes.
Breaking Changes
None
New Features / Improvements
triPOS is now capable of supporting Store and Forward on the Sale endpoint.
A new header field added to requests called tp-request-id. This request ID is used by triPOS to uniquely identify each request. It is echoed in the response header.
New Receipt Information
Added pinVerified property to all card based financial endpoint responses. This property may be used to print "PIN VERIFIED" on the receipt. Affected endpoints are:
/api/v1/sale
/api/v1/authorization
/api/v1/return/{transactionId}/{paymentType}
/api/v1/refund
/api/v1/force
/api/v1/pinpad/card/{laneId} and /api/v1/pinpad/card/nonfinancial/{laneId} now support clear card data from PIN pad whitelist.
ExpressResponseCode, ExpressResponseMessage, HostResponseCode, and HostResponseMessage have been added to endpoint responses that go to Express. NOTE: HostResponseCode and HostResponseMessage will not be returned for transactions that terminate at Express (e.g. payment account create/update).
MerchantId has been added to endpoint responses that go to Express. For Express, this value is the AcceptorId found in triPOS.config.
ExpirationYear and ExpirationMonth has been added to endpoint responses for processes that accept card input.
Patched an issue with attempting to enable P2PE for the XPI side of the VeriFoneFormAgentXpi driver.
Bug Fixes
On some financial endpoints, if a cardholder failed to press OK after signing, the transaction would appear to have timed out.
Fixed the processor response code being returned incorrectly in certain circumstances.
Fixed TerminalCapabilityCode being sent to Express incorrectly in certain circumstances.
Deprecated Features
In the _processor section of the response:
processorLogs - Use logs.
processorRawResponse - Use rawResponse.
processorReferenceNumber - Use the same reference number passed in the request.
processorRequestFailed - Use top level properties (e.g. hasErrors).
processorRequestWasApproved - Use top level properties (e.g isApproved).
processorResponseCode - Use expressResponseCode.
processorResponseMessage - Use expressResponseMessage.
Removed Features
N/A
Supported Devices
VeriFone Vx805
VeriFone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
In certain cases, the reversal endpoint POST /api/v1/reversal/{transactionId}/{paymentType} may not work correclty with First Data Canada.
New pinPadSelectionPrompt endpoint allows for setting a PIN pad prompt and selection options that the cardholder can choose from. Endpoint returns the 0-based index of the selection.
Bug Fixes
Deprecated Features
Deprecated Endpoints
N/A
Removed Features
N/A
Supported Devices
VeriFone Vx805
VeriFone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
In certain cases, the reversal endpoint POST /api/v1/reversal/{transactionId}/{paymentType} may not work correclty with First Data Canada.
Upgrading from any version of triPOS older than 4.2.203 will require the previous version of triPOS to be removed manually before installing the newest version of triPOS.
Going forward when upgrading from version 4.2.203 users will not be required to remove any older versions themselves.
New Features / Improvements
The CardLogo is now returned on the CreatePaymentAccount endpoint, as well as the UpdatePaymentAccount endpoint only when card data is updated.
Added new endpoint for completing a sale with an Express Pass payment account token.
Added new endpoint for completing an authorization with an Express Pass payment account token.
The default lane in the triPOS.config created by the installer is now formatted correctly.
Added new endpoint(s) for obtaining financial or non-financial card data.
[Only Supports MX915 with VeriFoneFormAgentXpi drivers]
[Only Supports Magswipe]
Bug Fixes
Installer no longer deletes registry entries during upgrade.
A copy of triPOS configuration is only created on triPOS removal this prevents multiple copies of the same configuration being created during upgrades.
Deprecated Features
Deprecated Endpoints
N/A
Removed Features
N/A
Supported Devices
VeriFone Vx805
VeriFone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
In certain cases, the reversal endpoint POST /api/v1/reversal/{transactionId}/{paymentType} may not work correclty with First Data Canada.
Reversal support for debit cards and gift cards, VeriFone Mx with Form Agent/XPI including P2PE, Express lane number support, installation improvements, and bug fixes
Breaking Changes
Removed SignatureStatusCode from the ActivateGift Response since it was not relevent.
Removed cashBackAmount parameter from sale endpoint. Cash back should only enter system through PIN pad prompts.
New Features / Improvements
Added support for VeriFone Mx with Form Agent/XPI that includes built-in point-to-point encryption (P2PE)
Reversal support for debit cards and Vantiv gift cards
triPOS now supports the new LaneNumber field of the Express Interface
triPOS installer now backs up existing triPOS.config if it is present in the selected installation directory (with a time stamp)
triPOS installation packages and executables are now signed by Element Payment Services
triPOS installer now indicates "Success" rather than "Setup Successful" upon a successful install and uninstall.
triPOS installer now indicates "Progress" rather than "Setup Progress" during install and uninstall.
Global exception handler implemented so that all exceptions that are not caught within triPOS or that occur outside of the API will be consistently returned with an HTTP Status Code of 500 and will contain a consistently formatted response with exceptionType, exceptionMessage and the requestId
Bug Fixes
Endpoint with path variables (e.g. Void) did not always serialize correctly when using XML
Cash back amount was not always being sent to Express properly
Note: A breaking change in the triPOS.config file from release 4.2.200 was not captured in the 4.2.200 release notes (*See 4.2.200 release notes for details)
Deprecated Features
Deprecated Endpoints
POST
/api/v1/credit
[Deprecated since 01/29/2015] Use /api/v1/refund instead.
POST
/api/v1/sale/{transactionId}/return/{paymentType}
[Deprecated since 01/29/2015] Use /api/v1/return/{transactionId}/{paymentType} instead.
Removed Features
None
Supported Devices
VeriFone Vx805
VeriFone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
In certain cases, the reversal endpoint POST /api/v1/reversal/{transactionId}/{paymentType} may not work correclty with First Data Canada.
Support for voiding transactions and other minor bug fixes.
Breaking Changes
None
New Features / Improvements
Support for contact EMV on the Ingenico RBA PIN pads.
Fixed installer bug so that it will write the install path to the 64-bit registry view on a 64-bit machine.
Changed the way that the TerminalCapabilityCode is determined to better fullfill the requirements of the Host Request.
New Endpoint
POST
/api/v1/void/{transactionId}
Voids the previous transaction with the passed in transaction ID.
Deprecated Features
None
Removed Features
None
Supported Devices
VeriFone Vx805
VeriFone Mx915, Mx925
Ingenico iSC250, iSC480, iPP320, iPP350
Bug Fixes
None
Known Issues
The current Ingenico RBA EMV implementation only allows basic EMV retail flow and no additional prompts like tip or ZIP code.
The current Ingenico RBA EMV implementation uses a built-in EMV configuration so changes to the EMV section of triPOS.config will not affect EMV transaction.
The current Ingenico RBA EMV implementation does not allow P2PE to be enabled.
Improvements to links in the API responses have been made that align better with the HATEOAS philosophy for REST APIs.
Breaking Changes
Changed Endpoints
New endpoint:
POST
/api/v1/force/credit
Previous endpoint: POST /api/v1/creditCardForce
Creates a new credit card force based on the passed in amounts.
New endpoint:
POST
/api/v1/gift/activate
Previous endpoint: POST /api/v1/giftCardActivate
Activates the given gift card with the specified amount.
Changed Configuration
triPOS.config: Change to lane section
Previous format: <lanes><lane> ...lane details... </lane></lanes>
New format:
<lanes><ipLane> ...lane details... </ipLane></lanes>
OR
<lanes><serialLane> ...lane details... </serialLane></lanes>
depending on the type of lane connection (Serial/USB or IP)
New Features / Improvements
System reversals now only wait 15 seconds for a response before sending another system reversal request to Express
The number of times to attempt an automatic reversal is now configurable in the triPOS.config
Add links in API responses
Added C++ sample application that demonstrates a card sale request.
Updated the SendRequestAndViewReceiptApp to use utf8 when formatting the response instead of utf16.
Refactored GET /api/v1/lanes response format to include an "errors", "hasErrors", "warnings", "logs" and "links" section for each lane.
The installer has been expanded to include more functionality and options. It now can install .NET 4.5 and allow for a custom installation path. For more information, consult the document "triPOS Installer Documentation.docx" in the main SDK directory.
New Endpoints
GET
/api/v1/configuration
Retrieve the HATEOAS links for accessing and modifying the triPOS configuration.
GET
/api/v1/configuration/application
Retrieve application settings.
PUT
/api/v1/configuration/application
Update application settings.
GET
/api/v1/configuration/host
Get host settings.
PUT
/api/v1/configuration/host
Update host settings.
GET
/api/v1/configuration/lanes
Retrieve all lanes settings.
GET
/api/v1/configuration/lanes/ip
Retrieve all IP lane settings.
POST
/api/v1/configuration/lanes/ip
Creates lane settings with options for IP Address and IP Port
DELETE
/api/v1/configuration/lanes/ip/{laneId}
Delete ip lanes settings for lane with laneId.
GET
/api/v1/configuration/lanes/ip/{laneId}
Retrieve specific IP lane settings.
PUT
/api/v1/configuration/lanes/ip/{laneId}
Updates IP lanes settings.
GET
/api/v1/configuration/lanes/serial
Retrieve all serial lane settings.
POST
/api/v1/configuration/lanes/serial
Creates lane settings with options for serial device.
DELETE
/api/v1/configuration/lanes/serial/{laneId}
Delete serial lanes settings for lane with laneId.
GET
/api/v1/configuration/lanes/serial/{laneId}
Retrieve specific serial lane settings.
PUT
/api/v1/configuration/lanes/serial/{laneId}
Updates serial lanes settings.
GET
/api/v1/configuration/server
Retrieve server settings.
PUT
/api/v1/configuration/server
Update server settings.
GET
/api/v1/configuration/transaction
Retrieve transaction settings.
PUT
/api/v1/configuration/transaction
Update transaction settings.
GET
/api/v1/force
Returns a the list of force endpoints
GET
/api/v1/gift
Return the endpoints used to manage Vantiv Gift Cards
GET
/api/v1/paymentAccount
Returns a the list of payment account endpoints.
POST
/api/v1/refund
Creates a new card refund based on the passed in parameters.
POST
/api/v1/return/{transactionId}/{paymentType}
Creates a new card return based on the passed in parameters.
POST
/api/v1/reversal/{transactionId}/{paymentType}
[BETA] Creates a new full reversal based on given transaction id, payment type, and the passed in amounts.
GET
/api/v1/signature
The list of links for the signature endpoints including only lanes with a pinpad capable of signature entry
GET
/api/v1/signature/{laneId}
Prompts the user to enter a signature on the pinpad and returns the result.
GET
/api/v1/status
Return a list of the triPOS status endpoints
GET
/api/v1/status/host
Get host status.
GET
/api/v1/status/lane/{laneId}
Returns the current status of the given lane.
GET
/api/v1/status/triPOS/{echo}
Echos the text passed to triPOS. A successful echo indicates that triPOS is running and responding to requests.
Deprecated Features
Deprecated Endpoints
POST
/api/v1/credit
[Deprecated] Use /api/v1/refund instead.
POST
/api/v1/sale/{transactionId}/return/{paymentType}
[Deprecated] Use /api/v1/return/{transactionId}/{paymentType} instead.
Removed Features
None
Supported Devices
VeriFone Vx805
VeriFone Mx915, Mx925
Bug Fixes
Fixed Swagger API documentation bug. Path variables no longer appear in the request body DTO model.
Known Issues
The Metadata documentation page does not show fields as being required. Please refer to the Swagger Documentation for this information.
In certain cases, the reversal endpoint POST /api/v1/reversal/{transactionId}/{paymentType} may not work correclty with First Data Canada.
In some scenarios, reversals may not be compatible with debit cards and Vantiv Gift cards.
There has been a major overhaul of the API design based on feedback from customers and internal reviews. Please read the breaking changes to determine if your integration to triPOS has been affected. In order to help ease integration, the API documentation has been built into triPOS and can be found at the root of your triPOS instance (e.g. http://localhost:8080/).
Breaking Changes
Changed Endpoints
New endpoint:
POST
/api/v1/authorization
Previous endpoint: POST /api/v1/cardAuthorization Creates a new card authorization based on the passed in parameters.
New endpoint:
POST
/api/v1/authorization/{transactionId}/completion
Previous endpoint: POST /api/v1/cardAuthorization/{transactionId} Updates a previous card authorization with the final totals.
New endpoint:
POST
/api/v1/creditCardForce
Previous endpoint: POST /api/v1/cardSale/force/{approvalNumber} Creates a new credit card force based on the passed in amounts.
New endpoint:
PUT
/api/v1/paymentAccount/{paymentAccountId}/credit
Previous endpoint: POST /api/v1/cardAccountToken/{paymentAccountId} Updates a payment account based on the given data.
New endpoint:
POST
/api/v1/paymentAccount/credi
t
Previous endpoint: POST /api/v1/cardAccountToken Creates a card account token based on the given data.
New endpoint:
POST
/api/v1/sale
Previous endpoint: POST /api/v1/cardSale Creates a new card sale based on the passed in amounts.
New endpoint:
POST
/api/v1/sale/{transactionId}/return/{paymentType}
Previous endpoint: POST /api/v1/cardReturn Creates a new card return based on the passed in parameters.
New Features / Improvements
Installer now allows for silent install
Installer now has a screen to configure triPOS during install
New Endpoints
POST
/api/v1/balance
Requests a balance for a credit or gift card.
POST
/api/v1/credit
Creates a new card credit based on the passed in parameters.
POST
/api/v1/giftCardActivate
Activates the given gift card with the specified amount.
GET
/api/v1/lanes
Retrieve all lanes settings.
POST
/api/v1/lanes
Creates a lane config based on the given data.
DELETE
/api/v1/lanes/{laneId}
Delete lanes settings for lane with laneId.
GET
/api/v1/lanes/{laneId}
Retrieve specific lane settings.
PUT
/api/v1/lanes/{laneId}
Updates lanes settings.
Deprecated Features
None
Removed Features
None
Supported Devices
VeriFone Vx805
VeriFone Mx915, Mx925
Bug Fixes
Finanancial Track 1 data was being incorrectly parsed. This is now fixed.
Signature property is now returned in a sale response when no signature is provided.
Windows Installer will no longer duplicate existing lanes when upgrading
Fix bug in SendRequestAndViewReceipt sample app to allow JSON
Fix bug in SendRequestAndViewReceipt where failed/cancelled transactions were not handled well
More support has been added for the restaurant industry with the addition of Authorization and Authorization Completion. In addition, it is now possible to create a payment account token.
Breaking Changes
None
New Features / Improvements
Contactless Magnetic Stripe Data (MSD) support added for the VeriFone Mx and Vx series
Display tip percentages on PIN pad as currency amount
New endpoints
GET
/api/v1/
Returns an array of links for accessing triPOS
POST
/api/v1/cardAccountToken
Creates a card account token based on the given data.
PUT
/api/v1/cardAccountToken/{paymentAccountId}
Updates a card account token based on the given data.
POST
/api/v1/cardAuthorization
Creates a new card authorization based on the passed in parameters.
PUT
/api/v1/cardAuthorization/{transactionId}
Updates a previous card authorization with the final totals.
POST
/api/v1/cardSale/force/{approvalNumber}
Creates a new card force based on the passed in amounts.
GET
/api/v1/lanes/{LaneId}/status
Returns the current status of the given lane.
Deprecated Features
None
Removed Features
None
Supported Devices
VeriFone Vx805
VeriFone Mx915, Mx925
Bug Fixes
Modify the VeriFone Form Agent driver to allow for optional CVV entry
Expiration dates are now handled properly on the Vx for manual entry (originally MMYY entries became YYMM)