File validation error
|Error cases||Cause of the error|
|The “REQ” file is always present in the directory. /depot||A technical incident prevented the files from being processed. Contact the tech support.|
|The “ANS” file is absent from the /id directory.||Your REQ file has been rejected.
Check for a _ERROR or _DUPLICATE file in the /depot directory.
|Presence of a file _ERROR||
|Presence of a file _DUPLICATE||A file with the same name has already been processed.|
Errors while processing the file, visible in the response file
In the table below, the lines for which the return code (position 19) is set to 00 are not errors and are indicated for information purposes for better understanding.
Additional return code
|Description / Cause of the error|
No risk assessment processes enabled.
|00||00||Payment accepted. All risk assessment processes successfully completed.|
Credit card velocity exceeded. The control is informative.
The card is on the Merchant’s greylist. The control is informative.
The country of origin of the card is on the Merchant’s greylist. The control is informative.
|00||05||Payment accepted. The IP address is on the Merchant’s greylist. The control is informative.|
The BIN code is on the Merchant’s greylist. The control is informative.
|00||07||Payment accepted. Detection of an e-carte bleue. The control is informative.|
|00||08||Payment accepted. Detection of a national commercial card. The control is informative.|
|00||09||Payment accepted. Detection of a foreign commercial card. The control is informative.|
|00||14||Payment accepted. Detection of a card that requires systematic authorization. The control is informative.|
No corresponding countries (country IP address, card country, buyer's country). The control is informative.
The country of the this IP address belongs to the greylist. The control is informative.
|00||99||Payment accepted. Technical issue encountered by the server during a local verification process.|
An communication error occurred during the authorization request.
The card number does not match the selected payment method.
The payment method exp. date does not allow to process this action.
The risk assessment has caused transaction refusal.
All risk assessment processes successfully completed.
See the authorization return code (position 20) to know the refusal reason.
|30||1||The record code must be set to 02.|
|30||2||The format of the record sequence number is incorrect.|
|30||3||The format of the payment date is incorrect.|
|30||4||The format of the payment time is incorrect.|
|30||5||The format of the transaction ID is incorrect.|
|30||6||The transaction type must be populated with CD.|
|30||7||The amount format is incorrect.|
|30||8||The currency is unknown or its format is incorrect.|
|30||13||The format of the order reference is incorrect.|
|96||contratAccepteur.nomatch.cardtype.notaccepted||The contract number defined in position 12 in the query file does not support the type of payment method corresponding to the alias/token defined in position 11.|
|96||transaction.exist||The transaction number defined in position 5 in the query file already exists.|
|96||identifiant.cardpurged||The payment method associated with the token is no longer valid.
In compliance with the banking data security and protection rules implemented by PCI DSS, the payment method details are destroyed after the associated token has not been used for 15 months.