# Custom Fields

Custom fields allow you to capture and track business-specific reference data - such as a policy number, application ID, or customer reference - alongside every payment, subscription, or order on Glomo. Once configured, these fields appear during creation flows on the dashboard and in your reports, making it easy to reconcile transactions against your internal records.

## How it works

Custom fields are configured by your account manager on the Glomo admin side. Once enabled for your account, they appear as additional input fields during:

- Payment Link creation
- Subscription creation
- Order creation via API


Values you enter are stored against the transaction and appear as columns in your Payment Report and Subscription Report downloads.

## Creating a payment link, subscription, or order with custom fields

When custom fields are enabled on your account, you will see them as labeled input fields in the creation form. Fill in the relevant value - for example, entering the policy number against a subscription for a life insurance customer - and proceed as normal. The value is saved automatically with the transaction.

## Passing custom fields via API

If you are creating payment links, subscriptions, or orders via the API, custom field values can be passed in the `notes` object. The key should match the field name configured on your account.


```json
{
  "notes": {
  "policy_number": "POL-00123456",
  "application_id": "APP-987654"
  }
}
```

Values passed via `notes` map automatically to the corresponding custom fields and appear in your reports the same way as values entered through the dashboard.

## Viewing custom fields in reports

Custom field values appear as additional columns in the following reports:

- **Payment Report** - one column per configured custom field, populated for each transaction where a value was provided.
- **Subscription Report** - same as above, scoped to subscription transactions.


Rows where no value was provided for a custom field will show an empty cell for that column.

## Things to keep in mind

- Custom fields are configured at the account level by Glomo - they cannot be added or modified self-serve from the merchant dashboard.
- Values passed via API in `notes` must match the exact field name configured on your account - unrecognised keys will not appear in reports.
- Custom fields apply to new transactions from the point of configuration - they are not backfilled on historical transactions.