Accessibility statement
The payment domain · pay.rieckflow.com
Last updated 2026-10-04
This statement covers the payment domain: the pages where you enter a payment code or open a payment link and complete the payment itself. The debtor portal, the customer portal and the signing domain are separate services, each with its own statement. The information has been prepared with reference to section 35 and annex 4 of the Danish Act on accessibility requirements for products and services, and WCAG 2.1 level AA is our technical target.
Compliance status
The payment pages are partially compliant with WCAG 2.1 level AA. The payment-code front page and the two confirmation pages make no database lookups and are checked automatically with axe-core at every release, where findings block the release. The payment page for a specific claim reads the amount and the wording from your reference and is not covered by that check; it has not been reviewed systematically with a screen reader.
The service and how to use it
You arrive here in one of two ways: by entering the short payment code from your invoice or letter on the front page, or by following the payment link directly. The page shows who you are paying, what the payment covers and the amount, and you pay by payment card or MobilePay. Where it is permitted, you can choose to pay a different amount. At the end you get a confirmation page — and the payment is registered even if you close the tab first.
How we address the requirements
The pages are short and each has a single purpose. The payment code can be entered by keyboard alone, the fields have names, autocomplete and a keyboard suited to the content on a phone, and errors — a wrong code, a declined card — appear as text next to the field and are announced to screen readers. The amount is shown as text, not only in a graphic. No time limit forces you onwards. Language and light/dark appearance can be changed at the bottom of the page.
Non-accessible content
The card fields sit on our own page, but the 3-D Secure security step is shown by your card issuer in a window we can neither change nor control. The same applies to MobilePay and to any pages you are sent on to at your bank. We record accessibility problems in those steps and follow them up with the provider. If you cannot complete the payment on screen, contact us — we will find another way, and you will not lose a deadline because of it.
Feedback and contact
If you find that something is not accessible to you, or you need content in another format, email rieck@rieckflow.com. Please describe the page and the action you were trying to complete. We reply as soon as possible and within 14 days at the latest.
Enforcement and complaints
If you do not receive a satisfactory reply, you can bring the matter before the relevant supervisory authority. For services within the Danish Safety Technology Authority's remit, inaccessible services can be reported through the reporting form at sik.dk/tip. Since January 2026, the Danish Safety Technology Authority has been part of the Danish Business Authority.
Monitoring and maintenance
The automated checks run at every release on the front page and the confirmation pages. The payment page for a specific claim and the journey at the payment provider are not covered by them and have not been reviewed with a screen reader. Findings are recorded as tasks with an owner and a status. The statement is updated when the service changes materially and at least once a year.