# Changelog

***

### 2026-04-01

**Updates to the Create Virtual Account flow**\
\
We’ve updated the [Create Virtual Account](https://developers.gurupay.eu/api-reference/virtual-ibans#post-api-v1-customers-customer_uuid-accounts-open-virtual) flow to support compliance  checks and document uploads.\
\
**What’s new:**

* **New optional request field:** `company.industry_type` has been added as a new enum field in the Create Virtual Account request.
* **Additional response fields:** The response now includes the metadata fields `uuid` and `status`.
* **New response status:** When a request is submitted, the response now returns `201` with status `WAITING_FOR_APPROVAL`.
* **Default approval behavior remains unchanged:** Virtual Account Creation requests are approved automatically by default. In some cases, additional compliance checks may be required, and the request may be placed in a review queue. The virtual account becomes available only after the process has been completed and confirmed by webhook.
* **Webhook status updates:** Once Virtual Account creation or review is completed, the webhook sends the status `CREATED` or `REJECTED`
* **New document upload endpoint:** A new endpoint has been added to support document uploads related to virtual accounts: `/api/v1/customers/{customer_uuid}/accounts/{account_uuid}/documents`

### 2025-11-19

#### Added

We've introduced new a field in [Virtual IBANs](/api-reference/virtual-ibans.md) resource.

* Introduced a new field: **`external_id`** (`string`) in the Virtual IBAN API response.
* This identifier can be used to **track and correlate virtual IBANs** with external systems.
* The value is a unique string (UUID format).
* **Example:** `bbf12075-90a8-462f-bc73-7c10cec42147`

### 2025-11-18

#### Added

We've introduced new API endpoints to streamline account statement management:

* **GET Single Statement**: Retrieve a specific account statement by its identifier.
* **GET List of Generated Statements**: Access a list of all available statements.
* **POST Generate New Statement**: Create a new account statement.

These endpoints improve the efficiency and flexibility of handling account statements.

### 2025-11-05

#### Added

* Optional `balance_type` parameter to [Transactions](/api-reference/transactions.md#get-api-v1-transactions-statements)  which determines how account balances are calculated (*settled* or *pending* transactions)

### 2025-10-15

#### Added

A new parameter has been introduced to show the result of payee verification. Before queuing the transaction for processing, we perform the verification of payee and provide the outcome.

* The [**Transaction**](/api-reference/transactions.md) **Create Response Resource** has been amended with a parameter **`verification_of_payee` .**
  * **Possible values:**
    * **`MATCH`** - the payee details fully match.
    * **`NO_MATCH`** - the payee details do not match.
    * **`CLOSE_MATCH`** - the payee details are similar but not identical.
    * **`CANNOT_VERIFY`**  - the payee verification could not be completed.

### 2025-09-11

* Added Virtual IBANs section

### 2025-06-05

#### Deprecated

* `aml_status` field in the [**Transactions**](/api-reference/transactions.md) resource has been deprecated.
  * ⚠️ This field will be **fully removed** from all API responses on **2025-08-04**.
  * Please update any integrations relying on this field before the removal date.

**Enhancement to `status` field in the** [**Transactions**](/api-reference/transactions.md) **resource.**

* ⚠️ **New statuses will be introduced on 2025-08-04,** released to production together with the removal of `aml_status`.
* The `status` field now includes five possible values:
  * `created` (changable): Transaction is created; processing not yet started.
  * `pending` (changable): Transaction is currently being processed.
  * `processed` (final): Transaction has been successfully processed.
  * `canceled` (final): Transaction has been canceled.
  * `rejected` (final): Transaction has been rejected.
* **Note:** Make sure your integration is prepared to handle these new `status` values.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developers.gurupay.eu/changelog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.