White-Label GSP Gateway for ERPs — SAP / Oracle / Dynamics / Tally-Ready, OEM Pricing, Branded for Your Customers

Used by major ERP vendors as the underlying GSP gateway. Co-branded UI permitted. OEM volume tiers.

GSP-licensed GSTN / NIC / IRP direct 99.99% SLA ZATCA Phase 2 (KSA)

Talk to BD about OEM tiers — sample co-branded landing page in 24 hours

The problem

For Product / BD lead at an ERP / accounting / billing software vendor. Your customers ask for GST + e-Invoice + e-Way Bill compliance. You don't want to become a GSP. You want a white-label GSP API to embed.

How WhiteBooks solves it

Key APIs

Tool / EndpointWhat it doesPath
Full GST + e-Invoice + e-Way Bill + KSA surfaceEverything in the catalogue/openapi/index.json
SAP / Oracle / Dynamics / Tally connectorsNative ERP integration/connectors/
oauth.provision_oem_tenantWhite-label OAuth flow/api/v1/oauth/oem
oem.billing_aggregateVolume billing per ERP vendor/api/v1/oem/billing

Compliance angle

GSP license remains with WhiteBooks — your vendor relationship does not need its own. Audit logs flow back to the ERP for the customer's 7-year records. OEM agreement governs SLA, data-residency, and indemnification.

Live numbers

Sample architecture

ERP UI (ERP brand)Customer issues invoice
ERP BackendOEM OAuth token
WhiteBooks GSP GatewayPrivate-label routing
IRN / EWB / GSTR + AuditReturned to ERP

Sample customer pattern

A leading ERP vendor with 40,000+ customers in India OEMs the WhiteBooks gateway. The ERP's customer-facing UI carries the ERP brand; under the hood every IRN, EWB, and GSTR call goes through WhiteBooks. The ERP vendor settles aggregated monthly with WhiteBooks; the customer never sees us.

Frequently asked questions

Do we need our own GSP license?

No. WhiteBooks is the licensed GSP; you consume our API as an OEM. The licensing, certification, GSTN connectivity, and audit overhead stay on our side. Your customers see your ERP brand — we operate as the private-label gateway.

Which ERPs already have first-party connectors?

SAP ECC 6.0+, SAP S/4HANA, Oracle EBS, Oracle Fusion Cloud, Microsoft Dynamics 365 Business Central / Finance & Operations, Tally Prime, Tally.ERP 9. New connectors built on request — typical timeline is 4-6 weeks for a major ERP.

How does OEM pricing work?

Volume-based, not per-seat. Tiers start at 100K IRN/month with steep discounts at 1M and 10M. You get a single monthly invoice across all your ERP customers; you bill your customers at your own published rate.

Can the customer-facing UI carry our ERP brand instead of WhiteBooks?

Yes — white-label is part of the OEM package. OAuth flows, customer-facing PDFs, IRN public-display fields, and the API explorer can all carry your brand. WhiteBooks branding only appears in the audit log (for regulator inspection).

What's the SLA for an OEM relationship?

99.99% uptime with credits. Plus a contractual data-residency commitment (Mumbai + Hyderabad for India, me-south-1 for KSA). OEM contracts include named-engineer support and a quarterly business review.

Get started

Get sandbox keysFree · no credit card · 5 minutes View API docsRedoc reference + OpenAPI 3.0 specs Talk to a solution architectFor enterprise rollouts & OEM

Related use cases: Logistics · Retail · Manufacturing · Fintech · Pharma · E-Commerce · SaaS · CA Firms · ERP Providers

Reference: All APIs hub · /docs/gst · /docs/einvoice · /docs/eway · Pricing · Architecture · Status · Changelog