UAEN
Get a quote
AgentsAutomationsPricingProcessFAQ
UAEN

Checkbox · Vchasno.Kasa · monobank

PRRO integration: automatic Ukrainian fiscal receipts from your website, CRM or ERP

Selling to customers in Ukraine? Card payments for online orders generally need a fiscal receipt from a PRRO, Ukraine’s software cash register. We connect Checkbox, Vchasno.Kasa or monobank to your systems, so each receipt is issued on time and reaches the customer by email, SMS or Viber.

  • Built for non-standard setups: 1C/BAS, custom CRMs, marketplaces plus a website, several ФОП
  • The receipt’s fiscal number and link are saved back to the order and your books
  • Fiscalization rules are agreed with your Ukrainian accountant; we build on test keys
Discuss your integrationWhen is a receipt needed?
Compliance review
from $150
Integration
from $800
Support
from $250/mo
Order #1042website · 10:14paid by cardHoodie black, M × 22,360Hoodie grey, L × 1910Total3,270 UAHCheckbox APIPOST /api/v1/receipts/sell→ receipt via Viber / SMS / emailReceipt for order #1042open receipt ↗3,270.00 UAH · FN 0001056731C/BAS · KeyCRMFN + receipt on the orderSOLE PROP. “YOUR STORE”online storeFISCAL RECEIPTHoodie black, M2 × 1,180.002,360.00Hoodie grey, L1 × 910.00910.00TOTAL3,270.00Card ··44173,270.00PRRO FN4000000000Receipt FN00010567303.10.202610:15:07PRRO · ONLINEsample for illustrationFISCAL NUMBER • RECEIPT REGISTERED • FN

№ 01Simulator

When do you need a fiscal receipt? Check your scenario

Pick how the customer pays and where the order comes from. You’ll see the rule, when the receipt is due and how the integration automates it.

How the customer pays
Where the order comes from

ResultCard on the websiteCash on delivery (Nova Poshta)Transfer to a ФОП account (IBAN)Card terminal in a shopRefundWebsiteProm or RozetkaInstagram or Telegram

Receipt required

Rule
A card payment for an online order is a settlement operation: it needs a fiscal receipt from a PRRO.
When to issue
At payment: once the payment provider confirms it, the integration creates the receipt and sends it to the customer.

Required — before dispatch

Rule
The carrier collects the money, but the receipt is yours: per tax-service guidance, it is issued before hand-over and goes inside the parcel.
When to issue
Before hand-over: created with the waybill and printed for the warehouse. The payment type on it is agreed with your accountant.

Depends — ask your accountant

Rule
A transfer by bank details is usually not a settlement operation, but card payments are the exception. Your accountant makes the final call.
When to issue
By your accountant’s rule: the integration either just marks the payment, or issues a receipt once the money arrives.

Receipt required

Rule
A card payment through a POS terminal is a settlement operation: it needs a receipt just like cash.
When to issue
Right at payment. The integration pulls the basket from your CRM or ERP so the cashier doesn’t key items twice.

Return receipt required

Rule
If the sale went through a PRRO, the refund usually needs a return receipt too. Partial refunds and refunds to a card are agreed with your accountant.
When to issue
When the money goes back: the integration finds the original receipt, issues the return receipt and marks it in the CRM.
Channel
We read orders and payment statuses from your CMS or CRM — WooCommerce, OpenCart, Horoshop or a custom stack.Orders come in through KeyCRM, SalesDrive or the marketplace API. If the marketplace’s payment service takes the money, who issues the receipt depends on its terms.A sale in a messenger is still a payment, with the same rules as the website. Orders from chats reach the CRM by hand or through an AI agent.

How the integration automates it

  1. OrderwebsiteProm · Rozetkamessenger
  2. Paymentcard ✓
  3. PRRO APIreceipt + FN
  4. To customerViber · SMS · email
  5. Books1C/BAS · KeyCRM
  1. OrderwebsiteProm · Rozetkamessenger
  2. Waybillready to ship
  3. PRRO APIreceipt pre-dispatch
  4. In the parcelprint + email
  5. Booksmatch carrier payouts
  1. OrderwebsiteProm · Rozetkamessenger
  2. InvoiceIBAN · statement
  3. Rulereceipt: yes or no
  4. To customerinvoice or receipt
  5. Books1C/BAS · KeyCRM
  1. Saleshop · pick-up
  2. Terminalcard ✓
  3. PRRO APIreceipt + FN
  4. To buyerprint · email
  5. Booksstock in 1C/BAS
  1. RefundwebsiteProm · Rozetkamessenger
  2. Moneyback to the card
  3. PRRO APIreturn receipt
  4. To customerViber · SMS · email
  5. Booksrefund in 1C/BAS

A guide, not tax advice. Fiscalization logic is agreed with your accountant.

Add this scenario to my request

№ 02Rules & risk

Selling online in Ukraine: fiscal receipt rules and what mistakes cost

Short, with sources. Not legal or tax advice: whether and how these rules apply to the way your company sells in Ukraine is for your accountant to confirm.

  • Card payment for an online order

    A settlement operation: a receipt through an RRO or PRRO is required.

    yankiv.com, tax-service guidance for online stores

  • Courier delivery, paid on receipt

    The receipt is issued before the parcel is handed over and goes inside it.

    yankiv.com

  • Transfer to a ФОП account by IBAN

    Depends: a transfer by bank details is usually not a settlement operation; card payments are the exception. Check with your accountant.

    yankiv.com, 2026

  • Fine for selling without a receipt

    100% of the value of goods sold in breach for a first violation, 150% for each repeat. For single-tax payers not registered for VAT — 25% and 50%.

    yankiv.com, 2026

Rough exposure of a month without receipts

Which fine rule
Sales without a receipt48,000 UAH
Fine, first violation48,000 UAH
Repeat violation72,000 UAH

Indicative only, not tax advice. The actual amount is set by the inspection.

№ 03Hard cases

Checkbox API integration with 1C, BAS, KeyCRM or your own CRM

A standard WooCommerce store already has a Checkbox plugin — if it covers you, we’ll say so. We take the setups no ready module covers.

  • 1C and BAS

    Receipts from sales documents in 1C/BAS, common Ukrainian ERPs; the fiscal number goes back into the document.

  • KeyCRM and SalesDrive

    Fiscalization on an order status, “paid” or “shipped”; the receipt sits on the order card.

  • Your own CRM or website

    A small service between your system and the PRRO API: queue, retries and a log of every receipt.

  • Prom and Rozetka plus a website

    Orders from several channels, one fiscalization logic and no receipt issued twice.

  • Cash on delivery

    Receipt before hand-over, printed with the Nova Poshta waybill, matched against the carrier’s payouts.

  • Refunds

    Full and partial refunds: a return receipt linked to the original sale.

  • Several ФОП or registers

    Routing rules: which product, warehouse or channel goes to which ФОП and register.

  • Shifts and Z-reports

    The shift opens before the first receipt and closes with a Z-report on schedule.

  • Outages and offline

    No lost receipts when the API is down: a queue, duplicate-safe retries, and PRRO offline mode if your provider supports it.

Need waybills, stock sync or a full order pipeline as well? See n8n & AI automation or hire developers in Ukraine.

№ 04Diagram

How Ukrainian fiscalization for e-commerce works, automated

Five steps for every order, plus branches for the events that break manual workflows.

Separate branches01Orderwebsite · Prom · RozetkaInstagram · Telegram02Paymentcard · cash on deliveryterminal · transfer03PRRO APICheckbox · Vchasno.Kasamonobank04To customerViber · SMS · emailor printed in parcel05Books1C/BAS · KeyCRMSalesDrive · your CRMFNCash on deliveryreceipt before hand-over,printed with the waybillRefundreturn receipt linkedto the original saleShift & Z-reportopens before first receipt,closes on scheduleAPI or network outagequeue, retries, no duplicates,alert in TelegramSeparate branchesOrderwebsite · Prom · RozetkaInstagram · Telegram01Paymentcard · cash on deliveryterminal · transfer02PRRO APICheckbox · Vchasno.Kasamonobank03To customerViber · SMS · emailor printed in parcel04Books1C/BAS · KeyCRMSalesDrive · your CRM05Cash on deliveryreceipt before hand-over,printed with the waybillRefundreturn receipt linkedto the original saleShift & Z-reportopens before first receipt,closes on scheduleAPI or network outagequeue, retries, no duplicates,alert in Telegram

  • Checkbox, Vchasno.Kasa or monobank

    We use the providers’ public APIs, most often Checkbox with its test mode. We are not an official partner of these services.

  • No receipt issued twice

    Each receipt is tied to an order key, so a retry never creates a duplicate; the log shows what was issued and when.

  • The fiscal number where your team works

    Fiscal number and receipt link live on the CRM order and the ERP document, not only in the PRRO dashboard.

№ 05Getting started

What we need from you

Four things and we can start. You grant the access and can revoke it at any time.

  1. PRRO access

    A test register and API keys; for Checkbox, the register key and cashier login. Live keys only at launch.

  2. A test environment

    A copy of 1C/BAS or a test API key for KeyCRM, SalesDrive or your CRM — we never touch live orders.

  3. Your accountant’s rules

    Which payments get receipts and when, how refunds and cash on delivery work, which ФОП and register for which products.

  4. Someone for the pilot day

    A manager or warehouse person who runs a few real orders with us.

Fiscalization rulesCard onlinereceipt at onceCash on deliverybefore dispatch?ФОП accountaccountant’s callRefundreturn receiptФОП 1 / ФОП 2by product groupaccountantAPPROVED

№ 06Process

From review to support: how we launch a PRRO integration

  1. Payment-flow review

    We map payments and channels, find missing or doubled receipts, list questions for your accountant and fix the price.

    1–2 days

  2. Build on test keys

    We build on a test register and test data; every scenario gets its own test.

    3–10 days

  3. Pilot day

    Real orders with your manager; receipts checked against the PRRO dashboard and the books.

    1 day

  4. Launch

    We switch to live keys, turn on outage alerts in Telegram and hand over a short guide.

    1 day

  5. Support

    We watch errors, add payment types, ФОП and registers, and track API changes.

    monthly

Business days, for one system and one PRRO.

№ 07Pricing

PRRO integration pricing

We quote the exact price after the review and fix it before work starts.

  • Compliance review

    • map of payments and channels: where receipts are due
    • questions for your accountant
    • integration plan at a fixed price
    • a straight answer if a plugin is enough

    TOTALfrom $150

    credited toward the integration

    Choose

  • Integration

    • Checkbox, Vchasno.Kasa or monobank via API
    • card, cash on delivery, refunds
    • fiscal number and receipt in your CRM or ERP
    • tests, pilot day, guide

    TOTALfrom $800

    one system + one PRRO

    Choose

  • Support

    • error and receipt-queue monitoring
    • new payment types, ФОП and registers
    • updates when provider APIs change
    • replies in business hours (Kyiv time)

    TOTALfrom $250/mo

    after launch

    Choose

№ 08Request

Tell us how you take payments

A few clicks and we understand your setup. We reply within an hour in business hours (Kyiv time) with questions and a first estimate.

What happens next

  1. We clarify your setup by message or a short call
  2. We run the review and fix the price
  3. We build on test keys and launch after the pilot day

01Your payment flow

Where orders live · pick any
PRRO provider
Payments · pick any
Orders per month
Specs, screenshots, photos, voice — drop them here or paste with Ctrl+V
    • Reply within 1 hour in business hours
    • Fiscalization logic agreed with your accountant
    • NDA on request

    By sending, you agree to our privacy policy.

    FAQ

    PRRO integration: common questions

    Didn’t find your answer? Ask in the request form above — we reply within an hour during business hours.

    How much does PRRO integration cost?

    A compliance review of your payment flow starts at $150 and is credited toward the integration. Integrating one system with one PRRO starts at $800; support after launch from $250 a month. We quote the exact price after the review and fix it before work starts — it depends on the number of systems, payment types, ФОП and cash registers.

    How long does a Checkbox integration take?

    The review takes 1–2 business days. A typical integration of one CRM or website with Checkbox takes 1–2 weeks, including tests and a pilot day. Setups with 1C/BAS, several ФОП or marketplaces take longer; we fix the timeline after the review.

    Which PRRO providers do you work with?

    Most often Checkbox, which has an open API and a test mode for development. Also Vchasno.Kasa and monobank through their public APIs. We are not an official partner of these services. If you use another PRRO with an API, we’ll review its documentation during the audit.

    How do you handle cash on delivery?

    Per Ukrainian tax-service guidance cited by yankiv.com, with courier delivery paid on receipt the fiscal receipt is issued before the parcel is handed over and goes inside it. The integration creates the receipt together with the Nova Poshta waybill, prints it for the warehouse and marks the payment in your CRM or ERP once the carrier pays out. Your accountant confirms the payment type and the reconciliation.

    How do refunds work?

    When a refund is recorded in your CRM or ERP, the integration finds the original receipt and issues a return receipt for the items and amount being refunded, including partial refunds. The return receipt number is stored next to the sale. How refunds to a card are handled is your accountant’s decision — we implement their rules.

    We have several ФОП or cash registers. Is that possible?

    Yes. Each ФОП (sole proprietor) has its own PRRO and keys, and the integration routes receipts by rules: product group, warehouse, sales channel or shop. You and your accountant define the routing; we automate it and test every scenario.

    What happens if the Checkbox API is down?

    The receipt isn’t lost. The integration queues it, retries and never creates duplicates — each receipt has a unique order key. If the outage drags on, you get a Telegram alert. If your provider supports the PRRO offline mode, we set it up according to the provider’s rules.

    Do you need my accountant?

    Yes. Your Ukrainian accountant decides which payments get receipts, when, with which tax groups and how refunds are handled — and whether the rules apply to your company’s setup in the first place. We prepare a list of questions after the review, then implement and test the agreed rules. This page is not legal or tax advice.

    Development

    Also from the studio