Skip to content
Rupee Craft
Trust centre

Security and integrity, described plainly.

We describe the controls that exist today, and we don’t claim certifications we don’t hold.

An invoice with a record.

  1. Invoice

    Structured seller, buyer and line-item data.

  2. Validated

    FBR validation must return valid before posting.

  3. Posted

    The returned FBR invoice number is stored.

  4. Locked

    Posted invoices cannot be edited.

  5. Audited

    Creation and edits have recorded audit history.

01

Access & identity

Accounts are provisioned by an admin. Passwords are hashed with bcrypt using 12 rounds. One-hour access tokens with refresh tokens and rate-limited login govern access.

What this means for youYour account is provisioned through onboarding, with authenticated API access.

02

Data isolation

Invoice and profile queries are scoped to the owning account. Admins see the users they onboarded. Super Admins can see the platform.

What this means for youAccount ownership and administrator roles determine which records are visible.

03

Transaction integrity

Every invoice is validated before posting. Posting is blocked while in progress or once an FBR invoice number exists. Posted invoices are locked, and money uses exact decimals.

What this means for youThe saved invoice and its FBR acknowledgement remain linked after posting.

04

Auditability

The audit log records who changed what, when and from where, with before and after values. It covers invoice creation, updates and deletion, user and admin changes, and logins.

What this means for youYou can review recorded changes rather than reconstructing them from memory.

05

Application hardening

API inputs are sanitised and validated. Security headers and API rate limits form additional application controls.

What this means for youRequests are checked at the API boundary as well as in the interface.

06

Infrastructure

Invoice records use PostgreSQL on managed cloud infrastructure. Monetary values are stored as decimals with two decimal places; quantities use three.

What this means for youRecorded money and quantities retain their defined storage precision.

Shared responsibility.

Application controls work alongside the decisions your team makes about access and invoice data. Your team manages these parts of the workflow.

  • Manage who can access your business account.
  • Keep your business’s FBR token current.
  • Review buyer details, scenario, line items and totals before posting.

Report a vulnerability

Describe the affected page, the steps to reproduce and the impact you observed. Email us with the subject “Security report”.

Report a vulnerability

An invoice with a record.

  1. Invoice

    Structured seller, buyer and line-item data.

  2. Validated

    FBR validation must return valid before posting.

  3. Posted

    The returned FBR invoice number is stored.

  4. Locked

    Posted invoices cannot be edited.

  5. Audited

    Creation and edits have recorded audit history.

Questions

Security questions.

Talk through your invoice workflow.

Book a demo to discuss your sectors, scenarios and setup.