5 posts tagged with "release"

Changelog​

Callbacks Can Be Re-Sent Manually​

A callback can now be re-sent manually from the back office. A callback for an operation you have already processed may arrive again.

Affected endpoints:

• Callback

Changelog​

A Payer Is Kept with Their Agent for 30 Minutes​

For 30 minutes after an agent is assigned to a payer, new operations with the same payerId and the same payment method type are assigned to the same agent. If that agent can no longer process the operation, it is distributed among the agents as usual.

Affected endpoints:

• Initialize a new session

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:

• Get available payment method types

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:

• Initialize a new session
• Retrieve session details
• Create a new P2P operation
• Retrieve P2P operation details
• Callback

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:

• Initialize a new session
• Retrieve session details
• Create a new P2P operation
• Retrieve P2P operation details

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:

• Initialize a new session
• Retrieve session details

number Requisite Type Removed​

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

Affected endpoints:

• Initialize a new session
• Retrieve session details
• Create a new P2P operation
• Retrieve P2P operation details

Changelog​

Operation Number​

• Initialize a new session: The operationNumber field is now optional.
• Create a new P2P operation: The operationNumber field is now available as an optional parameter.
• Retrieve P2P operation details: The operationNumber field is now optional in the response.

Changelog​

Enhanced Operation Status Information​

The Create a new P2P operation and Retrieve P2P operation details endpoints now include detailed operation status information through the new info object:

• comment: Optional comment provided by the back office operator when accepting or declining the operation, enabling better communication about transaction processing decisions.
• reason: Required field when declining an operation, with supported values including not_executed, wrong_credentinal, wrong_amount, and other.
• file: File identifier for transaction confirmation documents that back office operators can attach as proof when accepting operations.

This object is populated only when an operation is accepted or declined from the back office, providing merchants with transparent insight into the operation's processing status.