21 August 2024 - Release Notes
- Introducing new
MANUAL_ADJUSTMENT
payment type - New GET V2 dispute status
/customer/v2/dispute/{disputeId}
endpoint - Add grouping for the complaint and dispute workflows in the compliance management system
- 🛠️ Fix
dateUpdated
in webhook payloads to be consistent format for all notification types
Avenu API Release Notes 1.11.3
Overview
Introducing new MANUAL_ADJUSTMENT
payment type
MANUAL_ADJUSTMENT
payment typeWhen there is a situation that requires a customer account to be manually adjusted, Avenu Admin are now able to make this change via a manual adjustment transaction.
New GET dispute status /customer/v2/dispute/{disputeId}
endpoint
/customer/v2/dispute/{disputeId}
endpointThe V2 dispute endpoint gets an upgrade with the addition of a GET dispute status endpoint. In addition to receiving dispute webhook notifications, you can now call the dispute status endpoint whenever you need to check the current status of a dispute for a customer.
Add grouping for the complaint and dispute workflows in the compliance management system
This is a backend change in Avenu for processing complaints and disputes to more effectively manage those respective alerts and cases in the compliance management system.
🛠️ Fix dateUpdated
in webhook payloads to be consistent format for all notification types
dateUpdated
in webhook payloads to be consistent format for all notification typesWe have updated the format for the dateUpdated
field on the concern and dispute webhook notification payloads to be consistent with other notifications sending this value in date format "2024-08-21"
.
What's New?
Introducing new MANUAL_ADJUSTMENT
payment type
MANUAL_ADJUSTMENT
payment typeThe manual adjustment transactions will be available like any other transactions in the payments list /customer/v1/payments
endpoint, payment details /customer/v1/payment/{paymentId}
endpoint, and statements /customer/v1/statements
endpoint. Manual adjustment transactions will begin with the m.
prefix.
New GET dispute status /customer/v2/dispute/{disputeId}
endpoint
/customer/v2/dispute/{disputeId}
endpointThe dispute status endpoint functions similarly to the other GET status endpoints, like payment status and customer status. Passing the disputeId
as a parameter in the path will return a response body with the current status and other details regarding the dispute. See response body example below.
{
"disputeId": "7ea66f7b-d8bb-471e-ab9e-7c8489998b14",
"disputeStatus": "CREATED",
"dateUpdated": "2024-08-21T12:34:03.015560Z",
"customerAccountNumber": "5647420826641201",
"transactionId": "s.6f4c0c4a-b521-4321-9eb5-bae06752216e",
"amount": 123,
"currencyType": "USD",
"disputeReason": "Johnny Kreiger stole my wallet and phone while I was sleeping",
"disputeType": "UNAUTHORIZED",
"disputeResolution": "Dispute has been created in the Compliance Monitoring System - pending review",
"memo": "Johnny Kreiger stole my wallet and phone while I was sleeping"
}
Add grouping for the complaint and dispute workflows in the compliance management system
With this update when a customer submits a complaint or a dispute, and subsequently submits another complaint or dispute, the two alerts will both be associated with the same case for the customer in the compliance management system. The alerts will be able to be worked independently of each other on the same case, as well as any action decisions that need to be taken.
What's being fixed?
🛠️ Fix dateUpdated
in webhook payloads to be consistent format for all notification types
dateUpdated
in webhook payloads to be consistent format for all notification typesWe have updated the format for the dateUpdated
field on the concern and dispute webhook notification payloads to be consistent with other notifications sending this value in date format "2024-08-21"
. Example dispute webhook notification payload below.
{
"type": "dispute",
"data": {
"customer": {
"accountNumber": "6313280146131087"
},
"transaction": {
"id": "6f42051e-3e0b-4a30-b7b7-928ff0da3096",
"type": "UNAUTHORIZED",
"status": "COMPLETED",
"transactionResponse": {
"type": "DISPUTE_FINALIZED___ERROR_OCCURRED",
"description": "Narrative as provided by compliance under text_entries.narrative field",
"dateUpdated": "2024-08-21"
}
}
},
"created_at": "2024-05-07T23:03:25.271972Z"
}