Skip to main content

Release 24.11.2025

Changelog​

Upcoming Feature

These enhancements are expected to be available in upcoming releases.

The changes described in this release are currently under development. The final implementation details may change.

Antifraud​

Manual Review Action for Antifraud Rules​

Antifraud rules now support a new review action that allows merchants to pause transactions for manual review before they are processed by the payment provider.

New Review Action:

  • When configuring antifraud rules, you can now select the review action alongside existing actions (decline, alert, 3DS)
  • The review action pauses the transaction and sets both order and payment status to review
  • A configurable timeout period determines how long you have to make a decision
  • The system sends a callback notification with the new reviewTimeout field indicating the decision deadline

New API Endpoint:

  • Submit Antifraud Review Decision - POST /api/v1/order/review/result
  • Use this endpoint to submit your decision (accept or decline) for transactions in review status
  • Works for both orders (payments) and payouts

Updated Schemas:

For complete implementation details, see Antifraud Manual Review.

Orders and Payouts​

New payer Object in Payment Attempts​

In the Retrieve Order Details endpoint and the Order Status Callback, each payment attempt in the payments array now includes an optional payer object with the following structure:

  • personalData: Personal information including id, firstName, lastName, middleName, phone, email, birthDate, and ipAddress
  • addressData: Complete address information including type, zipCode, country, state, city, and address
  • documentData: Identity document details including type, series, number, issueCountry, and validBefore

All fields within these objects are optional.

New recipient Object in Payout Transactions​

In the Retrieve Payout Status endpoint and the Payout Status Callback, each payout transaction in the payoutTransactions array now includes an optional recipient object with the same structure as the payer object described above.

Use Cases​

This enriched data enables merchants to:

  • Antifraud Review: Make informed decisions on transactions flagged by antifraud systems with complete payer/recipient context