TRANXACT.AI Help

India statutory · Records

Upi handles

Read and maintain upi handles records (india.upi_handles).

Type REST6 operationsBase path /api/india/upi-handlesPublished as /api/v1/upi-handles

Download specification (OpenAPI 3.1)

Overview

PackageIndia statutory
AuthenticationBearer token: a service account's token (POST /api/auth/service-token) or, for the published path, an API key
AuthorizationThe caller's roles must hold India statutory › Upi handles on the Roles screen: display for GET, add for POST, change for PUT, delete for DELETE; an action needs the grant of the button that runs it on the screen.
Tableindia.upi_handles · kept per company (and organisational unit where it has one)
RecordCreated, changed and (where the screen allows) deleted; key id
RulesThe same as the screen: validation, numbering, approvals, posting, the company the caller belongs to, and the audit trail.

API reference

6 operations. Open one for its parameters, bodies, responses and a sample request.

GET/api/india/upi-handlesList upi handles

Query parameters

NameDescriptionExample
limitRows per page (50 by default, at most 200)limit=100
offsetRows to skipoffset=200
qFree-text search over the search columnsq=acme
sortcolumn:asc or column:desc, several separated by commassort=created_at:desc
filterA JSON condition or group (see the filter language), URL-encoded; any field below can be filtered and sortedfilter={"col":"status","op":"eq","value":"open"}
<field>=<value>Shorthand for "field is value" 

Response 200

{
  "rows": [
    {
      "id": "3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73",
      "org_unit_id": "3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73",
      "vpa": "text",
      "payee_name": "Example",
      "psp_code": "PSP-000001",
      "merchant_category_code": "MER-000001",
      "bank_account_id": "3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73",
      "settlement_ifsc": "text",
      "settlement_account": "text",
      "is_verified": true,
      "verified_at": "2026-10-30T09:00:00Z",
      "is_default": true,
      "is_active": true,
      "created_at": "2026-10-30T09:00:00Z"
    }
  ],
  "count": 1
}

Sample request

curl "https://demo.tranxact.ai/api/india/upi-handles?limit=20" \
  -H "Authorization: Bearer $TOKEN"
GET/api/india/upi-handles/{id}Read one upi handles

Path parameters

NameTypeDescription
idstring (uuid)The record's id, as a list returns it.

Response 200

{
  "id": "3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73",
  "org_unit_id": "3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73",
  "vpa": "text",
  "payee_name": "Example",
  "psp_code": "PSP-000001",
  "merchant_category_code": "MER-000001",
  "bank_account_id": "3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73",
  "settlement_ifsc": "text",
  "settlement_account": "text",
  "is_verified": true,
  "verified_at": "2026-10-30T09:00:00Z",
  "is_default": true,
  "is_active": true,
  "created_at": "2026-10-30T09:00:00Z"
}

404 when no record with that id is visible to the caller.

Sample request

curl "https://demo.tranxact.ai/api/india/upi-handles/3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73" \
  -H "Authorization: Bearer $TOKEN"
POST/api/india/upi-handlesCreate a upi handles

Request body

The record as JSON. Fields marked Yes are required.

FieldTypeRequiredDescription
vpatextYesVpa
payee_nametextYesPayee name
psp_codetextNoPsp code
merchant_category_codetextNoMerchant category code
settlement_ifsctextNoSettlement ifsc
settlement_accounttextNoSettlement account
is_verifiedbooleanNoIs verified
is_defaultbooleanNoIs default
is_activebooleanNoIs active

Sample body

{
  "vpa": "text",
  "payee_name": "Example",
  "psp_code": "PSP-000001",
  "merchant_category_code": "MER-000001",
  "settlement_ifsc": "text",
  "settlement_account": "text"
}

Response 201

{
  "id": "3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73",
  "org_unit_id": "3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73",
  "vpa": "text",
  "payee_name": "Example",
  "psp_code": "PSP-000001",
  "merchant_category_code": "MER-000001",
  "bank_account_id": "3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73",
  "settlement_ifsc": "text",
  "settlement_account": "text",
  "is_verified": true,
  "verified_at": "2026-10-30T09:00:00Z",
  "is_default": true,
  "is_active": true,
  "created_at": "2026-10-30T09:00:00Z"
}

Sample request

curl -X POST "https://demo.tranxact.ai/api/india/upi-handles" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"vpa":"text","payee_name":"Example","psp_code":"PSP-000001","merchant_category_code":"MER-000001","settlement_ifsc":"text","settlement_account":"text"}'
PUT/api/india/upi-handles/{id}Change a upi handles

Path parameters

NameTypeDescription
idstring (uuid)The record's id, as a list returns it.

Request body

Only the fields to change; fields left out keep their value.

FieldTypeRequiredDescription
vpatextYesVpa
payee_nametextYesPayee name
psp_codetextNoPsp code
merchant_category_codetextNoMerchant category code
settlement_ifsctextNoSettlement ifsc
settlement_accounttextNoSettlement account
is_verifiedbooleanNoIs verified
is_defaultbooleanNoIs default
is_activebooleanNoIs active

Sample body

{
  "vpa": "text",
  "payee_name": "Example"
}

Response 200

{
  "id": "3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73",
  "org_unit_id": "3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73",
  "vpa": "text",
  "payee_name": "Example",
  "psp_code": "PSP-000001",
  "merchant_category_code": "MER-000001",
  "bank_account_id": "3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73",
  "settlement_ifsc": "text",
  "settlement_account": "text",
  "is_verified": true,
  "verified_at": "2026-10-30T09:00:00Z",
  "is_default": true,
  "is_active": true,
  "created_at": "2026-10-30T09:00:00Z"
}

Sample request

curl -X PUT "https://demo.tranxact.ai/api/india/upi-handles/3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"vpa":"text","payee_name":"Example"}'
DELETE/api/india/upi-handles/{id}Delete a upi handles

Path parameters

NameTypeDescription
idstring (uuid)The record's id, as a list returns it.

Response 200

{ "deleted": true }

Many documents are cancelled or reversed instead; the API refuses a delete the screen would refuse.

Sample request

curl -X DELETE "https://demo.tranxact.ai/api/india/upi-handles/3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73" \
  -H "Authorization: Bearer $TOKEN"
POST/api/india/upi-handles/{id}/copyCopy

Path parameters

NameTypeDescription
idstring (uuid)The record's id, as a list returns it.

Request body

The keys this action reads (* = required; "one of" lists the only values):

overrides, preview, withLines

Response

200 or 201 with the record or result as JSON; a refusal is 409 or 422 with a sentence saying why.

Sample request

curl -X POST "https://demo.tranxact.ai/api/india/upi-handles/3f1c2a9e-5b7d-4c1e-9a2f-0d4b8e6c1a73/copy" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"overrides":"value","preview":"value","withLines":"value"}'

Data model

Every field of a upi handles, as the API returns it. Field names are the JSON keys; any of them can be filtered and sorted on a list.

FieldTypeAccessDescription
iduuidread onlyId
org_iduuidread onlyOrg id
org_unit_iduuidread onlyOrg unit id
vpatextread, writeVpa
payee_nametextread, writePayee name
psp_codetextread, writePsp code
merchant_category_codetextread, writeMerchant category code
bank_account_iduuidread onlyBank account id
settlement_ifsctextread, writeSettlement ifsc
settlement_accounttextread, writeSettlement account
is_verifiedbooleanread, writeIs verified
verified_attimestamp with time zoneread onlyVerified at
is_defaultbooleanread, writeIs default
is_activebooleanread, writeIs active
created_attimestamp with time zoneread onlyCreated at
created_byuuidread onlyCreated by
updated_attimestamp with time zoneread onlyUpdated at
updated_byuuidread onlyUpdated by
xf_text_1textread onlyXf text 1
xf_text_2textread onlyXf text 2
xf_text_3textread onlyXf text 3
xf_text_4textread onlyXf text 4
xf_text_5textread onlyXf text 5
xf_num_1numericread onlyXf num 1
xf_num_2numericread onlyXf num 2
xf_num_3numericread onlyXf num 3
xf_date_1dateread onlyXf date 1
xf_date_2dateread onlyXf date 2

Errors

StatusMeaning
400The request could not be read: a filter that is not JSON, a bad parameter
401No credential, or it is wrong, revoked or expired
403The caller's roles do not hold India statutory › Upi handles for this verb, or the address or origin is not allowed
404No record with that id is visible to the caller
409A conflict: a duplicate number, a document in a state that does not allow it, or a record changed or locked by someone else
422Refused by the same validation as the screen; the error names the field and why

Every error is JSON: {"error": "a sentence saying what was wrong"}, with field where it applies.