faq:vx805_emv_errors
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
faq:vx805_emv_errors [2020/01/21 10:15 (4 years ago)] – [Terminal Id not found in XML document] craig | faq:vx805_emv_errors [2024/01/31 09:22 (8 weeks ago)] (current) – [Duplicate Transactions] craig | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== EMV Pinpad Errors ====== |
===== No Response from Pinpad ===== | ===== No Response from Pinpad ===== | ||
* The wrong serial port is selected. | * The wrong serial port is selected. | ||
- | * [[ftp://ftp.windward-ca.com/pub/mercurypay/ | + | * [[https://datacapsystems.com/support-articles/how-to-change-pin-pad-interface-settings|The pinpad needs to be configured for USB Cabling]]. |
===== Expected DPT Encryption Got - NOE ===== | ===== Expected DPT Encryption Got - NOE ===== | ||
Line 12: | Line 12: | ||
* if it a Worldpay/ | * if it a Worldpay/ | ||
* https:// | * https:// | ||
+ | |||
+ | <note important> | ||
+ | |||
+ | ===== Datacap Configuration not found or is incorrect. ===== | ||
+ | * You have selected the incorrect pinpad | ||
+ | * The pinpad was not loaded with the datacap forms package. | ||
+ | * https:// | ||
+ | * https:// | ||
+ | * https:// | ||
+ | |||
===== vx805 Invalid Field - Encrypted Format ===== | ===== vx805 Invalid Field - Encrypted Format ===== | ||
- | * This means you have the wrong pinpad selected. | + | |
+ | * **Update dsiEMVX and dsiPDCX** to support new EMV transactions. | ||
+ | |||
+ | ===== Invalid trancode while performing a pre-auth on System Five version 6.4 ===== | ||
+ | * Ensure merchant is using datacap netepay version 5.07.30 (01/ | ||
====== Rapid Connect Error Messages ====== | ====== Rapid Connect Error Messages ====== | ||
Line 43: | Line 57: | ||
* utlities / diagnostics | * utlities / diagnostics | ||
* Gateway test | * Gateway test | ||
+ | {{: | ||
+ | |||
+ | ===== Other Not Accepted ===== | ||
+ | For a manual keyed transaction, | ||
+ | |||
+ | ===== Duplicate Transactions ===== | ||
+ | |||
+ | When the clerk receives a time out error, they should attempt the transaction a second time from the same invoice. | ||
+ | |||
+ | Your processor must have duplicate transaction checking turned on. When a duplicate transaction is sent (same invoice number and card number) and the processor returns Duplicate Transaction the clerk is presented with 3 options. Option 1 is the option the clerk should accept most of the time. | ||
+ | - **Retrieve approval information from previously errored transaction and apply payment** Select this option if you know that the first attempt to process the transaction failed and you attempted to approve the transaction a second time. | ||
+ | - **Reject Transaction** Select this option if you meant to process a duplicate transaction. Then process the amount on a different invoice number, card number or amount. | ||
+ | - **Force Duplicate** Select this option if you wish to force a duplicate transaction. | ||
+ | |||
+ | Duplicate transactions are usually the result of a time out error. | ||
+ | |||
+ | Duplicate transactions can be avoided by making sure you have a stable internet connection, that you are not using wireless networks. If you are having internet issues, test your internet with a web browser, not by attempting to process transactions. | ||
+ | |||
+ | If a timeout occurs between System Five and the remote POS device manager (cloud and terminal services), the remote pos device manager will also buffer the last transaction response. If a second identical request is made from System Five, the remote POS device manager will respond with the last response. | ||
+ | |||
+ | The datacap logs can help diagnose some issues. | ||
faq/vx805_emv_errors.1579630547.txt.gz · Last modified: 2020/01/21 10:15 (4 years ago) by craig