The name of the beneficiary.

The type of beneficiary.

The category of the beneficiary.

The email address of the beneficiary.

The phone number of the beneficiary.

A nickname for the beneficiary. If not provided, auto-generated as "{beneficiary_name} - {bank_name}".

The address of the beneficiary.

The bank account details of the beneficiary.

The current review status of the beneficiary.

• active — the beneficiary can receive payouts.
• rejected — the beneficiary did not pass review and cannot receive payouts. Terminal.

List of document IDs attached to the beneficiary.

The UPI account details of the beneficiary. Present when the beneficiary uses UPI, otherwise null.

Timestamp representing when the beneficiary was created in ISO 8601 format.

Timestamp representing when the beneficiary was last updated in ISO 8601 format.

Optional key-value pairs for attaching custom metadata (e.g. invoice references, project codes). Keys must be strings and cannot collide with reserved field names. Your account may require some notes fields: Glomo configures custom field rules per account, and for beneficiaries they are checked when the beneficiary is created. Some fields are also validated by the beneficiary's country (for example, a PAN format for Indian beneficiaries). A missing required field returns 422 with Validation failed: Notes <field> is required, and type and validation errors (such as enum constraints) are returned the same way. The rule is set on your account, not by currency or rail. No API lists the fields, but the 422 names each missing one: add that key to notes with the value your account expects, and ask your Glomo account manager if you don't know what the field should hold. See Custom fields. Each key appears as a separate column in CSV report exports, with corresponding values populating the rows.