Release Notes for 1.1.3-GA

Enhanced data passed to payment gateway integrations for Authorize & AuthorizeAndCapture transactions. This is done by gathering additional data point for Payments (esp. name, email address, & shipping address) & passing these values along to the PaymentRequest that’s provided to the gateway libraries.

Enhanced the PaymentTransaction & PaymentSummary to communicate when a transaction was flagged for manual fraud review.

Enhanced the PaymentTransaction to communicate the results of a manual fraud review.

Added support for recording the implied ReverseAuthorize transaction that some gateways automatically execute when a partial Capture is executed.

Updated the TransactionWebhookEndpoint & TransactionWebhookService to make use of request parameters, along with the headers and request body.

Introduced the ability for PaymentGatewayWebhookHandler implementations to declare the categories of notifications that they support, so that the DefaultTransactionWebhookMessageService will skip attempting to handle any other types. This allows you to support different categories of notifications for each gateway, without unintentionally processing an unexpected notification.

Introduced the ability for our webhooks to record manual fraud results for existing Authorize or AuthorizeAndCapture transactions.

Introduced the ability for our webhooks to record subsequent Capture and/or Refund transactions triggered from the gateway’s dashboard as part of the manual fraud review.