--- schema_version: "1" id: d92a2cbc98df5741371f3296cf3108f7285c6a3dee7c573bb084a34ce48c04e4 title: Use Fiserv (Mexico) to Make Payments collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/commerce/264-0-0/rt_cms_hardware_fiserv_mexico_payments.md canonical_url: https://help.salesforce.com/s/articleView?id=commerce.rt_cms_hardware_fiserv_mexico_payments.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: df8da8f9f2db2c64ff34822d2086e2a12a55ff3cd206ee45fb697094b655a574 description: Use the Point of Sale (POS) app to make payments with Ingenico Link 2500 terminals over Bluetooth. products: - Commerce release: "264" --- # Use Fiserv (Mexico) to Make Payments Use the Point of Sale (POS) app to make payments with Ingenico Link 2500 terminals over Bluetooth. ## POS Build, Platform Support & Technical Prerequisites - Modern POS App build: 7.10.5 or later - Platform Support: iPhone & iPad - Offline Support: no - This Link 2500 is only supported over Bluetooth ## Mobile Configuration Settings In **CMS > Modules > Peripherals**, set Fiserv for these flags in the **Card Readers** section - **Supported Card Readers For Store Associate Checkout**![Fiserv set as a supported card reader in the Mobile COnfiguration Settings section.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_supported_card_readers_fiserv.png) - **Default Card Reader**![Fiserv listed as the default card reader in the Mobile COnfiguration Settings section.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_default_card_reader_fiserv.png) ## Payment Gateway Settings In **CMS> Advanced > Payment Gateways**, create a Payment Gateway configuration for Fiserv by setting the **Store ID** value, which can be **DEFAULT** or specific store ID. Keep the default values for all other properties and save it. ![The pPayment Gateway Settings section configured for Fiserv.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_payment_gateway_settings_fiserv.png) ## Register Settings - In **CMS > Store management > Registers**, select the register ID which needs to be setup. - Move to the card reader section. - Select the model as “**Fiserv**” and connection type as “**Bluetooth**”. - Save the register settings.![The register settings configured for Fiserv.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_register_settings_fiserv.png) ## Return Policy Configuration All the returns done by Fiserv payment provider are unreferenced returns, so the CMS configuration needs to be enabled to handle the unreferenced refund flow. - In **CMS > Store management > Return policy configuration**, select the Online policy. - Scroll to the Unreferenced Refunds section and turn on the Allow Unreferenced refunds switch. - Select the payment method “**Credit Card**”. - Save the settings.![The refund fees settings configured for Fiserv.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_return_policy_config_fiserv.png) ## Software Update Deeplink Software updates on terminals can be triggered using **Update Card Reader Configuration Deeplink** on CMS. Deeplink can be added either in Hamburger menu or any layout on the POS app.![Update Card Reader Configuration set in the Select a Deep link section.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_software_update_deeplink_fiserv.png) ## Pair the Fiserv Terminal to iPad To make the device discoverable, press “**+**” key and type the “**47852**” code on the terminal. A new menu shows.![The menu on the payment terminal where you pair devices](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_terminal_fiserv_ipad.png) Press **F3** and move on to “**Phone Pairing**”. Press the green button to select it. This makes the device discoverable and you can pair it with the iPad.![The payment terminal showing the device name.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_ipad_discoverable_fiserv.png) Go to iPad Bluetooth settings and look for the Link2500 devices. Select the one ‌you want to pair it with. After the device is selected, the terminal shows a confirmation message.![A confirmation message with a mobile passkey on the terminal screen.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_terminal_confirm_fiserv.png) After the pairing is done successfully, go to the “**Paired Devices**” and you’ll see the paired iPad in the list. Also, the bluetooth icon on the top left of the screen turns green.![The Paired Devices section in ther terminal showing that the device is paired with an iPad.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_paired_devices_fiserv.png) Now the device is discoverable in the POS Device Manager ## Connect to Terminal in POS Device Manager Screen After the terminal is connected, it'll be seen and can be connected on the device manager screen of the POS app. If the terminal isn't visible, ‌select the refresh icon on the top right of the screen. Select “**Tap to Connect**” to connect to the terminal.![The Device Manager in the POS app where you can tap to connect the terminal.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_connect_terminal_pos_fiserv.png) ## Software update on Terminals Associates can select the **Update Card Reader** configuration deep link in the POS app to trigger a software update. If terminal isn't connected, then app shows an error message to connect to a terminal first. After the terminal is connected, updates begin to download and the terminal reboots after the updates finish. After the reboot is done and the terminal is ready, the associate connects to the terminal again and starts the payment transactions. To avoid any problems during any payment transaction, it is suggested that associates update the software on terminals at the start of the day. ## Terminal disconnection The POS app disconnects from the terminal if the Bluetooth connection drops, which can happen for multiple reasons. ## Reconnect to terminal upon payment If for some reason, Bluetooth connection gets dropped (terminal rebooted, iPad, or terminal's BLE was switched off), the app disconnects from the terminal and shows the option to connect to it again on the **Device Manager** screen. If the associate starts the transaction without connecting to the terminal, the app tries to connect to the device first and then starts the payment flow. Auto connection during the payment flow only happens if associated connected with the same device previously and connection was dropped. ## Payment using Card option in Cart Screen The **Credit Card** option in the **Unified Cart** screen allows you to initiate a payment for the order using the connected Fiserv terminal. If there's no Fiserv terminal to use for payment, the POS app takes you to the device manager screen to connect to a new terminal. The terminal asks you to put in or swipe the payment card. It processes the payment and gives you a message if the transaction is successful. If a payment is approved in Fiserv, the PS POS App shows a thank-you screen. If a payment is declined, the app shows the problem details in a popup. ## Card Payment in Multitender screen Card is one of the tender options in the multitender screen, and you can combine card payments with other tender options.![Add a credit card in the POS app on the multitender screen.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_card_payment_multitender_fiserv.png)![The multitender screen in the POS app where you can add more than one form of payment.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_multiple_payments_fiserv.png) ## Payment failure handling After processing the payment on the terminal, if the order submission fails, the POS app asks to start the refund flow. This confirms that the amount taken is returned to the user because the order wasn't placed successfully. This flow is applicable for unified card screen and multitender screen both.![A window that shows the transaction failed and gives you to option to start a refund.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_payment_failed_fiserv.png) After the refund is done successfully, the app refreshes the cart so the associate can start the transaction again. In case of refund failure, the app shows the option to "**Retry**" the refund or "**Skip**" it. Retry starts the refund flow again and **Skip** refreshes the cart. ![A window showing that the refund failed and gives you the option to skip the refund or retry.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_refund_failed_fiserv.png) ## Troubleshooting The sections below explain some common errors and how to solve them. ## Terminal beeps and show the “ESPERE POR FAVOR” message on the screen. “**ESPERE POR FAVOR**” isn't an error. The terminal is trying to sync some data and waiting for connection to be made.This is a process that happens automatically and it won’t represent any transactional blocker or stopper for processing further transactions. ## Test Terminal is showing the message “SIN CONFIGURACION” on screen. It means that the terminal doesn’t have any configuration downloaded to accept any transaction. Contact the Fiserv team for steps to download configuration. ## How to restart/reboot the terminal? To reboot the terminal, press the "**\-**" and the yellow "**<**" key together and it reboots. ## App is showing "Refund failed for " error while doing a refund transaction. This happens if the unreferenced refund policies aren't configured in Point of Sale CMS. Go through the Return Policy Configuration to make sure return policies are configured. ## App is showing error "Can not save order. Payment not authorized" while placing an order. This happens if the payment gateway settings aren't configured in Point of Sale CMS. ## App isn't showing the list of terminals on device manager screen. - Make sure iPad and terminal are bluetooth paired and connected. - Close and relaunch the app. - Go to **Device Manager** and select "**Refresh**" on the top right of the screen to get a list of terminals. - In case this issue persists, try rebooting the terminal and connecting to the iPad again. ## Limitations - More than one credit card payment on the multi tender screen is not supported using Fiserv terminals. - All the refunds are unreferenced refunds. - Order History search via credit card is not supported using Fiserv terminals. - Associates trigger the software update on terminals before store opening to avoid any update or reboot during the payment transactions. ## Receipt Elements Mexico CC payments have additional attributes to be shown based on the transaction. - **Customer Signature**—The receipt will have a signature section if the pinpad requires a customer signature for the CC transaction - **Authorized with PIN Message (version 8.3.1 and later)** - If the pinpad requires a pin entry, receipt includes the message "AUTHORIZED WITH ELECTRONIC SIGNATURE". - **Installments (version 8.3.1 and later)** - If the CC transaction is for installments, the receipt will show the installments information as well in the receipt lines. For this to work, make sure "**promotion**" key is added to the list of **Receipt Line Keys** in **ReceiptConfiguration > Settings**.![A Fiserv receipt with additional elemnts highlighted that are unique to Fiserv](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_fiserve_receipt_elements.jpeg)