Payments · LibraPay · PCI-DSS

Online Card Payments — LibraPay Processor

Version 1.0 · Effective date: 18 May 2026

Complementary to Terms and Conditions (Art. 6), Refund Policy and Privacy Policy. Compliant with GEO 34/2014 (consumer rights), Law 209/2019 (payment services — PSD2), Regulation (EU) 2016/679 (GDPR), Law 365/2002 (e-commerce).

Summary

  • Card payments are processed exclusively through LibraPay (commercial brand of Libra Internet Bank S.A., supervised by the National Bank of Romania).
  • We do NOT store full card numbers (PAN), CVV codes or PIN — all card data is processed directly by LibraPay, certified PCI-DSS Level 1.
  • Authentication via 3-D Secure (Visa Secure / Mastercard Identity Check) is mandatory at every payment.
  • Accepted cards: Visa and Mastercard, issued in Romania or in another country accepted by LibraPay.
  • For active subscriptions, automatic renewal uses a tokenisation mechanism (CMASK) provided by LibraPay — full card numbers are never accessible to us.
  • You can dispute a transaction through your issuing bank (chargeback Visa / Mastercard) regardless of the channel; we cooperate with the bank in providing transaction evidence.

1. Parties and roles

Merchant

NOIDEEA S.R.L.

CUI: RO48069626

Trade Register: J40/8019/2023

Address: Calea Vitan 242, Corp C2 Parter Birou 17, Sector 3, București

Web: statusdosar.ro

The merchant operates the platform, sets the price, issues the fiscal documents and is responsible for service delivery.

Payment processor

LibraPay

Operated by: Libra Internet Bank S.A.

Country: România (UE / SEE)

Supervision: Banca Națională a României (BNR)

Certification: PCI-DSS Level 1

Icon securitate LibraPay

The processor handles card data, performs 3-D Secure authentication, executes the transaction and returns only the result (not card details) to the merchant.

You can verify LibraPay's status via the Romanian National Bank at www.bnr.ro or via the LibraPay official documentation.

2. How a card payment flows

  1. You choose a subscription plan on /preturi and confirm billing data.
  2. You explicitly accept the Terms and Conditions, including Art. 6 (payments) and confirm that you give your express prior consent for the immediate provision of the digital service (GEO 34/2014 art. 16(m)).
  3. The platform redirects you securely to the official LibraPay gateway page.
  4. On the LibraPay page you enter the card number, expiry date and CVV. Card data is collected, validated and processed entirely by LibraPay — never by our servers.
  5. LibraPay triggers 3-D Secure authentication with your issuing bank (SMS code, banking app push, biometric — depending on the bank).
  6. Upon successful authentication, the amount is captured and LibraPay sends the platform an asynchronous payment confirmation. This confirmation is the authoritative source of payment status, validated by the platform before any subscription activation.
  7. The platform activates the subscription, sends a confirmation email and queues invoice generation. The fiscal document (informational "invoice suggestion") is issued within 5 working days.
  8. If you close the browser before LibraPay finishes, the IPN still arrives — your subscription will be activated regardless. You can check status anytime in your account.

3. Accepted cards and authentication

Accepted brands

  • Visa (debit, credit, prepaid)
  • Mastercard (debit, credit, prepaid)

American Express, Diners Club, JCB, UnionPay, Apple Pay and Google Pay are NOT currently supported.

Authentication 3-D Secure

  • Visa Secure
  • Mastercard Identity Check

Authentication is performed by your issuing bank, not by us or LibraPay. PSD2 SCA (Strong Customer Authentication) compliant.

A transaction can be declined for reasons exclusively on the issuing bank side (insufficient funds, blocked card, anti-fraud rules, limit exceeded). In such cases the merchant has no visibility on the cause; you must contact your issuing bank.

4. What card data we see vs. what stays at LibraPay

Data LibraPay Status Dosar
Full card number (PAN)Yes (PCI-DSS isolated)No — never
CVV / CVCYes (transient, never stored)No — never
PINNo (PIN is used only for ATM/POS)No — never
Card expiry dateYesOnly YYMM, only for MIT recurrence (column-encrypted)
Masked card number (CMASK)YesYes — last 4 digits + first 6, e.g. 411111****1111
Transaction reference (Order, RRN, INT_REF, APPROVAL)YesYes — needed for invoice and dispute
Transaction amount and currencyYesYes
Card holder nameYesNo (different from billing name)

Even if LibraPay's gateway page appears on our domain in some flows, the form fields where you type card data are served and processed by LibraPay (PCI-DSS scope). Our servers receive only the post-transaction confirmation (success / failure + masked references).

5. Automatic renewal (variable recurrence — MIT)

When you opt in for automatic renewal of a subscription, LibraPay sets up a MIT (Merchant Initiated Transaction) token for your card. The token is linked to your subscription and allows future charges to be initiated by the merchant, within strict limits:

  • The initial authorisation (first payment) is fully authenticated 3-D Secure — you approve the card and the variable recurrence at the same time.
  • For subsequent charges, the merchant initiates the transaction through LibraPay with the saved token (no card number ever leaves LibraPay); the issuing bank may, in some cases, request additional authentication.
  • Each renewal generates a separate IPN; the platform sends you an email confirmation per charge and a renewal reminder at least 7 days in advance.
  • You can cancel automatic renewal at any time from your account; the subscription continues until the end of the period already paid.
  • The token expires automatically at the recurrence expiry date (RECUR_EXP) or when the card expires (EXPIRY), whichever comes first — recorded by LibraPay.

6. Prices, currency, invoice

  • All prices are in Romanian Lei (RON) and include VAT according to current fiscal law.
  • For business subscribers (PJ), an informational "invoice suggestion" is generated through our partner FGO based on the billing data you provide. The document has informational value; for any fiscal correction, contact us via the contact form.
  • The fiscal document is issued and sent electronically within 5 working days from successful payment.
  • The price displayed at checkout is final — no hidden fees. Banking fees for issuing the card (if any) are entirely the responsibility of the issuing bank.

7. Consumer rights (GEO 34/2014)

Express prior consent at checkout

At checkout, the consumer (natural person) ticks the box: "I agree with the Terms and Conditions and request immediate provision of the digital service. I acknowledge that I lose my right of withdrawal under Art. 16(m) GEO 34/2014." — this tick constitutes the mandatory express prior consent. The Terms and Conditions version accepted is recorded with timestamp in the consent history.

The full Refund and Cancellation Policy is detailed in Refund Policy. In short:

  • 15-day free trial in advance allows you to evaluate the service without any payment;
  • After paid activation, no refund is granted per Art. 16(m) GEO 34/2014 — exception: proven major service defect attributable exclusively to the merchant;
  • You can cancel automatic renewal at any time; access continues until the end of the paid period.

8. Refund and chargeback

Refund initiated by the merchant

When a refund is justified (proven major defect, evident processing error, support agreement), the merchant initiates the refund through LibraPay. The refund is sent to the original card; arrival depends on the issuing bank rules (usually 3-10 working days).

Chargeback initiated by the cardholder

You can dispute a transaction directly with your issuing bank, under the Visa / Mastercard rules. The merchant cooperates with the acquirer and processor to provide transaction evidence (timestamps, IPN, billing data, access logs). We recommend contacting our support first — most issues can be resolved amicably within a few working days.

For dispute resolution via the National Authority for Consumer Protection (ANPC) or the EU online dispute platform, see the Complaints Policy.

9. Failed transactions and dispute resolution

  • Failed authentication 3-D Secure — the amount is NOT debited. You can retry with the same card or use a different one.
  • Debited but subscription not active — possible momentary delay in the payment confirmation. Usually self-resolves within 15 minutes. If after 30 minutes the subscription is still inactive, contact us with the transaction reference.
  • Double charge for the same order — the order reference is unique, and the platform prevents double activation for the same order. If the bank shows a double debit, contact us — we identify the second transaction (if it is a real one) and initiate the refund.
  • Charge without a corresponding subscription — possible authentication abandonment with the bank still locking the amount. Funds unlock automatically within 7 days (banking standard).

For investigation, the merchant needs the order reference (visible in the email confirmation). Without this reference, identification can take additional working days.

10. Security and compliance

  • PCI-DSS Level 1 at LibraPay — independently audited annually. The merchant is out of scope for storing card data (PAN, CVV, PIN); our scope is limited to receiving non-sensitive transaction references.
  • 3-D Secure 2.x (Visa Secure / Mastercard Identity Check) — mandatory at every transaction; PSD2 SCA compliant.
  • Encrypted communication end-to-end between your device, the LibraPay gateway and the platform.
  • Authenticity verification for every payment confirmation received from LibraPay — the platform validates that the confirmation genuinely originates from the processor before applying any account change.
  • Tamper-proof audit log — every payment, refund and subscription change is recorded with retention sufficient to support audit and accountability under GDPR.
  • Operational defence-in-depth — additional technical and organisational measures are in place, documented internally and reviewed periodically.

Specific technical configurations are kept confidential as a defensive measure. For PCI-DSS reference, see PCI Security Standards Council at www.pcisecuritystandards.org.

11. Contact and complaints

Merchant support

External authorities

For any issue specific to card data processing or how LibraPay handles your card information, you may also contact LibraPay (Libra Internet Bank) directly through their official channels.

Last updated: 18 May 2026 · Version 1.0

© 2026 NOIDEEA S.R.L. — All rights reserved.