BillDesk
BillDesk is an Indian integrated payment solutions platform founded in 2000, offering REST APIs for bill payments, recurring mandates, UPI payments, net banking, card payments, and enterprise payment gateway integrations. The platform provides three integration tiers (Neo full-redirect, Ace SDK, and CX+ deep API), supporting online payments, e-Mandate setup, invoicing, refunds, tokenization, and 150+ payment methods across web, mobile, and third-party e-commerce plugins.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles BillDesk the way a machine reads it — 51 machine-readable artifacts across 14 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — BillDesk scores 34.0/100 (thin), with a separate agent-readiness read of 39/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from BillDesk's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/billdesk/"
title="BillDesk on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/billdesk.svg"
alt="BillDesk Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/billdesk/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/billdesk/"
title="BillDesk on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/billdesk/card.svg"
alt="BillDesk Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile BillDesk
Each block below is one kind of artifact we hold for BillDesk. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 15
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
BillDesk Neo Full Redirect API
Pre-built hosted checkout solution for one-time and recurring online payments. Merchants redirect customers to BillDesk-hosted pages, minimizing PCI DSS scope.
BillDesk Ace SDK API
SDK-based payment integration for Android, iOS, Flutter, and web. Provides embedded payment experiences with BillDesk handling payment orchestration.
BillDesk CX+ Deep API
Direct REST API access for advanced payment processing, giving merchants full control over checkout UX. Supports transactions, mandates, refunds, card tokenization, invoices, pa...
BillDesk Authentication API
The Authentication API from BillDesk — 3 operation(s) for authentication.
BillDesk Card Account API
The Card Account API from BillDesk — 4 operation(s) for card account.
BillDesk Guest Checkout (AltID) API
The Guest Checkout (AltID) API from BillDesk — 1 operation(s) for guest checkout (altid).
BillDesk Invoice API
The Invoice API from BillDesk — 2 operation(s) for invoice.
BillDesk Mandate API
The Mandate API from BillDesk — 6 operation(s) for mandate.
BillDesk Order API
The Order API from BillDesk — 3 operation(s) for order.
BillDesk Payment Links API
The Payment Links API from BillDesk — 4 operation(s) for payment links.
BillDesk Penny Drop API
The Penny Drop API from BillDesk — 1 operation(s) for penny drop.
BillDesk Refund API
The Refund API from BillDesk — 2 operation(s) for refund.
BillDesk Settlement API
The Settlement API from BillDesk — 1 operation(s) for settlement.
BillDesk Transaction API
The Transaction API from BillDesk — 3 operation(s) for transaction.
BillDesk Validate VPA API
The Validate VPA API from BillDesk — 1 operation(s) for validate vpa.
Scroll within the panel for all 15 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Billdesk Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Billdesk Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Billdesk Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
BillDesk API Rules
SPECTRALJSON Schema 29
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Additional-Info
JSON SCHEMAAltid_card_request
JSON SCHEMABankaccount
JSON SCHEMAbankid
JSON SCHEMACardacc-network-issuer-token
JSON SCHEMAcardaccid auth data
JSON SCHEMACardaccount-in-txn-response
JSON SCHEMAcurrency
JSON SCHEMAcustomer-response
JSON SCHEMAcustomer
JSON SCHEMADevice object
JSON SCHEMADevice
JSON SCHEMAerror_desc
JSON SCHEMAMandate
JSON SCHEMAmercid
JSON SCHEMANetwork-issuer-token
JSON SCHEMAobjectid
JSON SCHEMAorderid
JSON SCHEMAPay using alt id token
JSON SCHEMAPay using card number - pan
JSON SCHEMAPay using issuer token
JSON SCHEMAPay using network token
JSON SCHEMApayment_method_type
JSON SCHEMApayment-object-response
JSON SCHEMApayment-object
JSON SCHEMAResponse-parameters
JSON SCHEMAUDF
JSON SCHEMAupi-response
JSON SCHEMAUpi
JSON SCHEMAScroll within the panel for all 29 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for BillDesk — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/billdesk · machine-readable index on apis.io
This is an independent, third-party profile of BillDesk, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.