Skip to main content

Release 13.10.2026

Changelog​

Requisite Templates in Payment Method Types​

The payment method types now carry a required requisiteTemplates object with three arrays:

  • agent — the agent's account details the customer transfers money to in payin operations;
  • payer — the fields the payer fills in for payin operations;
  • recipient — the recipient's details to be collected for payout operations.

Each template item contains name, isMain and an optional description; the payer and recipient items also contain type (string or file). The templates are the default set of fields of the method; an agent may adjust it, so take the final list of fields, with the agent's values, from the Initialize a new session response.

Affected endpoints:

Main Requisite and Field Descriptions​

  • The payerRequisites and paymentMethodRequisites arrays in the session responses now include a required isMain flag and an optional description with a hint to be displayed to the customer. The item marked isMain: true is always first in the array.
  • The payerDetails items in the operation responses also include the isMain flag.

Affected endpoints:

title Is Deprecated​

The title field of the session payerRequisites and the operation payerDetails is deprecated: it now returns the same value as name. Use name instead; a display hint, if any, is returned in description.

Affected endpoints:

Empty paymentMethodRequisites in Payout Sessions​

For payout operations, the paymentMethodRequisites array in the session responses is now empty. The operation responses still contain the filled array.

Affected endpoints:

number Requisite Type Removed​

The number requisite type is no longer used: every requisite field is either string or file.

Affected endpoints: