Return Codes List

Return Codes List

Numeric Return Codes (2 & 3-digit codes)

Because the list of all possible return codes is too large for a single page, this section describes the available numeric return codes with 2 or 3 digits.

Return Code

Description

Details

Merchant's Action Plan

00

Transaction approved

The transaction was completed without errors.

No action to take.

266

Transaction canceled

350

Transaction timeout

01

Guidance document / proposal refused

02

Refer to the card issuer

03

Invalid merchant

04

Declined – Seize card

The issuing bank sent a “seize card” status for reasons unknown.

Seize the card and contact the acquirer.

05

Transaction declined

The transaction was declined. This may be due to several reasons.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

06

Format error

A field (other than transaction code, amount, date, or card number) sent by the banking module as part of the transaction request is invalid or does not follow the acquirer’s criteria.

Retry the transaction with the same card. Retry the transaction with a different card. If the problem persists, contact PayFacto’s customer service.

07

Card seized / special conditions

08

Recognize with approved ID

09

Request being processed

10

Approved for a partial amount

11

VIP approved

12

Invalid transaction

The transaction code sent by the banking module as part of the transaction request is invalid or does not follow the acquirer’s criteria.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

13

Invalid amount

The amount sent as part of the transaction request is invalid or does not follow the acquirer’s criteria.

Confirm the amount and retry. If the problem persists, contact PayFacto’s customer service.

14

Invalid card number

The card number sent as part of the transaction request is invalid or does not follow the acquirer’s criteria.

Make sure you support this type of card and retry. Retry thetransaction with a different card. If the problem persists, contact PayFacto’s customer service.

15

Invalid issuer

16

Approved / update track 3

17

Canceled by the client

18

Conflict with the client

19

Retry transaction

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

20

Invalid response

21

No action taken

22

Suspected abnormality

23

Invalid transaction fees

The transaction fee amount sent as part of the transaction request is invalid or does not follow the acquirer’s criteria.

Confirm the transaction fee amount and retry. If the problem persists, contact PayFacto’s customer service.

24

Action File not received

25

Record not found

26

Duplicate record

27

System error – Acquirer

Problem with the acquirer’s system.

Retry the transaction. If the problem persists, contact the acquirer.

28

System error – Acquirer

Problem with the acquirer’s system.

Retry the transaction. If the problem persists, contact the acquirer.

29

System error – Acquirer

Problem with the acquirer’s system.

Retry the transaction. If the problem persists, contact the acquirer.

30

Invalid format

31

Bank not supported

32

Partially filled

33

Expired card

The client’s card is expired.

Retry the transaction with a different card.

34

Suspected fraud / seize card

35

Contact acquirer / seize card

36

Restricted card

The card is subject to restrictions and cannot be used.

Retry the transaction with a different card.

37

Call the security of the acquirer

38

Maximum number of PIN input attempts reached – Seize card

The maximum number of attempts to enter the PIN has been reached.

Seize the card and contact the acquirer.

39

No credit account linked to the card

There is no account linked to this card.

Retry the transaction with a different card.

40

Unsupported transaction

The requested transaction is not supported by the issuing bank.

Contact the acquirer.

41

Lost card

This card has been declared lost and deactivated.

Retry the transaction with a different card.

42

No universal account

43

Stolen card

This card has been declared stolen and deactivated.

Seize the client’s card and contact the acquirer.

44

No investment account

51

Insufficient funds

The client does not have sufficient funds in this account to perform the transaction.

Retry the transaction with a different card.

52

No checking account

There is no checking account linked to this card.

Retry the transaction with another account type or a different card.

53

No savings account

There is no savings account linked to this card.

Retry the transaction with another account type or a different card.

54

Expired card (from the issuing bank)

The client’s card has expired.

Retry the transaction with a different card.

55

Invalid PIN

The client has entered the wrong PIN.

Retry the transaction.

56

Inactive card

The issuing bank reports that this card has not been activated.

Retry the transaction with a different card.

57

Transaction not allowed with this card

This transaction cannot be performed with this card.

Retry the transaction with a different card. If the problempersists, contact PayFacto’s customer service.

58

Transaction not allowed on this terminal

The requested transaction cannot be performed on this terminal.

Contact PayFacto’s customer service.

59

Suspected fraud / refuse

60

Contact acquirer / refuse

61

Withdrawal limit exceeded for this account

The issuing bank has determined that the client has reached the maximum withdrawal amount.

Retry the transaction with a different card.

62

Limited use card

The issuing bank claims that this card is restricted. The card cannot be used at the moment.

Retry the transaction with a different card. If the problem persists, contact the acquirer.

63

MAC security failure

The MAC key is invalid.

Retry the transaction a few times (2 or 3). If the problem persists, contact PayFacto’s customer service.

64

Original amount incorrect

65

Card use frequency limit reached

The maximum number of withdrawals with this card has been reached.

Retry the transaction with a different card.

66

Call the security of the acquirer / refuse

67

No ATM

68

Response timed out

The maximum amount of time for the acquirer’s response has been reached.

Retry the transaction. If the problem persists, contact the acquirer.

75

Maximum number of PIN input attempts reached

The card has been blocked due to the high number of PIN entry attempts.

Retry the transaction with a different card.

77

Invalid transaction date

The transaction date sent by the banking module as part of the transaction request is not valid. It does not correspond to the current or next day’s date.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

78

Maximum number of invalid PINs reached

The card has been blocked due to the high number of PIN entry attempts.

Retry the transaction with a different card.

81

Invalid PIN block

Security problem.

Retry the transaction a few times (2 or 3). Retry the transaction with a different card. Contact PayFacto’s customer service.

82

PIN length error

The PIN must contain between 4 and 12 characters. The client is not entering the correct PIN.

Retry the transaction if the client requests it.

84

Invalid transaction sequence number

Synchronization problem with the acquirer.

Retry the transaction a few times (2 or 3). If the problem persists, contact PayFacto’s customer service.

87

PIN key synchronization error

Security problem.

Retry the transaction a few times (2 or 3). If the problem persists, contact PayFacto’s customer service.

88

MAC key synchronization error

Security problem.

Retry the transaction a few times (2 or 3). If the problem persists, contact PayFacto’s customer service.

90

Abort In progress

91

Issuing bank’s system is inoperative

The issuing bank’s system cannot be reached.

Contact the acquirer to report the problem.

92

Cannot find financial institution

The card’s issuing bank is unknown.

Retry the transaction with a different card.

93

Violation of the law

94

Duplicate transaction

The acquirer has already received this request.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

95

Error of approximation

96

Acquirer’s system is faulty

One or more of the acquirer’s processes are not functional.

Retry the transaction. If the problem persists, contact theacquirer to report the problem.


Numeric Return Codes (3XXX)

Because the list of all possible return codes is too large for a single page, this section describes the available numeric return codes between 3000 and 3999.

Return CodeDescriptionDetailsMerchant's Action Plan
3666One or more terminals are busyEach merchant has a set number of terminals. Code 3666 indicates that a transaction was sent by the merchant and all the merchant’s terminals are busy processing a transaction. This may be due to two causes: Pending transactions are all directed to a server, thus overloading the CT- Payment Solution; or The number of terminals is insufficient to support a merchant’s transaction during peak periods.If the problem persists, contact PayFacto’s customer service.
3667Semi-integrated terminal is busyA recovery is currently being processed.Wait 15 seconds and retry the transaction. If the problem persists, contact PayFacto’s customer service.
3668Waiting for a recoveryOn error has occurred with the semi-integrated terminal. A recovery must be executed before another transaction can be processed.Make sure everything is plugged in correctly. If needed, restart the driver, unplug and replug the power from the terminal. Wait 35 seconds and retry the transaction. If theproblem persists, contact PayFacto’s customer service.
3777Inexistent terminal and/or merchantA transaction merchant or terminal has not been configured in the Dispatcher module.If the problem persists, contact PayFacto’s customer service.

Numeric Return Codes (5XXX)

Because the list of all possible return codes is too large for a single page, this section describes the available numeric return codes between 5000 and 5999.

Return Code

Description

Details

Merchant's Action Plan

5000

Successful

No error.

Continue the transaction process according to the documentation.

5001

“Null” transaction code

The parameter is null or blank.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5002

Invalid size: transaction code

The parameter received does not respect the length given in the merchant’s API documentation.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5003

Code_rejected_cotrans

5004

“Null” value: company number

The parameter received is N or blank.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5005

Invalid size: company number

The parameter received does not respect the length given in the merchant’s API documentation.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5006

Rejected company number

5008

Invalid size: merchant number

The parameter received does not respect the length given in the merchant’s API documentation.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5009

Code_rejected_nummarch

5010

“Null” value: customer number

The parameter received is null or blank.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5011

Invalid size: customer number

The parameter received does not respect the length given in the merchant’s API documentation.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5012

Code_rejected_numclient

5013

“Null” value: amount

The parameter received is null or blank.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5014

Invalid size: amount

The parameter received does not respect the length given in the merchant’s API documentation.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5015

Code_rejected_montant

5016

“Null” value: invoice number

The parameter received is null or blank.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5017

Invalid size: invoice number

The parameter received does not respect the length given in the merchant’s API documentation.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5018

Code_rejected_numfact

5019

“Null” value: entry type

The parameter received is null or blank.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5020

Invalid size: entry type

The parameter received does not respect the length given in the merchant’s API documentation.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5021

Code_rejected_typesaisie

5022

“Null” value: card type

The parameter received is null or blank.

If the problem persists, contact PayFacto’s customer service.

5023

Invalid type: card type

The parameter received does not respect the length given in the merchant’s API documentation.

If the problem persists, contact PayFacto’s customer service.

5024

Code_rejected_typecarte

5025

“Null” value: card number

The parameter received is null or blank.

If the problem persists, contact PayFacto’s customer service.

5026

Invalid size: card number

As a result of human intervention, the length value is not valid.

If the problem persists, contact PayFacto’s customer service.

5027

Code_rejected_numcarte

5028

“Null” value: expiration date

The parameter received is null or blank.

If the problem persists, contact PayFacto’s customer service.

5029

Invalid size: expiration date

As a result of human intervention, the length value is not valid.

If the problem persists, contact PayFacto’s customer service.

5030

Code_rejected_dateexpi

5031

“Null” value: POS terminal number

The parameter received is null or blank.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5032

Invalid size: POS terminal number

As a result of human intervention, the length value is not valid.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5033

Code_rejected_numtpv

5034

“Null” value: language code

The parameter received is null or blank.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5035

Invalid size: language code

As a result of human intervention, the length value is not valid.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5036

Code_rejected_colang

5037

“Null” value: currency

The parameter received is null or blank.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5038

Invalid size: currency

As a result of human intervention, the length value is not valid.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5039

Code_rejected_devise

5040

“Null” value: cashier number

The parameter received is null or blank.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5041

Invalid size: cashier number

As a result of human intervention, the length value is not valid.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5042

Code_rejected_numcaissier

5043

“Null” value: “successful” URL

The parameter received is null or blank.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5044

“Null” value: “failure” URL

The parameter received is null or blank.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

5050

Customer’s time is up

The time allocated to the entry page was up before the customer could press the “Pay” button.

The customer must start the transaction over again. He/she has three minutes to enter his/her credit card data and press the Pay button.

5051

Interaction with the database has failed

1. The payment server cannot find the transaction information to be returned to the customer. 2. The payment server cannot connect to the payment solution database. 3. The payment solution database is not available to conduct a SQL request.

If the problem persists, contact PayFacto’s Customer Service.

5052

Invalid merchant

1. The merchant number in the request is not the one given in the PayFacto solution. 2. The merchant number is not configured on PayFacto’s servers.

Check your application. The field must correspond to the value provided by customer service when the payment solution was being integrated. If this is not the case, contact PayFacto’s customer service.

5053

Invalid company

1. The company number in the request is not the one given in the PayFacto solution. 2. The company number is not configured on PayFacto’s servers.

Check your application. The field must correspond to the value provided by customer service when the payment solution was being integrated. If this is not the case, contact PayFacto’s customer service.

5054

Inactive company

The customer is not active.

If the problem persists, contact PayFacto’s customer service.

5055

Invalid address

There is no configured address for the merchant.

Ask your customer administrator to configure the address in the management toolor contact PayFacto’s customer service.

5056

Code_error_redir_infos

5057

Code_error_client_address

5058

Code_error_url_cont_deta

5059

Code_error_card_list

5060

Session invalid or expired

The session is not valid or does not exist. The time has expired or the transaction has already been processed.

Start the transaction over.

5061

Code_w4redir_noresponse

5062

Code_w4redir_fatalerror

5071

Transaction cancelled by the customer

This happens when the client hits the “Cancel” button on the entry page.

The customer must start the transaction over if he/she has made an error. If not, processing ends.

5072

Invalid POST parameters

Acxsys returned parameters are invalid.

Contact PayFacto customer service.

5073

Transaction not completed

Transaction was not completed at the customer's financial institution.

Retry the transaction.

5074

IOP version not supported

The Interac online version returned by Acxsys is invalid

Contact PayFacto customer service.

5075

Invalid redirection URL

Acxsys redirection session parameters are invalid.

Contact PayFacto customer service.

5076

Invalid or expired session

The session is invalid or expired.

Retry the transaction.

5077

Cancellation of the transaction on the receipt page

Transaction cancelled by the customer on the receipt page.

Retry the transaction

5079

Transaction cancelled

Transaction is cancelled (ACK not received) before merchant's request for redirection's response

Retry the transaction

5110

Raw_Buf invalid

Encryption status. Impossible to decrypt the data received from the merchant API.

If the problem persists, contact PayFacto’s customer service.

5111

Decrypting is impossible

Encryption status. Impossible to decrypt the data received from the merchant API.

If the problem persists, contact PayFacto’s customer service.

5112

Backup request

Encryption status. The merchant’s unique identifier is not the one supplied in the API; the server recommends performing security encryption.

If the problem persists, contact PayFacto’s customer service.

5113

Merchant’s unique identification number is not valid

The merchant’s unique identification number is not valid.

If the problem persists, contact PayFacto’s customer service.

5800

Code_fatal_sql_exception

5801

Code_fatal_crypt_exception

5802

Code_fatal_user_api_exception

5803

Code_fatal_protocol_exception

5804

Code_fatal_sym_crypt_exception

5805

Code_fatal_unknown_exception

5806

Code_fatal_unknown_trx_exception

5807

Code_fatal_unknown_sid_exception

5808

Code_fatal_mercapi_exception

Numeric Return Codes (6XXX)

Because the list of all possible return codes is too large for a single page, this section describes the available numeric return codes between 6000 and 6999.

Return Code

Description

Details

Merchant's Action Plan

6000

Invalid file

Check file. If the problem persists, contact PayFacto’s Customer Service.

6001

Batch number already used

The batch number must be unique. Change the number and resend the file. If the problem persists, contact PayFacto’s Customer Service.

6002

Incorrect parameter in a transaction

One or more transactions have a parameter in an incorrect format. Check file. If the problem persists, contact PayFacto’s Customer Service.

6003

Invalid number of transactions

The number of transactions specified in the header does not match the number of transactions in the file. Check the file. If the problem persists, contact PayFacto’s Customer Service.

6004

Invalid header

The header has an invalid format. Check the file. If the problem persists, contact PayFacto’s Customer Service.

6005

Invalid merchant

The merchant specified in the header does not match the merchant whose batch is to be processed. Check the file. If the problem persists, contact PayFacto’s Customer Service.

6006

Cannot decrypt

Make sure that the file was properly encrypted and transmitted. If the problem persists, contact PayFacto’s Customer Service.

6007

Decryption error

If the problem persists, contact PayFacto’s Customer Service.

6008

Cannot encrypt

If the problem persists, contact PayFacto’s Customer Service.

6009

Encryption error

If the problem persists, contact PayFacto’s Customer Service.

6010

Cannot move file

The file could not be moved from the “out” directory to the “done” directory because of the FTP server security settings. Make sure that that user name used by PayFacto has the necessary rights to move files. If the problem persists, contact PayFacto’s Customer Service.

6012

No transaction found

A batch must contain at least one transaction. If the problem persists, contact PayFacto’s Customer Service.

6013

Invalid extension for an unencrypt file

The file extension must be CSV or TXT.

The extension must match the specifications stated in the documentation. If the problem persist, contact PayFacto’s customer service.

6014

Invalid extension for an encrypt file

The file extension must be ENC.

The extension must match the specifications stated in the documentation. If the problem persist, contact PayFacto’s customer service.

6015

An error occurred while archiving the file.

If the problem persists, contact PayFacto’s customer service.

6016

The batch processing number is invalid.

Verify the batch processing number.

The batch processing number must match the specifications stated in the documentation. If the problem persist, contact PayFacto’s customer service.

6020

Transaction timeout

Check the transaction report to determine whether that transaction was processed.If the problem persists, contact PayFacto’s Customer Service.

Numeric Return Codes (8XXX)

Because the list of all possible return codes is too large for a single page, this section describes the available numeric return codes between 8000 and 8999.

Return CodeDescriptionDetailsMerchant's Action Plan
8101Null value : client numberThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8102Invalid value : client numberThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8103Null value : nameThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8104Invalid value : nameThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8105Null value : emailThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8106Invalid value : emailThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8107Null value : credit cardThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8108Invalid value : credit cardThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8109Null value : expiration dateThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8110Invalid value : expiration dateThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8111Null value : tokenThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8112Invalid value : tokenThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8113Null value : languageThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8114Invalid value : languageThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8115Unknown client numberThe value of this field does not exist on the server.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8116Client not verifiedClient is not verified.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8117Client has no cardThere is no credit card associated with this client.Add a credit card to the client record.
8118Pre-authorization check failedThe pre-authorization to check if the card is valid to the issuer, failed.Check your transaction list to obtain the reason why it was refused.
8119Invalid value : statusThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8120Invalid value : merchant idThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8121Null value : sessionThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8122Unknown value : sessionThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8123Invalid value : sessionThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8124Invalid value : URLThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8125Invalid length : URLThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8130Invalid value : beginning dateThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8131Invalid value : end dateThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8132Invalid value : account numberThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8133Invalid value : descriptionThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8134Invalid value : TokenThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8135Invalid value : IDThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8136Wrong ID numberThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8137Wrong tokenThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8138Invalid value : merchantThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8139Invalid value : statusThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8140Invalid value : amountThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8141Invalid value : frequencyThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8142Invalid value : currencyThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8143Invalid value : number of withdrawalThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8144Wrong statusThe value of this field does not match the value on the server.Retry the transaction. If the problem persists, contact PayFacto’s customer service.
8145Wrong subscription numberThe value of this field does not match the value on the server.Retry the transaction. If the problem persists, contact PayFacto’s customer service.
8146Invalid recurring amountThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8147Invalid subscriberThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8148Invalid merchantThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8149Invalid next bill dateThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8150Invalid invoice numberThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8151Invalid invoice statusThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8152Wrong tokenThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8153Invalid last bill dateThe value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8154The start date must be earlier than the end date.The value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8155The next bill date must be earlier than the end date.The value of this field does not follow the specifications stated in the recurrence documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.
8156Invalid value: CVVThe value of this field does not follow the specifications stated in the documentation.Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

Return Code

Description

Details

Merchant's Action Plan

9001

Null value: transaction code

The received parameter is either null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9002

Invalid length: transaction code

The received parameter doesn’t follow the required length mentioned in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9003

Rejected value: transaction code

The received parameter is not in the list of possible values for this field, as mentioned in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9004

Null value: company number

The received parameter is either null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9005

Invalid length: company number

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9006

Rejected value: company number

The received parameter is not configured in the payment solution.

Make sure that the application uses the correct company number, provided by PayFacto when the payment solution was integrated. Ifit does, contact PayFacto’s Customer Service.

9007

Null value: merchant number

The received parameter is either null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9008

Invalid length: merchant number

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9009

Rejected value: merchant number

The received parameter is not configured in the payment solution.

Make sure that your application uses the merchant number provided by PayFacto when the payment solution was integrated. If it does, contact PayFacto’s Customer Service.

9010

Null value: customer number

The received parameter is either null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9011

Invalid length: customer number

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9012

Rejected value: customer number

The received parameter doesn’t follow the specifications described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9013

Null value: amount

The received parameter is either null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9014

Invalid length: amount

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9015

Rejected value: amount

The received parameter doesn’t follow the specifications described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9016

Null value: bill number

The received parameter is either null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9017

Invalid length: bill number

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9018

Rejected value: bill number

The received parameter doesn’t follow the specifications described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9019

Null value: input type

The received parameter is either null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9020

Invalid length: input type

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9021

Rejected value: input type

The received parameter is not in the list of possible values for this field, as mentioned in the documentation, or the input type is valid but not associated with the merchant.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9022

Null value: card type

The received parameter is either null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9023

Invalid length: card type

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9024

Rejected value: card type

The received parameter is not in the list of possible values for this field, as mentioned in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9025

Null value: card number

The received parameter is either null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9026

Invalid length: card number

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9027

Rejected value: card number

The received parameter doesn’t follow the specifications described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9028

Null value: expiration date

The received parameter is either null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9029

Invalid length: expiration date

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9030

Rejected value: expiration date

The received parameter doesn’t follow the specifications described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9031

Null value: POS terminal number

The received parameter is either null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9032

Invalid length: POS terminal number

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9033

Rejected value: POS terminal number

The received parameter doesn’t follow the specifications prescribed in the documentation, or the merchant is not a POS terminal merchant.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9034

Null value: language code

The received parameter is either null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9035

Invalid length: language code

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9036

Rejected value: language code

The received parameter is not in the list of possible values for this field, as mentioned in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9037

Null value: currency

The received parameter is either null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9038

Invalid length: currency

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9039

Rejected value: currency

The received parameter is not in the list of possible values for this field, as mentioned in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9040

Null value: operator id

The received parameter is either null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9041

Invalid length: operator id

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9042

Rejected value: operator id

The received parameter is rejected, because it does not respect the specifications of the field mentioned in the documentation.

Check your application. The field must correspond to the given specification in the documentation; If it is not the case; contact the PayFacto customer service.

9043

Database error

The parameter received was null.

Contact PayFacto’s Customer Service.

9044

Empty character

[banking module’s response]

The received parameter is null.

If the problem persists, contact PayFacto’s Customer Service.

9045

Invalid response

Invalid response coming from the monitoring transactions.

You should not receive this return code. It is reserved for an internal PayFacto solution application.

9046

Incomplete response

The Dispatcher module’s response is incomplete according to the communication protocol. This is often caused by a communication problem.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9047

Banking module protocol error

Critical error recording a terminal’s status into the database.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9048

Submitted twice

The bill number submitted has already been used for another transaction and the merchant’s management tool’s configuration prohibits bill duplicates.

Configure the application so as not to send the same bill number twice,or contact PayFacto’s Customer Service to modify the configuration in order to allow the change.

9049

Fatal error 1

A critical error occurred while processing the transaction.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9050

Fatal error 2

A critical error occurred while processing the transaction.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9051

Time out

Transaction processing has timed out. This is often caused by an inactive Dispatcher module.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9052

Protocol error

9053

Server error

9054

Inactive merchant code

POS terminal merchant is deactivated in the payment solution’s configuration.

If the problem persists, contact PayFacto’s Customer Service.

9055

Database error

A critical error occurred while processing the transaction with the database.

If the problem persists, contact PayFacto’s Customer Service.

9056

Null value: original invoice number

The received parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9057

Invalid length: original invoice number

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9058

Rejected value: original invoice number

The received parameter was rejected because it does not follow the documentation’s guidelines.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9059

Terminal busy

In POS terminal mode, the terminal passed as a parameter is busy processing a transaction. This may occur when two transactions are sent simultaneously to the same terminal.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9060

Terminal busy in Dispatcher

In POS terminal mode, the terminal passed as a parameter is unavailable in the Dispatcher module. This can be caused by a reversal, which congests the terminal for a moment.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9061

Invalid response

Invalid response coming from the monitoring transactions.

No return code should appear. It is reserved for an internal PayFactosolution application.

9062

Company number does not match that of original transaction

The original transaction number you submitted exists, but is not associated with your company number. This code is possible for refunds without a card and preauthorization transactions.

Check your application .You may perform preauthorization or refunds without a card only for original transactions performed in your business. Make sure you have the correct original transaction number and company number.

9063

Merchant number does not match that of original transaction

The original transaction number you submitted exists but is not associated with your merchant number. This code is possible for refunds without a card and preauthorization transactions.

Check your application. You may perform preauthorization or refunds without a card only for original transactions performed in your business. Make sure you have the correct original transaction number and company number.

9064

Original invoice number does not match that of original transaction

The original transaction number you submitted is different from that received when processing the original transaction. This code is possible for refunds without a card and preauthorization transactions.

The original invoice number must be the same as that of the original transaction.

9065

Original transaction is not a purchase

You are trying to perform a refund without a card for an original transaction that is not a purchase.

You may only perform refunds without a card for purchase transactions. Make sure you have the correct original transaction number.

9066

Invalid original transaction status

The original transaction’s status is invalid and does not allow you to perform the transaction. The transaction was most likely declined or cancelled. This code is possible for refunds without a card and preauthorization transactions.

Make sure the original transaction has a suitable status for the transaction you just tried. If it does, contact PayFacto’s Customer Service.

9067

Original authorization number does not match that of the original transaction

The authorization number parameter you have entered exists, but is not associated with your merchant number. The original authorization number or the original transaction number may be incorrect.

Check your application. The original authorization number must matchthat of the original transaction that you are trying to perform (preauthorization). Ensure that you have the correct original transaction number.

9068

The original transaction number does not match any actual transaction

There is no transaction in the system matching the original transaction number you have sent. This code is possible for refunds without a card or preauthorization transactions.

Check your application. Make sure that you are sending the correct original transaction number.

9069

Original transaction is not a preauthorization

The original transaction parameter sent during the transaction is not a refund.

Check your application. You may only perform preauthorization transactions. Make sure that you are sending the correct original transaction number.

9070

Code_null_notx_orig

9071

Code_invalidsize_notx_orig

9072

Code_rejected_notx_orig

9073

Code_cancelation_code_tran_mismatch

9074

Code_cancelation_alreadycanceled

9075

Code_cancelation_unabletocancel

9076

Code_cancelation_fatalerror

9077

Code_null_nbtxtotal

9078

Code_invalidsize_nbtxtotal

9079

Code_rejected_nbtxtotal

9080

Code_null_grandtotal

9081

Code_invalidsize_grandtotal

9082

Code_rejeted_grandtotal

9083

Code_null_nbtxach

9084

Code_invalidsize_nbtxach

9085

Code_rejected_nbtxach

9086

Code_null_totalach

9087

Code_invalidsize_totalalach

9088

Code_rejected_totalalach

9089

Code_null_nbtxremb

9090

Code_invalidsize_nbtxremb

9091

Code_rejected_nbtxremb

9092

Code_null_totalremb

9093

Code_invalidsize_totalremb

9094

Code_rejected_totalremb

9095

Code_null_nbtxannul

9096

Code_invalidsize_nbtxannul

9097

Code_rejected_nbtxannul

9098

Code_null_totalannul

9099

Code_invalidsize_totalannul

9100

Code_rejected_totalannul

9101

Code_no_record_found

9102

Invalid length: original reference number

The parameter received doesn’t respect the length that the documentation mentioned.

No return code should be received. It is reserved for an internal PayFacto solution application.

9103

Invalid length: original authorization number

The parameter received doesn’t respect the length that the documentation mentioned.

No return code should be received. It is reserved for an internal PayFacto solution application.

9104

Code_null_noauto

9105

Code_invalidsize_noauto

9106

Code_batch_not_ready_to_close

9107

Invalid amount for cancellation manager

The amount of the cancelled transaction is not equal to the amount of the original transaction

9108

Completion error

There was an error completing a preauthorization.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9109

Preauthorization already completed

A preauthorization has already been performed for the transaction. You can only perform a preauthorization once.

Check your application. Make sure that the preauthorization has not already been performed.

9110

Amount is too high for transaction

The transaction amount is higher than that of the preauthorization. The transaction amount must be equal to or lower than the preauthorization number.

Check your application. Make sure that the amount you are sending is equal to or lower than the preauthorized amount when performing thetransaction.

9111

Raw buffer impossible

Decryption status. Cannot decrypt the data sent by the merchant API.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9112

Cannot decrypt

Decryption status. Cannot decrypt the data sent by the merchant API.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9113

Backup requested

Decryption status. The merchant’s unique identifier is not that provided by the API; the server recommends switching to safety encryption.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9114

Merchant cannot perform transaction

This transaction is deactivated in the payment solution’s configuration.

Contact PayFacto’s Customer Service to enable this transaction in your configuration.

9115

Administrative transaction in progress

A batch closing process is in progress for this merchant. No transaction can be performed while closing a batch.

Wait a few moments and retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9116

Transaction code is not compatible with input type

A refund without card is attempted for a POS terminal merchant (PIN pad input). You cannot perform a refund without card transaction on a PIN pad.

Check your application. Make sure that you have not sent the refund transaction without card on a point-of-sale terminal.

9117

Null value: track field

The received parameter is either null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9118

Invalid length: track field

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9119

Rejected value: track field

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9120

Invalid transaction with selected input type

The selected transaction type cannot be performed with this input type.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9121

Validation status of the verification code is invalid

The transmitter received an invalid verification code.

Retry the transaction

9122

Validation status of the verification code is invalid (CVV/CVC2 = N)

The transmitter received the verification code but the received code does not correspond with that which should be on the chart.

Communicate with the cardholder to check the three digits code beforecarrying out the transaction even if the request for authorization were approved. Retry the transaction

9123

Validation status of the verification code is invalid (CVV/CVC2 = S)

The transmitter could not carry out the verification of the three digits code and warns the merchant that the card should contain a three digits code.

Communicate with the cardholder to check the three digits code beforecarrying out the transaction. Retry the transaction.

9126

Invalid token

The received parameter doesn’t follow the length described in the documentation or is valid but not associated with the merchant/client.

Verify your data. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9127

Inactive client

The received token matches a client who was removed from the recurrence.

Verify your data.

9128

Invalid transaction for the acquirer

The transaction type is not supported by the acquirer.

Contact PayFacto’s Customer Service.

9129

Invalid input type for the acquirer

The input type is not supported by the acquirer.

Contact PayFacto’s Customer Service.

9130

Invalid transactions status for a recovery

The transaction is not in a valid status for a recovery.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9131

Recovery impossible for the terminal

The recovery can only be done with a semi-integrated terminal.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9132

Card Bin blocked

AThe Card Bin was blocked by risk team to avoid Bin attacks.

The client must use another card.

9133

Token with expired credit card

Received token matches a customer with an expired credit card.

You must obtain customer's new credit card information and update the customer profile in order to process transaction with that token.

9134

Token with no credit card

Received token corresponds to a customer who has no credit card in his profile.

You must obtain customer's credit card information and update the customer profile in order to process transaction with that token.

9135

Invalid length: Transaction ID

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9136

Rejected value: Transaction ID

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9137

Invalid transaction with selected input type

The selected transaction type cannot be performed with this input type.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9138

Invalid Acquirer configuration

Acquirer selected for the merchant is invalid.

Contact PayFacto’s Customer Service.

9139

Invalid transaction for the acquirer

The transaction type is not supported by the acquirer.

Contact PayFacto’s Customer Service.

9140

Invalid length: Issuer confirmation number

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9141

Rejected value: Issuer confirmation number

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9142

Invalid length: Issuer name

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9143

Rejected value: Issuer name

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9144

“Null” value: AVS Address

The parameter is null or blank.

Check your application. The field must correspond to the specificationprovided in the documentation. If it does not, contact PayFacto’s customer service.

9145

“Null” value: Postal code

The parameter is null or blank.

Check your application. The field must correspond to the specificationprovided in the documentation. If it does not, contact PayFacto’s customer service.

9146

Validation status of the verification code is invalid (AVS = Z)

9147

Validation status of the verification code is invalid (AVS = A)

9148

Validation status of the verification code is invalid (AVS = N)

9149

Validation status of the verification code is invalid (AVS = U)

9149

Invalid length : CAVV

The value of this field does not follow the specifications stated in the recurrence documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9150

“Null” value: XID

The parameter is null or blank.

Check your application. The field must correspond to the specificationprovided in the documentation. If it does not, contact PayFacto’s customer service.

9151

Invalid length : XID

The value of this field does not follow the specifications stated in the recurrence documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9152

Invalid length : UCAF

The value of this field does not follow the specifications stated in the recurrence documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9155

Transaction not cancellable.

The original transaction type is not cancellable.

The merchant must retry with another original transaction.

9160

Invalid length: OEM Wallet Data

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9161

Rejected value: OEM Wallet Data

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9162

Original transaction is not an In-App Purchase

Original transaction provided is not an In-App Purchase.

Make sure you have the correct original transaction number.

9163

Original transaction is not an In-App refund

Original transaction provided is not an In-App Refund.

Make sure you have the correct original transaction number.

9164

Null value:TUID

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9165

Invalid length:TUID

The received parameter doesn’t follow the length described in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9166

Rejected value:TUID

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9200

Null value : Transaction type

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9201

Invalid length : Transaction type

The value of this field does not follow the specifications stated in the recurrence documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9202

Rejected value : Transaction type

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9203

Null value: Debit type

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9204

Invalid length : Debit type

The value of this field does not follow the specifications stated in the recurrence documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9205

Rejected value : Debit type

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9206

Null value: Start date

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9207

Invalid length : Start date

The value of this field does not follow the specifications stated in the recurrence documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9208

Rejected value : Start date

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9209

Null value: End date

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9210

Invalid length : End date

The value of this field does not follow the specifications stated in the recurrence documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9211

Rejected value : End date

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9212

Null value: Frequency

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9213

Invalid length : Frequency

The value of this field does not follow the specifications stated in the recurrence documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9214

Rejected value : Frequency

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9215

Null value: Number of debits

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9216

Invalid length : Number of debits

The value of this field does not follow the specifications stated in the recurrence documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9217

Rejected value : Number of debits

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9218

Fatal error

9219

Rejected value : Batch number

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9220

Invalid length : Batch number

The value of this field does not follow the specifications stated in the recurrence documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9221

Batch not open

9222

Batch not found or not closable

9223

Batch total not found

The selected batch does not exist or is empty

The merchant must use another batch number.

9224

CAVV Status : P

9225

CAVV Status : F

Transaction refused

Retry the transaction with a valid CAVV value.

9226

CAVV Status : N

9227

Pending transaction

The transaction is pending for acknowledgement

Acknowledge the transaction and retry.

9228

Protocol: maximum number of send attempts reached

9229

Batch error

9230

CODE_BATCH_OPERATION_NOT_ALLOWED_SIMULATION_LOT

9231

Void impossible

9233

CODE_DISPLAY_TEXT_NULL

9234

CODE_DISPLAY_TEXT_INVALIDSIZE

9235

Recurring options error

isCredential, isInstallment & isCredentialOnFile are mutually exclusive options

Submit one of the three options

9300

Null value : Amount

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9301

The CVV value does not correspond to the card type.

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9302

Null value : IOP Transaction number

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9303

Rejected value : IOP Transaction number

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9304

Rejected value : Expiration date

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9305

Null value :CVV/CVC2

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9306

Rejected value : CVV/CVC2

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9307

Null value :Type CVV/CVC2

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9308

Rejected value : CVV/CVC2 Type

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9309

Null value : Transaction date

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9310

Null value : Financial information

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9311

Null value : Card holder

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9312

Null value : Card holder first name

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9313

Null value : Card holder last name

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9314

Null value : Card holder address

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9315

Rejected value : Card holder name

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9316

Rejected value : merchant owning institution

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9317

Null value : Merchant status

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9318

Null value : Date de la dernière modification

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9319

Null value : Transaction status

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9320

Null value : Merchant

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9321

Rejected value : Advanced options type

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9322

Rejected value : Advanced options

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9323

Null value : IOP number

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9324

Rejected value : IOP Number

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9325

Rejected value : Manageable option type

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9326

Rejected value : Simple option

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9327

Rejected value : Simple option type

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9328

Null value : Simple Option

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9329

Null value : Client terminal number

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9330

Null value : Bank terminal number

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9331

Null value : Serial number

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9333

Rejected value : Bank terminal number

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9334

Rejected value : Numéro de terminal bancaire

The value must be alphanumeric.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9335

Rejected value : Client terminal number

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9336

Rejected value : Serial number

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9337

Rejected value : Serial number

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9338

Rejected value : Serial number

La valeur du champ doit être alphanumérique.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9339

Null value :Terminal

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9340

Null value : System

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9341

Null value : Keep alive

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9342

Rejected value : Keep alive

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9343

Rejected value in that context : keep alive

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9344

Null value : Configuration

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9345

Null value : Owner

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9346

Null value : Owner id

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9347

Null value : Owner name

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9348

Null value : Processing transaction information

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9349

Null value : Processing transaction information type

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9350

Null value : Processing transaction token information

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9351

Rejected value : Processing transaction information

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9352

Null value : Province

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9353

Rejected value : Province

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9354

Null value : Transaction category

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9355

Null value : Creation date

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9356

Null value : Transaction Id

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9357

Null value : Transaction status

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9358

Null value : Transaction number

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9359

Invalid transaction

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9360

Null value : Transaction data

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9361

Null value : One of the transaction data

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9362

Null value : Terminal database identifier

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9363

Rejected value : Settlement date

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9364

Null value : Last modify date

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9365

Null value : Settlement status

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9366

Null value : Settlement configuration

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9367

Null value : Identifier (id)

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9368

Rejected value : Owner

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9369

Null value :Connect Timestamp

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9370

Null value :Use Timestamp

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9371

Null value :Terminal Id

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9372

Rejected value : Terminal Id

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9373

Null value :Terminal

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9374

Rejected value : Bill type

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9375

Rejected value : Bill Prefix

The received parameter was rejected: it does not follow the field’s specifications stated in the documentation.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9376

Null value : Now date

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9377

Null value : Recur Merchant

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9378

Rejected value : Reference Number

The parameter is null or blank.

The field must match the specifications stated in the documentation; If it does, contact PayFacto’s Customer Service.

9500

Number of attempts to submit request exceeded

Number of attempts exceeded.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9501

Transaction refused by the acquirer

The transaction is refused. Several reasons are possible

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9502

The amount exceeds the maximum amount of the acquirer.

The transaction is refused.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9503

The processor for the acquirer’s transactions is not found.

The transaction is refused.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9504

Rejected value : Owner

The transaction’s holder is not a merchant.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9505

The transaction can’t be processed because the chosen terminal is already reserved.

Retry the transaction with a non-reserved terminal.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9506

The chosen terminal does not belong to the merchant.

Retry the transaction with a terminal owned by the merchant.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9507

Merchant found.

Retry with a valid merchant.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9508

Merchant not found.

Retry with a valid merchant.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9509

Null value : Converted merchant

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9510

Merchant internal id not found.

Retry with a valid merchant.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9511

Multiple merchant found.

Retry with a valid merchant.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9512

Terminal not found.

Retry with a valid terminal.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9513

Null value : Terminal number sequence

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9514

Terminal found.

Retry with a valid terminal.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9515

Null value : Converted terminal

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9516

Transaction settings insertion failed.

Contact PayFacto’s Customer Service.

9517

Transaction settings deletion failed.

Contact PayFacto’s Customer Service.

9518

Null value :Converted settlement configuration

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9519

Settlement update failed.

Contact PayFacto’s Customer Service.

9520

Settlement configuration not found.

Contact PayFacto’s Customer Service.

9521

Multiple settlement configuration found.

Contact PayFacto’s Customer Service.

9522

Client not found.

Retry with a valid client.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9523

Terminal status not found.

Retry with a valid terminal status.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9524

Terminal found.

Retry with a valid terminal.

Retry the transaction. If the problem persists, contact PayFacto’s Customer Service.

9525

Null value :Converted terminal

The parameter is null or blank.

Check your application. The field must match the specifications stated in the documentation. If it does, contact PayFacto’s Customer Service.

9800

SQL fatal error

The payment server was unable to send a request to the database.

Retry the transaction. If the problem persists, contact PayFacto’sCustomer Service.

9801

Cannot decrypt message contents

The payment server was unable to decrypt the merchant API’s message.

Retry the transaction. If the problem persists, contact PayFacto’sCustomer Service.

9802

Merchant API version error

The merchant API’s version is not compatible with the payment server.

Retry the transaction. If the problem persists, contact PayFacto’sCustomer Service.

9803

Data Validation Error

The payment informations returned by the acquirer do not match PayFacto data.

Retry the transaction. If the problem persists, contact PayFacto’sCustomer Service.

9804

reCAPTCHA verification failed

This is most likely a fraudulent transaction being attempted by a bot.

Decline the transaction.

9991

Fatal error for a purchase for TPVV

9992

Fatal error for a refund for TPVV

9993

Fatal error for a cancellation for TPVV

9994

Fatal error for a batch process for a TPVV

9995

Fatal error for other transaction for TPVV

9996

Fatal error for other transaction for TOTAL

9999

Fatal error



A-prefix Return Codes

The following table lists all return codes that begin with the letter A:

Return CodeDescriptionDetailsMerchant's Action Plan
A0Payment server did not return a transaction response (API)Possible network problem.Retry the transaction. If the problem persists, contact PayFacto’s customer service.
A1Communication problem with payment server (API)A problem occurred while sending the message. Either there is a network problem or the payment server is down.Retry the transaction. If the problem persists, contact PayFacto’s customer service.
A2Problem sending the transaction to payment server (API)Possible network problem.Retry the transaction. If the problem persists, contact PayFacto’s customer service.
A3Problem writing transaction list (API)Internal banking module problem.If the problem persists, contact PayFacto’s customer service.
A4Response problem (API)There is a problem with the payment server’s response. It may be caused by a TCP network problem.Retry the transaction. If the problem persists, contact PayFacto’s customer service.

B-prefix Return Codes

The following table lists all return codes that begin with the letter B:

Return Code

Description

Details

Merchant's Action Plan

B1

Bank manager error

An error was detected in the banking module. One or more fields were not received.

If the problem persists, contact PayFacto’s customer service

B2

Invalid sequence number

This return code is similar to code 84 but is for administrative transactions

You should not receive this return code. It is reserved for an internal PayFacto solution application.

B3

Transaction code not supported by terminal

The transaction is unsupported by the acquirer’s configuration for this terminal.

If this transaction must be supported, contact PayFacto’s customer service.

B4

Card not supported by terminal

This card number is not supported by the acquirer.

If this card type must be supported, contact PayFacto’s customer service.

B5

Invalid acquirer’s response format

The server cannot recognize the format of the acquirer’s response.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

B6

Network switch is incapable of delivering the message

B7

Format of the header for the banking response is invalid

The header of the purchaser’s received answer is invalid, possibly because of a telecommunication problem. This transaction cannot be reversed. It is possible to have an imbalance during batch closure.

Contact PayFacto’s customer service to reverse the transaction. Retry the transaction.

BH

Maximum number of PIN tries reached


H-prefix Return Codes

The following table lists all return codes that begin with the letter H:

Return Code

Description

Details

Merchant's Action Plan

H0

No available session

Internal banking module problem.

If the problem persists, contact PayFacto’s customer service.

H1

Link out of order

Link 3201 (or another dedicated link) is down.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

H2

Telecommunication session closing in progress

A problem with the link to the acquirer may have occurred while a transaction was waiting to be sent.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

H3

Application cannot establish telecommunication link because its data structures are full

There is not enough available memory to establish a connection.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

H4

Invalid parameter

The received request’s format is invalid.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

H6

The received data is corrupted


M-prefix Return Codes

The following table lists all return codes that begin with the letter M:

Return Code

Description

Details

Merchant's Action Plan

M0

Batch closing required

The transaction log has reached its maximum capacity, or the maximum number of transactions per batch is reached. A batch closing will be initiated automatically upon reception of this code.

Wait a few moments and retry the transaction. If the problem persists, contact PayFacto’s customer service.

M1

Terminal is not initialized

The terminal was not initialized after being installed or has not been redefined in the CT- Payment Solution’s banking module. Upon receipt of this return code, the banking module automatically initiates a transaction to load banking parameters in the terminal.

Wait a few moments and retry the transaction. If the problem persists, contact PayFacto’s customer service.

M2

Attempting to cancel an unknown transaction

The transaction to be cancelled is in a batch file which was already closed or the data indicated on the original transaction at the time of cancellation are incorrect. To cancel a transaction, it is necessary that it be in an active batch file.

You should not receive this return code. It is reserved for an internal PayFacto Solution application.

M3

Treatment of the SAF

M4

Invalid transaction

The transaction data is invalid.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

M5

Invalid transaction amount

The transaction amount is invalid (missing, zero or negative).

Retry the transaction with a valid amount.

M6

Invalid card number

The card number is either missing or incorrect.

Retry the transaction with a valid credit card matching the selected input type.

M7

Invalid card expiration date

The client’s card has expired.

Retry the transaction with an unexpired card.

M8

Error processing acquirer’s response

The main module has timed out. The banking module has received a response, but the main module has not received the transaction’s response.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

M9

Partial success of a multi-purchaser transaction

MA

Administrative transaction failure

The transaction failed for all acquirers.

You should not be receiving this return code. It is reserved for aninternal PayFacto Solution application.

MB

Request to close a batch file which is already closed

MC

Priority reversal pending in the SAF (Store and Forward) file

There is a reversal pending in the banking module. No other transaction can be performed until the reversal is completed.

Wait a few moments and retry. If the problem persists, contact PayFacto’s customer service.

MD

Confirmation message of the purchaser on standby in SAF

ME

Main module detected invalid response

The response was not adequately processed because one or more transactional fields are missing in the response.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

MF

Rectification forced by HPOS

MH

Cancelled transaction

The transaction that you tried to cancel was already cancelled successfully.

You should not receive this return code. It is reserved for an internal PayFacto solution application.

MI

The terminal indicates that the batch is off balance (between the terminal and the acquirer)

The batch will be closed and the reconciliation files created. (If configurated)

MJ

The terminal indicates that the batch is empty. The batch has been closed manually or automatically at the terminal)

The batch will be closed and the reconciliation files created. (If configurated)

P-prefix Return Codes

The following table lists all return codes that begin with the letter P:

Return Code

Description

Details

Merchant's Action Plan

P2

PIN pad module error

An internal error was detected by the PIN pad.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

P3

PIN pad communication error

Communication error between the payment server and the PIN pad driver, or between the PIN pad driver and the PIN pad.

Make sure that the PIN pad is properly connected and that the PIN pad driver is operational. In the PIN pad configuration module, make sure that the IP address and the port are accurate;Retry the transaction. If the problem persists, contact PayFacto’s customer service.

P4

Transaction authentication error

The PIN pad has detected a security problem with the acquirer’s response.

Retry the transaction a few times. If the problem persists, contact PayFacto’s customer service.

P5

PIN pad timed out

The client did not confirm the transaction on the PIN pad within the allotted time.

Retry the transaction if the client requests it.

P6

Transaction cancelled by client on PIN pad

The client pressed the PIN pads ANNUL/CANCEL button.

Retry the transaction if the client requests it.

P108

CONTACTLESS DECLINED CARD ERROR

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P120

HOST INVALID DATA

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P121

SENDING TRX WHEN TERMINAL WAITING FOR REVERSAL IF REVERSAL FAILS TRX CANCELLED

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P122

OPERATION NOT SUPPORTED

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P200

SALE ADD TIP CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P201

SALE ADD TIP PERCENTAGE PRESET 1 CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P202

SALE ADD TIP PERCENTAGE PRESET 2 CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P203

SALE ADD TIP PERCENTAGE PRESET 3 CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P204

SALE ADD TIP PERCENTAGE OTHER CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P205

SALE ADD TIP AMOUNT CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P206

SALE SWIPE INSERT TAP KEY CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P207

SALE CASHBACK CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P208

SALE CASHBACK UP CASHBACK PRESET 1 CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P209

SALE CASHBACK UP CASHBACK PRESET 2 CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P210

SALE CASHBACK UP CASHBACK PRESET 3 CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P211

SALE CASHBACK UP CASHBACK AMOUNT CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P212

SALE SELECT ACCOUNT CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P213

SALE SELECT ACCOUNT CARD REMOVED

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P214

SALE SELECT ACCOUNT CHEQUING ENTER PIN CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P215

SALE SELECT ACCOUNT SAVING ENTER PIN CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P216

PRE AUTH SWIPE INSERT TAP KEY CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P217

PRE AUTH NO SUPPORTED APPLICATIONS CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P218

PRE AUTH NO SUPPORTED APPLICATIONS SWIPE KEY CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P219

PRE AUTH NO SUPPORTED APPLICATIONS INVALID CARD CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P220

REFUND SWIPE INSERT TAP KEY CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P221

REFUND SELECT ACCOUNT CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P222

REFUND SALE SELECT ACCOUNT CARD REMOVED

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P223

REFUND SELECT ACCOUNT CHEQUING ENTER PIN CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P224

REFUND SELECT ACCOUNT SAVING ENTER PIN CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P225

VOID SWIPE INSERT TAP KEY CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P226

VOID SWIPE INSERT TAP KEY ENTER PIN CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P227

CASH ADD TIP CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P228

CASH ADD TIP PERCENTAGE PRESET 1 CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P229

CASH ADD TIP PERCENTAGE PRESET 2 CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P230

CASH ADD TIP PERCENTAGE PRESET 3 CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P231

CASH ADD TIP PERCENTAGE OTHER CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P232

CASH ADD TIP AMOUNT CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P233

VERIFY ACCOUNT SWIPE INSERT TAP KEY CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P234

SWIPE PROMPT MERCHANT PASSWORD CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P235

SWIPE PROMPT LAST 4 DIGITS CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P236

MANUAL ENTRY PROMPT MERCHANT PASSWORD CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P237

MANUAL ENTRY PROMPT EXPIRY DATE CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P238

MANUAL ENTRY PROMPT CVV CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P239

VERIFY ACCOUNT PIN CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P240

CREDIT PIN CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P241

SALE PIN CARD REMOVED

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P242

REFUND PIN CARD REMOVED

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P243

SWIPE INSERT TAP KEY CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P244

MANUAL ENTRY PROMPT CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P245

VOID PIN CARD REMOVED

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P246

CASHBACK PRESET 1 CARD REMOVED

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P247

CASHBACK PRESET 2 CARD REMOVED

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P248

CASHBACK PRESET 3 CARD REMOVED

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P249

CASHBACK AMOUNT CARD REMOVED

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P250

CREDIT PIN CARD REMOVED

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P251

SALE GENERIC CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P252

CASH GENERIC CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P270

AMOUNT CONFIRMATION SCREEN CANCEL

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P300

SALE ADD TIP TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P301

SALE ADD TIP PERCENTAGE PRESET 1 TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P302

SALE ADD TIP PERCENTAGE PRESET 2 TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P303

SALE ADD TIP PERCENTAGE PRESET 3 TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P304

SALE ADD TIP PERCENTAGE OTHER TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P305

SALE ADD TIP AMOUNT TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P306

SALE SWIPE INSERT TAP KEY TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P307

SALE CASHBACK TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P308

SALE CASHBACK UP CASHBACK PRESET 1 TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P309

SALE CASHBACK UP CASHBACK PRESET 2 TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P310

SALE CASHBACK UP CASHBACK PRESET 3 TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P311

SALE CASHBACK UP CASHBACK AMOUNT TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P312

SALE SELECT ACCOUNT TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P313

SALE SELECT ACCOUNT CHEQUING ENTER PIN TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P314

SALE SELECT ACCOUNT SAVING ENTER PIN TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P315

PRE AUTH SWIPE INSERT TAP KEY TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P316

PRE AUTH NO SUPPORTED APPLICATIONS TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P317

PRE AUTH NO SUPPORTED APPLICATIONS SWIPE KEY TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P318

PRE AUTH NO SUPPORTED APPLICATIONS INVALID CARD TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P319

REFUND SWIPE INSERT TAP KEY TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P320

REFUND SELECT ACCOUNT TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P321

REFUND SELECT ACCOUNT CHEQUING ENTER PIN TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P322

REFUND SELECT ACCOUNT SAVING ENTER PIN TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P323

VOID SWIPE INSERT TAP KEY TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P324

VOID SWIPE INSERT TAP KEY ENTER PIN TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P325

CASH ADD TIP TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P326

CASH ADD TIP PERCENTAGE PRESET 1 TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P327

CASH ADD TIP PERCENTAGE PRESET 2 TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P328

CASH ADD TIP PERCENTAGE PRESET 3 TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P329

CASH ADD TIP PERCENTAGE OTHER TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P330

CASH ADD TIP AMOUNT TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P331

VERIFY ACCOUNT SWIPE INSERT TAP KEY TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P332

SWIPE PROMPT MERCHANT PASSWORD TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P333

SWIPE PROMPT LAST 4 DIGITS TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P334

MANUAL ENTRY PROMPT MERCHANT PASSWORD TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P335

MANUAL ENTRY PROMPT EXPIRY DATE TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P336

MANUAL ENTRY PROMPT CVV TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P337

VERIFY ACCOUNT PIN TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P338

CREDIT PIN TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P339

SWIPE INSERT TAP KEY TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P340

MANUAL ENTRY PROMPT TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P341

SALE GENERIC TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P342

CASH GENERIC TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P344

SALE ADD TIP PERCENTAGE SELECT PRESET TIMEOUT

Abandonment tracking return code. This return code give the screen or menu where the transaction was cancelled or timeout.

Please retry the transaction if the client requests it.

P7

Magnetic card reading error

The card is illegible (demagnetized) or was not properly swiped in the terminal.

Retry the transaction. If the problem persists, retry the transaction with a different card.

P8

Error on number of tracks

P9

Terminal busy

The terminal indicates that it is busy.

Retry the transaction. If the problem still persists, unplug and replug the power from the terminal. If the problem still persists, contact PayFacto’s customer service.

PD

Unexpected Terminal Behavior

PE

NAK received from terminal

The terminal indicates it can’t process the transaction.

Retry the transaction. If the problem still persists, unplug and replug the power from the terminal. If the problem still persists, contact PayFacto’s customer service.

PF

Driver reset

The user has selected “Free terminal” while a transaction is in progress on the terminal.

The merchant must keep a copy of the terminal receipt. Do not resend the transaction if the receipt indicates that the transaction was approved.

PN

Bank module internal error

Unexpected error with the main payment application.

If the problem persists, contact PayFacto’s customer service.

PP

Transaction reversed

Receipt shows approved transaction but SOFTPAY application didn’t return an authorization code and has reversed the transaction.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

PQ

No recovery data available

Recovery data is unavailable in the terminal recovery file.

Check your application. The field must correspond to the specification provided inthe documentation. If it does not, contact PayFacto’s customer service.

PR

Communication error with terminal

Communication error. The transaction has been sent but no response has been received. A recovery will be done automatically by PayFacto to try to get the response from the terminal.

The merchant must keep a copy of the terminal receipt. Do not resend the transaction if the receipt indicates that the transaction was approved. Make sure everything is plugged in correctly.

PS

Following PR, the recovery can’t get the information for the transaction.

The transaction can be accepted, refused or cancelled. The communication error can be caused by the power cable, the serial cable or the network cable that was unplugged during the transaction.

Nothing to do. If the problem persists, contact PayFacto’s customer service.

PT

Following PR, the recovery can’t get the information for the transaction.

The transaction can be accepted, refused or cancelled. The communication error can be caused by the power cable or the network cable that was unplugged during the transaction.

Nothing to do. If the problem persists, contact PayFacto’s customer service.

PU

Communication error with terminal

Communication error between the driver and the terminal.

Make sure the serial cable of the terminal is plugged correctly inthe computer running the driver.

PV

Error communicating with terminal

Following the information of reconnection, the pilot never sent to the transaction terminal.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

PW

Driver restarted while a transaction is in progress

The driver was restarted while a transaction is in progress on the terminal. The transaction can be accepted, refused or cancelled.

The merchant must keep a copy of the terminal receipt. Do not resend the transaction if the receipt indicates that the transaction was approved.

PX

Can’t write on driver’s hard disk.

The driver can’t write his work file on the disk, either because it does not have write permissions on the directory, either because the chosen directory does not exist.

Verify the driver configuration. If no directory is configured, press the “Log file” to check the location of the log file. The working file is written in the same directory as the log file. Checkthe write permissions on this directory.

PZ

Timeout

The driver did not receive a response from the terminal within the prescribed time.

Make sure there is no current transaction on the terminal. Retry the transaction. If a transaction is in progress on the terminal, press the ANNUL/CANCEL button on the terminal before you resubmit the transaction.



Q-prefix Return Codes

Return CodeDescriptionDetailsMerchant's Action Plan
Q0Invalid transaction dateThe transaction date sent by the banking module as part of the transaction request does not follow the acquirer’s criteria.Retry the transaction. If the problem persists, contact PayFacto’s customer service.
Q7Merchant’s amount limit reachedThe transaction’s amount is greater than the acquirer’s limit.Split the transaction into smaller portions.
Q9Unknown errorAn error different from those mentioned has occurred.Retry the transaction. If the problem persists, contact the acquirer.

T-prefix Return Codes

The following table lists all return codes that begin with the letter T:

Return Code

Description

Details

Merchant's Action Plan

T0

Transaction already in progress for requested terminal

The terminal is busy. A transaction is in progress.

Wait a few moments and retry. If the problem persists, contact PayFacto’s customer service.

T1

HPOS internal error

General error in the HPOS module.

If the problem persists, contact PayFacto’s customer service.

T2

Payment application received a format error

The format of the message sent to the payment server was incorrect. It may be due to the format of the payment server’s date.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

T3

Terminal number not found on payment server to which transaction was sent

The POS terminal number sent to the payment server is not set up on the server.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

T4

Wrong API version


Z-prefix Return Codes

The following table lists all return codes that begin with the letter Z:

Return Code

Description

Details

Merchant's Action Plan

Z0

Prolongation – time passed for the TPV

Z1

Acquirer’s response timed out

This code is usually due to a communication problem or to the acquirer’s response timing out.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

Z2

Acquirer unavailable Connection between payment solution and/or acquirer’s two host sites is severed

The TCP/IP reports that the opening of a socket with the acquirer’s primary and secondary host systems has failed.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

Z3

Server problems

Z4

Transaction’s PIN pad interaction timed out

PIN pad interaction timed out. The client has not entered the necessary information within the allotted time.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

Z5

No dial tone

Z6

Invalid phone number

Z7

Failed modem connection

Z8

Occupied line

Z9

Redialling on the line

ZA

Connection between payment solution and acquirer is severed

Link problem.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

ZB

Protocol: maximum number of send attempts reached

The acquirer’s host system has answered, but there are problems sending the transaction.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

ZC

Protocol: timed out

The acquirer’s host system has answered, but there are timeout problems when communicating.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

ZD

Connection 3201 between payment server and acquirer was severed while sending a transaction (poll code down or link down).

The payment solution cannot see the poll code, or link 3201 is severed.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

ZE

Communication driver internal error

General communication error. The payment server’s 3201 driver may not be operational.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

ZF

Connection disabled

ZG

No response for code DATAPAC

ZH

No response for the PROF command

ZI

Acquirer’s primary host site unavailable Connections between payment solution and acquirer are severed

The TCP/IP driver reports that the opening of a socket with the acquirer’s primary host system has failed.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.

ZJ

Acquirer’s secondary host site unavailable. Connections between payment solution and secondary acquirer are severed

The TCP/IP driver reports that the opening of a socket with the acquirer’s secondary host system has failed.

Retry the transaction. If the problem persists, contact PayFacto’s customer service.






    • Related Articles

    • Android PayFacto Error Codes

      This page lists the meaning of error codes if the application rejects the transaction. Error code value Description -1 No extra data -2 Amount or the Invoice sent is invalid -3 Transaction type is invalid -4 Invoice sent is already used or do not ...
    • Address Verification Status (AVS) Result Codes

      INTRODUCTION During a transaction where the customer's card is not presented at the merchant's location (inputType : I or M), the merchant can enter the address corresponding to his credit card statement on the payment page. This validation technique ...
    • Payment Manager User Guide

      INTRODUCTION Foreword Due to the administrative interface, the client can control all transactions that are transmitted by its representatives or clients to the PayFacto server. With this tool the client can assigns users, who may then generate ...
    • Transactions Activity Result

      On the onActivityResult(int requestCode, int resultCode, Intent data) The Intent data will contain the return value as extra all in String value. If there is a problem with the data sent to the application, an error code will be sent back into the ...
    • Batch Payments

      Introduction Batch payment allows a merchant to prepare a file containing a list of transactions that will subsequently be processed by PayFacto’s solution. The files may be submitted manually via PayFacto Solution’s on-line interface, or more ...