Use the recommendations on this page to give shoppers a clear meal voucher payment experience. Regardless of sales channel, you should:<\/p>\n
Other recommendations on this page apply to either online payments or in-person payments.<\/p>\n
The setup depends on the voucher network.<\/p>\n
For single-branded vouchers, such as Monizze and Pluxee in Belgium through Intersolve or French vouchers through Conecs:<\/p>\n
For vouchers that are co-branded with Mastercard, such as Edenred in Belgium and Spain:<\/p>\n
Proceed as follows:<\/p>\n
Follow these guidelines:<\/p>\n
You need to prepare your integration to collect any remaining amount with a second payment method. The available approach depends on the sales channel and the voucher network.<\/p>\n
For online payments, you can integrate partial payments<\/a> to split an order between payment methods. However, this only works for single-branded \"non-scheme\" meal vouchers, which are routed through Intersolve or Conecs. Meal vouchers that are co-branded with Mastercard are \"scheme\" meal vouchers.<\/p>\n<\/li>\n For both online and in-person payments you can integrate partial authorizations<\/a>, also called partial approvals. When the voucher does not cover the transaction amount in full, the issuer normally declines the transaction. But if your payment request includes a parameter to allow partial authorization, this asks the issuer to authorize less than the transaction amount instead of declining the transaction. You can then make a second payment request for the remainder.<\/p>\n<\/li>\n Because there is no guarantee that all issuers support partial authorizations, we recommend that for certain vouchers you first check the balance<\/a> on the meal voucher. You can then make a voucher payment that does not exceed the funds on the voucher, and a second payment request for any remaining amount.<\/p>\n<\/li>\n<\/ul>\n Also note that for in-person payments you need to verify that your POS system supports multiple tenders for one transaction.<\/p>\n This applies to meal vouchers co-branded with Mastercard, including Edenred in Belgium and Spain. For these voucher types, you can use partial authorizations. If the voucher balance is lower than the requested amount, the issuer can authorize the available amount instead of declining the payment. You can then collect the remaining amount with another payment method.<\/p>\n For online payments, you need to ask our Support Team<\/a> to enable partial authorizations.<\/p>\n<\/div>\n To handle an insufficient balance:<\/p>\n Send a payment request for the full eligible basket amount and a parameter to allow partial authorization.<\/p>\n\n Check the response and decide if you need to follow up on the initial payment request.<\/p>\n If the full amount is authorized, no follow-up is needed.<\/p>\n\n<\/li>\n If the response shows a partial amount is authorized, collect the remaining amount with a different payment method by sending a follow-up payment request with:<\/p>\n If the payment is declined, ask the shopper to enter a lower voucher amount and try again. You can then make a follow-up payment request as described above to collect the remaining amount.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n This applies to Monizze, Pluxee in Belgium, and Lunch Check in Switzerland. For these issuers, first check the available funds on the voucher. This minimizes the number of declines and retry attempts. Inform the customer, so that they understand the situation beforehand. You can then make a payment request for the available amount on the voucher and collect the remaining amount with another payment method.<\/p>\n One of the ways to check the balance on gift cards and meal vouchers is to use the Stored Value API<\/a>. However, this only works for \"non-scheme\" meal vouchers. For \"scheme\" meal vouchers (vouchers that are co-branded with Mastercard) you can check the balance using a Checkout API To handle a split tender:<\/p>\n Ask the shopper for their voucher details.<\/p>\n<\/li>\n Check the balance using the method that matches your integration and the voucher type.<\/p>\n\n Tell the shopper how much the voucher can pay and what amount remains.<\/p>\n<\/li>\n Send a voucher payment request for the available balance, or for the full amount when the balance is sufficient.<\/p>\n<\/li>\n If an amount remains, send another payment request, letting the shopper choose a different payment method.<\/p>\n<\/li>\n<\/ol>\n Refund behavior depends on the voucher network. Refund a voucher payment to the original voucher whenever possible, in case the issuer or applicable regulation does not permit refunding to a different payment method.<\/p>\nMastercard-based vouchers<\/h3>\n
\n
\n
\n
Intersolve-based vouchers<\/h3>\n
\/paymentMethods\/balance<\/code> request in the case of online payments, or a Terminal API BalanceInquiry<\/code> request in the case of in-person payments.<\/p>\n\n
Show a clear receipt<\/h2>\n
\nPrint a receipt that shows the voucher amount and, when the issuer supports it, the remaining balance.<\/p>\nShow a clear decline message<\/h2>\n
\nDo not show a generic payment failure message when a voucher payment is declined. Explain the reason and the next step.<\/p>\n\n
Recurring payments and refunds<\/h2>\n
\nDo not save voucher tokens for recurring or saved-payment flows unless the issuer explicitly supports this. Most voucher types do not support recurring payments.<\/p>\n