Valeur X
Valeur X ZATCA API

Compliance is one HTTP call

Your system already knows how to raise an invoice. It should not also have to learn certificate onboarding, XML signing, hashing chains and clearance. Post the invoice to us and get back the signed document the authority accepts.

  • Onboarding in minutes
  • Your own certificate
  • Sandbox and production
Get an API keySee the modules
  • 1Endpoint to integrate against
  • XML+QR+PDFReturned for every invoice
  • SDKByte-equivalent to the official one

The hard part was never the invoice

Phase 2 is a cryptography project wearing an accounting hat: a CSR and an OTP exchange with Fatoora, a per-device certificate, a hash chain that must never break, canonical XML that must sign byte-for-byte, then clearance for standard invoices and reporting for simplified ones. Every company that sells anything now has to solve it, and none of them wanted a cryptography project.

  • Onboarding handled by a wizard that exchanges the OTPs for you
  • Your certificate, encrypted at rest and never shared between tenants
  • Signed XML that matches the official SDK byte for byte
  • Webhooks when the authority accepts, rejects or is slow to answer
What is inside

Everything in the service

A compliance layer for a system that already exists — not a system to replace it.

  • Onboarding wizard

    Certificate request, OTP exchange with Fatoora and device registration, walked through in minutes rather than read out of a specification.

  • One invoicing endpoint

    POST an invoice and receive the signed XML, the QR and a PDF. Standard invoices are cleared, simplified ones reported — the service knows which is which.

  • Webhooks

    Told when the status changes rather than polled for it, with retries and a delivery log you can inspect.

  • API keys & environments

    Separate keys for sandbox and production, rotatable, with per-key usage so an integration gone wrong is visible before the bill is.

  • Dashboard & usage

    Every invoice, its status, the authority's response, and what you have used this month — for the finance team, not just the developer.

  • Buyers & documents

    B2B buyer records, credit and debit notes, and the archive the regulation requires you to keep.

Getting started

From sign-up to your first cleared invoice

  1. 01

    Sign up & onboard

    The wizard takes your commercial details, requests the certificate and completes the OTP exchange with Fatoora.

  2. 02

    Sandbox

    Integrate against the sandbox with your real invoice shapes until the responses are what you expect.

  3. 03

    Go live

    Swap the key for the production one. Nothing else in your integration changes.

  4. 04

    Watch it

    Webhooks into your system, the dashboard for your finance team, and us on the other end when the authority behaves oddly.

How it is priced

Priced by invoices

By volume, with a sandbox that costs nothing. Quoted after a short call about how many invoices you issue and how many entities you issue them from.

  • Pay as you go

    For a business making its own system compliant.

    • Per invoice, per month
    • Sandbox included
    • Webhooks and dashboard

  • Volume

    For a high-volume issuer, or a group of entities under one account.

    • Committed volume pricing
    • Several entities, one login
    • Priority support

  • White label

    For a software vendor making their own customers compliant.

    • Your brand on the portal
    • Per-tenant certificates
    • Reseller terms
Get an API key

Connects with

It is designed to sit behind something that already invoices.

FAQ

Questions about the ZATCA API

  • No, and that is the point. This sits behind whatever raises your invoices today — your own software, an ERP, a POS — and makes what it produces compliant. If you wanted to replace the accounting system we would be selling you a different product.

  • Yours. The onboarding wizard requests it in your name and it is encrypted at rest, per tenant. Nothing is shared between customers, which is what makes an audit answerable.

  • The implementation is byte-equivalent to the official ZATCA SDK and proven against the live validator. That is a testable claim, not a reassurance — and the sandbox is where you test it with your own invoices.

  • The invoice is queued and retried, the status stays visible, and your webhook fires when it resolves. Your system is never left holding a request that silently failed.

Send us one invoice from your system

The sandbox will tell you in an afternoon whether this removes the problem. That is usually the whole evaluation.

Get an API keyAll products