July 17, 2026

Payments now expose custom field values as a read-only field, and Custom
Field definitions can be scoped to either Applications or Payments.

Added

Payments

• Added a custom_fields field to Payments, returning the company's
  Payments-scoped custom field values for each charge. This field is
  read-only — custom field values on Payments cannot be created or edited
  through the API. custom_fields can be filtered like any other field.

Custom Fields

• Added an entity_type field to Custom Field definitions, indicating
  whether a custom field applies to Applications or Payments. Accepts
  applications or payments; defaults to applications when omitted.

Changed

Applications

• The custom_fields field on Applications now returns only
  Applications-scoped custom field values. Previously the response also
  included keys for Payments-scoped custom fields — these only ever held the
  field's default value (a Payments field can't carry a real value on an
  application), so no application data is lost. Clients reading
  custom_fields on Applications will see those default-only keys disappear.