Curlec · Schema

VirtualAccount

A virtual bank account or VPA that accepts NEFT/RTGS/IMPS/UPI payments (Smart Collect). Each payment creates a BankTransfer entity. Auto-closes after 90 days of inactivity. Prefix: va_

CompanyPaymentsPayment GatewayRecurring PaymentsSubscriptionDirect DebitFintechMalaysiaDuitNowFPXWebhookRazorpayA2A

Properties

Name Type Description
id string Virtual account ID. Prefix: va_
name string Display name of the virtual account.
entity string
description string Purpose or description of the virtual account.
amount_expected integer Expected payment amount in paise. 0 means any amount is accepted.
amount_paid integer Total amount received so far in paise.
status string active = accepting payments; closed = no longer accepting payments.
receivers array Payment receivers assigned to this virtual account. Can include bank_account (ba_*) and/or vpa (vpa_*) receivers.
close_by integer Unix timestamp by which the account will auto-close. Maximum value: 2147483647.
closed_at integer Unix timestamp when the account was closed.
customer_id string Customer ID linked to this virtual account (cust_*).
notes object
created_at integer
View JSON Schema on GitHub

JSON Schema

curlec-virtual-account-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/curlec/json-schema/curlec-virtual-account-schema.json",
  "title": "VirtualAccount",
  "description": "A virtual bank account or VPA that accepts NEFT/RTGS/IMPS/UPI payments (Smart Collect). Each payment creates a BankTransfer entity. Auto-closes after 90 days of inactivity. Prefix: va_",
  "x-generated": "2026-11-04",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/curlec-virtual-accounts-api-openapi.yml#/components/schemas/VirtualAccount",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Virtual account ID. Prefix: va_"
    },
    "name": {
      "type": "string",
      "description": "Display name of the virtual account."
    },
    "entity": {
      "type": "string",
      "enum": [
        "virtual_account"
      ]
    },
    "description": {
      "type": "string",
      "description": "Purpose or description of the virtual account."
    },
    "amount_expected": {
      "type": "integer",
      "description": "Expected payment amount in paise. 0 means any amount is accepted."
    },
    "amount_paid": {
      "type": "integer",
      "description": "Total amount received so far in paise."
    },
    "status": {
      "type": "string",
      "enum": [
        "active",
        "closed"
      ],
      "description": "active = accepting payments; closed = no longer accepting payments."
    },
    "receivers": {
      "type": "array",
      "description": "Payment receivers assigned to this virtual account. Can include bank_account (ba_*) and/or vpa (vpa_*) receivers.",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string",
            "description": "Receiver ID. Prefix: ba_ for bank account, vpa_ for VPA."
          },
          "entity": {
            "type": "string",
            "enum": [
              "bank_account",
              "vpa"
            ]
          },
          "ifsc": {
            "type": "string",
            "description": "IFSC code (bank accounts only)."
          },
          "bank_name": {
            "type": "string",
            "description": "Bank name (bank accounts only)."
          },
          "name": {
            "type": "string",
            "description": "Account holder name (bank accounts) or VPA address (VPAs)."
          },
          "notes": {
            "$ref": "#/$defs/Notes"
          },
          "account_number": {
            "type": "string",
            "description": "Virtual account number (bank accounts only)."
          },
          "username": {
            "type": "string",
            "description": "UPI username part of the VPA (VPAs only)."
          },
          "handle": {
            "type": "string",
            "description": "UPI handle (e.g., razorpay) (VPAs only)."
          },
          "flow": {
            "type": "string",
            "enum": [
              "upi_qr"
            ],
            "description": "Flow type for VPA receivers."
          }
        }
      }
    },
    "close_by": {
      "type": "integer",
      "description": "Unix timestamp by which the account will auto-close. Maximum value: 2147483647."
    },
    "closed_at": {
      "type": "integer",
      "description": "Unix timestamp when the account was closed."
    },
    "customer_id": {
      "type": "string",
      "description": "Customer ID linked to this virtual account (cust_*)."
    },
    "notes": {
      "$ref": "#/$defs/Notes"
    },
    "created_at": {
      "type": "integer"
    }
  },
  "$defs": {
    "Notes": {
      "type": "object",
      "description": "Key-value pairs for storing custom metadata. Maximum 15 pairs. Each key and value must not exceed 256 characters.",
      "additionalProperties": {
        "type": "string"
      },
      "maxProperties": 15
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/curlec-virtual-account"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.