This article explains which one-time-payment (OTP) methods support scheduled tariffs (formerly named alternate tariff), why this is changing, and what it means for you as a CPO or EMSP.
From 1 October 2026, webOTP will support the default tariff only, in line with payment terminals.
Which OTP methods support scheduled tariffs?
| Payment channel | How the driver pays | Scheduled tariff support |
|---|---|---|
| Payment terminals (integrated, cloud-based, and kiosks) | Card or mobile wallet at the charger | No, default tariff only |
| webOTP | Browser-based payment page, no app or account | No, default tariff only (from 1 October 2026) |
| appOTP | Virta app, without a registered account | Yes |
| In-app payments (registered drivers) | Logged in via the Virta app | Yes |
Scheduled tariff is the new name for what was formerly named alternate tariff. The name changes on 1 October 2026, but the underlying functionality does not.
Why is this changing?
Under AFIR (Regulation (EU) 2023/1804), the price charged for ad hoc charging must be reasonable, transparent, clearly comparable, and non-discriminatory to the driver before charging starts. Payment terminals already only support the default tariff, because they can't technically support scheduled pricing. To keep ad hoc pricing consistent across every channel, webOTP is being aligned to the same default-tariff-only logic.
AFIR itself applies in the EU, and GB follows equivalent rules. This change is being rolled out globally, including for customers in Asia, so that ad hoc pricing stays transparent and consistent everywhere Virta operates, not only where it's required by regulation.
In-app payments and appOTP are not ad hoc payment channels under AFIR, since both require the Virta app to be installed. These remain unaffected and continue to support scheduled tariffs.
What this means for you
This change does not affect your pricing settings in Virta Hub. Your default and scheduled tariffs stay configured exactly as they are today. The only thing that changes is which price a webOTP driver sees and pays: from 1 October 2026, that will always be your default tariff, even during a scheduled tariff window. No action is required from you.
FAQ
Will this affect in-app payments or appOTP?
No. Both continue to support scheduled tariffs as before, since neither is an ad hoc payment channel under AFIR.
What happens if I have a scheduled tariff set and a driver pays via webOTP?
From 1 October 2026, webOTP no longer supports scheduled tariffs. A driver paying via webOTP will always see and be charged your default tariff, even during a scheduled tariff window. The scheduled tariff itself isn't affected. It stays configured in Virta Hub and continues to apply to in-app payments and appOTP.
Why is webOTP changing when payment terminals already work this way? Payment terminals have never been able to support scheduled tariffs, for technical reasons. webOTP could, but keeping it default-tariff-only brings ad hoc pricing in line across every ad hoc channel, so drivers see the same, predictable price regardless of how they pay.
Do I need to change anything in Virta Hub? No. Your tariff configuration doesn't change. Only the price shown to webOTP drivers changes, from 1 October 2026 onward.