In a brick-and-mortar store you can see the opening date from the street. First the shelves appear, then the counter, someone hangs the sign, and in the last week the crew washes the windows and dresses the display. Every stage has an owner and a date, so the day the doors open goes into the calendar a month ahead.
In e-commerce the last shelf is the payment plugin. Behind it sits a stage no offer mentions: a stranger has to read the store’s terms, check the account number and decide that this person is fit to take money.
It happens in Poland more often than the silence around the topic suggests. According to Dun & Bradstreet nearly 75,000 online stores operate today, and in 2025 almost 7,800 new ones opened against 5,400 closed — a net 2,400 more, or about 3% of the base in a year). For onboarding, though, the gross figure matters: about twenty-one stores a day go through that verification for the first time and try to put its result in the calendar. Whose deadline is that, exactly?
How long does online payment rollout take in a store if you count only code?
Here the numbers agree and are low. One Polish operator breaks the process into stages in its guide: account registration is “a few minutes”, verification “even up to 24 hours”, and technical integration — if the store sits on a ready platform such as WooCommerce, PrestaShop or Shoper — about 15 minutes, because it comes down to installing a plugin and pasting merchant details. For a custom-built solution the same guide talks about 3–4 business days for an experienced developer.
A second schedule comes from firms that build stores. A rollout on ready SaaS is, they say, 2–7 days (“a start in 48 hours is realistic”), a WooCommerce store 4–8 weeks, PrestaShop or Magento 8–16 weeks, and a system written from scratch: three to nine months. Hooking up payments and logistics appears in that schedule as a separate line: 3–5 days. Those are vendor claims from their own offers. No study on a sample measured those timelines, so treat them as an order of magnitude.
And here is the thing that explains the whole category’s messaging. In a project counted in weeks or months the payment plugin is the shortest schedule item, because it really takes a quarter of an hour. The trouble starts when the question is: from when can this store take the first zloty.
The go-live date is set by a one-zloty transfer and a 2018 statute
Verification starts with a transfer. The amount is symbolic — a zloty, sometimes one grosz — and its purpose is to confirm identity and that the named account belongs to the applicant. The transfer must leave the account given in the application; from another account verification does not close, because the institution compares transfer data with form data.
The operator has no leeway here: the duty to verify customer identity comes from the anti-money-laundering and counter-terrorist financing act of 1 March 2018. The act requires verifying the identity of the customer and the beneficial owner before establishing a business relationship; finishing verification during the relationship is an exception, allowed at low risk and when continuity of operations requires it.
Then the spread begins. One operator says verification usually closes “within 24 hours of the transfer posting — weekends included”. Another provider talks about 1–3 business days as the market standard and 24 hours when documents are complete. From the two claims you only learn that a complete file shortens the wait. By how much — unknown, because neither publishes a distribution.
And then there is one more sentence that never appears in any ad. The same operator that verifies an account within a day writes in its developer FAQ that card payments activate separately and can take up to 14 days, because card schemes apply stricter security rules.
What does the operator read before saying “yes”?
Verification covers far more than the account. One operator describes its checklist outright: terms and privacy policy, assortment matching the contract, even cart checkboxes accepting the terms and acknowledging privacy rules. The company-registration document set repeats across providers: a KRS extract or CEIDG entry, tax ID (NIP), REGON, a business account with a statement, details of representatives and beneficial owners, and in higher-risk industries separate AML statements.
The most common cause of delay sits on the store’s side and is banal: missing terms or a privacy policy. On the same list, in no fixed order, sit data mismatches with registry entries and a private account given where the operator requires a business one.
The list of things that must be on the site also grows independently of payments. In September 2026 a draft amendment to the consumer rights act (UC169), implementing Directive 2023/2673, went to consultation. The draft provides for a withdrawal button, easily available throughout the withdrawal period; the button is to cover all distance contracts, and a ban on dark patterns — financial services. At consultation stage this is not yet binding law, but the direction of work for stores is already priced.
How much that work costs, e-commerce has counted for itself. In the Polish Chamber of Electronic Economy’s “e-Accurate” report (475 Polish B2C and B2B firms, published 4 December 2024) the average cost of adapting one firm to GDPR, the Omnibus directive and the DSA was PLN 159,500, and for the largest entities reached a million. Most firms rolled those changes out over several months; one in ten took more than two years. The Chamber extrapolates the sample to the whole sector and arrives at PLN 55.4 billion a year — about 6% of its sales — its own calculation for a population much wider than online stores alone. “Although these changes increase consumer trust, they also generate high costs,” commented Patrycja Sass-Staniszewska, president of the Chamber.
The report measures GDPR, Omnibus and DSA; it does not cover payment onboarding at all, so putting those amounts next to an operator’s activation fee would be a misuse and I will not do it. What remains is the time ratio, and it is unambiguous: the activation fee is sometimes free; at one operator it is PLN 59 refunded after ten transactions in two months (as of August 2024) and can be paid in five minutes. The documents the operator looks for in verification are produced in the same store over weeks or months — and have no price list of their own.
Online payment rollout in a store is counted backwards from launch day
The usual work order is: first the store, then the plugin, and the operator application goes last, when the launch date is already announced. Slip comes exactly from that order, because the application is the only schedule item whose timing the store does not set itself.
If card payments are to work on launch day, the application goes roughly two weeks earlier. Terms, privacy policy and cart checkboxes must already sit on the live site on the day of filing, because the operator assesses the store in the public version it opens itself in a browser.
A business account must be open, because the operator will not accept a personal account for settlement. The plugin can calmly wait until the end: fifteen minutes fit any free window in the calendar.
Those 2 weeks are the upper bound from one FAQ. What the typical value is remains unknown — I found no public median onboarding time from operators or industry chambers. Anyone planning a launch therefore plans on a range where the lower bound is a day and the upper bound two weeks.
What does it look like at Paymove?
On the Paymove site we write “three moves and you sell” and “there is no rollout stage, because there is nothing to roll out”. On the technical side it looks like this: the docs reduce integration to four steps — create a payment, redirect the customer, receive the webhook and verify the signature, and if in doubt ask for status. The merchant generates a sandbox key in the panel themselves, so once the account is open they can write and test the integration without waiting for verification to finish.
That is why before signing with any operator it is worth asking three questions, none of which is about integration speed: from which day can I take the first card payment, what must be on the site on the day of filing, and when will the first money hit the account. Everyone answers the first. Answers to the other two show how many times the counterpart has actually run that onboarding — and whether a number appears at all.
Anyone planning a launch therefore has two dates to put in the calendar earlier than go-live: the day terms and privacy policy are already public, and the day the card-acceptance application is filed. The plugin will fit any free quarter-hour between them.



