Visa Voucher

This is a category rather than a branded payment method, so no country or currency is recorded for it. A category that inherits one product's footprint states something false: "cash payment: 1 country" would tell a reader that paying in cash exists in one country. Where the write-up below refers to a recorded country or currency, this line is the correction.

Checked 2026-10-21: CATEGORY, CONFIRMED — and the record already reached this conclusion with empty arrays, so there is nothing to correct in its coverage. I am returning "not_a_method" rather than "sound" because that is the structural classification the row needs; the write-up's substance holds up.

This is a category rather than a branded payment method, so no country or currency is recorded for it — a category that inherits one product's footprint states something false.

"Visa Voucher" is a generic category, not a rail. Ten documentation hosts were checked and none publishes a method by that name: Adyen (113 methods), Airwallex (98), Antom (109), Stripe (64), Rapyd, Mollie, dLocal, Checkout.com, EBANX and Worldline. In all of them Visa appears only as a card network — Rapyd's page says Visa "partners with financial institutions to issue credit or debit cards" and types it exclusively as `*_visa_card`; Adyen files it under "Credit and debit cards".

"Voucher", meanwhile, is a flow or a category in gateway docs rather than a brand. Stripe's "Vouchers" group contains Boleto, Konbini, Multibanco and OXXO. Adyen marks Boleto (BR/BRL) and OXXO (MX/MXN) with flow "voucher". Airwallex classifies Paysafecard as a "Prepaid voucher". Mollie splits it in two: "Vouchers" (BE, EUR — eco, gift, sport & culture, meal) and "Gift cards" (NL, EUR — 36 brands handled by the Dutch broker Intersolve). dLocal documents "Brazil / Food vouchers" (BR, BRL) with benefit-provider IDs LO, VR, UL and TI. Not one of them names Visa.

For an integrator the consequence is simple: Visa-branded prepaid and gift value arrives over ordinary Visa card acquiring, identified by BIN, with no separate integration to build. Accepting an actual voucher means integrating a named brand instead.

Where documentation is silent: nobody defines "Visa Voucher", so the existing country and currency rows have nothing behind them — the directory's own research files hold only "visa-voucher | Visa Voucher | method" with no provider attribution. It may be a garbled reference to Visa-branded Brazilian meal-benefit cards, but that is an unverified hypothesis. This turn's web-search budget was exhausted, so checking was confined to documentation hosts.

One caveat on identity: the review could not settle beyond doubt that this is the right entity, so read the country and currency here as the best available answer rather than a confirmed one.

Checked against Visa Voucher’s own documentation on 21 October 2026. Coverage changes; confirm anything you are about to build on.