Skip to content
Legal & policies

Accessibility Statement

Updated Nov 7, 2026Version 1.0

This describes the Marketplace at launch. It is not yet open to buyers.

This statement is the information on how the Paysera Marketplace meets the accessibility requirements that the Marketplace Terms of Use refer to. It is published under Annex V of Directive (EU) 2019/882 (the European Accessibility Act) and Article 13 of the Law of the Republic of Lithuania on Accessibility Requirements for Products and Services No XIV-1633.

1. About the service

The Paysera Marketplace (the Marketplace) is an online marketplace where you can find products from independent sellers, compare their offers and buy from them. Each purchase is a contract between you and the seller.

  • Where you use it – in the Paysera app for iOS and Android. The information pages about the Marketplace, including this statement and the Terms of Use, are on marketplace.paysera.com.
  • Who provides it – Paysera LT, UAB, company code 300060819, Pilaitės pr. 16, LT-04352 Vilnius, Lithuania.

The Marketplace is not offered to buyers on a website. If we offer it on a website later, we will assess that website before it opens and add it to this statement.

2. How the service works

You use the Marketplace inside the Paysera app, signed in with your Paysera app login. The Marketplace has no sign-in of its own. The Paysera app's own accessibility information is at paysera.com/v2/en/accessibility.

A purchase goes through these steps:

  1. Find – search for a product or browse the catalogue.
  2. Product – open a product to see what it is and which options it comes in.
  3. Variant – choose the options you want, such as colour or size.
  4. Offer – compare the offers that sellers make for that variant and pick one.
  5. Cart – add the offer to your cart, where you can change the quantity or remove items.
  6. Checkout – choose a delivery option and a delivery address.
  7. Payment – choose a payment method and pay on the Paysera Checkout payment page.
  8. Order – see the order's confirmation, status, and details in your orders.
  9. Cancel or withdraw – cancel an order, or withdraw from a purchase within 14 days, as section 6 of the Terms of Use explains.
  10. Support – ask the seller about your order, or ask Paysera about the Marketplace (section 5).

3. How the service meets the requirements

All statuses last reviewed 7 November 2026.

Our baseline

Paysera has chosen this technical baseline for the Marketplace: WCAG 2.1 level AA, as incorporated in the European standard EN 301 549 V3.2.1 (clause 9 for web pages and clause 11 for software, including mobile apps), plus six WCAG 2.2 success criteria at levels A and AA: 2.4.11 Focus Not Obscured (Minimum), 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), 3.2.6 Consistent Help, 3.3.7 Redundant Entry and 3.3.8 Accessible Authentication (Minimum).

No harmonised standard has yet been published in the Official Journal of the European Union under Directive (EU) 2019/882. This baseline is therefore our own engineering choice; it is not a claim of presumed conformity with the Directive.

Requirements and status

The list below gives the requirements of Annex I to Directive (EU) 2019/882 that apply to the Marketplace, where in the service each one applies, and how we meet it. "How we meet it" describes what our baseline requires of that part of the service; "Status" shows whether we have confirmed it.

We are assessing every part of the service against our baseline. Until that assessment is complete, we do not state that any part meets the requirements, so every requirement shows Assessment in progress. We will complete the assessment, and update this section with its results, before the Marketplace opens to buyers.

Annex I, III(a) – products used to provide the service

  • Where: Paysera app (iOS, Android)
  • How we meet it: The service runs in the Paysera app on your own phone; we supply no terminal or other device. The Marketplace screens must work with the accessibility features of iOS and Android, such as screen readers and larger text.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, III(b) – information about how the service works and about its accessibility

  • Where: This statement and the information pages on marketplace.paysera.com
  • How we meet it: The information is published as text web pages with headings, lists, and tables, which can be converted into other formats. Images have text alternatives. Pages not yet translated into your language are shown in English with a notice, and their English text is marked as English so that screen readers read it correctly. Before the Marketplace opens to buyers, we will check that screen readers can read the pages and that the pages can be enlarged without losing content. On request, we will give the information in writing (section 5).
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, III(c) – mobile app

  • Where: Marketplace screens in the Paysera app (iOS, Android)
  • How we meet it: In the Marketplace screens, every control must have a name, role, and state that screen readers announce; text must follow the system text size; screens must work in portrait and landscape; text and controls must have sufficient contrast; touch targets must be large enough; meaning must never depend on colour or a gesture alone; and errors and status messages must be announced. A time limit in checkout must never make you start again: if checkout takes a long time, what you entered must be kept, and if a price has changed, we must show it and ask you to confirm it before you pay. An order you confirmed but did not pay for is cancelled after its payment deadline passes; the app must show you that deadline and tell you when the order is cancelled.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, III(c) – website

  • Where: Information pages on marketplace.paysera.com
  • How we meet it: The pages must meet our baseline. Automated accessibility checks, and keyboard checks of the site's header and footer menus, run on changes to these pages before the change is added to the site's code. A change added without these checks must pass them before it is released.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, III(d) – support services

  • Where: Marketplace point of contact (info@paysera.lt)
  • How we meet it: We will answer in writing the questions on the accessibility of the service and its compatibility with assistive technologies that you send to the Marketplace point of contact at info@paysera.lt (section 5).
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, IV(g)(i) – accessibility information about the products sold

  • Where: Product pages in the Paysera app
  • How we meet it: We will add a field in which sellers can give accessibility information about the products they sell. Where a seller gives it, we will show it with that seller's offer.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, IV(g)(ii) – identification, security and payment functions

  • Where: Paysera app login; payment method choice in checkout; Paysera Checkout payment page
  • How we meet it: The Marketplace uses the Paysera app login and has no sign-in of its own. The payment method choice must meet our baseline, and we are assessing the Paysera Checkout payment page against the same baseline. If your session ends during a purchase, the app must let you sign in again and return to the same step with what you entered.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, IV(g)(iii) – identification methods, electronic signatures and payment services

  • Where: Paysera app login; Paysera Checkout
  • How we meet it: We are assessing Paysera Checkout against our baseline, and we will assess the Paysera app login against it before the Marketplace opens to buyers. The Marketplace uses no electronic signatures.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, IV(e) – payment services that are part of consumer banking (our reading: the Paysera Checkout payment step)

  • Where: Paysera Checkout payment page
  • How we meet it: This entry is Paysera's interpretation: we treat the Paysera Checkout payment step as a consumer banking service. Its payment, identification, and security functions must therefore be perceivable, operable, understandable, and robust, and its payment information must be written no more complex than level B2 of the Common European Framework of Reference for Languages.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, VII – use without vision

  • Where: All parts of the service
  • How we meet it: Every part of the service must let screen readers (VoiceOver, TalkBack) reach and operate every element; images must have text alternatives; the reading order must follow the visual order.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, VII – use with limited vision

  • Where: All parts of the service
  • How we meet it: It must be possible to enlarge text through the system text size or browser zoom without losing content or function; text and controls must have sufficient contrast.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, VII – use without perception of colour

  • Where: All parts of the service
  • How we meet it: Information and states must never be shown by colour alone; text or a symbol must always go with the colour.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, VII – use without hearing

  • Where: All parts of the service
  • How we meet it: All information must be given as text and images; the service must not rely on sound.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, VII – use with limited hearing

  • Where: All parts of the service
  • How we meet it: No part of the service may need sound to be used.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, VII – use without vocal capability

  • Where: All parts of the service
  • How we meet it: No step may need your voice; every step must work by touch, keyboard, or assistive technology.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, VII – use with limited manipulation or strength

  • Where: All parts of the service
  • How we meet it: Touch targets must be large enough; no action may need a dragging or multi-finger gesture without a simple alternative; the service must work with a keyboard and with switch access.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, VII – use with limited reach

  • Where: All parts of the service
  • How we meet it: You use the service on your own device; there is no terminal to reach. The service must work in the position that suits you.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, VII – minimising the risk of photosensitive seizures

  • Where: All parts of the service
  • How we meet it: No content may flash more than three times in any one second.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, VII – use with limited cognition

  • Where: All parts of the service
  • How we meet it: The service must use plain language, a consistent layout and consistent navigation, and help in the same place on every screen; error messages must say how to fix the problem; and the service must never ask you to enter again what you already gave in the same process.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

Annex I, VII – privacy

  • Where: All parts of the service
  • How we meet it: Using accessibility features must not require any extra personal data, and the service must never ask about a disability.
  • Status: Assessment in progress; target: before the Marketplace opens to buyers

4. How we keep it accessible

  • Release checks – automated accessibility checks, and keyboard checks of the site's header and footer menus, run on changes to the information pages before the change is added to the site's code; a change added without these checks must pass them before it is released. Before the Marketplace app screens are released to buyers, they will be checked against our baseline with accessibility tests, and with screen readers (VoiceOver and TalkBack) and large text; from then on, every change to them will be checked the same way, on the changed journeys, before it is released.
  • When we assess again – we assess the affected part again, and update this statement, when we add a new journey or screen, when we change the shared design components the service is built from, when the accessibility requirements that apply to the service change (Directive (EU) 2019/882, the Lithuanian, Latvian, or Estonian laws that transpose it, or acts adopted under it), when a harmonised standard or technical specification is published in the Official Journal of the European Union under Directive (EU) 2019/882, when a standard our baseline is built on (EN 301 549 or WCAG) is revised, when an authority asks us, and when we receive a complaint. We also check the Official Journal again before the Marketplace opens to buyers.
  • When something does not meet the requirements – we fix it. Without delay, we inform the authority of each country where the problem affects buyers (section 6) of the problem and of the corrective measures; in Lithuania, no later than 5 working days after we learn of it, as Article 13 of Law No XIV-1633 requires. We then update this statement.
  • Requests from an authority – we give the authority the information it needs to check that the service meets the requirements, within the time it sets.
  • No exemption claimed – we do not rely on the exceptions for a fundamental alteration or a disproportionate burden (Article 14 of Directive (EU) 2019/882).
  • Records – we keep this statement and the records of our assessments for as long as the service is offered.

5. Support and feedback

To ask about the accessibility of the Marketplace and how it works with assistive technologies, such as screen readers, or to report an accessibility problem, email the Marketplace point of contact at info@paysera.lt.

On request, we will give you this statement in writing; ask at info@paysera.lt.

6. Complaints

If you think the Marketplace does not meet the accessibility requirements, you can tell us (section 5). You can also turn to the authority that supervises the accessibility of e-commerce services in the country where you live:

  • Lithuania – Valstybinė vartotojų teisių apsaugos tarnyba (State Consumer Rights Protection Authority, VVTAT), legal-entity code 188770044 – vvtat.lrv.lt. Under Law No XIV-1633 (Articles 6 and 26), VVTAT examines complaints that a service does not meet the accessibility requirements. Anyone with an interest may complain, including a consumer or a consumer association, and VVTAT examines a complaint within 3 months. You can complain through the Consumer Rights Information System at www.vtis.lt, by e-mail to tarnyba@vvtat.lt, or by post to A. Goštauto g. 12, LT-01108 Vilnius.
  • Latvia – Patērētāju tiesību aizsardzības centrs (Consumer Rights Protection Centre, PTAC) – ptac.gov.lv. Under Article 21 of the Latvian Law on the Accessibility of Goods and Services, first send your complaint to us. We will answer in writing within one month, or, for an objective reason, within two months, in which case we will tell you why. If you write in Latvian, we will answer in Latvian. If the accessibility is not improved, or we do not answer, you can send the same complaint to PTAC, with our answer if we sent one. An organisation that protects the interests of persons with disabilities may do this for you, with your consent.
  • Estonia – Tarbijakaitse ja Tehnilise Järelevalve Amet (Consumer Protection and Technical Regulatory Authority, TTJA) – ttja.ee. The Estonian Accessibility of Products and Services Act sets no separate consumer complaint procedure or deadline. Under its § 16, TTJA supervises compliance with the accessibility requirements; you can contact it at info@ttja.ee or +372 667 2000. For a consumer dispute in general, you first contact the trader, and then you can apply to the Consumer Disputes Committee (tarbijavaidluste komisjon) at TTJA.

7. Dates

  • Prepared: 4 November 2026
  • Last reviewed: 7 November 2026

Previous versions

There are no previous versions — this is the first published version.