16 October 2024 - Release Notes

• Updated error codes for transfer endpoint
• Onboarding endpoint allowing some special characters in firstName and lastName fields
• Customer status webhook notification updates for when accounts are suspended, unsuspended, and closed
• 🛠️ Fix customer status webhook notifications from sending generic CONTACT_SUPPORT message
• 🛠️ Allow disputes and adjustments to be made on ACH_TRANSFER payment types

Avenu API Release Notes 1.12.1

What's New?

Updated error codes for transfer endpoint

The following new error code and message was added for the scenario where an ACH transfer limit is exceeded:

Onboarding endpoint allowing some special characters in firstName and lastName fields

The onboarding endpoint has been updated to allow some special characters in the firstName and lastName fields. The modified requirements are listed below:

• no empty/null values
• no numerical values
• dashes - allowed
• apostrophes ' allowed
• spaces between names [Mary Kate] allowed

Customer status webhook notification updates for when accounts are suspended, unsuspended, and closed

When a customer's account status is updated to suspended or closed, the Avenu customer status will update to DISABLED. We've added some additional context in the transaction response to the webhook notifications for these customer status events to differentiate them from the DISABLED status notification that could be sent during the initial onboarding process. Please see example payloads below:

Webhook notification customer status payload data - Customer account SUSPENDED

{
  "type": "customer_status",
  "created_at": "2021-12-07T00:21:40.670058Z",
  "data": {
    "newCustomerTag": "abcdefxxxxxx",
    "accountNumber": "12345",
    "transaction": {
      "id": "12345abc",
      "status": "DISABLED",
      "transactionResponse" : {
        "type": "CUSTOMER_ACCOUNT_SUSPENDED",
        "description": "Customer Account Suspended",
        "dateUpdated": "2021-12-07"
      }
    }
  }
} 

Webhook notification customer status payload data - Customer account UNSUSPENDED (re-enabled)

{
  "type": "customer_status",
  "created_at": "2021-12-07T00:21:40.670058Z",
  "data": {
    "newCustomerTag": "abcdefxxxxxx",
    "accountNumber": "12345",
    "transaction": {
      "id": "12345abc",
      "status": "ENABLED",
      "transactionResponse" : {
        "type": "CUSTOMER_ACCOUNT_UNSUSPENDED",
        "description": "Customer Account Un-Suspended",
        "dateUpdated": "2021-12-07"
      }
    }
  }
} 

Webhook notification customer status payload data - Customer account CLOSED

{
  "type": "customer_status",
  "created_at": "2021-12-07T00:21:40.670058Z",
  "data": {
    "newCustomerTag": "abcdefxxxxxx",
    "accountNumber": "12345",
    "transaction": {
        "id": "12345abc",
        "status": "DISABLED",
        "transactionResponse" : {
          "type": "CUSTOMER_ACCOUNT_CLOSED",
          "description": "Customer Account Closed",
          "dateUpdated": "2021-12-07"
        }       
      }    
  }
} 

🛠️ What's being fixed?

Fix customer status webhook notifications from sending generic CONTACT_SUPPORT message

An issue was discovered where the customer status webhooks were not picking up the specific transactionResponse and instead sending a generic CONTACT_SUPPORT. This issue has been resolved and the transactionResponse is being sent as expected for customer status webhook notifications.

Allow disputes and adjustments to be made on ACH_TRANSFER payment types

We found there was an issue with the dispute and adjustment automation when specific payment types were disputed. Our team has made changes to now allow disputes and adjustments to be processed for ACH_TRANSFER payment types. The following payment types are able to be disputed now within Avenu:

• ACH
• AVENU (Intra client payments from one customer to another customer)
• ACH_TRANSFER (transfers to the REMITTANCE and/or OPERATING account(s) via the transfer endpoint)