# its\_cashback\_only {% columns %} {% column width="33%" %} ![](/files/L1sbo2d59Up3a6UBRsN1) {% endcolumn %} {% column %} **Description** Customer can insert, tap, or swipe a card. customer can view the items purchased by clicking the Basket icon present at the top right. \ **Configuration Parameters** `acquirer.ChipMaxTriesBeforeFallback` - Controls the number of times the customer is prompted to retry chip in case of chip read failure before the customer is prompted to fallback to MSR. Fallback can be disabled by setting this to 0. `acquirer.MsrMaxTriesBeforeFallback` - Controls the number of times the customer is prompted to retry MSR in case of MSR read failure before the customer is prompted to fallback to manual. Fallback can be disabled by setting this to 0. `Terminal.DisplayCardBrandLogos` - Controls displaying card brand logos on the card presentation screen. `CardBinRange.LuhnCheck` - If this is enabled and the luhn check fails for an MSR card, the card is declined. `CardBinRange.ExpiryDateCheck` - If this is enabled and expiry date checking fails for an MSR card, the card is declined. `CardBinRange.PanMinLen` - Minimum length to match the PAN `CardBinRange.PanMaxLen` - Maximum length to match the PAN `CardBinRange.ExtendedServiceCodeCheck` - If this is enables, the service code is checked to determine whether the card should be inserted \ **Error ScenariosFor chip cards,** Immediate Fallback to Card Swipe will be prompted after a single failed attempt for the following conditions: Card Expiry EMV Blocked When the card type is not supported for chip (i.e. no matching AIDs found) If there is a chip read error, the customer is asked to present the card again. If fallback is enabled, after the configured number of retries, the customer is prompted to use MSR. If no fallback is enabled, the device will keep asking customer to retry when the card is inserted. If the card is declined, the customer is notified that the card is declined and is asked to remove card. \ **For CTLS,** In case of a fallback to Chip, the customer is asked to insert the card In case other errors, the customer is asked to try again If the card is declined, the customer is notified that the card is declined \ **For Msr,** If there is MSR read error, the customer is asked to present the card again. If fallback is enabled, after the configured number of retries, the customer is prompted to use Manual entry. If no fallback is enabled, the device will keep asking customer to retry If the service code indicates a fallback, the customer is prompted to insert card If the card is expired and the expiry check is needed for this bin range, the card is declined If the card’s luhn check fails and the luhn check is needed for this bin range, the card is declined **For chip cards,** **For CTLS,** **For Msr,** If the customer cancels the transaction, payment not completed message will be shown If the screen times out, payment not completed message will be shown If the device crashes or device reboots while on this screen, when the payment application restarts or device boots up , no power failure recovery will happen {% endcolumn %} {% endcolumns %} \--- --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.verifone.com/functional-specification/its_cashback_only.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.