Skip to main content

2025

This changelog contains the changes that took place in 2025 in chronological order.

4 Jun 2025 v1.40
Deployment DateEnvironment
16 Jun 2025UAT
25 Jun 2025Production

Modified endpoints:

  • GET /customers/{customer_id}/authentication-securities - Retrieve the authentication security details of a customer by customer id
    • The response body will change by returning an empty list along with status code 200 if authentication security details do not exist for the customer. This will replace error code 4040001 which is currently being returned.
1 Apr 2025 v1.39
Deployment DateEnvironment
1 Apr 2025UAT
1 Apr 2025Production

Modified endpoints:

  • GET /accounts/{account_id}/transactions - Retrieve all transactions by account id
  • GET /cards/{card_id}/transactions - Retrieve all transactions by card id
  • GET /accounts/{account_id}/transactions/{transaction_id} - Retrieve transaction details by account id and transaction id
    • New enum values added SepaIncomingPaymentReturn, SepaIncomingPaymentCancellation, SepaOutgoingPaymentReturn and SepaOutgoingPaymentCancellation in property processing_code_type which will be returned according to the transaction codes used in the credit and debit endpoints
  • GET /corporate/accounts/{corporate_account_id}/transactions - Retrieve all transactions by corporate account id
  • GET /corporate/accounts/{account_id}/transactions/{transaction_id} - Retrieve transaction details by corporate account id
    • New enum values added SepaIncomingPaymentReturn, SepaIncomingPaymentReturnAdjustment, SepaIncomingPaymentCancellation, SepaIncomingPaymentCancellationAdjustment, SepaOutgoingPaymentReturn, SepaOutgoingPaymentReturnAdjustment, SepaOutgoingPaymentCancellation and SepaOutgoingPaymentCancellationAdjustment in property processing_code_type which will be returned according to the transaction codes used in the credit and debit endpoints
24 Feb 2025 v1.38
Deployment DateEnvironment
24 Feb 2025UAT
24 Feb 2025Production

Modified endpoints:

  • PATCH /customers/{customer_id} - Update details
    • Adding a new optional property update_reason in model UpdateCustomerRequest
  • PUT /customers/{customer_id}/address - Add or Update phone details
    • Adding a new optional property update_reason in model UpdateAddressRequest
  • PUT /customers/{customer_id}/phones - Add or Update address details
    • Adding a new optional property update_reason in model UpdatePhoneRequest
11 Feb 2025 v1.37
Deployment DateEnvironment
11 Feb 2025UAT
11 Feb 2025Production

All endpoints:

  • To ensure that none of the properties start or end with a whitespace, the pattern: (?!\s)(?!.\s$) was added to each property with an existing regex.
  • To ensure that required properties do not allow strings consisting only of whitespace, the pattern: (?!\s$) was added to the existing regex.

Modified endpoints:

  • POST /customers - Create new customer
  • POST /customers/{customer_id}/cards - Create a new card for a customer by customer_id
  • PATCH /customers/{customer_id}/addresses - Update a customer address by customer_id
  • GET /cards/{card_id} - Retrieve card details by card_id
  • GET /customers/{customer_id} - Retrieve customer details by customer_id
  • GET /corporates/{corporate_id} - Retrieve corporate details by corporate_id
  • POST /corporate - Creates a new corporate
  • PATCH /corporates/{corporate_id} - Update a corporate by corporate_id
  • POST /corporates/accounts/{corporate_account_id}/outgoing-credit-transfer - Initiate SCT payment
  • POST /accounts/{account_id}/outgoing-credit-transfer - Initiate SCT payment
    • Property ‘line_1’ to change from 100 to maximum 70 characters
    • Property ‘line_2’ to change from 100 to maximum 70 characters
    • Property ‘line_3’ to change from 100 to maximum 70 characters
    • Property ‘city’ to change from 50 to maximum 35 characters
    • Property ‘postal_code’ to change from 10 to maximum 9 characters