• Accepts EMV chip cards, magnetic stripe cards, and contactless payments

• Utilizes Quest™ PCI-Validated P2PE for secure transactions

• Compatible with Clearent's Cloud EMV

• Ethernet

• USB

• Accepts EMV chip cards, magnetic stripe cards, and contactless payments

• Utilizes Quest™ PCI-Validated P2PE for secure transactions

• Compatible with Clearent's Cloud EMV

• Countertop

• Ethernet

• Wi-Fi

• Accepts EMV chip cards, magnetic stripe cards, and contactless payments

• Utilizes Quest™ PCI-Validated P2PE for secure transactions

• Compatible with Clearent's Cloud EMV

• Wireless

• Ethernet

• Wi-Fi

• GPR

• Accepts EMV chip cards, magnetic stripe cards, and contactless payments

• Utilizes Quest™ PCI-Validated P2PE for secure transactions

• Compatible with Clearent's Cloud EMV

• Countertop

• Ethernet

• Wi-Fi

• Supports EMV chip cards, magnetic stripe cards, and NFC contactless payments

• Internal PIN Pad and contactless

• Large touch screen

• Utilizes Quest™ PCI-Validated P2PE for secure transactions

• Compatible with Clearent's Cloud EMV

• Wireless

• GPRS

• Wi-Fi

• Supports EMV chip cards, magnetic stripe cards, and NFC contactless payments

• Large touch screen

• Supports external PIN Pad (QD3 PIN Pad)

• Utilizes Quest™ PCI-Validated P2PE for secure transactions

• Compatible with Clearent's Cloud EMV

• Ethernet

• Wi-Fi

• Accepts EMV chip cards, magnetic stripe cards, and NFC contactless payments

• Internal PIN Pad and contactless

• Large touch screen

• Utilizes Quest™ PCI-Validated P2PE for secure transactions

• Compatible with the QD4 terminal via a USB-to-USB (U-U) cable

• Ethernet

• Wi-Fi

• Bluetooth 4.0

• Smart Android PIN Pad Designed for Multilane Implementations Accepts Contactless, Chip, Magstripe

• Power Over Ethernet (POE)

• Utilizes Quest™ PCI-Validated P2PE for secure transactions

• Clearent’s Cloud EMV

• Semi-integration to Clearent’s Quest™ Gateway API

• Ethernet

• WiFi

• Smart Android Terminal Accepts Contactless, Chip, Magstripe

• Utilizes Quest™ PCI-Validated P2PE for secure transactions

• Compatible with Clearent's Cloud EMV

• Ethernet

• Wi-Fi

• Smart and Wireless Android Terminal Accepts Contactless, Chip, Magstripe

• Large HD screen

• Utilizes Quest™ PCI-Validated P2PE for secure transactions

• Compatible with Clearent's Cloud EMV

• WiFi

• Wireless

• GPRS

• Bluetooth

Secure and compact PIN pad with advanced security, versatile connectivity, and a user-friendly design for seamless payments.

Countertop terminal providing secure and efficient transactions, ideal for retail, restaurants, and service industries.

Durable wireless terminal for mobile payments, suitable for retail, hospitality, and mobile services.

Compact countertop terminal with a touchscreen interface.

Android-based mobile wireless PIN pad for flexible, on-the-go payments.

Android-based countertop terminal for businesses needing a stationary POS solution.

Compact Android-based mobile PIN pad that integrates with the QD4 terminal via USB.

High-performance Android Smart PIN pad for various retail scenarios.

Countertop device that also functions as a portable indoor terminal.

Mobile touchscreen Android terminal combining an Android tablet with a powerful payment processor.

Countertop payment reader supporting EMV chip, magnetic stripe, and NFC contactless payments.

Compact, versatile payment reader that accepts multiple payment methods, including Apple Pay and Google Pay.

• Accepts Contactless, Chip, Magstripe

• Utilizes Quest™ PCI-Validated P2PE for secure transactions

• Javascript SDK

• Quest™ Mobile Payments API

• Countertop

• USB

• Accepts EMV Chip, Magstripe, Contactless including Apple Pay and Google Pay

• Utilizes Quest™ PCI-Validated P2PE for secure transactions

• Mobile SDK

• Quest™ Mobile Payments API

• Audio jack

• Bluetooth

000

200

Approve

0.49, 0.80, 0.81, 0.82

003

402

Declined by Issuer – Card expired

0.29

004

402

Card Expired

0.05, 0.04

006

402

Allowable Pin Entries Exceeded

0.40

007

402

Declined by Issuer – Referred – Please call Card Issuer

0.01, 0.02

008

402

Declined by Issuer – Invalid Amount

0.11, 0.32

009

400

Invalid Card Number

0.14

010

402

Declined by Issuer – Account not found

0.36, 0.37, 0.38

011

400

Invalid Request

0.31, 0.35, 0.39

012

402

Not Sufficient Funds

0.21

014

402

Declined by Issuer – Exceeds amount limit

0.23, 0.70

015

402

Declined by Issuer – Transaction not permitted

0.43, 0.44

016

402

Declined by Issuer – Frequency limit exceeded

0.22, 0.25, 0.71

018

400

Invalid Pin

0.12, 0.13, 0.47

021

402

Declined by Issuer – Invalid card security code

0.48

022

400

Cashback Amount Exceeded

0.16

023

402

Transaction Declined By Issuer

0.04, 0.09, 0.15, 0.17, 51.00

024

402

Previously Reversed

0.1

027

402

Original Not Found

0.34

030

402

Invalid merchant ID – Please call Customer Support

0.46

031

402

Transaction Did Not Complete Normally, Please Retry

0.03

032

402

Duplicate Transaction

0.54

034

402

Card Lost

0.07

035

402

Card Stolen

0.08

037

200

Advice Accepted, No Action Taken

0.33

041

400

Field Validation

$0.00

000

200

This amount will trigger the sale to take over 60 seconds to process. Used to test timeout scenarios.- Only for Mobile Gateway

$999.00

000

200

This amount will trigger the sale to take over 60 seconds to process. Used to test timeout scenarios.- Only for transaction EMV

$1,000.00

M

The CSC matches the issuing bank’s records

N

The CSC does not match the issuing bank’s records

P

The CSC was not processed

S

The card should have a CSC, but merchant indicated it was not present

U

Card issuing bank does not participate

X

Unknown / No response

X

Match of address and 9-digit zip code

Y

Match of address and 5-digit zip code

W

Match of 9-digit zip code; address does not match

Z

Match of 5-digit zip code; address does not match

A

Address: Address Matches ZIP Does Not Match

N

No: Address and ZIP Do Not Match

G

Address information not verified

S

Service Not Supported: Issuer does not support address verification

U

Address information is unavailable

E

Error: Transaction ineligible for address verification

R

Retry: System Unavailable or Timeout

000

200

SUCCESS

001

400

Could not communicate with Terminal

001

404

Signature not found

002

500

Failed to process batch

002

402

Force Approval

002

400

Validation error

003

500

Failed to process batch

003

500

Declined by Issuer – Card expired

003

400

transaction-id required

005

402

Card Suspended

013

402

Transaction Not Permitted To Cardholder

017

402

Card Not Active

019

500

PIN Key sync error – Please call Customer Support

020

400

Invalid Currency

025

402

Exceeds Maximum Refundable Amount

026

402

Declined by Issuer – Invalid Card Number

028

402

Invalid Terminal – Please call Customer Support

029

402

Inactive Terminal

033

402

Capture Card, Please Call Processor

036

200

Advice Accepted

038

402

Reconciled, In Balance

039

402

Not Reconciled, Totals Provided

040

402

No Opened Batch

041

400

Field Validation

042

401

Unauthorized

043

400

Amount Minimum

044

400

Amount Maximum

045

402

Duplicate Transaction

046

402

Avs Response Not Accepted

047

402

Csc Response Not Accepted

048

402

Csc Response Not Accepted

049

500

No Response From Server

050

500

Internal Error

051

500

Could Not Connect

052

500

Exception Condition Contact Support

053

500

Exception Condition Contact Support

054

402

Data Element Error

055

500

Acquirer Not Supported By Switch

056

402

Transaction Destination Cannot Be Found

057

402

Card Issuer Timed Out

058

402

Card Issuer Unavailable

059

402

Duplicate Transmission

060

500

System Error, Database

061

402

Aborted, Threshold Exceeded

062

500

System misconfiguration: {MAY INCLUDE ADDITIONAL ERROR TEXT}

063

500

System Error, Transaction

064

500

System Error, Hsm

065

500

Configuration Error, Invalid Terminal

066

500

Configuration Error, Invalid Terminal

067

500

Configuration Error, Configuration Error

067

500

Configuration error, invalid merchant

068

500

Configuration Error, Configuration Error

068

500

Configuration error, inactive merchant

069

500

Configuration Error, Configuration Error

069

500

Configuration error, invalid store

070

500

Configuration error, inactive store

070

500

Configuration Error, System Error

071

500

System Error, Other

072

500

System Error Other

073

500

System Error Other

074

400

HPP Generic Error Message; query transaction for error details.

074

400

Invalid Request

074

400

Merchant-id from request does not match merchant-id of initial transaction

081

400

Create entity failed

081

400

Update entity failed

081

500

Update failed

082

400

Add entity failed

082

500

Add failed

082

404

Device not found

082

404

Entity not found

082

500

Get failed

083

400

Get entity failed

083

500

Get failed

083

400

Resource not found

084

500

Add Token To Customer Failed

084

400

Apikey on device does not belong to the terminal you have authenticated. Please check that the device was configured correctly

085

404

Unable to delete setting

085

400

Valid Content-Type Header Required for PUT or POST

086

400

Missing or Invalid Accept Type Header. Accept Type Header must be of type ‘application/json or ‘application/xml

087

400

Metadata can only have a maximum of ten key/value pairs

088

400

No body in request

089

200

Delete Successful

089

500

Error Deleting resource

089

400

Unable to delete Customer token

090

400

Required request body content is missing

090

400

Required request body content is missing, malformed, or datatype usage (ex- boolean, number) is invalid

091

402

Delete Token Failed. Token Associated With Payment Plan

091

204

No batch found to process

091

404

Object not found

091

404

Transaction not found

092

405

Http Method not supported

092

404

URL Parameter Invalid not found

093

400

Customer Delete Failed – Customer has active plans

093

400

Merchant Opt Out Delete Failed

094

400

Cannot delete Plan that has been used to charge the customer

280

400

Transaction failed

281

400

Void failed. Cannot void ach transactions that are returned or settled.

282

400

Authorization failed

283

400

Validation failed

284

400

ACH Account not found

285

400

Cannot process request. Contact Clearent for assistance

286

400

An error occurred we did not account for with Drools rules or otherwise

287

404

Transaction not found

288

400

Request failed

289

400

Provider failed

290

500

Transaction Failed

291

400

Cannot process request. Contact Clearent for assistance

292

404

Transaction not found

293

404

Transaction not found

294

500

Cannot process request. Contact Clearent for assistance

295

500

Cannot process request. Contact Clearent for assistance

880

400

Error parsing request

880

400

Error while submitting request to pax terminal

880

400

Failed to process hpp request.

880

400

Transaction failed

880

500

Unexpected Error – please contact customer support

881

400

Device communications unsupported

881

400

Manufacturer unsupported

882

400

Transaction type unsupported for this manufacturer

883

500

Terminal not connected

884

400

Terminal cannot be determined. Configure from Virtual Terminal Settings

884

400

Terminal cannot be determined. Confirm terminal is configured for Semi-Integrated mode

885

400

Device disabled

886

400

Failed to connect to Clearent Gateway. Please check device configuration

886

400

Terminal connection error

887

400

Transaction failed

888

400

Failed to serialize request as xml

889

400

Token only request failed

889

400

Transaction failed

890

400

Transaction endpoint does not match transaction type

8801

402

Could not determine if transaction succeeded or failed

8831

500

Terminal is busy. Check terminal and try again

13005

400

Signature not valid for HPP response

Amount must include two decimal places

Amount must only contain digits and a decimal point

Amount must be 0.00 for validate transaction

Amount required (absolute number with two decimal places)

Routing number required

Account number required

Individual name required

Account type required (Checking or Savings)

Routing number should be 9 digits

10.

Account number should be 1 to 17 digits

11.

Transaction-key should not be provided

12.

Valid values are ‘true’ or ‘false

13.

Type should be ‘Debit’ — Transfer funds from the customer bank account to your (merchant) bank account or ‘Credit’ — Transfer funds from your (merchant) bank account to customer bank account

14.

Software type required. Please provide the name of your software, product, or service

15.

Software type version required. Provide version of software-type

16.

Provider Account Id required

17.

Valid values are ‘Pending’, ‘Settling’, ‘Returned’, or ‘Settled’

18.

Invoice value required if invoice is the check-field

R02

Account closed A previously open account is now closed

R03

No account or unable to locate account The account number does not correspond to the individual identified in the entry or a valid account.

R04

Invalid account number The account number fails the check digit validation or may contain an incorrect number of digits

R05

Uncollected funds Available balance is sufficient, but the collected balance is not sufficient to cover the entry

R06

Returned per ODFI’s request The ODFI has requested that the RDFI return the entry

R07

Authorization revoked by customer Member who previously authorized an entry has revoked authorization with the Originator

R08

Payment stopped or stop payment on item Member had previously requested a stop payment of a single or recurring entry

R09

Uncollected funds Available balance is sufficient, but collected balance is not sufficient to cover the entry

R10

Customer advises not authorized Member advises not authorized, notice not provided, improper source document, or amount of entry not accurately obtained from source document

R11

Check truncation entry return To be used when returning a check truncation entry

R12

Branch sold to another DFI RDFI unable to post entry destined for a bank account maintained at a branch sold to another financial institution

R13

Invalid ACH routing number Financial institution does not receive commercial ACH entries

R14

Representment payee deceased or unable to continue in that capacity Representative payee is deceased or unable to continue in that capacity, beneficiary is not deceased

R15

Beneficiary of account holder deceased Beneficiary or Account Holder Deceased

R16

Account frozen Access to account is restricted due to specific action taken by the RDFI or by legal action

R17

File record edit criteria Fields rejected by RDFI processing (identified in return addenda)

R18

Improper effective entry date Entries have been presented prior to the first available processing window for the effective date.

R19

Amount field error Improper formatting of the amount field

R20

Nontransaction account Policies or regulations (such as Regulation D) prohibit or limit activity to the account indicated

R21

Invalid company identification The company ID information not valid (normally CIE entries)

R22

Invalid individual ID number Individual id used by receiver is incorrect (CIE entries)

R23

Credit entry refused by receiver Receiver returned entry because minimum or exact amount not remitted, bank account is subject to litigation, or payment represents an overpayment, originator is not known to receiver or receiver has not authorized this credit entry to this bank account

R24

Duplicate entry RDFI has received a duplicate entry

R25

Addenda error Improper formatting of the addenda record information

R26

Mandatory field error Improper information in one of the mandatory fields

R27

Trace number error Original entry trace number is not valid for return entry; or addenda trace numbers do not correspond with entry detail record

R28

Routing number or check digit error Check digit for the transit routing number is incorrect

R29

Corporate customer advises not authorized RDFI has been notified by business account holder that a specific transaction is unauthorized

R30

RDFI not participant in check truncation program Financial institution not participating in automated check safekeeping application

R31

Permissible return entry RDFI has been notified by business account holder that a specific transaction is unauthorized

R32

RDFI nonsettlement RDFI is not able to settle the entry

R33

Return of XCK entry RDFI determines at its sole discretion to return an XCK entry; an XCK return entry may be initiated by midnight of the sixtieth day following the settlement date if the XCK entry

R34

Limited participation DFI RDFI participation has been limited by a federal or state supervisor

R35

Return of improper debit entry ACH debit not permitted for use with the CIE standard entry class code (except for reversals)

R36

Return of improper credit entry

R37

Source Document Presented for Payment Check used for an ARC, BOC or POP entry has also been presented for payment

R38

Stop payment on source document Stop payment has been placed on a check used for an ARC entry

R40

Return of ENR entry by federal government agency (ENR only)

R41

Invalid transaction code (ENR only)

R42

Routing number or check digit error (ENR only)

R43

Invalid DFI account number (ENR only)

R44

Invalid individual ID number (ENR only)

R45

Invalid individual name/company name (ENR only)

R46

Invalid representative payee indicator (ENR only)

R47

Duplicate enrollment

R50

State law affecting RCK acceptance

R51

Item is ineligible, notice not provided, signature not genuine

R52

Stop payment on item

R61

Misrouted return Return entry was sent by RDFI to an incorrect ODFI routing/transit number

R62

Incorrect trace number

R63

Incorrect dollar amount

R64

Incorrect individual identification

R65