Log in Start free

Integrations

Online payments

Seven processors — Romanian banks, PayU, NETOPIA and Stripe. Pick one; the card never touches ELVPro.

At a glance

Plan
Business+
Last updated
September 2, 2026

What this covers

Card payment on your storefront, through whichever processor you already bank with. ELVPro speaks to seven of them and a yard runs one at a time — the integration work is done, so choosing is a business decision rather than a technical one.

How it works in ELVPro

Seven processors, one seam

LibraPay (Libra Bank), EuPlătesc, ING WebPay, BT iPay, PayU, NETOPIA and Stripe. Whichever you pick, checkout, settlement, refunds and reporting behave identically inside ELVPro — you are choosing a bank relationship, not a different shop.

The card never reaches your shop

Every one of them is a hosted page or a redirect: the buyer types their card on the processor's own page. Nothing card-shaped is stored or logged here, which keeps your PCI obligations at the lightest tier. 3-D Secure is applied by the processor.

Nothing is believed until it is verified

A "paid" message is only acted on once proven — an HMAC signature recomputed over the processor's exact field order, a JWT checked against its public key, or a fresh query to the processor's own API. An unverified callback creates no order.

Settled exactly once

The server-to-server notification, the buyer's return and a scheduled sweep for processors that never push all lead to the same place: whichever arrives first settles the order. A buyer who closes the tab mid-payment still gets their order.

The part is consumed when the money is confirmed

not when the buyer clicks pay. The reservation held during checkout becomes a sale only on a verified success.

An invoice follows automatically

The order carries the per-line VAT resolution decided at checkout — margin scheme for salvaged parts, standard VAT, reverse charge or an exemption — and the invoice is issued from that snapshot and emailed to the buyer.

Currency handled per processor

The RON-only ones are sent the RON-converted amount at the current BNR rate; Stripe and PayU are charged in the order's own currency. Your books stay in your base currency either way.

Switching later is safe

Every payment stays attributed to the processor that handled it, so last quarter's payments remain explainable after you move.

Your money never passes through us

Settlement goes from your processor to your bank account; ELVPro holds nothing and stores your processor keys encrypted.

When it happens

When What happens
At checkout the signed hand-off to the processor you have enabled.
On the callback verification first, then the order, the invoice and the emails.
Every few minutes the reconcile sweep, for processors that never push a notification or when one goes missing.
On a declined or abandoned attempt the processor's own code and wording are recorded against the checkout, so you can see why a sale did not happen even months later.

Why it matters

Card payment is the difference between an enquiry and a sale — but taking cards badly is how shops end up with chargebacks, orders marked paid that never were, or a PCI questionnaire they cannot answer. Supporting the Romanian banks matters just as much: for most yards the processor is decided by who they already bank with, not by what a platform happens to have integrated.

What we don't claim

Online payments are part of checkout, which is available on Business and Enterprise. Your contract, fees and settlement are with the processor you choose. Two of the seven (LibraPay and NETOPIA) expose no refund API, so a refund there is a deliberate manual step in the bank's panel — ELVPro flags it rather than pretending it happened.

Other integrations

Ready to connect it?

Start a free trial and set this up in your own yard — no card required.

Start free All integrations