- PCI PTS 5 terminals: long-term support version 1.120.11<\/strong>.<\/li>
- PCI PTS 6 terminals: long-term support version 1.126.5<\/strong> or version 1.129<\/strong> or later.<\/li><\/ul><\/td>\n<\/tr>\n
\n Limitations<\/strong><\/td>\n The standalone solution only supports the Adyen UI flow<\/a>.
There are compliance<\/a> rules you must meet before you can accept meal or food voucher payments.<\/td>\n<\/tr>\n\n Setup steps<\/strong><\/td>\n Before you begin: - Ask our Support Team<\/a> to enable the Brazilian meal voucher functionality for your merchant account.<\/li>
- If you want to use the Adyen UI flow<\/a>, ask our Support Team<\/a> to enable that flow. Let them know whether you want this to be configured for a company account, merchant account, store, or terminal.<\/li><\/ul><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Ways to accept meal vouchers<\/h2>\n
To accept meal and food voucher payments, you can use the following flows:<\/p>\n
- \n
- \n
Adyen UI<\/a>
\nWith this flow enabled, the terminal automatically shows a screen that lets the customer select if they want to make a credit, debit, or voucher payment. After selecting voucher, the customer taps, inserts, or swipes the meal or food voucher card to make the payment. This flow works for integrated and standalone payment terminals.<\/p>\n<\/li>\n- \n
Your own UI<\/a>
\nYou use your own custom POS UI or some other process to let the customer indicate they want to make a credit, debit, or voucher payment. You then send a Terminal API payment request specifying the chosen payment type as theselectedAccountType<\/code>, in this case with a value of MEAL_VOUCHER<\/strong><\/span>. On the terminal, the customer then taps, inserts, or swipes the meal or food voucher card to make the payment.<\/p>\n<\/li>\n<\/ul>\nStandalone payment terminals only support the Adyen UI flow. If your Adyen terminals are integrated with your POS system, you can use either flow.<\/p>\n
Note that if the balance on a voucher is not enough for the amount due, the transaction is refused in both flows.<\/p>\n
Adyen UI<\/h2>\n
To use the Adyen UI flow, you must contact our Support Team<\/a> and let them know whether you want this to be enabled for a company or merchant account, a store, or a terminal. The Adyen UI flow works for integrated and standalone payment terminals.<\/p>\n
When enabled, the flow is as follows:<\/p>\n
- \n
- \n
You initiate a payment like you usually do.<\/p>\n<\/li>\n
- \n
The terminal asks the customer to choose if they want to pay by credit, debit, or voucher.<\/p>\n
![\"Screen](\"\/images\/c\/d\/9\/c\/8\/cd9c8166170bdf7ec8636158c12be712826406d3-screen-encard-selection-screen.png\")
<\/p>\n<\/li>\n - \n
If the shopper selects voucher, the terminal asks the customer to tap, insert, or swipe.<\/p>\n
\nFor information about the flow if the shopper selects credit or debit, see Installments in Brazil<\/a>.<\/p>\n<\/div>\n<\/li>\n
- \n
The customer presents their voucher card to the terminal and completes the payment. If the payment amount is above the CVM limit, the customer may need to enter their PIN.<\/p>\n<\/li>\n<\/ol>\n
On an integrated terminal, when the voucher payment succeeds, the Terminal API
AdditionalResponse<\/code> includes:<\/p>\n- \n
- fundingSource=PREPAID<\/strong><\/span>.<\/li>\n
- The voucher brand used for the payment, for example, paymentMethodVariant=elo_voucher_br<\/strong><\/span>.<\/li>\n<\/ul>\n
Your own UI<\/h2>\n
As an alternative to the Ayden UI, you can design your own custom UI to collect the customer's preference. Your Terminal API request then needs to flag the transaction as a meal voucher payment. This flow does not apply to standalone terminals.<\/p>\n
The flow at the point of sale is as follows:<\/p>\n
- \n
- You collect the information about whether the customer wants to pay by voucher. You can do this in various ways, for example:\n
- \n
- Your store staff asks the customer.<\/li>\n
- You collect the customer's preference on a secondary screen, for instance a tablet.<\/li>\n
- You use input requests<\/a> to collect the customer's preference on the payment terminal.<\/li>\n<\/ul><\/li>\n
- You use logic to pass the collected information to your POS app, or your store staff enters this information manually into your POS app.<\/li>\n
- Your POS app passes this information to the payment request<\/a>.<\/li>\n
- The customer presents their voucher card to the terminal and completes the payment.<\/li>\n<\/ol>\n
When the transaction is approved, you receive a response containing the voucher brand used for the payment.<\/p>\n
Make a meal voucher payment<\/h3>\n
If the customer has indicated they want to pay with a meal or food voucher:<\/p>\n
- \n
- \n
Create a JSON object consisting of the
selectedAccountType<\/code> parameter with the value MEAL_VOUCHER<\/strong><\/span>.<\/p>\n\n<\/code-sample>\n<\/div>\n \nSee Interaction with installment parameters<\/a> for more information.<\/p>\n<\/div>\n<\/li>\n
- \n
Encode the JSON object to Base64. You will pass the resulting string in
SaleData.SaleToPOIData<\/code>.<\/p>\n\n<\/code-sample>\n<\/div>\n<\/li>\n - \n
Make a payment request<\/a>, specifying:<\/p>\n
- \n
- \n
The standard \n
SaleToPOIRequest.MessageHeader<\/code>\n<\/a> object, withMessageClass<\/code> set to Service<\/strong><\/span> andMessageCategory<\/code> set to Payment<\/strong><\/span>.<\/p>\n
- \n
- The voucher brand used for the payment, for example, paymentMethodVariant=elo_voucher_br<\/strong><\/span>.<\/li>\n<\/ul>\n
- \n
- \n
- If you want to use the Adyen UI flow<\/a>, ask our Support Team<\/a> to enable that flow. Let them know whether you want this to be configured for a company account, merchant account, store, or terminal.<\/li><\/ul><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
- PCI PTS 6 terminals: long-term support version 1.126.5<\/strong> or version 1.129<\/strong> or later.<\/li><\/ul><\/td>\n<\/tr>\n
![\"-white_check_mark-\"](\"\/user\/data\/smileys\/emoji\/white_check_mark.png\" "\\"-white_check_mark-\\"")
<\/td>\n