Skip to main content
AllRide decides which voucher sets are available to you and at what price per redemption. You see your own price for every voucher set in your catalog and must accept it before you can redeem from that set. No consumer is ever billed at a price it has not accepted.

​
Price terms

For every voucher set visible to you, your Price Terms state what one redemption costs you: Prices change over time, so the terms come in Price Terms Periods: a current period (the one in force now, null when the set has no price yet) and up to 5 upcoming periods, each with startsAt, endsAt (null when open-ended), terms, a termsDigest (a SHA-256 fingerprint of the terms) and your acceptance.
Instants are UTC; 2026-11-30T23:00:00Z is midnight on 1 December in Berlin. You see only the price that applies to you, never how AllRide derived it, and never the prices of other consumers. Providers never see prices, and end customers never see prices on landing pages. Availability. Which voucher sets you see at all is also decided by AllRide, per provider and per voucher set. A set you have no access to is absent from your catalog and from the pricing endpoints (404 voucher-set-not-found). See Catalog and toggles.

​
Accepting prices

Accepting a price is a commercial commitment, so a person in your team makes it:
  • Accept on the Prices page of the consumer dashboard. It lists the sets that need acceptance and the terms you accept.
  • The member needs the permission accept-consumer-pricing and a sign-in within the last 15 minutes. The default groups owners, administrators and billing have it.
  • API keys cannot accept prices: accept-consumer-pricing cannot be delegated, and an API key calling the accept operation gets 403 missing-permission. AllRide cannot accept on your behalf either.
The dashboard calls Accept Price Terms (POST /consumer/v1/pricing/acceptances) with the periods it showed, identified by voucher set, periodStartsAt and termsDigest. Up to 200 periods are accepted in one all-or-nothing request. You can accept the current period or any upcoming one in advance. Accepting the same terms again changes nothing. Every acceptance is immutable and recorded in your audit log with the exact terms, who accepted and when. If the terms changed while you were deciding, the request fails with 409 price-terms-changed and nothing is recorded; reload the Prices page and accept again. A suspended partner cannot accept prices.

​
Price changes

When AllRide changes a price you have accepted, the new price starts at least 14 days later (the platform notice period). Only in exceptional cases, with a recorded reason, can AllRide schedule a change at shorter notice, never earlier than the next day. You hear about a change through:
  • an email to your members with accept-consumer-pricing, with reminders 7 days and 1 day before the start;
  • the webhook price-terms-change-scheduled;
  • a banner in the consumer dashboard and the counts of the pricing summary.
Until the new price starts you keep redeeming, and are billed, at the price you accepted. From the start date the voucher set pauses for you until you accept the new price; you then receive price-terms-acceptance-required. Accept before the start date (acceptBy) to avoid a pause. The status of a voucher set (also shown on catalog entries as priceAcceptance.status) tells you where you stand:

​
Redeeming and the price gate

A voucher set is redeemable for you only when you have accepted the Price Terms in force at the moment of the redemption. Otherwise:
  • Create a redemption and batch redemptions answer 409 price-acceptance-required. more names the voucherSetId and the priceAcceptanceStatus (acceptance-required or not-priced). Accept the price in the dashboard, then retry with a new Idempotency-Key (the 409 is stored for the old key).
  • When you redeem by providerId, sets you have not accepted are skipped; the 409 occurs only when nothing else blocks the redemption.
  • On landing pages a set without an accepted price is absent, as if it were switched off. End customers never see prices or an acceptance message.
Watch priceAcceptance.status on your catalog entries, or the pricing summary, to find sets that need attention before your customers notice.

​
Pricing webhooks

These consumer-only webhook types require view-consumer-pricing on the member or API key that subscribes the endpoint.

​
Permissions

The default groups owners, administrators and billing hold both. developers, viewers and redemption-operators hold neither, because prices are finance data.