Proof

2025-11-03 Proof Release Notes – Proof Help Center

The November 3, 2025 Proof release introduces a new Defend Risk Score that boosts fraud detection by over 33% using recipient behavior and history data, a Mark as Safe feature for Risk Routing customers to exempt trusted recipients from holds for a set period, and an API enhancement allowing expiration times to be updated without recalling transactions, benefiting especially real estate clients.

Summary: New Defend Risk Score significantly improves fraud detection, now mark recipients as safe for Risk Routing customers, and make API-based changes to expiration times without recalling the transaction.

Enhancements

DEPLOY-1216 shipping on November 03, 2025

Defend Risk Score

The new Defend Risk Score brings industry-leading confidence and trust in every transaction at levels never before seen. By incorporating risk signals about who a recipient is, how they are behaving on the platform, and their previous history across the Proof network, the new Risk Score increases fraud detection by over 33% from the last model while letting legitimate users continue to transact without friction (DFND-236).

  • Audience: Available for all customers of Defend
  • User roles: User with the Defend Role enabled
  • Availability: On by default for Defend customers
  • Release stage: General availability
  • Transaction types: Future transactions

Mark as Safe

The new Mark as Safe feature enables customers who are utilizing Risk Routing to mark a recipient as “safe” after an investigation of a risky transaction that was put on hold. With this feature, the recipient will not be put on-hold for the remaining transactions associated with that recipient for a preconfigured period of time (DFND-579).

  • Audience: All Defend customers that utilize the Risk Routing feature
  • User roles: Customers with the Defend role enabled
  • Availability: Configurable via organizational flags
  • Release stage: General availability
  • Transaction types: Future transactions

Change expiration date via API

Related to our change to respect the expiry time if set via the API, we now also support the ability to update the expiry time via the API without having to first recall the transaction. This change is especially useful for real estate customers, who were typically required to recall transactions in order to make changes (BIZ-8670).

  • Audience: All customers can update the expiry time via the API
  • User roles: All
  • Availability: Opt-in (contact your Customer Success Manager)
  • Release stage: General availability
  • Transaction types: Future transactions that are not yet expired