F25-POINT OF SERVICE (POS) CONDITION CODE: this is the field that defines the condition under which the transaction was performed at the POS.
It can take the following values:
| Value | Description |
| 00 | Normal presentment |
| 01 | Customer not present |
| 02 | Unattended terminal – card can be retained |
| 03 | Merchant suspicious |
| 04 | Electronic Cash Register interface |
| 05 | Customer present, card not present |
| 06 | Pre-authorized request |
| 07 | Telephone device required |
| 08 | Mail/telephone order |
| 09 | POS security alert |
| 10 | Customer identity verified |
| 11 | Suspected fraud |
| 12 | Security reasons |
| 13 | Representation of item |
| 14 | Public utility terminal |
| 15 | Customer's terminal |
| 16 | Administrative terminal |
| 17 | Returned item |
| 18 | No check in envelope - return |
| 19 | Deposit out of balance - return |
| 20 | Payment out of balance - return |
| 21 | Manual reversal |
| 22 | Terminal error - counted |
| 23 | Terminal error – not counted |
| 24 | Deposit out of balance - apply |
| 25 | Payment out of balance - apply |
| 26 | Withdrawal error - reversed |
| 27 | Unattended terminal – card cannot be retained Additional codes can be defined for private use. |
Practical use of F25
F25 indicates the conditions under which the transaction was carried out. If the cardholder is not present, the terminal is unattended, or the transaction is a mail or telephone order, this information becomes an input to the risk engine.
Based on the F25 value, the bank can apply different limit and verification rules. If the merchant sends an incorrect value, the transaction may be declined, or the merchant may run into problems in the event of a chargeback dispute.
Software teams should maintain a mapping table that sets F25 correctly based on terminal type and transaction type.
