20 March 2024 - Release Notes

• Providing actionable feedback for dormant accounts due to inactivity.
• (Coming Soon‼️) Part 1 of implementing iFrame for KYC ID Scans and Liveliness

Avenu API Release Notes 1.9.5

Overview

Providing actionable feedback for dormant accounts due to inactivity.

This enhancement entails providing a meaningful and actionable message to the customer after a customer account is rendered dormant after the configured period of inactivity with our fraud detection vendor.

(Coming Soon!) Part 1 of implementing iFrame for KYC ID Scans and Liveliness

We are releasing the first part of the new iFrame implementation that will allow clients to serve the integrated KYC vendor through iFrame in their application. This first step is to include the iFrame URL in the customer status response. PLEASE NOTE: Until the implementation is fully complete this URL will be inactive and CAN NOT be used to facilitate ID Scans. Stay tuned for more details!

What's New?

The following release notes detail the updates we have included in this release.

Providing actionable feedback for dormant accounts due to inactivity.

Specifically, when a customer initiates a direct debit transaction after the period of inactivity (currently configured as 3 months), the fraud service will decline the transaction and render the customer account as “dormant”. However, while doing so, the fraud service also kicks off the process of reinstating the customer account and allowing them to retry the transaction after the cooling off period of 24 hours. Previous to this change, all this information was not provided to the Fintech client or customer. The change introduces a message that is sent as part of the response for the “Get Payment Status” call customer/v1/payment/status, as well as a message in the payment webhook notification, when initiated for such a payment transaction alerting the customer as to what has transpired with the transaction and what steps to take next.

Example payment status response

{
    "paymentId": "",
    "status": "CANCELLED",
    "transactionResponse": {
        "transactionResponseType": "TRANSACTION",
        "description": "The transaction failed because the customer account is marked as dormant due to an extended period of inactivity.  The process to reactivate the customer account has begun and a new transaction may be submitted after 24 hours has elapsed from the time of the original transaction.",
        "dateUpdated": ""
    }
}

Example webhook notification payload

{
  "type": "payment",
  "created_at": "2021-12-07T00:21:40.670058Z",
  "data": {
    "customer": {
        "accountNumber" : "12345"
    },
    "transaction": {        
        "id": "12345abc",
        "type": "ACH",
        "status": "CANCELLED",
        "transactionResponse": {
            "type": "TRANSACTION",
            "description": "The transaction failed because the customer account is marked as dormant due to an extended period of inactivity. The process to reactivate the customer account has begun and a new transaction may be submitted after 24 hours has elapsed from the time of the original transaction.",
            "dateUpdated": "2021-12-07T00:21:40.670058Z"
        }        
    }
  }
}

(Coming Soon!) Part 1 of implementing iFrame for KYC ID Scans and Liveliness

The additional parameter idScanURLis returned as part of the customer status endpoint. Currently, the URL value will be inactive and CAN NOT be used for facilitating ID scans. We wanted to provide this new information so development can be planned around the upcoming changes. In coming releases we will announce when the service is fully live.

Example customer status response

{
    "newCustomerTag": "",
    "customerAccountNumber": "",
    "status": "",
    "statusInfo": "",
    "idScanURL": ""   // this will now be included in the response object
}