• Websites · Next.js

Online payment for services: when people pay for work, not for an item in a cart

Paying for services works differently from paying for goods. There is no cart, no quantity and no delivery — there is a specific amount for specific work, sometimes a prepayment, sometimes an invoice for a legal entity. The mechanism for connecting a payment provider is the same as in a store, but the scenario is completely different, and that is exactly where solutions built on catalog logic stumble. We build payment that matches how you actually take money.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
Experience
commercial development since 2015
Price
after a free audit
Guarantee
30
days after project sign-off
Experience
commercial development since 2015
Timeline
7
to 21 working days
Start
free review of the task
Warranty
30
days from the date the acceptance act is signed
Reply
within 2 hours
Terms
under a written contract
What's included

Complete list of work and what you get as a result

  • payment for a specific service without a cart or catalog
  • a payment link with an arbitrary amount for individual cases
  • prepayment or payment in installments, if that is how your business works
  • an invoice for sole traders and LLCs with VAT alongside card payment
  • clear behavior when a payment fails: the client returns to payment, not to nowhere
  • a confirmation for the client and a notification to you about every payment
  • a note of what exactly was paid for, so that you do not reconcile by hand
  • testing of each payment method separately, including a bank decline
  • handover with a description of how to change amounts and add services
When this service isn't right

What's not included — so there are no surprises at delivery

  • accounting and preparing financial reports
  • opening an account and signing a contract with a payment provider — you do that
  • refunds to clients: the decision and the action stay with you
  • promises of sales growth
  • dealing with the tax consequences of your payments
Who it's for

Situations where this service delivers results

Scenario 1 of 4

A service business with fixed services

A consultation, an inspection, a membership, a one-off job with a known price. A payment button next to the service is enough here — a cart only gets in the way.

We'll review your situation in a free audit
Free review of your task

We look at how you actually take money now and which parts of it can be moved to the site without harm.

What we measure

  1. How payment happens nowAn invoice by email, a transfer to bank details, cash on site. This determines what exactly should appear on the site.
  2. How many clients are legal entitiesIf there are many, an invoice with bank details matters more than card payment, and it should be built first.
  3. Whether prepayment is neededAn advance disciplines both sides but adds work with refunds. We look at whether it is justified in your case.
  4. Whether the amounts are fixedIf the price is set after a conversation, what is needed is not a button on the page but a payment link with an arbitrary amount.
  5. Which payment provider you have a contract withWe connect to your provider. If there is no contract yet, we will suggest what to look at, but signing it is up to you.
  6. What happens now when a payment failsMost often nothing: the client is left on their own. This is the part almost nobody tests.

What you get

  • an answer on which payment scenarios you need and which are unnecessary
  • a list of what can be moved to the site now
  • an estimate of the work
  • an honest answer on whether this work is worth the effort in your case

Timeline: 1–3 working days

Why is it free

A single payment button and a set of scenarios with invoices and prepayment differ in scope several times over. Without a review, any amount would be guesswork.

What's next

You receive a list and an estimate. Then you decide for yourself — the document stays with you.

Short form: your contact and site URL
Contract and paperwork

We work officially

Contract, act and invoice — for every project, not just large ones.

Trusted by6 brands

Trusted by: Kvant Energy, GYPSUN, Naturel Cosmetics, Pancer Protection, LUGI, BeeTech

Terms fixed in writing8 points

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

We sign NDAs on request. After completing the work, we delete our access to your services ourselves.

What affects the price

Why two seemingly identical tasks are priced differently

  • Number of payment scenariosA single fixed amount is quick to build. Card, an invoice for legal entities, prepayment and an arbitrary amount are four different paths, each with its own testing.
  • Working with legal entitiesAn invoice with bank details and VAT requires fields in the client profile and document generation — this is a separate part, not a setting.
  • Recurring chargesA membership or subscription adds storing consent to charge, handling declines and cancellations — the most complex scenario in this task.
  • What to do when a payment failsThe right behavior is to return the client to payment with an explanation. This is small but mandatory work that usually gets skipped.
  • Where to send payment dataEmail is the simplest. Passing it to a CRM with a note of what was paid for removes manual reconciliation but adds agreeing the fields.
  • State of the existing siteIf the site was built long ago on someone else's code, you first need to understand where to embed payment. This is the least predictable part.
Cases

Tasks and results in numbers — all metrics measured by us

Textory

Ukrainian SaaS platform for rewriting product descriptions of online stores

Task
Build a service that imports catalogs from marketplaces, rewrites descriptions with an SEO structure, and sells it on a transparent pay-per-use model.
Solution
Application on Next.js with import of directories in four formats, customization of text style, public part and markup for search. Payment — for actual use, with balance replenishment.
Result
Measured on 07/31/2026: First server response of 220 ms at 141 KB of HTML, the fastest response of the 16 portfolio sites measured at that time. 8 public pages, JSON-LD markup with SoftwareApplication, Offer, Organization, WebSite and FAQPage, working PWA manifest.

Chocomaker

B2B supplier of professional equipment for food production

Task
Show a line of equipment with performance and technical characteristics and collect requests for calculation: such equipment is not bought in a basket, it is selected for specific production.
Solution
A catalog site with a calculation request form, two language versions and a complete list of calculation methods on a separate page of conditions. Connected GTM, GA4 and call tracking, messengers in one click from the card.
Result
Measurement 07/31/2026: 106 items in two language versions — 230 addresses in the sitemap-index of four files. First server response 351.4ms, full HTML download 490.4ms at 297.6KB. The six payment methods on the shipping and payment page are the widest set among the sample projects measured. A fair limit: calls are tracked by call tracking, but it is impossible to measure their number from the outside, so we do not provide numbers for calls here.

Did not find your case?

Describe how it works on your side — we will tell you whether “Online payment for a service website” fits and what it means in your situation. No brief and no call: one question, one answer.

Process steps

Transparent stages with approval at every step

Total duration:5–20 days

  1. Reviewing the scenarios

    1–3 working days

    We find out how you take money now and which scenarios are really needed on the site. Unnecessary ones are dropped at this same step.

  2. Connecting the payment provider

    2–5 working days

    We connect your payment provider in test mode and set up how the amount and the payment purpose are passed.

  3. Payment scenarios

    2–8 working days

    We build service payment, links with an arbitrary amount and invoices for legal entities — whichever of these you need.

  4. Failed payments and confirmations

    1–4 working days

    We set up the behavior on a bank decline, the retry, the confirmation for the client and the notification for you.

  5. Testing

    1–3 working days

    We go through each payment method separately, including a decline and closing the tab mid-payment. We test on a phone.

  6. Go-live and handover

    1 working day

    We switch the payment provider to live mode, make the first real payment together with you and hand over the instructions. After that the 30-day warranty from the date the acceptance act is signed applies.

Technologies & integrations

What we build on and what it connects to

Stack

  • Next.js
  • TypeScript
  • PostgreSQL
  • WordPress
  • PHP
  • MySQL
  • Git

Integrations

  • monobank
  • LiqPay
  • WayForPay
  • Privat24
  • Visa
  • Mastercard
  • Google Analytics 4
  • CRM
Payment on the site or an invoice by email

How this option differs from the alternative

An invoice emailed by handOur approach
When the client can payafter a manager sends an invoiceright away, while the decision is fresh
Manager's workloadan invoice for every paymentonly atypical cases
Legal entitiesissued by hand, often with errors in the bank detailsthe invoice is generated from the client's data
Payment reconciliationthe payment purpose has to be decipheredyou can see exactly what was paid for
Costsno fee, but people's time is spentone-off work plus the payment provider's fee
What we need from you

We can't start without this — best to prepare in advance

  1. a list of the services and amounts to accept
  2. whether there are legal entities among your clients and whether VAT is needed on the invoice
  3. whether prepayment, installments or recurring charges are needed
  4. which payment provider you have a contract with
  5. where the payment data should go
  6. who on your side accepts the work
If something is missing — let us know, we'll help you gather it or do it as a separate task.
FAQ

Most frequently asked questions — with concrete answers

How is this different from payment in an online store?

The mechanism for connecting a payment provider is the same, but the scenario is different. A store has a cart, quantities, delivery and stock; services have a specific amount for specific work, often a prepayment, often an invoice for a legal entity. A solution built on catalog logic forces a service business to pretend to be a store, and the client notices.

We do not know the amount in advance. What do we do?

Use a payment link with an arbitrary amount: you agree the price in conversation, send the link, the client pays. For businesses where every job is estimated separately, this works better than a button on a page, and it is simpler to build than a full client account.

Can we accept payment from sole traders and LLCs?

Yes, and it is usually even more important than card payment. The client needs an invoice with bank details, sometimes with VAT. The site can generate the document from data the client enters once, and then it is paid by an ordinary bank transfer. This does not replace accounting: the site prepares the document, it does not keep the books.

What happens if a payment fails?

The right thing is to return the client to the payment step with an explanation and the option to try again with another card. Most often there is nothing like that at all: the person sees a blank page and cannot tell whether the money was charged. This is exactly the scenario we test on purpose rather than hoping it will not happen.

Who is responsible for refunds?

You are. We build the technical ability to refund if you need it, but the decision to refund and the action itself stay with you: it is a matter of your arrangements with the client, not of how the site works.

Do we need a contract with the payment provider?

Yes, and you sign it — as a sole trader or an LLC. We connect to your own merchant account, so the money goes directly to you, with no intermediaries. During the review we can suggest what to look at when choosing, but we will not sign the contract for you.

How long does the setup take?

7 to 21 working days. The connection itself is quick; the time goes into the scenarios — invoices for legal entities, prepayment, behavior on decline — and testing each of them separately.

Do you guarantee that people will pay more often?

No. Online payment removes the delay between the decision and the payment, and for some businesses this is noticeable. But if clients already pay invoices quickly, the difference will be small — and we will say so directly during the review, not after the work.

Let's look at how you take payment now

We will show which scenarios are worth moving to the site and which are better left with a manager. The review is free.

From measured casesMeasurement 07/31/2026: 106 items in two language versions

View cases
  • Reply within 2 hours
  • No commitment
  • We work under a contract

There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.