{"title":"Bespoke interaction on the terminal","category":"default","creationDate":1776961628,"content":"<p>You can use the payment terminal to interact with the customer, by sending input requests and display requests to the terminal.<\/p>\n<ul>\n<li>Using <a href=\"#collect-information\">input requests<\/a> you can collect personal details from customers, ask for their consent (for example, to store their details, or to enroll in your loyalty program), or get feedback.<\/li>\n<li>Using <a href=\"#show-information\">display requests<\/a> you can show static or animated images on the terminal display, a QR code with a URL to something that you want to draw attention to, or an overview of the customer's purchase.<\/li>\n<\/ul>\n<h2>Requirements<\/h2>\n<p>To use payment terminals in this way:<\/p>\n<ul>\n<li>You need to have a Terminal API integration using either cloud or local communications.<\/li>\n<li>When using input requests, you need to implement logic in your back-end system to process the received input.<\/li>\n<li>When you collect personal details, you need to consider <a href=\"\/pt\/unified-commerce\/shopper-engagement#data-privacy\">data privacy<\/a>.<\/li>\n<\/ul>\n<h3 id=\"data-privacy\">Data privacy<\/h3>\n<p>Before storing any customer data, including payment data, you need to consider data privacy.<\/p>\n<ul>\n<li>Consult your legal department or an accredited third-party company to understand the data privacy regulations of the countries\/regions that you operate in.<\/li>\n<li>Ask for your customer's explicit permission to store their data, and be clear about what you intend to use it for.  For this, you could use the Terms and Conditions on your website, or you can <a href=\"\/pt\/unified-commerce\/terminal-interaction\">use the payment terminal to interact with the customer<\/a>. <\/li>\n<\/ul>\n<p>If the customer asks to remove their information, you can use our <a href=\"\/pt\/development-resources\/data-protection-api\">Data Protection API<\/a> to remove any customer-related data that you have stored with Adyen. The API also enables you to comply with the General Data Protection Regulation (GDPR) <a href=\"https:\/\/gdpr-info.eu\/art-17-gdpr\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">right to erasure<\/a>.<\/p>\n<h2 id=\"collect-information\">Collect information<\/h2>\n<p>An input request lets you gather information from your customer or staff. There are several types of input request:<\/p>\n<ul>\n<li><a href=\"\/pt\/point-of-sale\/shopper-engagement\/shopper-input\/confirmation\">Confirmation<\/a>: show some information and ask the user to confirm they agree.<\/li>\n<li><a href=\"\/pt\/point-of-sale\/shopper-engagement\/shopper-input\/signature\">Signature<\/a>: show some information and ask the user to confirm by supplying their signature.<\/li>\n<li><a href=\"\/pt\/point-of-sale\/shopper-engagement\/shopper-input\/menu\">Multiple choice\u2014single answer<\/a>: show a multiple-choice question and let the user select one of the answers. You can use this for NPS surveys, order lists, and such.<\/li>\n<li><a href=\"\/pt\/point-of-sale\/shopper-engagement\/shopper-input\/multi-menu\">Multiple choice\u2014multiple answers<\/a>: show a multiple-choice question and let the user select more than one of the answers.<\/li>\n<li><a href=\"\/pt\/point-of-sale\/shopper-engagement\/shopper-input\/digit\">Digit<\/a>: ask for numeric input, like a zip code. Another example is a pay-at-table flow where you ask your staff for the table number. This input accepts input of whole numbers.<\/li>\n<li><a href=\"\/pt\/point-of-sale\/shopper-engagement\/shopper-input\/amount\">Amount<\/a>: ask for an amount. This input request shows the currency and accepts input of a number with two decimals.<\/li>\n<li><a href=\"\/pt\/point-of-sale\/shopper-engagement\/shopper-input\/phone-number\">Phone number<\/a>: ask for a telephone number. The country code is prefilled based on the location of the terminal, but can be changed.<\/li>\n<li><a href=\"\/pt\/point-of-sale\/shopper-engagement\/shopper-input\/rating\">Rating<\/a>: show a question and let the user select a rating from 0 to 10.<\/li>\n<li><a href=\"\/pt\/point-of-sale\/shopper-engagement\/shopper-input\/text\">Text<\/a>: you'd typically use this to collect an email address.<\/li>\n<\/ul>\n<p>For each input type, we provide predefined elements to show on the terminal display, and fields that you need to populate with your own text. The user enters a response with the terminal keypad or the on-screen keyboard and buttons.<\/p>\n<p>You can make these input request before or after a payment, or as part of a payment flow involving <a href=\"\/pt\/unified-commerce\/loyalty-program\">shopper recognition<\/a>. For example, if<\/p>\n<p>Note that the communication flow is between your POS app and the terminal, and does not involve the Adyen backend. You need to process the collected input with your own business logic.<\/p>\n<p>Here are some examples of what it looks like on terminal displays of various sizes when you ask for information through input requests.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\"><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Ask for personal details: <br> <img alt=\"\" src=\"\/images\/8\/0\/f\/5\/b\/80f5bb39a4dfb4e55a74e22e1177f36f7c0e277d-gettextlandscape.png\" \/><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\"><\/th>\n<th style=\"text-align: left;\"><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Get a rating: <br> <img style=\"width: 275px;\" alt=\"\" src=\"\/user\/pages\/docs\/06.unified-commerce\/13.terminal-interaction\/GetNPS_portrait.svg?decoding=auto&amp;fetchpriority=auto\" \/><\/td>\n<td style=\"text-align: left;\">Ask for consent: <br> <img alt=\"\" src=\"\/images\/f\/3\/8\/1\/f\/f381ff0d4ffd76daea41d81caed734856b66e59e-getconfirmationportrait.png\" \/><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>For more examples and implementation instructions, refer to our <a href=\"\/pt\/point-of-sale\/shopper-engagement\/shopper-input\">Terminal API input request documentation<\/a>.<\/p>\n<h2 id=\"show-information\">Show information<\/h2>\n<p>A display request lets you show information on the display of the payment terminal outside of a payment flow. You can:<\/p>\n<ul>\n<li>Engage shoppers by <a href=\"\/pt\/point-of-sale\/shopper-engagement\/display-data\/display-image\">showing an image<\/a> in PNG, JPEG, GIF, or BMP format. For example, an advertisement or an offer generated by the POS app.<\/li>\n<li><a href=\"\/pt\/point-of-sale\/shopper-engagement\/display-data\/display-qr-code\">Show a QR code<\/a> that the shopper can scan with their mobile device. For example, a QR code with the URL to join your loyalty program or to download an app.<\/li>\n<li><a href=\"\/pt\/point-of-sale\/shopper-engagement\/display-data\/display-receipt\">Show a virtual receipt<\/a> with an overview of the customer's purchase, before you initiate payment.<\/li>\n<\/ul>\n<p>Here are some examples of what it looks like on terminal displays of various sizes when you make a display request.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\"><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Show an image: <br> <img title=\"Show image\" alt=\"\" src=\"\/images\/0\/d\/a\/5\/7\/0da57d415ea406be587cf384876430c35311086d-showimagelandscape.png\" \/><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\"><\/th>\n<th style=\"text-align: left;\"><\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Show a QR code: <br> <img title=\"Show QR code\" alt=\"\" src=\"\/images\/e\/8\/4\/1\/4\/e84140a6a35db45cad7a6200c52d0a3dc34d9d4c-showqrcodeportrait.png\" \/><\/td>\n<td style=\"text-align: left;\">Show a virtual receipt: <br> <img title=\"Show receipt\" alt=\"\" src=\"\/images\/6\/4\/c\/d\/2\/64cd281d768e4219799b0c502be8ac875820207a-lineitemportrait.png\" \/><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>For more examples and implementation instructions, refer to our <a href=\"\/pt\/point-of-sale\/shopper-engagement\/display-data\">Terminal API display request documentation<\/a>.<\/p>\n<h2>See also<\/h2>\n<div class=\"see-also-links output-inline\" id=\"see-also\">\n<ul><li><a href=\"\/unified-commerce\/shopper-engagement\"\n                        target=\"_self\"\n                        >\n                    Shopper engagement\n                <\/a><\/li><li><a href=\"\/point-of-sale\/shopper-engagement\/shopper-input\"\n                        target=\"_self\"\n                        >\n                    Input requests\n                <\/a><\/li><li><a href=\"\/point-of-sale\/shopper-engagement\/display-data\"\n                        target=\"_self\"\n                        >\n                    Display requests\n                <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/unified-commerce\/terminal-interaction","articleFields":{"description":"Collect information using the terminal, and show information on the display.","feedback_component":true,"last_edit_on":"06-07-2021 12:16"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/unified-commerce\/terminal-interaction","title":"Bespoke interaction on the terminal","content":"You can use the payment terminal to interact with the customer, by sending input requests and display requests to the terminal.\n\nUsing input requests you can collect personal details from customers, ask for their consent (for example, to store their details, or to enroll in your loyalty program), or get feedback.\nUsing display requests you can show static or animated images on the terminal display, a QR code with a URL to something that you want to draw attention to, or an overview of the customer's purchase.\n\nRequirements\nTo use payment terminals in this way:\n\nYou need to have a Terminal API integration using either cloud or local communications.\nWhen using input requests, you need to implement logic in your back-end system to process the received input.\nWhen you collect personal details, you need to consider data privacy.\n\nData privacy\nBefore storing any customer data, including payment data, you need to consider data privacy.\n\nConsult your legal department or an accredited third-party company to understand the data privacy regulations of the countries\/regions that you operate in.\nAsk for your customer's explicit permission to store their data, and be clear about what you intend to use it for.  For this, you could use the Terms and Conditions on your website, or you can use the payment terminal to interact with the customer. \n\nIf the customer asks to remove their information, you can use our Data Protection API to remove any customer-related data that you have stored with Adyen. The API also enables you to comply with the General Data Protection Regulation (GDPR) right to erasure.\nCollect information\nAn input request lets you gather information from your customer or staff. There are several types of input request:\n\nConfirmation: show some information and ask the user to confirm they agree.\nSignature: show some information and ask the user to confirm by supplying their signature.\nMultiple choice\u2014single answer: show a multiple-choice question and let the user select one of the answers. You can use this for NPS surveys, order lists, and such.\nMultiple choice\u2014multiple answers: show a multiple-choice question and let the user select more than one of the answers.\nDigit: ask for numeric input, like a zip code. Another example is a pay-at-table flow where you ask your staff for the table number. This input accepts input of whole numbers.\nAmount: ask for an amount. This input request shows the currency and accepts input of a number with two decimals.\nPhone number: ask for a telephone number. The country code is prefilled based on the location of the terminal, but can be changed.\nRating: show a question and let the user select a rating from 0 to 10.\nText: you'd typically use this to collect an email address.\n\nFor each input type, we provide predefined elements to show on the terminal display, and fields that you need to populate with your own text. The user enters a response with the terminal keypad or the on-screen keyboard and buttons.\nYou can make these input request before or after a payment, or as part of a payment flow involving shopper recognition. For example, if\nNote that the communication flow is between your POS app and the terminal, and does not involve the Adyen backend. You need to process the collected input with your own business logic.\nHere are some examples of what it looks like on terminal displays of various sizes when you ask for information through input requests.\n\n\n\n\n\n\n\n\nAsk for personal details:  \n\n\n\n\n\n\n\n\n\n\n\n\nGet a rating:  \nAsk for consent:  \n\n\n\nFor more examples and implementation instructions, refer to our Terminal API input request documentation.\nShow information\nA display request lets you show information on the display of the payment terminal outside of a payment flow. You can:\n\nEngage shoppers by showing an image in PNG, JPEG, GIF, or BMP format. For example, an advertisement or an offer generated by the POS app.\nShow a QR code that the shopper can scan with their mobile device. For example, a QR code with the URL to join your loyalty program or to download an app.\nShow a virtual receipt with an overview of the customer's purchase, before you initiate payment.\n\nHere are some examples of what it looks like on terminal displays of various sizes when you make a display request.\n\n\n\n\n\n\n\n\nShow an image:  \n\n\n\n\n\n\n\n\n\n\n\n\nShow a QR code:  \nShow a virtual receipt:  \n\n\n\nFor more examples and implementation instructions, refer to our Terminal API display request documentation.\nSee also\n\n\n                    Shopper engagement\n                \n                    Input requests\n                \n                    Display requests\n                \n","type":"page","locale":"pt","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"Omnichannel","lvl2":"Bespoke interaction on the terminal"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/unified-commerce","lvl2":"\/pt\/unified-commerce\/terminal-interaction"},"levels":3,"category":"Omnichannel","category_color":"green","tags":["Bespoke","interaction","terminal"]},"articleFiles":{"GetConfirmation_portrait.png":"<img alt=\"\" src=\"https:\/\/docs.adyen.com\/images\/b\/9\/6\/a\/4\/b96a4c0791c02ad0b190d727e444c780ad325db0-getconfirmationportrait.png\" \/>","GetText_landscape.png":"<img alt=\"\" src=\"https:\/\/docs.adyen.com\/images\/b\/d\/1\/f\/0\/bd1f0be71bb6ea065f0f29d85da19025c1916878-gettextlandscape.png\" \/>","LineItem_portrait.png":"<img alt=\"\" src=\"https:\/\/docs.adyen.com\/images\/8\/1\/c\/7\/3\/81c73a174067befffc0e213770ee1de7219acd54-lineitemportrait.png\" \/>","ShowImage_landscape.png":"<img alt=\"\" src=\"https:\/\/docs.adyen.com\/images\/1\/7\/8\/5\/b\/1785b5d7bef326988164f29c0af754e946f72459-showimagelandscape.png\" \/>","ShowQrCode_portrait.png":"<img alt=\"\" src=\"https:\/\/docs.adyen.com\/images\/9\/1\/4\/b\/6\/914b6225b5b9e461aa4ffa4b11ea9f0e6280a295-showqrcodeportrait.png\" \/>","GetNPS_portrait.svg":"<img style=\"width: 275px;\" alt=\"\" src=\"https:\/\/docs.adyen.com\/user\/pages\/docs\/06.unified-commerce\/13.terminal-interaction\/GetNPS_portrait.svg?decoding=auto&amp;fetchpriority=auto\" \/>"}}