Xirag Payments stack for PAs and PGs

The payments technology stack Xirag provides to payment aggregator (PA) and payment gateway (PG) companies, built as a module of the Xirag operating system, so approvals, audit and identity come from the same core as every other module.

In development, sandbox
Payments console · Lotus Foods (demo)Sandbox
128orders (demo)
3refunds to approve
1batch to reconcile
  • OrderLotus Foods (demo), INR 4,850.00Paid
  • RefundAcme Traders (demo), INR 2,400.00Needs approval
  • LinkKaveri Textiles (demo), INR 18,000.00Created
  • PayoutSettlement batch (demo)Reconciled
Illustrative mock-up with fictional demo data; not a live console.
Capability areas

Payment aggregator operations, UPI and reconciliation on one stack

Each area is specified in the Xirag Payments requirements and built in phases. Capabilities that hold or move money are completed when a licensed partner is connected.

  • Payments core and orders
  • Payment methods
  • Refunds and disputes
  • Settlements and balances
  • Checkout and client kits
  • Links, pages, buttons and QR
  • Recurring: mandates, subscriptions and invoices
  • Bank-transfer collection, virtual accounts and registered-account payments
  • Split settlements and marketplaces
  • Orchestration
  • Vault, tokens and saved methods
  • Reconciliation, reports and analytics
  • Risk, fraud and validation
  • Payouts
  • Developer platform
  • Console platform
Developers

Built to integrate once

One contract describes the whole API, so documentation, SDKs and test tools stay in step with it.

Developer support

  • Versioned REST API described by one OpenAPI document, with breaking changes only in a new version.
  • Signed webhooks with versioned events, and guides to verify and recover deliveries.
  • SDKs and client kits: server SDKs, a browser SDK and checkout client kits, designed to be generated from the same contract.
  • Sandbox and test mode, kept separate from live data, with published test values.
  • Docs and guides: quickstarts, how-to guides, an error index, an event index and a request collection.
  • Correlation IDs: send an X-Correlation-Id and it comes back on the response and its events. See it in the Trust trace.

Delivered in phases

  1. Phase 1The foundation across 15 areas: payments core, methods, refunds, checkout, links, orchestration, reconciliation, validation, the developer platform and the console.
  2. Phases 2 to 6Each later phase extends the areas. Capabilities that hold or move money are completed when a licensed partner is connected.

Xirag Payments is in development and runs in a sandbox; nothing is in production yet. Xirag holds no payment licence: licensed partners hold and move the money, while Xirag instructs, records, reconciles and audits.

Status

In development, sandbox only. Agents are not offered at launch; they are provided on request later. Where an agent is configured, a person still approves every money-out action.

Works with

Early access

Building a PA or PG business?

Register for early access, or write to us about the payment flows you run today.