Open (open.money)
Open is one of India's leading SMB neobanks, pioneering "connected banking" - a unified business finance platform that layers payments, automated reconciliation, accounting, payroll, expense management, vendor payouts, and GST-compliant invoicing on top of partner-bank current accounts (ICICI, SBI, Axis Bank, Yes Bank and 20+ others). Beyond its SMB application, Open also ships an embedded-finance / Banking-as-a-Service stack branded as Zwitch (zwitch.io), which exposes the same connected-banking primitives - virtual accounts, payouts via NEFT/IMPS/RTGS, UPI collect and intent flows, the Layer hosted payment gateway, beneficiary management, PAN/bank/VPA verification, webhooks, and split settlements - as REST APIs for fintechs and platforms that want to embed account-to-account payments and Indian payment rails into their own products. Open's broader portfolio also includes BankingStack (white-label connected banking for partner banks), the Open Capital lending product, and a suite of e-commerce plugins (WooCommerce, Magento, OpenCart, PrestaShop, CS-Cart, WHMCS) plus PHP, Java, Node.js, iOS, and Android SDKs for the Layer payment gateway.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Open (open.money) the way a machine reads it — 11 machine-readable artifacts across 10 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 — Open (open.money) scores 27.0/100 (emerging), with a separate agent-readiness read of 10/100 (human only). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Open (open.money)
Each block below is one kind of artifact we hold for Open (open.money). 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 10
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.
Open Zwitch Virtual Accounts API
Programmatic creation and management of virtual accounts used as transfer wallets, collection wallets, and collection tools on top of partner-bank infrastructure. Virtual accoun...
Open Zwitch Transfers API
Initiate single or bulk fund transfers from a virtual account to bank beneficiaries over NEFT, IMPS, or RTGS, and inspect transfer status, UTR, and settlement details. Powers ve...
Open Zwitch Beneficiaries API
Manage the set of bank-account beneficiaries that can be paid from a virtual account. Supports creating beneficiaries, listing, retrieving, updating, and deleting, with optional...
Open Zwitch UPI API
UPI collect requests, UPI Intent strings, and dynamic UPI QR codes for accepting customer-initiated payments on India's Unified Payments Interface rails. Includes mandate flows ...
Open Layer Payment Gateway API
Layer is Zwitch's hosted payment gateway. A few lines of layer.js render a fully PCI-compliant checkout pop-up that accepts net banking, UPI, credit/debit cards, and wallets. Se...
Open Zwitch Verification API
Identity and account-validation suite used during merchant onboarding, KYB, and pre-payout checks. Endpoints cover PAN verification, name matching, bank-account validation (stan...
Open Zwitch Split Settlements API
Configure split-settlement rules so that incoming payments are automatically apportioned across multiple beneficiary accounts at settlement time. Used by marketplaces, aggregato...
Open Zwitch Webhooks
Real-time event delivery for payment, transfer, refund, settlement, virtual-account, and verification lifecycle events, with HMAC signature verification and configurable retry p...
Open Zwitch Payment Pages API
No-code hosted payment pages and payment links that small businesses can share over email, SMS, or WhatsApp to collect one-time or recurring payments without writing integration...
Open Connected Banking Platform
Open's flagship SMB neobanking application. Connects one or more partner-bank current accounts (ICICI, SBI, Axis Bank, Yes Bank, and others) and layers on bill and invoice manag...
Scroll within the panel for all 10 ·
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.
Resources
Every other property we hold for Open (open.money) — 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.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Commercial 4
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/open-financial · machine-readable index on apis.io